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.
An analytics team is running interactive dashboard queries in BigQuery using an Enterprise Edition reservation configured with baseline slots and autoscaling capacity. During peak reporting hours, numerous concurrent queries execute simultaneously, diluting the slot allocation per query and causing unacceptable latency. Additionally, finance reports discrepancies between query-level slot runtime metrics and compute reservation charges.
Which combination of configuration and observability practices should the data engineering team implement to stabilize query performance and correctly analyze compute costs?
This option demotes dashboard queries to batch priority jobs and relies on INFORMATION_SCHEMA.RECOMMENDATIONS for partition and clustering savings.
INFORMATION_SCHEMA.RECOMMENDATIONS highlights structural schema optimizations (such as clustering or partitioning), rather than explaining the mechanics of slot autoscaling compute pricing and scale-down window retention.The workload consisted of non-urgent, background ELT pipelines that could be deferred until cluster capacity became completely idle.
This solution configures a specific target job concurrency on the BigQuery reservation using the ALTER RESERVATION SET OPTIONS statement or the Google Cloud console, while adopting reservation-level capacity monitoring for billing evaluation rather than individual job metrics.
target_job_concurrency = 0), which may allow too many queries to execute at the same time and spread slot capacity too thinly. Setting a non-zero target_job_concurrency imposes an upper bound on simultaneous executions within that reservation, ensuring each running query receives a guaranteed minimum slot allocation while excess queries queue safely.INFORMATION_SCHEMA.JOBS ensures accurate financial tracking.This approach directly resolves query contention by tuning reservation concurrency settings and aligns monitoring practices with the true billing mechanics of BigQuery autoscaling editions.
This approach disables query queuing entirely by setting the queue timeout to -1 and scales baseline slot capacity permanently to cover peak burst traffic.
ADMISSION_DENIED error, degrading user experience for dashboard consumers.default_interactive_query_queue_timeout_ms = -1 creates brittle production behavior where queries hard-fail under momentary traffic spikes.The architectural requirement dictated that queries must fail fast rather than tolerate queuing delay, and financial policy favored fixed baseline reservations over autoscaling compute models.
This configuration sets ignore_idle_slots = true on the reservation to prevent queries from borrowing unused baseline slots from other reservations, and attempts to reconcile autoscaling compute costs by querying total_slot_ms from INFORMATION_SCHEMA.JOBS.
ignore_idle_slots only isolates the reservation from external idle capacity; it does not cap the number of concurrent queries executing within the reservation itself, leaving slot dilution unresolved.total_slot_ms from INFORMATION_SCHEMA.JOBS accounts only for actual query execution time, failing to capture the provisioned autoscaled slot duration and scaling steps.The primary goal were to strictly isolate workloads from sharing unallocated baseline capacity with adjacent reservations and the organization used flat-rate legacy commitments rather than autoscaling editions.
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