Free LookML-Developer – Looker LookML Developer Exam Practice Test Question

Select all that apply, then click Submit answer.

• ○

  Apply the hidden parameter with a value of yes to Explores that only exist to power specific Looks, dashboards, or suggestion menus.

• ○

  Modify the business users’ roles so they do nothave this model in their model set.

• ○

  Combine the Explores into just a few Explores that each join to many views.

• ○

  Apply the group_label parameter to organize the Explores under different headings.

• ○

  Apply the fields parameter so that each Explore hasfewer fields in it.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Number of databases used by dashboard elements

• ○

  Number of queries used by the dashboard

• ○

  Ratio of visualizations to text tiles

• ○

  Format used to deliver these reports

• ○

  Amount of data rendered for each query
  
  
  

Select all that apply, then click Submit answer.

• ○

  Add a description parameter to each field with context so that users can search key terms.

• ○

  Create a separate project for each business unit containing only the fields that the unit needs.

• ○

  Add a group_label parameter to relevant fields to organize them into logical categories.

• ○

  Use the hidden parameter to remove irrelevant fields from the Explore.

• ○

  Use a derived table to show only the relevant fields.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Option A

• ○

  Option B

• ○

  Option C

• ○

  Option D

• ○

  Option E
  
  
  

Select all that apply, then click Submit answer.

• ○

  View name was changed from users to customers.

• ○

  Field type was changed from number to string.

• ○

  Model name was changed from e_commerce to reporting.

• ○

  Explore label was changed from users to customers.

• ○

  Field name was changed from id to user_id.
  
  

Select an option, then click Submit answer.

• ○

  Option A

• ○

  Option B

• ○

  Option C

• ○

  Option D

Select an option, then click Submit answer.

• ○

  There is a missing join.

• ○

  The field is set to “hidden”.

• ○

  The join relationship is incorrect.

• ○

  The field uses incorrect SQL syntax.
  
  
  

Select an option, then click Submit answer.

• ○

  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.

• ○

  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.

• ○

  Create two view files for the users table. One view file will have all possible fields for the users Explore, and theother will have only the fields required for the products Explore.

• ○

  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.
  
  
  

Select an option, then click Submit answer.

• ○

  Option A

• ○

  Option B

• ○

  Option C

• ○

  Option D
  
  
  

Select an option, then click Submit answer.

• ○

  Use a conditional WHERE clause for Development Mode.

• ○

  Build a user attribute filter into the Explore.

• ○

  Use index distribution_key or sort_key for this derived table.

• ○

  Persist the derived table.