Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
A retail enterprise maintains a central BigQuery table containing precalculated hourly sales performance metrics. A Looker Studio executive dashboard connected to this dataset is accessed frequently by hundreds of regional managers throughout the business day.
The underlying data pipeline updates the BigQuery precalculated table every hour on the hour. You need to configure the Looker Studio data source connection to minimize BigQuery query costs and visualization latency while strictly honoring the 1-hour reporting freshness SLA.
How should you configure the data source connection in Looker Studio?
This approach bypasses precalculated summary tables and connects Looker Studio directly to detailed transactional records, using chart-specific calculated fields and runtime aggregation functions (such as SUM and CASE) to calculate KPIs on demand.
Users required ad hoc, non-standard slice-and-dice operations with dynamic parameters over transactional data that could not be precomputed ahead of time.
Setting the data source to Viewer's Credentials executes queries against BigQuery using the identity and permissions of each individual user viewing the dashboard, maintaining isolated data freshness settings per user.
The dashboard enforced BigQuery row-level security or user-specific IAM dataset permissions where each individual viewer must authenticate and scan only their permitted data partitions.
Configuring a Looker Studio data source with Owner's Credentials and setting a 1-hour data freshness threshold optimizes cached query reuse across all dashboard consumers while aligning cache invalidation with the underlying hourly ingestion pipeline.
This approach directly balances performance, storage, and freshness SLAs by pairing centralized cache management (via Owner's Credentials) with scheduled pipeline cadence (1-hour cache eviction).
This configuration relies on Looker Studio's default 12-hour data freshness cache duration with Owner's Credentials, requiring report viewers or editors to manually trigger Refresh Data from the options menu when new hourly records arrive.
The underlying data pipeline ran on a daily or half-day batch schedule where intra-day updates were unnecessary.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated