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 analytics spend using the on-demand billing model. You need to help the marketing team establish a consistent BigQuery analytics spend each month. What should you do?
To help the marketing team establish a consistent BigQuery analytics spend each month, you should create a BigQuery reservation with a baseline of 500 slots with no autoscaling. This setup ensures that the marketing team will have a predictable and fixed monthly cost for their BigQuery usage, avoiding the variability associated with the on-demand billing model. By having 500 slots reserved, the team can perform their analytics tasks without worrying about sudden cost spikes due to autoscaling or exceeding query quotas.
Reservations guarantee a fixed number of slots (computational resources) for BigQuery queries, ensuring a predictable monthly cost, addressing the marketing team's concern about variability.
Why 500 slots?
But seems only C makes sense. https://cloud.google.com/bigquery/quotas#query_jobs "There is no limit to the number of bytes that can be processed by queries in a project."
"However, you can set limits on the amount of data users can query by creating custom quotas to control query usage per day or query usage per day per user." https://cloud.google.com/blog/products/data-analytics/manage-bigquery-costs-with-custom-quotas B would be correct
If you use B - the marketing team wouldn't be able to run their queries when the quota is reached, which could harm the business. Having a reservation for 500 slots and no autoscaling gives you exact predictable cost for each month without harming the business or have variable cost with autoscaling So C should be the right answer
https://cloud.google.com/blog/products/data-analytics/manage-bigquery-costs-with-custom-quotas
at first I thought C for best practices but the questions does not ask to lower the cost just to make the spend consistent
u spot on MissK1371
anybody for D ? https://cloud.google.com/bigquery/docs/slots-autoscaling-intro
The question clearly mentions, that team is using the on-demand billing mode in BiqQuery, which charges for the number of bytes processed by each query. So limiting the bytes processed will be the solution. https://cloud.google.com/blog/products/data-analytics/manage-bigquery-costs-with-custom-quotas
C. Create a BigQuery reservation with a baseline of 500 slots with no autoscaling for the marketing team, and bill them back accordingly. This option provides the marketing team with a predictable monthly cost by reserving a fixed number of slots, ensuring that they have dedicated resources without the variability introduced by autoscaling or on-demand pricing. This setup also simplifies budgeting and financial planning for the marketing team, as they will have a consistent expense each month.
I agree that at first sight option C seems best. However, the question mentions that they are currently on the on-demand billing model and option C does not mention anything about changing the pricing model from on-demand to capacity computing (BigQuery Standard or Enterprise edition). I don't believe it is possible to reserve slots with on-demand billing.
Option D - https://cloud.google.com/bigquery/pricing Standard Pay-as-you-go Reservation: This model charges only for the slots used, aligning with the marketing team's need for predictable costs. On-demand pricing would lead to variable costs, while committed use discounts or reservations with fixed costs wouldn't provide the needed flexibility. Baseline of 0 Slots: Setting a baseline of 0 ensures no upfront commitment and avoids unused capacity charges if the marketing team's usage is lower than expected. Autoscaling Up to 500 Slots: Autoscaling provides the flexibility to handle unexpected spikes in usage without incurring on-demand pricing costs. The 500-slot limit sets a reasonable upper bound to control spending. Billing Back: Billing the marketing team based on their actual usage promotes cost awareness and encourages responsible resource utilization.
Looks like only the baseline slots are guaranteed and immediately available for use where as autoscaling slots are not guaranteed immediately.
So C is a better option
which will give a consistent bill per month
Explanation: Predictability: The baseline of 250 slots ensures a predictable minimum spend each month. Flexibility: Autoscaling up to 500 slots allows the team to handle peak workloads without interruptions. Balanced Cost: While Option B limits daily spend, it can lead to disruptions in service. Option A offers a consistent monthly cost while still accommodating variable workloads efficiently.
Why 500 slots?
C. Create a BigQuery reservation with a baseline of 500 slots with no autoscaling for the marketing team, and bill them back accordingly.
C. Create a BigQuery reservation with a baseline of 500 slots with no autoscaling for the marketing team, and bill them back accordingly.
As wrote @Sofia98 the company using "on-demand billing model", so the best solution should be the B, https://cloud.google.com/blog/products/data-analytics/manage-bigquery-costs-with-custom-quotas
C. Create a BigQuery reservation with a baseline of 500 slots with no autoscaling for the marketing team, and bill them back accordingly.
Provide, please, the reference