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.
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:
Which configuration should you implement?
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'.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.
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.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.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.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.
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.This configuration attempts to allocate slot capacity using the PIPELINE assignment job type and tries to target individual BigQuery dataset objects directly.
PIPELINE job type assignment is exclusively used for BigQuery load and extract jobs (data ingestion and export). SQL transformation queries, scheduled queries, and dashboard reporting require assignments with job_type = 'QUERY'.PIPELINE job types manage ingestion/export slots, while QUERY job types manage SQL execution and ELT queries.The workload consisted exclusively of batch ingestion jobs loading files from Cloud Storage into BigQuery tables and needed dedicated extraction/load capacity.
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.This configuration attempts to manage mixed workloads by consolidating all organizational traffic into a single BigQuery reservation pool while relying on on-demand byte quotas to restrict data science queries.
The organization operated entirely on the on-demand pricing model and needed a hard stop to prevent data science projects from exceeding a monetary billing threshold.
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.This approach leaves business-critical production workloads on the default on-demand pricing model while assigning ad-hoc exploratory analytics workloads to a dedicated, capacity-based reservation.
Production workloads were small, infrequent queries where paying per byte scanned was more cost-effective, while analytics required a fixed, predictable monthly compute budget.
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