An organization is planning its Google Compute Engine infrastructure for two new enterprise services with distinct operational profiles:
1. Workload 1: An offline rendering and data processing pipeline that runs daily. The application is stateless, fault-tolerant, and designed to checkpoint progress so it can be safely paused and resumed.
2. Workload 2: A core relational database instance requiring heavy RAM usage per vCPU that must run continuously 24/7 with zero unannounced downtime.
Which TWO architectural decisions correctly align with Google Cloud resource planning and pricing best practices for these workloads? (Select TWO.)
- Provision Spot VMs for Workload 1 to minimize compute overhead for fault-tolerant batch jobs.Cevap
- Provision a memory-optimized machine family instance combined with a 1-year or 3-year Committed Use Discount (CUD) for Workload 2.Cevap
- CProvision Spot VMs for Workload 2 to eliminate baseline instance infrastructure costs for persistent database hosting.
- DRely primarily on default Sustained Use Discounts (SUDs) rather than Committed Use Discounts to maximize savings on predictable 3-year production database workloads.
Cevap
The two correct architectural decisions are: using Spot VMs for the stateless, fault-tolerant offline data processing pipeline (Workload 1), and provisioning a memory-optimized machine family with Committed Use Discounts for the continuous 24/7 relational database (Workload 2).
Deploying Spot VMs for fault-tolerant, checkpoint-enabled batch jobs takes advantage of extreme cost discounts without risking job completion. For steady-state 24/7 databases needing high RAM, selecting a memory-optimized machine family with Committed Use Discounts maximizes performance while securing the deepest contractual cost reduction.
Adım Adım Çözüm
Anahtar Kavram
Selecting machine families and pricing models based on fault tolerance, memory density, and uptime predictability.
Tahmini Süre:2m 0s