Explanation:
The correct approach is to create two separate reservations tailored to each project's needs. For the production jobs with strict SLAs, an Enterprise Edition reservation with a baseline of 300 slots and autoscaling up to 500 slots ensures consistent resource availability. For the ad-hoc queries, on-demand billing aligns with the preference to pay based on data scanned, not slot capacity. This setup optimally addresses the distinct requirements of each project.
Ultimate access to all questions.
You are managing two BigQuery projects with distinct requirements: one for production jobs with strict SLAs needing high priority and consistent access to 300 slots (spiking to 800), and another for ad-hoc analytical queries preferring billing based on data scanned, typically using up to 200 slots. How should you allocate compute resources to meet both projects' needs?
A
Establish two Enterprise Edition reservations, one for each project. For the SLA project, set a baseline of 300 slots and enable autoscaling up to 500 slots. For the ad-hoc project, set a reservation baseline of 0 slots and disable the ignore idle slots flag.
B
Create a single Enterprise Edition reservation for both projects with a baseline of 300 slots and enable autoscaling up to 700 slots.
C
Set up two reservations, one for each project. For the SLA project, use an Enterprise Edition with a baseline of 300 slots and enable autoscaling up to 500 slots. For the ad-hoc project, opt for on-demand billing.
D
Configure two Enterprise Edition reservations, one for each project. For the SLA project, set a baseline of 800 slots. For the ad-hoc project, enable autoscaling up to 200 slots.
No comments yet.