PDE Maintaining and Automating Data Workloads Practice Question
Your organization has a BigQuery flat-rate reservation with 500 slots. During peak hours, queries are queued and you need additional capacity temporarily. You want to add slots for a burst of activity without committing to a long-term purchase. What should you do?
⚠ Common exam trap
PDE often tests the distinction between temporary and committed capacity options, and candidates may confuse flex slots with autoscaling or committed use discounts, leading them to pick options that imply long-term commitments or automatic scaling rather than a short-term, manual burst.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use flex slots
Flex slots are a BigQuery feature that allows you to purchase slots for a short, fixed duration (e.g., 1 hour, 1 day, 1 week) without a long-term commitment. They are designed exactly for temporary bursts of query activity, such as peak-hour spikes, and can be added to an existing flat-rate reservation. By using flex slots, you temporarily increase the slot capacity of your reservation, reducing queuing, and then the slots automatically expire after the chosen period, avoiding ongoing costs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Switch to on-demand pricing
Why it's wrong here
On-demand pricing bills per byte scanned and abandons the flat-rate reservation's slot model entirely, so it cannot top up the existing 500-slot commitment during a burst. It is tempting because on-demand suits unpredictable, low-volume workloads where no reservation exists, but here it would replace rather than augment the reservation.
- ✓
Use flex slots
Why this is correct
Flex slots add short-term BigQuery capacity in 500-slot increments for as little as 60 seconds, then delete automatically. They satisfy the stem's temporary burst requirement without a long-term commitment, unlike annual or three-year commitments, and supplement the existing flat-rate reservation's 500 slots during peak queueing.
- ✗
Create a secondary reservation with autoscaling
Why it's wrong here
A secondary reservation with autoscaling adds slots only within its own reservation and cannot draw on the existing 500-slot commitment, so it fails to extend the primary reservation's capacity. Autoscaling reservations suit workloads with predictable, separate baselines, not temporary bursts on an existing flat-rate commitment.
- ✗
Purchase additional committed use reservations
Why it's wrong here
Committed use reservations lock in slots for a one- or three-year term, directly contradicting the requirement to avoid a long-term purchase for a temporary burst. It is tempting because commitments reduce per-slot cost for steady, predictable workloads, but they cannot flex down once peak activity ends.
About these practice questions
This PDE question is part of Courseiva's 747-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This PDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PDE exam.