Free Google LookML-Developer Exam Dumps Questions & Answers

A developer needs to model out LookML to convert existing reports into Looker. The existing reports are:
Report 1: A report with order and order_items data, which finds the order with the largest total value of the order_item prices.
Report 2: A report with order and order_items data, which finds the order with the largest total number of products ordered.
Report 3: A report with data on every product, whether or not it has been ordered.
Each database table used is updated in real time as orders are made.
How should the developer construct an Explore using the order_items view as the base view?

• A.  Create one persistent derived table to calculate Report 1, create one persistent derived table to calculate Report 2, and join in the products view with a full_outer join.
• B.  Create one ephemeral derived table to calculate Reports 1 and 2, and join in the products view with a full_outer join.
• C.  Create one persistent derived table to calculate Reports 1 and 2, and join in the products view with a full_outer join.
• D.  Create one ephemeral derived table to calculate Report 1, create one ephemeral derived table to calculate Report 2, and join in the products view with a left_outer join.

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.  link
• B.  tags
• C.  url_encode
• D.  drill_fields

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

• A.  Field type was changed from number to string.
• B.  Explore label was changed from users to customers.
• C.  Model name was changed from e_commerce to reporting.
• D.  View name was changed from users to customers.
• E.  Field name was changed from id to user_id.

A developer has User Specific Time Zones enabled for a Looker instance, but wants to ensure that queries run in Looker are as performant as they can be. The developer wants to add a datatype: date parameter to all dimension_group definitions without time data in a table-based view, so that time conversions don't occur for these fields.
How can the developer determine to which fields this parameter should be applied through SQL Runner?

• A.  Open the Explore query in SQL Runner and validate whether removing the conversion from date fields changes the results.
• B.  Use the Describe feature in SQL Runner to determine which fields include time data.
• C.  Open the Explore query in SQL Runner to determine which fields are converted.
• D.  Use the CAST function in SQL Runner to ensure that all underlying fields are dates and conversions are not applied.

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 measure using a derived table, and then join that derived table back into the Explore.
• B.  Create a measure filtered on Category, and make the filter value controlled by a parameter.
• C.  Calculate the overall count using table calculations in the Explore.
• D.  Create a measure with type: sum_over_dimension, and make the dimension value controlled by a parameter.