New Year Special Limited Time 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: 70special

Google LookML-Developer Looker LookML Developer Exam Exam Practice Test

Looker LookML Developer Exam Questions and Answers

Testing Engine

  • Product Type: Testing Engine
$37.5  $124.99

PDF Study Guide

  • Product Type: PDF Study Guide
$33  $109.99
Question 1

Business users reportthat an ephemeral derived table tile on the dashboard is slow.

Information about the dashboard includes:

The dashboard filter is linked to the user attributes.

This tile usually takes approximately 5 minutes to complete running.

Which solution should be used to improve the dashboard load time?

Options:

A.

Use a conditional WHERE clause for Development Mode.

B.

Build a user attribute filter into the Explore.

C.

Use index distribution_key or sort_key for this derived table.

D.

Persist the derived table.

Question 2

A LookML developer is creating a new view with 20 dimensions in Development Mode using the Create View fromTable 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?

Options:

A.

Set definition

B.

Join condition

C.

Fields parameter

D.

Hidden parameter

Question 3

The daily_forecast Explore used by the sales team needs to be cached for 24 hours. All other Explores usedby the sales team need to be cached for one hour.

What is a scalable way to configure this caching logic?

Options:

A.

Define two datagroups for the model. Apply persist_with at the model level with the datagroup for 1-hour caching, and apply persist_with to daily_forecast with the datagroup for 24-hour caching.

B.

Define max_cache_age on daily_forecast Explores of 24 hours. Define max_cache_age on all other Explores for one hour.

C.

Define two datagroups for the model. Create a persistent derived table (PDT) forthe daily_forecast Explore, and apply datagroup_trigger to it using the datagroup for 24-hour caching.

D.

Define for the model one datagroup that caches for 1 hour. Create a persistent derived table (PDT) for the daily_forecast Explore, and apply sql_trigger_value to it selecting the current date.

Question 4

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?

Options:

A.

Create one datagroup tied to all three PDTs that runs when the total row count across all three tables changes.

B.

Create one datagroup tied to all three PDTs that parameterizes the view name for each PDT in the SQL trigger condition.

C.

Create three separate datagroups tied to three PDTs that run when each corresponding table’s row count changes.

D.

Create threeseparate datagroups tied to three PDTs that run when a new row is added to the ETL log table.

Question 5

Only users with department attributes of Finance and Executive should be able to access the revenue view. Only users with the value ofExecutive for the department user attribute should be able to view the total_revenue field.

Given the code snippet below:

How should the required access grants be structured to set up this system of access?

Options:

A.

required_access_grants: [grant_b] in the revenue view, required_access_grants: [grant_a] in the total_revenue field

B.

required_access_grants: [grant_a] in the revenue view, required_access_grants: [grant_a, grant_b] in the total_revenue field

C.

required_access_grants: [grant_b] in the financial_data Explore, required_access_grants: [grant_a] in the total_revenue field

D.

required_access_grants: [grant_a, grant_b] in the revenue view, required_access_grants: [grant_a] in the total_revenue field

Question 6

A LookML developer creates a new model and a test dashboard from the model. The developer shares the link to the new dashboard with users, but the users report that all they see is the “Model Not Found” error.

What is a possible cause of this issue?

Options:

A.

The developer has not pushed the new model to Production Mode.

B.

The developer has not added users to the new model set.

C.

The users do not have permission to access this dashboard.

D.

The new model is missing an Explore definition.

Question 7

After validating LookML code, a developer receives the following error message:

“Unknown or Inaccessible Field users.name”

What is causing this error?

Options:

A.

There is a missing join.

B.

The field is set to “hidden”.

C.

The join relationship is incorrect.

D.

The field uses incorrect SQL syntax.