Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Associate Data Practitioner practice bank has 1,156 more like it. Try 10 free: instant score, no account.
A data analyst is setting up an automated workflow in BigQuery that executes a daily SQL aggregation query to refresh an executive reporting table. Before configuring the scheduled query, the analyst wants to validate the SQL syntax and estimate the number of bytes the query will scan to optimize performance and prevent unexpected billing, without executing the query or incurring on-demand query costs.
Which feature should the analyst use in BigQuery?
A dry run in BigQuery is a query execution simulation mode that evaluates and parses the SQL statement without actually running it against the data engine or scanning table rows. When a query is submitted as a dry run (by setting the dryRun flag to true in API requests, client libraries, or the Google Cloud console), BigQuery validates query syntax, verifies schema and table references, and calculates the exact number of bytes billed and processed if the query were executed.

totalBytesProcessed metric in the returned job statistics, allowing the analyst to understand resource usage and query cost.A dry run is the only native BigQuery capability designed specifically to validate query correctness and calculate byte consumption without running the job or incurring execution costs. It provides the exact prerequisite metrics needed before committing queries to automated schedules.
Batch query priority is an execution mode in BigQuery that queues a query job and executes it as soon as idle compute resources (slots) become available in the shared resource pool, typically within a few minutes to a few hours.
The scenario required running historical ETL transformations or background reports overnight where execution latency is not critical and jobs should run using idle capacity without competing with interactive user dashboards.
A slot reservation in BigQuery's capacity-based billing model is a dedicated or autoscaling pool of compute slots allocated to specific projects, folders, or workload types (such as pipeline, interactive, or background queries).
The scenario required guaranteeing predictable execution performance and preventing resource contention for mission-critical scheduled queries by allocating dedicated processing capacity.
Table expiration is a lifecycle management configuration applied to BigQuery datasets or individual tables that automatically deletes the table and its associated storage after a specified duration or at a specific timestamp.
The scenario stated that the daily query writes intermediate staging data to a temporary dataset that must be automatically deleted after 48 hours to minimize long-term storage expenses.
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