A user reports that a query run against the orders Explore takes a long time to run. The query includes only fields from the users view. Data for both views is updated in real time. The developer runs the following query in SQL Runner and quickly receives results:

SELECT * FROM users.

What should the developer do to improve the performance of the query in the Explore?

A. Create an Explore with users as the base table.

B. Create a persistent derived table from the user's query.

C. Create an ephemeral derived table from the user's query.

D. Add persist_for: “24 hours” to the orders Explore.

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?

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

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

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

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

Business users report that an ephemeral derived table tile on the dashboard is slow.

Information about the dashboard includes:

The dashboard filter is linked to the user attributes.

This tile usually takes approximately 5 minutes to complete running.

Which solution should be used to improve the dashboard load time?

A. Use a conditional WHERE clause for Development Mode.

B. Build a user attribute filter into the Explore.

C. Use index distribution_key or sort_key for this derived table.

D. Persist the derived table.

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. Use ${user_facts.SQL_TABLE_NAME} to reference the user_facts derived table.

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

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

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

A developer wants to create a new Explore based on the order_items view. The developer creates an

Explore in the ecommerce model file with the following definition:

explore: order_items {}

After saving and validations, the developer receives this LookML validator error:

Inaccessible view “inventory_items”, “inventory_items” is not accessible in explore” “order_items”. Check

for typos and missing joins in explore “order_items”.

What caused this error to appear?

A. A field in the order_items view references a field in the inventory_items view.

B. A field in the inventory_items view references a field in the order_items view.

C. There is an Explore named inventory_items which references the order_items view.

D. There is another Explore named order_items which references the inventory_items view.

A user reports an error message on an Explore: “Non-unique value/primary key (or sql_distinct_key), value overflow or collision when computing sum”.

What should the LookML developer check for in the joined views of the Explore?

A. The sum measure used is defined correctly.

B. A unique primary key is defined in each view.

C. Symmetric_aggregates: no is not present in the Explore definition.

D. No concatenated primary keys are used.

After running the Content Validator, a developer can see the error “Unknown field”. Which two changes could cause this issue? (Choose two.)

A. View name was changed from users to customers.

B. Field type was changed from number to string.

C. Model name was changed from e_commerce to reporting.

D. Explore label was changed from users to customers.

E. Field name was changed from id to user_id.

After validating LookML code, a developer receives the following error message:

“Unknown or Inaccessible Field users.name”

What is causing this error?

A. There is a missing join.

B. The field is set to “hidden”.

C. The join relationship is incorrect.

D. The field uses incorrect SQL syntax.

A developer needs to build a new dimension that offers an age-based cohort representation of users. Which LookML code should the developer use to meet the requirement?

A. Option A

B. Option B

C. Option C

D. Option D

A LookML developer finishes some LookML work and commits changes in their personal development branch. The developer is asked to Pull and Merge Other Changes.

What does this indicate?

A. A change has been deployed to a shared branch.

B. A change has been committed in another developer's personal branch.

C. A change has been committed in another shared branch.

D. A change has been deployed to production.