Looker LookML Developer: LOOKML-DEVELOPER

A LookML developer creates a new model and a test dashboard from the model. The developer shares the link to the new dashboard with users, but the users report that all they see is the “Model Not Found” error.

What is a possible cause of this issue?

A. The developer has not pushed the new model to Production Mode.

B. The developer has not added users to the new model set.

C. The users do not have permission to access this dashboard.

D. The new model is missing an Explore definition.

The daily_forecast Explore used by the sales team needs to be cached for 24 hours. All other Explores used by the sales team need to be cached for one hour.

What is a scalable way to configure this caching logic?

A. Define two datagroups for the model. Apply persist_with at the model level with the datagroup for 1hour caching, and apply persist_with to daily_forecast with the datagroup for 24-hour caching.

B. Define max_cache_age on daily_forecast Explores of 24 hours. Define max_cache_age on all other Explores for one hour.

C. Define two datagroups for the model. Create a persistent derived table (PDT) for the daily_forecast Explore, and apply datagroup_trigger to it using the datagroup for 24-hour caching.

D. Define for the model one datagroup that caches for 1 hour. Create a persistent derived table (PDT) for the daily_forecast Explore, and apply sql_trigger_value to it selecting the current date.

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

C. access_filter

D. sql_always_where