An enterprise SaaS provider is evaluating Compute Engine resource configurations for two new background processing workloads:
1. Workload Alpha: An event-driven image rendering worker pool that processes decoupled queue messages. Each task takes 3 to 10 seconds to process, operates statelessly, and can tolerate immediate instance termination without data loss.
2. Workload Beta: A stateful, high-throughput in-memory database cache node that requires 128 GB of RAM, runs continuously 24/7, and cannot tolerate unexpected interruptions.
Which TWO cost-effective and architecturally suitable provisioning strategies should the lead cloud architect select for these Compute Engine workloads? (Select TWO.)
- Provision Spot Virtual Machines for Workload Alpha to take advantage of significant compute discounts while maintaining fault tolerance via queue re-processing.Answer
- Purchase a 1-year or 3-year Committed Use Discount (CUD) for the memory-optimized or custom machine family resources required by Workload Beta.Answer
- CDeploy Workload Beta on Spot Virtual Machines with attached local SSDs to lower memory hosting costs while maintaining rapid I/O recovery.
- DRely solely on automatic Sustained Use Discounts (SUDs) for Workload Beta instead of committing to long-term commitments to achieve maximum possible savings.
Answer
The architect should provision Spot Virtual Machines for the stateless queue processing workload (Workload Alpha) and purchase a 1-year or 3-year Committed Use Discount for the continuous, stateful memory workload (Workload Beta).
For stateless, fault-tolerant queue workers (Workload Alpha), Spot VMs drastically cut compute costs without risking application failure. For 24/7 stateful, high-memory database workloads (Workload Beta), Committed Use Discounts offer the highest cost reduction while ensuring standard VM stability.
Step-by-Step Solution
Key Concept
Compute Engine Workload Planning: Spot VM Suitability vs Committed Use Discounts