Attested LookML-Developer Dumps PDF Resource [2021]
Latest LookML-Developer Actual Free Exam Questions Updated 51 Questions
NEW QUESTION 27
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)
- A. Option D
- B. Option A
- C. Option C
- D. Option B
Answer: C
NEW QUESTION 28
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?
- A. Fields parameter
- B. Hidden parameter
- C. Set definition
- D. Join condition
Answer: D
NEW QUESTION 29
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?
- A. In one user's personal branch, with both users writing to the branch
- B. In the master 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
Answer: C
NEW QUESTION 30
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. Writhe the query form user_facts into a common table expression (WITH user_facts AS...).
- B. Write a subquery in the FROM clause and alias with ${user_facts}.
- C. Use ${user_facts.SQL_TABLE_NAME} to reference the user_facts derived table.
- D. Copy the name of the database table in the scratch schema for the user_facts derived table.
Answer: A
NEW QUESTION 31
After running the LookML Validator, a developer sees the following error message in the Looker development environment:
"Measures with Looker aggregations (sum, average, min, max, list types) may not reference other measures".
What could be causing this error?
- A. A measure of type: number has a SUM function written in the sql parameter.
- B. A measure of type: sum has a SUM function written in the sql parameter.
- C. A measure of type: count has a sql parameter defined.
- D. A measure of type: sum adds up other measures in the sql parameter.
Answer: C
NEW QUESTION 32
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?
- A. access_grant
- B. sql_always_where
- C. access_filter
- D. always_filter
Answer: A
NEW QUESTION 33
After running the Content Validator, a developer can see the error "Unknown field".
Which two changes could cause this issue? (Choose two.)
- A. Field type was changed from number to string.
- B. Field name was changed from id to user_id.
- C. Explore label was changed from users to customers.
- D. View name was changed from users to customers.
- E. Model name was changed from e_commerce to reporting.
Answer: A,B
NEW QUESTION 34
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)
- A. Option D
- B. Option A
- C. Option C
- D. Option B
Answer: D
NEW QUESTION 35
A LookML developer creates an Explore that joins two views. The base view has information about users' interactions with the support team. The joined view contains data about the users. The support team using this Explore feels overwhelmed by the amount of data this Explore shows them and decides to just look at open tickets.
What should the developer add to the Explore in the model to achieve these requirements?
- A. The sql_always_where parameter
- B. A filtered measure
- C. The hidden parameter
- D. A relationship definition
Answer: D
NEW QUESTION 36
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.
Answer: B
NEW QUESTION 37
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 is the likely cause of the SQL error?
- A. The discounted_sale_price field should have a group_by: yes parameter.
- B. The discounted_sale_price field should be defined as a dimension of type: number, not as a measure.
- C. The sale_price field should be defined as a measure of type: number, not as a dimension.
- D. The underlying database table does not have a field called sale_price.
Answer: C
NEW QUESTION 38
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?
- A. Limit the filter suggestions using the suggestions parameter.
- B. Add an always_filter parameter to restrict the filter suggestions.
- C. Add persistence to the base view of the Explore.
- D. Use an access_filter parameter to automatically apply filters.
Answer: A
NEW QUESTION 39
A user reports that, when a date dimension is filtered to "before now" results are returned that consistently include tomorrow. Dimension fill has been ruled out as a cause of the issue.
Which LookML parameter should be used to resolve this issue?
- A. Datatype
- B. Convert_tz
- C. Fiscal_month_offset
- D. Week_start_day
Answer: C
NEW QUESTION 40
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 to use 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 D
- C. Option C
- D. Option B
Answer: A
NEW QUESTION 41
The code below shows a view order_items with its measures total_revenue and user_count
Which code correctly represents a new measure that calculates average revenue per user?
A)
B)
C)
D)
- A. Option D
- B. Option A
- C. Option C
- D. Option B
Answer: C
NEW QUESTION 42
A LookML developer has written the following persistent derived table. It references orders_rollup, another persistent derived table that also rebuilds with the same SQL trigger value.
Which change is needed to guarantee that user_facts will always rebuild with the latest data from orders_rollup?
- A. Change the orders_rollup view reference to the literal table name from the database's scratch schema.
- B. Change the sql_trigger_value parameter for both persistent derived tables to a datagroup_trigger parameter, and set them to use the same datagroup.
- C. Change the orders_rollup view reference to ${orders_rollup.DERVIED_TABLE_NAME}
- D. Change the sql_trigger_value parameter of user_facts to select the current date plus one hour, so it triggers an hour after orders_rollup.
Answer: B
NEW QUESTION 43
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?
- A. Create three separate datagroups tied to three PDTs that run when a new row is added to the ETL log table.
- 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 one datagroup tied to all three PDTs that runs when the total row count across all three tables changes.
Answer: A
NEW QUESTION 44
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?
- A. Symmetric_aggregates: no is not present in the Explore definition.
- B. A unique primary key is defined in each view.
- C. The sum measure used is defined correctly.
- D. No concatenated primary keys are used.
Answer: A
NEW QUESTION 45
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?
- A. required_access_grants: ["000","999"]
- B. required_access_grants: [leadership]
- C. required_access_grants: [can_view_financial_data]
- D. required_access_grants: [total_revenue]
Answer: C
NEW QUESTION 46
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 A
- B. Option D
- C. Option C
- D. Option B
Answer: A
NEW QUESTION 47
......
LookML-Developer Certification Overview Latest LookML-Developer PDF Dumps: https://www.testsimulate.com/LookML-Developer-study-materials.html