Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise organization operates multiple Google Cloud projects under a single Cloud Billing account. The central Site Reliability Engineering (SRE) team must provision guaranteed compute capacity for three separate service projects (project-core, project-analytics, and project-services) in us-central1-a ahead of a high-traffic seasonal event.
The capacity planning strategy must satisfy the following requirements:
StudyCerts
StudyCertsn2-standard-16 virtual machines (VMs) in zone us-central1-a across the three projects.project-infra).Which combination of configuration steps meets these requirements?
Add project-infra to the allowlist for the compute.sharedReservationsOwnerProjects organization policy constraint, create a shared on-demand reservation in project-infra targeting us-central1-a with consumer projects added, and enable CUD sharing on the Cloud Billing account.
Submit a shared future reservation request in project-infra specifying compact placement policies, and rely on the request to automatically bill all unconsumed capacity to the three consumer projects equally.
Create three separate single-project reservations of 20 VMs each across the three consumer projects with default automatic consumption, and rely on automatic cross-project reservation overflow to handle imbalance.
Create a shared on-demand reservation in project-infra configured with consumption type SPECIFIC_RESERVATION, and configure all consumer VMs with reservationAffinity=none.
Add project-infra to the allowlist for the compute.sharedReservationsOwnerProjects organization policy constraint, create a shared on-demand reservation in project-infra targeting us-central1-a with consumer projects added, and enable CUD sharing on the Cloud Billing account.
Shared reservations allow a central owner project in Google Cloud to allocate and guarantee zonal Compute Engine capacity that multiple consumer projects within the same organization can consume. The compute.sharedReservationsOwnerProjects organization policy constraint provides governance by strictly restricting which projects have permission to create and manage shared reservations.
project-infra for 60 n2-standard-16 VMs in us-central1-a and specifying project-core, project-analytics, and project-services as consumer projects enables VMs in any of those projects to consume the shared capacity pool dynamically.project-infra). However, as soon as a consumer project runs a matching VM that consumes reserved capacity, Compute Engine switches the billing of that consumed portion directly to the consumer project.project-infra to the allowlist for the compute.sharedReservationsOwnerProjects constraint prevents unauthorized teams from creating shared reservations elsewhere in the organization.This architecture directly adheres to Google Cloud's multi-project capacity planning best practices by pairing organization policy controls, shared zonal reservations, and billing-level CUD sharing.
Submit a shared future reservation request in project-infra specifying compact placement policies, and rely on the request to automatically bill all unconsumed capacity to the three consumer projects equally.
Create three separate single-project reservations of 20 VMs each across the three consumer projects with default automatic consumption, and rely on automatic cross-project reservation overflow to handle imbalance.
Create a shared on-demand reservation in project-infra configured with consumption type SPECIFIC_RESERVATION, and configure all consumer VMs with reservationAffinity=none.