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 organization is architecting a multi-tier application environment on Google Cloud with the following workload profiles:
You need to choose the appropriate Compute Engine VM provisioning model for each workload to optimize cost efficiency while meeting operational availability requirements.
Which compute configuration should you recommend?
This configuration provisions both the transactional service and the batch processing pipeline on fully dedicated standard VM instances backed by regional Persistent Disks.
Budget and cost optimization were not constraints, and the batch processing workload had strict data replication SLAs that prohibited any task interruption or replay.
This configuration inverts the recommended workload provisioning model by hosting the mission-critical transactional service on volatile Spot VM instances and the interruptible batch processing pipeline on standard VM instances.
The image processing pipeline had strict, immovable delivery deadlines with zero tolerance for re-computation, while the transactional service was an internal, non-urgent development tool.
This approach attempts to use Spot VM instances across all application tiers, relying on multi-zone distribution to protect the core transactional service from downtime while minimizing compute costs.
All workloads in the scenario were completely non-critical, fully interruptible, and designed without strict RTO or uptime guarantees.
Standard VM instances provide predictable availability and persistent execution without the risk of voluntary preemption by Compute Engine. In contrast, Spot VM instances are excess compute capacity offered at a substantial discount (typically 60-91% savings compared to standard provisioning) but can be preemptively stopped or reclaimed by Compute Engine at any time when capacity is needed elsewhere.

Aligning standard instances with transactional, high-uptime services and Spot instances with interruptible, checkpointed batch jobs strictly matches the operational characteristics and economic trade-offs recommended for cloud workload resilience.
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