Cisco®
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
Scrum
All Vendors
  2. Home
  3. Exams
  4. Google
  5. LookML Developer

Free LookML Developer Exam Braindumps (page: 2)

Page 1 of 13
PDF with 50 Questions

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?





Answer(s): C


Reference:

https://hevodata.com/learn/understanding-looker-ml/



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

  1. Add a description parameter to each field with context so that users can search key terms.
  2. Create a separate project for each business unit containing only the fields that the unit needs.
  3. Add a group_label parameter to relevant fields to organize them into logical categories.
  4. Use the hidden parameter to remove irrelevant fields from the Explore.
  5. Use a derived table to show only the relevant fields.

Answer(s): A,C,E



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?

  1. Create an Explore with users as the base table.
  2. Create a persistent derived table from the user’s query.
  3. Create an ephemeral derived table from the user’s query.
  4. Add persist_for: “24 hours” to the orders Explore.

Answer(s): A


Reference:

https://docs.looker.com/data-modeling/learning-lookml/sql-runner



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

  1. Open the Explore query in SQL Runner and validate whether removing the conversion from date fields changes the results.
  2. Open the Explore query in SQL Runner to determine which fields are converted.
  3. Use the CAST function in SQL Runner to ensure that all underlying fields are dates and conversions are not applied.
  4. Use the Describe feature in SQL Runner to determine which fields include time data.

Answer(s): C


Reference:

https://community.looker.com/technical-tips-tricks-1021/how-looker-does-timezones-and-how-to-troubleshoot-them-25477






Post your Comments and Discuss Google LookML Developer exam with other Community members: