google google-lookml-developer practice test

Google LookML Developer


Question 1

The developer is creating an Explore that includes the product users, and orders views that will meet the following
guidelines.
Joins between the orders and users views should not incur high performance costs.
Users of this Explore will primarily be looking at data from the orders view.
Users of this Explore should only be able to see orders from the retailer Fashion.ly.
The only field the users need from the products view is product.name.
Which LookML should the developer use?


  • A. Option A
  • B. Option B
  • C. Option C
  • D. Option D
Answer:

D

Discussions

Question 2

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.
Answer:

B

Discussions

Question 3

A developer is connecting a LookML project to a remote Git repository. The developer wants to track which users are
committing code changes, creating pull requests, or deploying to production when the different Git commands are initiated
from within Looker.
Which type of Git connection should be utilized to meet this business requirement?

  • A. A bare Git repository
  • B. Multiple account HTTPS
  • C. Single account HTTPS
  • D. SSH
Answer:

D

Explanation:
Reference: https://docs.looker.com/data-modeling/getting-started/version-control-and-deploying-changes

Discussions

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 revenue view, 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 financial_data Explore, 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
Answer:

B

Discussions

Question 5

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 tables definition in order to satisfy this use case?

  • A. persist_with: “12 hours”
  • B. datagroup: 12_hours { max_cache_age: “12 hours”
  • C. persist_for: “12 hours”
  • D. sql_trigger_value: SELECT FLOOR{UNIX_TIMESTAMP{} / {6*60*60}} ;;
Answer:

A

Explanation:
Reference: https://docs.looker.com/data-modeling/learning-lookml/caching

Discussions

Question 6

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
Answer:

B

Discussions

Question 7

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.
Answer:

A

Explanation:
Reference: https://help.looker.com/hc/en-us/articles/360038371614--Error-Measures-with-Looker-Aggregations-Sum-
Average-Min-Max-List-Types-May-Not-Reference-Other-Measures

Discussions

Question 8

Users report that the main dashboard has been slow to show results.
Which two options should the developer evaluate to improve dashboard performance? (hoose two.)

  • A. Number of databases used by dashboard elements
  • B. Number of queries used by the dashboard
  • C. Ratio of visualizations to text tiles
  • D. Format used to deliver these reports
  • E. Amount of data rendered for each query
Answer:

B C

Explanation:
Reference: https://help.looker.com/hc/en-us/articles/360038233334-Considerations-When-Building-Performant-Looker-
Dashboards

Discussions

Question 9

A LookML developer has created a model with many Explores in it. Business users are having a difficult time locating the
Explore they want in the long list displayed.
Which two actions can the LookML developer take to improve the user interface? (Choose two.)

  • A. Apply the hidden parameter with a value of yes to Explores that only exist to power specific Looks, dashboards, or suggestion menus.
  • B. Modify the business users’ roles so they do not have this model in their model set.
  • C. Combine the Explores into just a few Explores that each join to many views.
  • D. Apply the group_label parameter to organize the Explores under different headings.
  • E. Apply the fields parameter so that each Explore has fewer fields in it.
Answer:

B C

Discussions

Question 10

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.
Answer:

A

Discussions
To page 2