Looker LookML Developer (LookML-Developer) Free Practice Test

Question 1

A developer has a persistent derived table view called user_facts that contains aggregated data for each user. The developer needs to query the data from this table in another derived table view called user_region_facts.
Which strategy should the developer use to write the query for user_region_facts that will leverage the existing derived table?

A. Copy the name of the database table in the scratch schema for the user_facts derived table.

B. Writhe the query form user_facts into a common table expression (WITH user_facts AS...).

C. Write a subquery in the FROM clause and alias with ${user_facts}.

D. Use ${user_facts.SQL_TABLE_NAME} to reference the user_facts derived table.

Correct Answer: B

Question 2

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?

A. Calculate the overall count using table calculations in the Explore.

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

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

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

Correct Answer: C

Question 3

A developer needs to add an Explore built off of the orders view, which surfaces only completed orders. An orders Explore exists that contains all order information. Fields from the orders view are also referenced in other existing views such as ${orders.fieldname}.
How should developer define a new Explore for completed orders and keep all field references working correctly?
A)

B)

C)

D)

A. Option D

B. Option C

C. Option A

D. Option B

Correct Answer: B

Question 4

Only users with department attributes of Finance and Executive should be able to access the revenue view. Only users with the value of Executive for the department user attribute should be able to view the total_revenue field.
Given the code snippet below:

How should the required access grants be structured to set up this system of access?

A. required_access_grants: [grant_b] in the financial_data Explore, required_access_grants: [grant_a] in the total_revenue field

B. required_access_grants: [grant_a] in the revenue view, required_access_grants: [grant_a, grant_b] in the total_revenue field

C. required_access_grants: [grant_b] in the revenue view, required_access_grants: [grant_a] in the total_revenue field

D. required_access_grants: [grant_a, grant_b] in the revenue view, required_access_grants: [grant_a] in the total_revenue field

Correct Answer: B

Question 5

The developer has moved the orders Explore (shown below) from model_a to model_b, where both models are in the same project, and all users have access to both models.
Connection: "demo"
include: ".view"
explore: orders {}
What will happen after making this change?

A. Dashboard tiles and Looks will redirect to the new database connection.

B. Dashboard tiles and Looks will be automatically pointed to the orders Explore in model_b.

C. Dashboard tiles and Looks that rely on this Explore will be deleted.

D. Dashboard tiles and Looks that rely on this Explore will return an error.

Correct Answer: C

Question 6

A LookML Developer is working with denormalized tables and needs to create a measure adding up the Order Shipping column in the table below: