LOOKML-DEVELOPER Online Practice Questions and Answers

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. Option A

B. Option B

C. Option C

D. Option D

A LookML developer has written the following persistent derived table. It references orders_rollup, another persistent derived table that also rebuilds with the same SQL trigger value.

Which change is needed to guarantee that user_facts will always rebuild with the latest data from orders_rollup?

A. Change the sql_trigger_value parameter of user_facts to select the current date plus one hour, so it triggers an hour after orders_rollup.

B. Change the orders_rollup view reference to ${orders_rollup.DERVIED_TABLE_NAME}

C. Change the sql_trigger_value parameter for both persistent derived tables to a datagroup_trigger parameter, and set them to use the same datagroup.

D. Change the orders_rollup view reference to the literal table name from the database's scratch schema.

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?

A. Option A

B. Option B

C. Option C

D. Option D

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 be automatically pointed to the orders Explore in model_b.

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

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.

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 is building an e-commerce Explore with the following datasets: orders and users. The business user needs to be able to answer questions about sellers and buyers within the same Explore. Each order in the orders table reports a buyer and seller ID. The users table has the detailed information about the individual buyer and seller.

How should the Explore be defined to meet this requirement?

A. Option A

B. Option B

C. Option C

D. Option D

A user reports the following SQL error when selecting the discounted sale price field:

ERROR: column “order_items.sale_price”; must appear in the GROUP BY clause or be used in an

aggregate function.

The developer checks the field definition and finds it to be:

measure: discounted_sale_price {

type: number

sql: ${sale_price} * 0.8 ;;

}

The developer also finds the LookML definition of the sale_price field to be:

dimension: sale_price {

type: number

sql: ${TABLE}.sale_price ;;

}

What is the likely cause of the SQL error?

A. The discounted_sale_price field should have a group_by: yes parameter.

B. The sale_price field should be defined as a measure of type: number, not as a dimension.

C. The underlying database table does not have a field called sale_price.

D. The discounted_sale_price field should be defined as a dimension of type: number, not as a measure.

A LookML developer is creating a new view with 20 dimensions in Development Mode using the Create View from Table functionality. Now users want the developer to add only four dimensions from this new view to an existing Explore.

What can the developer add to the Explore to limit the number of fields from the view that are accessible to the user in the Explore?

A. Set definition

B. Join condition

C. Fields parameter

D. Hidden parameter

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.

Users must be able to click on the Country field in their Explore and be redirected to another Explore that shows all countries compared.

Which parameter should be added to the country dimension to create a connection to this other associated Explore?

A. url_encode

B. drill_fields

C. tags

D. link

A developer commits changes after adding LookML for a new measure. Upon pulling from production, the developer notices the following lines in the LookML:

A. Remove “andlt;<<<<< HEAD”, “======”, and “andgt;>>>>> branch ‘master’”

B. Remove “andlt;<<<<< HEAD”, “======”, and everything following “======”

C. Remove everything between “andlt;<<<<< HEAD” and “======”, and “andgt;>>>>> branch ‘master’”

D. Remove everything between “andlt;<<<<< HEAD” and “andgt;>>>>> branch ‘master’”

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

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.

A user reports that, when a date dimension is filtered to “before now” results are returned that consistently include tomorrow. Dimension fill has been ruled out as a cause of the issue.

Which LookML parameter should be used to resolve this issue?

A. Week_start_day

B. Convert_tz

C. Datatype

D. Fiscal_month_offset

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?

A. Use 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.

B. Create 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.

C. Create 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.

D. Use 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.