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 analytics organization is designing a compute architecture on Google Cloud to process incoming data batches. The data processing pipeline has the following requirements:
Which compute provisioning and optimization strategy should you implement?
This architecture combines Compute Engine Spot VMs, custom machine types, and stateless Managed Instance Group (MIG) autoscaling to build a highly elastic, cost-optimized batch data processing pipeline.
n2-standard-8 (8 vCPUs, 32 GB RAM) and eliminating waste.This strategy directly addresses all workload constraints: it eliminates over-provisioning through custom sizing, lowers unit cost via Spot instances, and ensures resources match fluctuating demand dynamically through stateless autoscaling.
Future reservations in calendar mode allow organizations to reserve specific compute capacity (such as GPU or compute-optimized instances) for a designated delivery date and duration (up to 90 days). Committed Use Discounts (CUDs) provide discounted hourly rates in exchange for committing to a continuous level of resource usage over a 1-year or 3-year term.
n2-standard-8 instances allocate 8 vCPUs and 32 GB of RAM, which wastes 2 vCPUs and 10 GB of RAM per worker.The workload were non-interruptible, mission-critical, ran continuously 24/7 with a predictable baseline, and required guaranteed capacity availability.
Reservations provide capacity assurance rather than dynamic elasticity, making them suboptimal for fluctuating, fault-tolerant batch processing.
On-demand standard VMs run on the standard Compute Engine provisioning model without preemption risks at full pay-as-you-go pricing. Autohealing health checks monitor application-level health metrics and automatically recreate or repair unhealthy virtual machines.
n2-standard-8 instances provide 8 vCPUs and 32 GB RAM, resulting in unneeded overhead compared to configuring a custom 6 vCPU / 22 GB RAM machine type.The workload required steady-state capacity for an application that cannot tolerate preemptions and needed automated repair for crashed processes.
While autohealing is a valuable reliability feature, it does not replace autoscaling for managing fluctuating demand and cost optimization.
Stateful Managed Instance Groups (MIGs) preserve the unique state of each VM instance (such as attached persistent disks, IP addresses, and instance names) across VM restarts, recreations, and updates. Schedule-based autoscaling adjusts group capacity based on predefined recurring calendar schedules.
e2-standard-8 instances provisions 8 vCPUs and 32 GB of RAM, which exceeds the required 6 vCPUs and 22 GB, causing unnecessary compute and memory expenditure.The workload required preserving unique instance IDs, hostnames, and persistent disk state across restarts for fixed, scheduled operations.
For stateless processing pipelines, deploying stateful configurations prevents automatic scaling and increases maintenance complexity.
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