Free Looker LookML Developer Exam LookML-Developer Exam Practice Test

Business users report that they are unable to build useful queries because the list of fields in the Explore is too long to find what they need.Which three LookML options should a developer use to curate the business user's experience? (Choose three.)

• 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.
  

Two developers are working on adding a new view to a project. Once both developers have finished their work in the view, the changes will be pushed to production.Where should the developers write the LookML for this view?

• In the master branch, with both users writing to the branch
  
• In one user's personal branch, with both users writing to the branch
  
• In a new shared branch created from the master branch
  
• In each of their personal branches, with each user writing code separately
  

A developer needs to implement three persistent derived tables (PDTs) as described below.The PDTs need to be refreshed after the daily ETL pipeline adds incremental loads to the underlying tables.Each PDT is built off of one underlying table in the database (one PDT per table).The underlying tables for each PDT are updated one after the other, and a new row is added to an ETL log table each time a table is updated.Due to the unpredictable nature of the ETL pipeline, each PDT does not refresh at the same time from day to day.Each PDT takes over an hour to build, and to save on compute costs each PDT should only be refreshed once per day.How can the developer set up the PDTs according to these requirements?

• Create one datagroup tied to all three PDTs that runs when the total row count across all three tables changes.
  
• Create one datagroup tied to all three PDTs that parameterizes the view name for each PDT in the SQL trigger condition.
  
• Create three separate datagroups tied to three PDTs that run when each corresponding table's row count changes.
  
• Create three separate datagroups tied to three PDTs that run when a new row is added to the ETL log table.
  

A user is seeing an error in the Explore that indicates the primary key defined for a one-million-row table is not unique.How can the developer use SQL Runner to troubleshoot quickly?

• Create a query that selects all the fields from the table, and sort by primary key.
  
• Create a query that selects the primary key from the base view, and look for duplicates.
  
• Create a query that counts how many occurrences of the primary key value are in the base view, and sort by count.
  
• Create a query that concatenates two columns to create a compound primary key.
  

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?

• Use ${user_facts.SQL_TABLE_NAME} to reference the user_facts derived table.
  
• Copy the name of the database table in the scratch schema for the user_facts derived table.
  
• Writhe the query form user_facts into a common table expression (WITH user_facts AS...).
  
• Write a subquery in the FROM clause and alias with ${user_facts}.
  

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 change has been deployed to a shared branch.
  
• A change has been committed in another developer's personal branch
  
• A change has been committed in another shared branch.
  
• A change has been deployed to production.
  

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 bare Git repository
  
• Multiple account HTTPS
  
• Single account HTTPS
  
• SSH
  

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?

• Create an Explore with users as the base table.
  
• Create a persistent derived table from the user's query.
  
• Create an ephemeral derived table from the user's query.
  
• Add persist_for: ''24 hours'' to the orders Explore.
  

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

• 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.
  

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?

• Dashboard tiles and Looks will be automatically pointed to the orders Explore in model_b.
  
• Dashboard tiles and Looks will redirect to the new database connection.
  
• Dashboard tiles and Looks that rely on this Explore will be deleted.
  
• Dashboard tiles and Looks that rely on this Explore will return an error.