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.
A financial analytics company runs large-scale, fault-tolerant nightly batch processing workloads on Google Compute Engine. The processing application can gracefully checkpoint progress, handle node terminations, and run on various CPU architectures and sizes.
Management requires a compute architecture that minimizes infrastructure costs using Spot VMs while mitigating the risk of batch processing delays caused by high localized preemption rates or capacity shortages for a single machine type.
Which configuration should the cloud architect recommend?
This approach restricts a Managed Instance Group (MIG) to a single Google Cloud zone, fixes the deployment to a single machine type template, and disables the auto-repair / VM repair mechanism to avoid automated recreation of preempted instances.
The workload were an ephemeral test run that must terminate entirely upon the first failure and could not tolerate any automated retries or multi-zone routing.
Instance flexibility in a regional Managed Instance Group (MIG) allows the group to provision virtual machines from a list of multiple configured machine types rather than being constrained to a single VM size or family. When applied to Spot VMs, the MIG intelligently selects from the specified machine types and zones based on real-time resource availability and historical stability.

Using Spot VMs with instance flexibility provides the best balance of aggressive cost reduction and workload reliability for batch processing. Because the application can run across different CPU types and handles terminations gracefully, opening the resource pool across multiple machine types prevents job stalls caused by localized Spot preemption spikes.
This approach deploys an Apache Spark or Hadoop cluster via Google Cloud Dataproc and configures both the primary master and primary worker nodes as Spot VMs instead of standard, non-preemptible instances.
Dataproc supported running master coordinators on ephemeral Spot nodes with state preservation, or if the architecture specifically designated Spot VMs exclusively for secondary processing workers.
This approach deploys non-preemptible, standard Compute Engine virtual machines within a regional MIG and covers the compute baseline with Committed Use Discounts (CUDs) across a 1-year contract period for a specific machine series.
The application were a continuous, non-fault-tolerant, 24/7 production service that cannot tolerate node preemptions or interruptions.
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