PDE Preparing and Using Data for Analysis Practice Question
A financial analytics team uses Looker to explore BigQuery data. They need to allow business users to filter by a custom date range that is not tied to an existing dimension. The date range must be user-input at query time. What is the best approach in Looker?
⚠ Common exam trap
PDE often tests Looker customization, and candidates might think UI-based filters suffice, but for arbitrary user input, LookML parameters with Liquid are required.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a parameter in LookML using Liquid templating
Creating a parameter in LookML using Liquid templating allows business users to input a custom date range at query time. Parameters are user-input fields that can be referenced in SQL queries via Liquid, enabling dynamic filtering. This is the most flexible approach for ad-hoc date ranges not tied to existing dimensions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create an explore with a custom filter field in the Looker UI
Why it's wrong here
A custom filter field created in the Explore UI is saved per-user and cannot be surfaced to business users as a reusable query-time control. Looker's parameter and templated-filter mechanism is what accepts user input. UI filters suit one-off analyst exploration, not a governed input for many users.
- ✗
Use a filter parameter directly on the date dimension
Why it's wrong here
A filter parameter binds to an existing date dimension, so it cannot express a range the model does not already expose; the stem requires an ad-hoc user-input range. Parameter filters are correct when users must supply a value for a defined field, such as a specific start date on an existing dimension.
- ✗
Add a dimension with a yesno filter that toggles the date range
Why it's wrong here
A yesno dimension toggles a fixed, developer-defined condition; it cannot accept an arbitrary start and end date typed by the user. Yesno parameters suit binary switches, such as including or excluding a segment. The stem needs a free-form date range supplied at query time.
- ✓
Create a parameter in LookML using Liquid templating
Why this is correct
A LookML parameter with Liquid templating injects a user-supplied value into the generated SQL at query time, letting business users enter an arbitrary date range not bound to any existing dimension. This satisfies the stem's user-input-at-query-time constraint.
About these practice questions
This PDE question is part of Courseiva's 747-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This PDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PDE exam.