Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
Your organization is deploying containerized database workloads (AlloyDB Omni) on Google Compute Engine virtual machines in production.
Performance analysis and sizing assessments define the following technical and operational requirements:
Which compute provisioning strategy should you implement to optimize resource allocation and cost?
Rightsizing recommendations in Google Cloud analyze past resource utilization (CPU, memory) over an observation window (typically 8 to 14 days) and generate advisory suggestions in the Google Cloud Console or Recommender API.
The goal was to periodically review fleet-wide resource utilization trends to find candidates for optimization after weeks of operation.
Predefined n2-standard machine types offer a fixed ratio of 4 GB of system memory per vCPU (e.g., n2-standard-16 provides 16 vCPUs and 64 GB of RAM).
n2-standard-16, which forces the provisioning of 16 vCPUs.The workload was CPU-bound and fully utilized 16 vCPUs alongside standard memory ratios.
Spot VMs are excess Compute Engine capacity available at significant discounts (60–91%), but Google Cloud can preemptively reclaim and stop them at any time with a 30-second warning. n2-highcpu instances provide only 1 GB of RAM per vCPU.
n2-highcpu-16 VM provides only 16 GB of memory, far below the required 64 GB needed to fit the database buffer pool and working set.highcpu families allocate a 1:1 or 2:1 RAM-to-CPU ratio.The workload were a fault-tolerant, ephemeral batch processing or simulation job that can handle abrupt termination.
Custom machine types in Google Compute Engine allow you to customize the exact number of vCPUs and amount of memory (RAM) for a virtual machine instance, rather than selecting from predefined machine types.
n2-standard-16) provide 4 GB per vCPU, meaning 64 GB of RAM would mandate purchasing 16 vCPUs—doubling vCPU costs for compute capacity that provides no performance benefit.Using custom machine types satisfies the specific 8:1 memory-to-vCPU ratio needed by the database while preventing the waste associated with predefined machine types that force higher core counts.
Change the inputs and watch how the outcome changes.

Change the provisioning strategy and uptime requirement to see how vCPUs, RAM, billing, and preemption risk play out.
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