Online Access Free LookML-Developer Exam Questions

A LookML developer is creating a new view with 20 dimensions in Development Mode using the Create View from Table functionality. Now users want the developer to add only four dimensions from this new view to an existing Explore.
What can the developer add to the Explore to limit the number of fields from the view that are accessible to the user in the Explore?

• A.Join condition
• B.Hidden parameter
• C.Set definition
• D.Fields parameter

A developer needs to add an Explore built off of the orders view, which surfaces only completed orders. An orders Explore exists that contains all order information. Fields from the orders view are also referenced in other existing views such as ${orders.fieldname}.
How should developer define a new Explore for completed orders and keep all field references working correctly?
A)

B)

C)

D)

• A.Option A
• B.Option D
• C.Option C
• D.Option B

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

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

A developer commits changes after adding LookML for a new measure. Upon pulling from production, the developer notices the following lines in the LookML:

• A.Remove everything between "<<<<<< HEAD" and "======", and ">>>>>> branch 'master'"
• B.Remove everything between "<<<<<< HEAD" and ">>>>>> branch 'master'"
• C.Remove "<<<<<< HEAD", "======", and ">>>>>> branch 'master'"
• D.Remove "<<<<<< HEAD", "======", and everything following "======"

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?

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