You are a head of BI at a large enterprise company with multiple business units that each have different priorities and budgets. You use on-demand pricing for BigQuery with a quota of 2K concurrent…

Question

Options

• AConvert your batch BQ queries into interactive BQ queries.
• BCreate an additional project to overcome the 2K on-demand per-project quota.
• CSwitch to flat-rate pricing and establish a hierarchical priority model for your projects.
• DIncrease the amount of concurrent slots per project at the Quotas page at the Cloud Console.

• A
  25% (5)
• B
  10% (2)
• C
  50% (10)
• D
  15% (3)

Explanation

Switching to flat-rate pricing (now called BigQuery Capacity Commitments) removes the per-project on-demand slot cap entirely by giving your organization a dedicated pool of purchased slots. Combined with BigQuery's Reservations and Assignments, you can carve that pool into named reservations and assign them hierarchically at the organization, folder, or project level - letting you set guaranteed slot allocations and priorities per business unit without touching project structure.

Why the distractors fail:

• A - Batch queries queue for slots rather than competing in real-time, but converting them to interactive doesn't add more slots; the 2K ceiling still applies to everyone.
• B - Directly ruled out by the constraint in the question ("avoid introducing new projects"), and it just splits the problem rather than solving it architecturally.
• D - The 2,000 concurrent on-demand slots is a firm per-project quota for on-demand pricing; it is not adjustable via the Cloud Console Quotas page the way soft quotas are.

Memory tip: When you see "multiple business units + different priorities + slot starvation," think flat-rate + Reservations hierarchy - on-demand is a shared free-for-all with hard caps, while flat-rate lets you act like a landlord assigning guaranteed space to each tenant.

No community discussion yet for this question.