Pass Your LookML-Developer Dumps as PDF Updated on 2022 With 51 Questions [Q17-Q38]

4/5 - (1 vote)

Pass Your LookML-Developer Dumps as PDF Updated on 2022 With 51 Questions

Google LookML-Developer Real Exam Questions and Answers FREE

Google LookML-Developer Exam Syllabus Topics:

Topic	Details
Topic 1	Reconcile merge conflicts with other developer branches Implement version control based on given requirements
Topic 2	Optimize SQLs for cost or efficiency based on business requirements Determine why specific queries return results by looking at the generated SQL in SQL Runner
Topic 3	Decide which Looker features to use to implement data security Apply procedural concepts to implement data security requirements
Topic 4	Apply procedural concepts to evaluate the performance of queries and reports Apply procedural concepts to optimize queries and reports for performance
Topic 5	Determine appropriate caching settings based on data warehouse’s update frequency Apply procedural concepts to implement persistent derived tables and caching policies based on requirements

Q17. 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 is based.
What should the developer build to meet the business requirement?

A native derived table based on the dashboard.

A dashboard LookML file included in the project.

A link to the dashboard included in the project.

An Explore LookML file based on the dashboard.

Q18. A retail company wants to limit who can see the financial information in their reports to executives and store managers. The LookML Developer creates a user attribute called leadership with the value “000” for executives and “999” for store managers. The developer creates three access grant objects and one dimension:

How should the developer ensure that only authorized users see the data in the Total Revenue dimension?

required_access_grants: [can_view_financial_data]

required_access_grants: [leadership]

required_access_grants: [“000″,”999”]

required_access_grants: [total_revenue]

Q19. Only users with department attributes of Finance and Executive should be able to access the revenue view. Only users with the value of Executive 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?

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

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

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

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

Q20. 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.)

Number of databases used by dashboard elements

Number of queries used by the dashboard

Ratio of visualizations to text tiles

Format used to deliver these reports

Amount of data rendered for each query

Q21. A developer wants to calculate the ratio of total sales from the orders view and total users from the users view.
Which two methods can be used to create a measure that meets these requirements? (Choose two.)

B)

C)

D)

E)

Option A

Option B

Option C

Option D

Option E

Q22. Business users report that they are unable to build useful queries because the list of fields in the Explore is too long to find what they need.
Which three LookML options should a developer use to curate the business user’s experience? (Choose three.)

Add a description parameter to each field with context so that users can search key terms.

Create a separate project for each business unit containing only the fields that the unit needs.

Add a group_label parameter to relevant fields to organize them into logical categories.

Use the hidden parameter to remove irrelevant fields from the Explore.

Use a derived table to show only the relevant fields.

Q23. 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?

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

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

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

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

Q24. Users viewing an Explore should be able to view rows of data only where the value of the product.brand column matches the value of the user’s company user attribute.
Which access filter should the developer use to meet this requirement?
A)

B)

C)

D)

Option A

Option B

Option C

Option D

Q25. 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?

Create an Explore with users as the base table.

Create a persistent derived table from the user’s query.

Create an ephemeral derived table from the user’s query.

Add persist_for: “24 hours” to the orders Explore.

Q26. A user is seeing an error in the Explore that indicates the primary key defined for a one-million-row table is not unique.
How can the developer use SQL Runner to troubleshoot quickly?

Create a query that selects all the fields from the table, and sort by primary key.

Create a query that selects the primary key from the base view, and look for duplicates.

Create a query that counts how many occurrences of the primary key value are in the base view, and sort by count.

Create a query that concatenates two columns to create a compound primary key.

Q27. A developer needs to build a new dimension that offers an age-based cohort representation of users.
Which LookML code should the developer use to meet the requirement?
A)

B)

C)

D)

Option A

Option B

Option C

Option D

Q28. A developer wants to create a measure that shows the item count broken out by category. When a second, more granular dimension is added to the same query, the count broken out by category should still represent the original aggregation and be duplicated on each line. The business wants this “count” in “category” available in the Explore section without any additional work done by the end user. For example:
The Count column represents the count for each combination of Category and Item.
The Count in Category column represents the count for each Category only.

How can the developer address this need with a LookML object?

Create a measure filtered on Category, and make the filter value controlled by a parameter.

Calculate the measure using a derived table, and then join that derived table back into the Explore.

Create a measure with type: sum_over_dimension, and make the dimension value controlled by a parameter.

Calculate the overall count using table calculations in the Explore.

Q29. 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 the table 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?

persist_with: “12 hours”

datagroup: 12_hours {
max_cache_age: “12 hours”
}

persist_for: “12 hours”

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

Q30. A LookML developer has a transactions view with several measures that each perform complex calculations involving multiple fields. The LookML developer creates an Explore based on the transactions view. The product team wants to perform further functions on these measures, such as SUM, AVG, MIN, MAX, and RANK. The team wants these further functions to be performed at different levels of detail: weekly, monthly, and yearly.
How can the LookML developer model these requirements and minimize the amount of code rewriting?

Add measures to the transactions view of type: number to apply the required functions.

Change the existing measures in the transactions view to dimensions, and add measures of the different required types.

Create a constant for each measure so it can be reused across other areas of the LookML project.

Create native derived tables using transactions as the explore_source.

Q31. A LookML developer builds a view that contains sensitive information. Only members of the Management group should have access to the view. The developer needs to restrict the view from appearing in the field picker for any Explore where it might be joined for users outside of the Management group.
Which LookML parameter should the developer use to meet this requirement?

access_grant

always_filter

access_filter

sql_always_where

Q32. Users report that every time they change the filter on their Explore, the filters take a very long time to populate.
How can the developer improve the filtering experience with this Explore?

Limit the filter suggestions using the suggestions parameter.

Add an always_filter parameter to restrict the filter suggestions.

Use an access_filter parameter to automatically apply filters.

Add persistence to the base view of the Explore.

Q33. 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?

Set definition

Join condition

Fields parameter

Hidden parameter

Q34. After running the Content Validator, a developer can see the error “Unknown field”.
Which two changes could cause this issue? (Choose two.)

View name was changed from users to customers.

Field type was changed from number to string.

Model name was changed from e_commerce to reporting.

Explore label was changed from users to customers.

Field name was changed from id to user_id.

Q35. 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)

Option A

Option B

Option C

Option D

Q36. A user reports an error message 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?

The sum measure used is defined correctly.

A unique primary key is defined in each view.

Symmetric_aggregates: no is not present in the Explore definition.

No concatenated primary keys are used.