An enterprise organization is architecting a multi-tier application environment on Google Cloud with the following workload profiles: Transactional Ordering Service: A core, mission-critical service that processes financial transactions in real time, requiring strict high availability (HA) and minimal Recovery Time Objective (RTO). Nightly Image Processing: A scalable batch-processing pipeline that performs stateless image transformation tasks where progress can be regularly checkpointed and resume upon restart. 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?

Deploy the transactional ordering service on standard VM instances and run the nightly image processing pipeline on Spot VM instances with checkpointing enabled: ### What standard and Spot VMs are **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. ### How it meets the workload requirements - **Mission-Critical Transactional Ordering Service**: Running this service on **standard VM instances** (within a regional Managed Instance Group) satisfies the high-availability and minimal **RTO** requirements, as standard instances are not subject to compute preemption and guarantee service continuity for latency-sensitive transactions. - **Stateless Nightly Image Processing**: Running this pipeline on **Spot VM instances** drastically reduces infrastructure costs. Because the workload is **fault-tolerant**, stateless, and implements regular **checkpointing**, tasks can tolerate abrupt terminations and resume from the latest checkpoint when replacement instances are provisioned. ### Key advantages and capabilities - **Significant Cost Optimization**: Exploits steep price discounts for high-throughput batch and processing jobs without paying standard baseline costs. - **Resilience through Checkpointing**: Ensures minimal lost computation during preemption events by saving state externally. - **SLA Guarantees for Core Services**: Protects revenue-generating customer transactions from unexpected interruptions. - **Dynamic Scaling**: Managed Instance Groups (MIGs) can automatically replace preempted Spot VMs when resource capacity becomes available again. ### Why this is optimal 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.

StudyCerts

Standard Vs Spot Vms Workload Suitability | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Standard Vs Spot Vms Workload Suitability

Section: Compute volatility configuration (spot vs. standard)

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise organization is architecting a multi-tier application environment on Google Cloud with the following workload profiles:

Transactional Ordering Service: A core, mission-critical service that processes financial transactions in real time, requiring strict high availability (HA) and minimal Recovery Time Objective (RTO).
Nightly Image Processing: A scalable batch-processing pipeline that performs stateless image transformation tasks where progress can be regularly checkpointed and resume upon restart.

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?

Deploy the transactional ordering service on standard VM instances and run the nightly image processing pipeline on Spot VM instances with checkpointing enabled

Deploy both the transactional ordering service and the nightly image processing pipeline on standard VM instances with regional Persistent Disks

Deploy both the transactional ordering service and the nightly image processing pipeline entirely on Spot VM instances across multiple zones to maximize cost savings

Deploy the transactional ordering service on Spot VM instances with automated restart scripts and provision the nightly image processing pipeline on standard VM instances

Professional Cloud Architect

Standard Vs Spot Vms Workload Suitability

Related questions