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

Activedumpsnet Logo
  1. Home
  2. Google
  3. Looker certifications
  4. LookML-Developer - Looker LookML Developer Exam

Google LookML-Developer Looker LookML Developer Exam Exam Practice Test

Page: 1 / 5
Total 50 questions
Get LookML-Developer Full Access Download LookML-Developer PDF

Looker LookML Developer Exam Questions and Answers

Question 1

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:

Question # 1

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 2

Adeveloper is connecting a LookML project to a remote Git repository. The developer wants to track which users are committing code changes, creating pull requests, or deploying to production when the different Git commands are initiated from within Looker.

Which type of Git connection should be utilized to meet this business requirement?

Options:

A.

A bare Git repository

B.

Multiple account HTTPS

C.

Single account HTTPS

D.

SSH

Question 3

A developer is defining the users table within a view file in Looker. Theusers 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?

Options:

A.

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.

B.

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.

C.

Create two view files for the users table. One view file will have all possible fields for the users Explore, and theother will have only the fields required for the products Explore.

D.

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.

Question 4

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.

Question 5

A developer has User Specific Time Zones enabled fora 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?

Options:

A.

Open the Explore query in SQL Runner and validate whether removing the conversion from date fields changes the results.

B.

Open the Explore query in SQL Runner to determine which fields are converted.

C.

Use the CAST function in SQL Runner to ensure that all underlying fields are dates and conversions are not applied.

D.

Use the Describe feature in SQL Runner to determine which fields include time data.

Question 6

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?

Options:

A.

In the master branch, with both users writing to the branch

B.

In one user’s personal branch, with both users writing to the branch

C.

In a new shared branch created from the master branch

D.

In each of their personal branches, with each user writing code separately

Question 7

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

Question # 7

Options:

A.

Remove “<<<<<< HEAD”, “======”, and “>>>>>> branch ‘master’”

B.

Remove “<<<<<< HEAD”, “======”, and everything following “======”

C.

Remove everything between “<<<<<< HEAD” and “======”, and “>>>>>> branch ‘master’”

D.

Remove everything between “<<<<<< HEAD” and “>>>>>> branch ‘master’”

Load More LookML-Developer Questions 
Page: 1 / 5
Total 50 questions
Get LookML-Developer Full Access Download LookML-Developer PDF