An enterprise financial institution is designing the Compute Engine infrastructure for two core workloads:
1. A mission-critical, stateful transaction processing service that operates continuously 24/7 with a predictable high-memory footprint and zero tolerance for unexpected instance terminations.
2. An overnight Monte Carlo risk simulation batch engine that executes thousands of independent, stateless calculation tasks with native checkpointing.
Which TWO provisioning and cost-optimization strategies should you recommend to minimize operational costs while satisfying all SLA requirements? (Select TWO answers.)
- Purchase 3-year Committed Use Discounts (CUDs) for the baseline compute capacity required by the stateful transaction processing service.Answer
- Provision the Monte Carlo risk simulation batch engine using Spot Virtual Machines across multiple availability zones.Answer
- CProvision the stateful transaction processing service on Spot VMs configured with custom memory-optimized machine types.
- DRely on automatic Sustained Use Discounts (SUDs) on standard compute instances for the Monte Carlo risk simulation batch engine rather than using Spot VMs.
Answer
The optimal architecture combines purchasing 3-year Committed Use Discounts (CUDs) for the 24/7 stateful transaction processing service and provisioning the Monte Carlo risk simulation batch engine using Spot Virtual Machines.
Purchasing Committed Use Discounts (CUDs) provides deep savings for baseline 24/7 stateful workloads without risking node preemption, while Spot VMs provide maximum cost reduction (60-91%) for fault-tolerant overnight batch jobs that support native checkpointing.
Step-by-Step Solution
Key Concept
Selecting Compute Engine purchasing and provisioning models based on workload persistence and availability SLAs