Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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:
n2-standard-16 virtual machines (VMs) in zone us-central1-a across the three projects.project-infra).Which combination of configuration steps meets these requirements?
Future reservations allow organizations to request assurance for compute capacity starting at a future date up to one year in advance. Compact placement policies specify that VMs must be placed in close physical proximity to reduce network latency.
project-infra), not divided equally among consumer projects.SPECIFIC_RESERVATION).The workload required advance assurance for high-demand hardware blocks (like specialized AI accelerators) starting on a distant fixed date without compact placement constraints.
SPECIFIC_RESERVATION, and configure all consumer VMs with reservationAffinity=none.A specifically targeted reservation (SPECIFIC_RESERVATION) requires VM instances to explicitly specify the reservation by name in order to consume its allocated capacity. The reservationAffinity property on a Compute Engine instance dictates how that instance matches and consumes reservations.
reservationAffinity to none (or omitting affinity while targeting a specific reservation) explicitly instructs Compute Engine that the VM must not consume any reservation. Consequently, the VMs will run as standard on-demand instances, completely bypassing the reserved capacity.project-infra, and again for the 60 unreserved on-demand VMs running in the consumer projects.ANY).reservationAffinity=none: Guarantees that an instance never consumes reserved capacity.reservationAffinity=SPECIFIC_RESERVATION: Requires specifying the exact reservation name and owning project.You wanted to isolate reserved capacity exclusively for a distinct, critical batch process while explicitly preventing general production or development VMs in the consumer projects from consuming the reservation.
Single-project reservations allocate Compute Engine capacity exclusively for virtual machines located in the specific project where the reservation was created. By default, they can be consumed automatically by matching VMs in that same project.
project-core requires 35 VMs while project-analytics requires only 5 VMs, project-core cannot overflow into or consume unused capacity from project-analytics's reservation.project-infra.Each application team operated completely independent, predictable workloads with separate budgets and had strict isolation requirements preventing any shared infrastructure pools.
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.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated