A retail analytics company is planning its Google Compute Engine infrastructure for two distinct application services:
1. An online, memory-intensive analytics engine requiring large RAM allocations, predictable baseline CPU performance, and continuous 24/7 availability over a multi-year timeframe.
2. A stateless data ingestion pipeline that processes incoming messages asynchronously from a queue and can recover gracefully if individual instances are terminated unexpectedly.
Which TWO deployment strategies should the cloud engineer select to meet operational requirements while optimizing cost efficiency? (Select 2 answers.)
- Provision High-Memory or Memory-Optimized VM instances coupled with Committed Use Discounts (CUDs) for the 24/7 analytics engine.Cevap
- Provision Spot Virtual Machines for the stateless data ingestion pipeline to minimize compute costs.Cevap
- CProvision Spot Virtual Machines for the 24/7 analytics engine to achieve maximum compute discount rates.
- DDeploy the memory-intensive analytics engine to Cloud Functions to automatically eliminate VM infrastructure management.
Cevap
The cloud engineer should select provisioning High-Memory or Memory-Optimized VM instances with Committed Use Discounts (CUDs) for the steady-state analytics engine, and provisioning Spot Virtual Machines for the fault-tolerant data ingestion pipeline.
Provisioning High-Memory or Memory-Optimized instances with Committed Use Discounts fulfills the high-RAM 24/7 availability requirements of the analytics engine while securing deep steady-state discounts. Provisioning Spot VMs for the stateless data ingestion pipeline leverages maximum discounts for a workload that easily handles sudden instance terminations.
Adım Adım Çözüm
Anahtar Kavram
Matching Compute Engine machine families and purchasing models (Spot VMs vs. CUDs) to workload memory demands and fault tolerance.