An organization is designing its Compute Engine architecture for a new IoT telemetry processing system. The architecture consists of two primary components:
1. A stateful PostgreSQL database instance that requires exactly 6 vCPUs and 45 GB of memory, running continuously 24/7 without interruption.
2. A stateless worker fleet that processes incoming message batches in parallel, where individual task interruptions are acceptable and automatically retried by an upstream queue.
Which TWO deployment strategies should the cloud engineer choose to meet these requirements while optimizing compute costs? (Select TWO.)
- Provision a custom machine type with 6 vCPUs and 45 GB of RAM for the stateful database instance.Answer
- Deploy Spot VM instances for the stateless batch processing worker fleet.Answer
- CProvision Spot VM instances for the stateful PostgreSQL database to maximize overall infrastructure savings.
- DRefactor the stateful PostgreSQL database to execute inside event-driven Cloud Functions snippets.
Answer
The cloud engineer should provision a custom machine type (6 vCPUs, 45 GB memory) for the persistent PostgreSQL database and deploy Spot VMs for the fault-tolerant, stateless batch worker fleet.
For the stateful database instance requiring a non-standard 6 vCPU / 45 GB RAM ratio, creating a custom machine type ensures exact resource allocation without paying for unused capacity in larger predefined sizes. For the stateless batch worker fleet, using Spot VMs provides maximum cost efficiency because the workload is designed to tolerate instance preemption and task retries.
Step-by-Step Solution
Key Concept
Selecting optimal Compute Engine machine types and instance lifecycles based on workload statefulness and custom resource ratios.