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.
An enterprise is optimizing compute costs for three distinct workloads hosted on Google Cloud:
us-central1 with predictable, steady-state CPU and memory utilization.Which combination of Google Cloud pricing models and discount strategies should you recommend to minimize costs?
This strategy purchases spend-based CUDs for fixed-infrastructure database servers, attempts to bind resource-based CUDs across disparate regional services for container workloads, and relies on Sustained Use Discounts (SUDs) for batch processing.
Workload 2 was confined to a single machine family in a single static zone, and Workload 3 ran 24/7 mission-critical services that could not tolerate preemption.
Using on-demand instances when Spot VMs are viable leaves substantial cost savings unrealized.
This configuration commits spend-based CUDs to cover ephemeral batch jobs while shifting production microservices entirely to Spot VMs.
The microservices were entirely non-critical test environments and the batch processing pipeline operated at a constant 100% capacity 24 hours a day on standard instances.
Flexible CUDs cannot offset Spot instance pricing, creating double financial inefficiency.
This multi-tiered pricing architecture aligns specific Google Cloud commitment models and execution tiers to the distinct predictability, geographical distribution, and fault-tolerance characteristics of each workload.
us-central1) and machine series (N2).This architecture pairs the highest discount tier available for fixed, long-running regional workloads (resource-based CUDs) with broad elasticity for distributed architectures (flexible CUDs) and hyper-discounted ephemeral capacity (Spot VMs).
This approach relies strictly on passive Sustained Use Discounts (SUDs) without making contractual commitments, while attaching Compute Engine hardware reservations to the batch processing cluster.
The enterprise had unpredictable future infrastructure plans, refused any multi-month financial commitments, and required guaranteed capacity for critical batch processing that could not tolerate delays.
Reservations guarantee capacity but increase costs if applied to non-continuous workloads.
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