Summer Sale Limited Time 65% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: ecus65

Google LookML-Developer - Looker LookML Developer Exam

Google LookML-Developer Premium Access     Download Demo    
Page: 1 / 2
Total 50 questions

A developer creates a derived table and wants to add persistence to it. Because the table is not used on a frequent basis, the developer wants thetable to be cached for 12 hours, but only when a user has queried it.

Which persistence parameter should be added to the derived table’s definition in order to satisfy this use case?

A.

persist_with: “12 hours”

B.

datagroup: 12_hours {

max_cache_age: “12 hours”

}

C.

persist_for: “12 hours”

D.

sql_trigger_value: SELECT FLOOR{UNIX_TIMESTAMP{} / {6*60*60}} ;;

Users must be able to click on the Country field in their Explore and be redirected to another Explore that shows all countries compared.

Which parameter should be added to the country dimension to create a connection to this other associated Explore?

A.

url_encode

B.

drill_fields

C.

tags

D.

link

A developer has the dimensions enrollment_month and graduation_month already defined in the view. Both were created as part of dimension_groups of type: time. The developer need touse these two dimensions in the sql_start and sql_end parameters of a dimension group of type: duration.

Which LookML should be used to calculate the number of month and years between enrollment month and graduation month?

A)

B)

C)

D)

A.

Option A

B.

Option B

C.

Option C

D.

Option D

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?

A.

Use ${user_facts.SQL_TABLE_NAME} to reference the user_facts derived table.

B.

Copy the name of the database table inthe scratch schema for the user_facts derived table.

C.

Writhe the query form user_facts into a common table expression (WITH user_facts AS...).

D.

Write a subquery in the FROM clause and alias with ${user_facts}.

A user reports an errormessage on an Explore: “Non-unique value/primary key (or sql_distinct_key), value overflow or collision when computing sum”.

What should the LookML developer check for in the joined views of the Explore?

A.

The sum measure used is defined correctly.

B.

A unique primary key is defined in each view.

C.

Symmetric_aggregates: no is not present in the Explore definition.

D.

No concatenated primary keys are used.

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 will redirect to the new database connection.

C.

Dashboard tiles and Looks that rely on this Explore will be deleted.

D.

Dashboard tiles and Looks that rely on this Explore will return an error.

A developer would like to add a new dimension of type: yesno for the enabled column in their users table. The column is of type: string in the database and returns yes and no values.

How should the developer define the yesno dimension?

A)

B)

C)

D)

A.

Option A

B.

Option B

C.

Option C

D.

Option D

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

What should the developer build to meet the business requirement?

A.

A native derived table based on the dashboard.

B.

A dashboard LookML file included in the project.

C.

A link to the dashboard included in the project.

D.

An Explore LookML file based on the dashboard.

A user reports the following SQL error when selecting the discounted sale price field:

ERROR: column “order_items.sale_price”; must appear in the GROUP BY clause or be used in an aggregate function.

The developer checks the field definition and finds it to be:

measure: discounted_sale_price {

type: number

sql: ${sale_price} * 0.8 ;;

}

The developer also finds the LookML definition of the sale_price field to be:

dimension: sale_price {

type: number

sql: ${TABLE}.sale_price ;;

}

What isthe likely cause of the SQL error?

A.

The discounted_sale_price field should have a group_by: yes parameter.

B.

The sale_price field should be defined as a measure of type: number, not as a dimension.

C.

The underlying database table does not have a fieldcalled sale_price.

D.

The discounted_sale_price field should be defined as a dimension of type: number, not as a measure.

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.

A changehas been deployed to a shared branch.

B.

A change has been committed in another developer’s personal branch

C.

A change has been committed in another shared branch.

D.

A change has been deployed to production.