LookML-Developer 무료 덤프문제 온라인 액세스

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?

• A.A sql_always_where parameter
• B.A front-end filter in the Explore
• C.A filtered measure
• D.An always_filter parameter

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 "<<<<<< HEAD", "======", and ">>>>>> branch 'master'"
• B.Remove everything between "<<<<<< HEAD" and "======", and ">>>>>> branch 'master'"
• C.Remove "<<<<<< HEAD", "======", and everything following "======"
• D.Remove everything between "<<<<<< HEAD" and ">>>>>> branch 'master'"

A developer has created a persistent derived table that tracks new or updated orders and they want to cache the results. The cache should be refreshed whenever some new order is available on the underlying datasource table my tablename or at least every 24 hours.
Which datagroup definition will refresh the cache as expected?
A)

B)

C)

D)

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

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?

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

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.