You are administering shared BigQuery datasets that contain views used by multiple teams in your organization. The marketing team is concerned about the variability of their monthly BigQuery…

Question

Options

• ACreate a BigQuery Enterprise reservation with a baseline of 250 slots and autoscaling set to 500 for the marketing team, and bill them back accordingly.
• BEstablish a BigQuery quota for the marketing team, and limit the maximum number of bytes scanned each day.
• CCreate a BigQuery reservation with a baseline of 500 slots with no autoscaling for the marketing team, and bill them back accordingly.
• DCreate a BigQuery Standard pay-as-you go reservation with a baseline of 0 slots and autoscaling set to 500 for the marketing team, and bill them back

• A
  6% (1)
• B
  11% (2)
• C
  83% (15)

Explanation

Option C is correct because a fixed reservation of 500 slots with no autoscaling moves the marketing team from on-demand (pay-per-byte-scanned) to capacity-based pricing, where they pay for a fixed number of slots regardless of query volume - making their monthly cost entirely predictable.

Why the distractors fail:

• A introduces autoscaling (baseline 250, max 500), which means slot usage - and therefore cost - still varies with workload demand, preserving the variability problem.
• B sets a daily byte-scan quota, which acts as a hard cap rather than a consistent spend; queries can fail when the limit is hit, and the cost can still fluctuate anywhere below that ceiling.
• D uses a pay-as-you-go reservation with a 0-slot baseline and full autoscaling, which is functionally similar to on-demand billing - slots (and costs) scale up and down with usage.

Memory tip: Autoscaling = variability. If the question asks for consistent or predictable spend, look for the option with a fixed baseline and zero autoscaling - that's the only way to guarantee a flat, foreseeable bill each month.

No community discussion yet for this question.