An online video platform is designing its Google Compute Engine compute infrastructure for two distinct backend components:
1. Media Transcoding Fleet: A fault-tolerant, stateless batch processing workload that picks up jobs from a queue and can resume interrupted tasks without data corruption.
2. Primary User Database: A continuous, high-availability relational database running 24/7 with highly predictable vCPU and memory utilization.
Which TWO deployment strategies should you select to minimize compute costs while meeting the operational availability requirements of both workloads?
- Provision Spot Virtual Machines (VMs) for the Media Transcoding Fleet.Answer
- Purchase Committed Use Discounts (CUDs) for the Primary User Database compute capacity.Answer
- CDeploy the Primary User Database on Spot VMs with auto-restart enabled to reduce licensing and infrastructure costs.
- DApply automatic Sustained Use Discounts (SUDs) on top of Committed Use Discounts for the database instances to achieve additive savings.
Answer
Select Spot VMs for the stateless Media Transcoding Fleet to leverage steep pricing discounts for fault-tolerant jobs, and purchase Committed Use Discounts (CUDs) for the Primary User Database to secure cost savings for steady-state 24/7 compute usage.
The correct strategy leverages Spot Virtual Machines for the stateless media transcoding batch fleet because the job pipeline can easily recover from instance preemptions. Concurrently, purchasing Committed Use Discounts for the database guarantees lower pricing for steady, uninterrupted 24/7 compute consumption.
Step-by-Step Solution
Key Concept
Selecting Compute Engine Purchasing Models Based on Workload Preemptibility and Usage Predictability