Your enterprise runs mission-critical hourly data transformation pipelines and executive dashboards in a dedicated Production folder, while data scientists run unpredictable, heavy ad-hoc queries in an Analytics folder. During peak hours, ad-hoc queries consume excessive compute resources, causing slot contention and delayed execution for production pipelines. You need to implement a capacity-based workload management architecture in BigQuery that: Guarantees dedicated, predictable processing capacity for production workloads with the ability to dynamically burst during unexpected demand spikes. Fully isolates production capacity so idle slots are never shared with or preempted by ad-hoc analytics jobs. Allows ad-hoc analytics workloads to scale dynamically up to a defined ceiling without impacting the production workloads. Minimizes administrative overhead by managing assignments hierarchically. Which configuration should you implement?

Create a dedicated administration project. In this project, configure two regional Enterprise edition reservations: a `prod` reservation configured with baseline slots, an autoscaling maximum slot size, and the `ignore_idle_slots` setting set to true, and an `analytics` reservation configured with autoscaling slots. Assign the `Production` folder to the `prod` reservation and the `Analytics` folder to the `analytics` reservation with `job_type = 'QUERY'`.: ### What BigQuery Reservations and Slot Allocations Are **BigQuery reservations** provide dedicated compute capacity measured in **slots** (virtual CPUs) to execute SQL queries, data manipulation, and pipeline transformations. Within capacity-based billing (available in BigQuery editions such as **Enterprise**), administrators can structure compute capacity into isolated pools and allocate them across projects, folders, or organizations. ### How This Configuration Meets All Requirements - **Dedicated and bursting production capacity**: Configuring baseline slots guarantees a dedicated minimum processing capacity that is always provisioned and instantly available for scheduled pipelines. Specifying a higher **max reservation size** enables **slots autoscaling**, allowing production workloads to dynamically burst when data volumes spike. - **Workload isolation via `ignore_idle_slots`**: Setting `ignore_idle_slots = true` (or enabling the **Ignore idle slots** toggle) disables idle slot sharing. This ensures that unused baseline capacity in the `prod` reservation is never loaned out to other reservations, eliminating any risk of slot preemption or delayed reclaiming when critical production jobs start. - **Controlled ad-hoc scaling**: Configuring the `analytics` reservation with autoscaling slots and an upper bound max reservation size allows data science queries to scale dynamically without ever competing for or exhausting production resources. - **Hierarchical resource assignment**: Assigning the reservations at the **folder level** (`Production` and `Analytics`) using `job_type = 'QUERY'` leverages resource hierarchy inheritance, ensuring all current and future projects within those folders automatically route their query jobs to the designated reservation pool without manual per-project administration. ### Key Advantages - **Complete workload isolation**: Guarantees zero resource contention between mission-critical operations and experimental queries. - **Cost governance**: Establishes deterministic upper bounds on compute spend across organizational units. - **Operational efficiency**: Centralizes slot purchasing and commitment management inside a single administration project. ### Why This Is Optimal Using edition-based reservations with baseline slots, autoscaling limits, idle slot isolation, and folder-level assignments is the architectural best practice for enterprise multi-tenant BigQuery environments requiring strict SLA guarantees.

Bigquery Reservations Workload Isolation Slot Allocation | professional-cloud-data-engineer

Bigquery Reservations Workload Isolation Slot Allocation

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.

Your enterprise runs mission-critical hourly data transformation pipelines and executive dashboards in a dedicated Production folder, while data scientists run unpredictable, heavy ad-hoc queries in an Analytics folder. During peak hours, ad-hoc queries consume excessive compute resources, causing slot contention and delayed execution for production pipelines.

You need to implement a capacity-based workload management architecture in BigQuery that:

Guarantees dedicated, predictable processing capacity for production workloads with the ability to dynamically burst during unexpected demand spikes.
Fully isolates production capacity so idle slots are never shared with or preempted by ad-hoc analytics jobs.
Allows ad-hoc analytics workloads to scale dynamically up to a defined ceiling without impacting the production workloads.
Minimizes administrative overhead by managing assignments hierarchically.

Which configuration should you implement?

Create a single shared-prod reservation in an administration project with baseline slots and autoscaling enabled. Assign the entire Google Cloud organization to this reservation with job_type = 'QUERY', and set up project-level custom daily bytes scanned quotas on every project inside the Analytics folder.

Leave the Production folder unassigned so that it defaults to the shared on-demand slot pool with a 2,000-slot cap. Create an Enterprise edition reservation for the Analytics folder with baseline slots and configure ignore_idle_slots = true to restrict analytics to its own dedicated pool.

Create a dedicated administration project. In this project, configure two regional Enterprise edition reservations: a prod reservation configured with baseline slots, an autoscaling maximum slot size, and the ignore_idle_slots setting set to true, and an analytics reservation configured with autoscaling slots. Assign the Production folder to the prod reservation and the Analytics folder to the analytics reservation with job_type = 'QUERY'.

Create two separate regional reservations in the administration project: prod and analytics. Configure both reservations with job_type = 'PIPELINE', enable idle slot sharing on both, and assign individual BigQuery dataset IDs to their respective reservations.

Professional Cloud Data Engineer

Bigquery Reservations Workload Isolation Slot Allocation

Related questions