Google LookML-Developer Exam Practice Test Instant Access

Question 1

A developer wants to create a measure that shows the item count broken out by category. When a second, more granular dimension is added to the same query, the count broken out by category should still represent the original aggregation and be duplicated on each line. The business wants this ''count'' in ''category'' available in the Explore section without any additional work done by the end user. For example:

The Count column represents the count for each combination of Category and Item.

The Count in Category column represents the count for each Category only.

How can the developer address this need with a LookML object?

ACreate a measure filtered on Category, and make the filter value controlled by a parameter.

BCalculate the measure using a derived table, and then join that derived table back into the Explore.

CCreate a measure with type: sum_over_dimension, and make the dimension value controlled by a parameter.

DCalculate the overall count using table calculations in the Explore.

Answer : B

Question 2

A developer creates a derived table and wants to add persistence to it. Because the table is not used on a frequent basis, the developer wants the table to be cached for 12 hours, but only when a user has queried it.

Which persistence parameter should be added to the derived table's definition in order to satisfy this use case?

Apersist_with: ''12 hours''

Bdatagroup: 12_hours {
max_cache_age: ''12 hours''
}

Cpersist_for: ''12 hours''

Dsql_trigger_value: SELECT FLOOR{UNIX_TIMESTAMP{} / {6*60*60}} ;;

Answer : A

Question 3

The code below shows a view order_items with its measures total_revenue and user_count

Which code correctly represents a new measure that calculates average revenue per user?

AOption A

BOption B

COption C

DOption D

Answer : C

Question 4

After running the LookML Validator, a developer sees the following error message in the Looker development environment:

''Measures with Looker aggregations (sum, average, min, max, list types) may not reference other measures''.

What could be causing this error?

AA measure of type: count has a sql parameter defined.

BA measure of type: sum adds up other measures in the sql parameter.

CA measure of type: sum has a SUM function written in the sql parameter.

DA measure of type: number has a SUM function written in the sql parameter.

Answer : A

Question 5

The daily_forecast Explore used by the sales team needs to be cached for 24 hours. All other Explores used by the sales team need to be cached for one hour.

What is a scalable way to configure this caching logic?

ADefine two datagroups for the model. Apply persist_with at the model level with the datagroup for 1-hour caching, and apply persist_with to daily_forecast with the datagroup for 24-hour caching.

BDefine max_cache_age on daily_forecast Explores of 24 hours. Define max_cache_age on all other Explores for one hour.

CDefine two datagroups for the model. Create a persistent derived table (PDT) for the daily_forecast Explore, and apply datagroup_trigger to it using the datagroup for 24-hour caching.

DDefine for the model one datagroup that caches for 1 hour. Create a persistent derived table (PDT) for the daily_forecast Explore, and apply sql_trigger_value to it selecting the current date.

Answer : A

Question 6

A developer is defining the users table within a view file in Looker. The users table will be available as an individual Explore and it will also be joined into other Explores, such as the products Explore. The developer needs to limit the fields visible in the products Explore without affecting the visibility of the fields in the users Explore.

How should the developer meet this requirement?

AUse the fields parameter at the join level for the products Explore to specify which fields should be included and leave the users Explore as is.

BCreate duplicate dimensions and measures, one for the users Explore and one for the products Explore, and use the hidden parameter to modify the visibility of the fields.

CCreate two view files for the users table. One view file will have all possible fields for the users Explore, and the other will have only the fields required for the products Explore.

DUse the hidden parameter in the users view file for the fields that should not come over to the products Explore and leave the users Explore as is.

Answer : A

Question 7

Users report that every time they change the filter on their Explore, the filters take a very long time to populate.

How can the developer improve the filtering experience with this Explore?

ALimit the filter suggestions using the suggestions parameter.

BAdd an always_filter parameter to restrict the filter suggestions.

CUse an access_filter parameter to automatically apply filters.

DAdd persistence to the base view of the Explore.

Answer : A

Google Looker LookML Developer LookML-Developer Exam Practice Test