professional-cloud-data-engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise is operating BigQuery on the Enterprise edition across several departments. The data engineering team manages a multi-tenant environment with the following workload requirements:
Which configuration strategy should the team implement across their reservations to satisfy these workload requirements while optimizing cost?
Assign all ETL/ELT and ad-hoc query projects directly to the on-demand compute model without creating BigQuery reservations.
Create a dedicated reservation for ETL/ELT with baseline slots and set ignore_idle_slots = true; create a separate reservation for ad-hoc queries configured with autoscaling slots and set ignore_idle_slots = false.
Create a single shared reservation with autoscaling slots only and set ignore_idle_slots = true for all projects across the organization.
Create a dedicated reservation for ETL/ELT with autoscaling slots and set ignore_idle_slots = false; create a separate reservation for ad-hoc queries with baseline slots only and set ignore_idle_slots = true.
Assign all ETL/ELT and ad-hoc query projects directly to the on-demand compute model without creating BigQuery reservations.
Create a dedicated reservation for ETL/ELT with baseline slots and set ignore_idle_slots = true; create a separate reservation for ad-hoc queries configured with autoscaling slots and set ignore_idle_slots = false.
This strategy uses BigQuery Editions reservation workload management to isolate workloads by defining distinct reservations with customized capacity configurations and idle slot sharing behaviors.
StudyCerts
StudyCertsignore_idle_slots = true ensures that queries in this reservation rely strictly on dedicated capacity, preventing external slot contention or unpredictable performance variations.ignore_idle_slots = false on the ad-hoc analytics reservation permits analyst queries to opportunistically consume unused baseline slots from other reservations in the same administration project, minimizing paid autoscaling events.Separating the workloads into dedicated reservations allows fine-grained control over slot predictability and autoscaling elasticity. Combining baseline guarantees with isolated idle policies provides deterministic execution for ELT while delivering elasticity and cost efficiency for interactive analytics.
Create a single shared reservation with autoscaling slots only and set ignore_idle_slots = true for all projects across the organization.
Create a dedicated reservation for ETL/ELT with autoscaling slots and set ignore_idle_slots = false; create a separate reservation for ad-hoc queries with baseline slots only and set ignore_idle_slots = true.