Free Looker LookML Developer Exam LookML-Developer Exam Practice Test

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 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 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?

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

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?

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

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.
  

Users have built a popular dashboard and want to have change management built in for any edits made to the dashboard. The developer sets up version control for the model on which the dashboard is based.What should the developer build to meet the business requirement?

• A native derived table based on the dashboard.
  
• A dashboard LookML file included in the project.
  
• A link to the dashboard included in the project.
  
• An Explore LookML file based on the dashboard.
  

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 field in the order_items view references a field in the inventory_items view.
  
• A field in the inventory_items view references a field in the order_items view.
  
• There is an Explore named inventory_items which references the order_items view.
  
• There is another Explore named order_items which references the inventory_items view.
  

A user needs to create a report that shows a count of all orders and of orders over $100.Which solution should the developer implement to meet these requirements?

• An always_filter parameter
  
• A front-end filter in the Explore
  
• A sql_always_where parameter
  
• A filtered measure
  

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.
  

Users report that every time they change the filter on their Explore, the filters take a very long time to populate.How can the developer improve the filtering experience with this Explore?

• Limit the filter suggestions using the suggestions parameter.
  
• Add an always_filter parameter to restrict the filter suggestions.
  
• Use an access_filter parameter to automatically apply filters.
  
• Add persistence to the base view of the Explore.