A financial analytics firm is planning the compute deployment on Google Compute Engine for two distinct workloads:
1. Workload 1: A stateless Monte Carlo risk simulation engine that runs overnight batch jobs. The application is highly fault-tolerant and saves state checkpoints every 5 minutes.
2. Workload 2: A core customer backend service operating continuous 24/7 traffic with precise memory demands requiring 8 vCPUs and 52 GB of RAM to prevent memory spilling.
Which TWO machine type selection and provisioning strategies should the Cloud Engineer implement to optimize cost and performance for these workloads? (Select TWO answers.)
- Provision Workload 1 using Spot Virtual Machines (Spot VMs) to obtain deep discounts for fault-tolerant, interruptible batch processing.Cevap
- Configure Workload 2 on an N2 custom machine type with 8 vCPUs and 52 GB RAM, and purchase a 1-year or 3-year Committed Use Discount (CUD) for predictable resource usage.Cevap
- CProvision Workload 2 on Spot VMs within an auto-healing Managed Instance Group (MIG) to maximize cost savings while relying on auto-healing for 24/7 availability.
- DRely solely on automatic Sustained Use Discounts (SUDs) instead of Committed Use Discounts (CUDs) for Workload 2 to obtain the maximum possible financial discount for continuous execution.
Cevap
The Cloud Engineer should provision Workload 1 using Spot VMs for cost-effective batch execution, and deploy Workload 2 on a custom N2 machine type (8 vCPUs, 52 GB RAM) backed by Committed Use Discounts (CUDs).
Stateless, checkpointed batch jobs are perfectly suited for Spot VMs because they can tolerate interruptions in exchange for massive price reductions. Meanwhile, 24/7 production workloads with precise CPU-to-memory needs benefit from custom machine types to avoid over-provisioning, paired with Committed Use Discounts to secure the maximum possible savings on predictable baseline usage.
Adım Adım Çözüm
Anahtar Kavram
Compute Engine Machine Type Selection and Pricing Model Optimization