What's changed: Created Professional Cloud Architect Chapter 4 (Domain 2 "Manage and provision" part 2: compute/container config = machine types/MIG/templates, GKE Autopilot/Standard/node pools, Cloud Run revisions/traffic splitting, Spot VMs/CUDs/SUDs; data config and ops/monitoring = Cloud SQL HA/read replicas/Spanner, Cloud Storage lifecycle/uniform access, Cloud Monitoring/Logging/Trace, SLOs/error budgets).
4.1Configuring compute and containers
Understand Compute Engine machine types/MIGs/instance templates, GKE Autopilot/Standard with node pools/workloads, Cloud Run revisions and traffic splitting, and cost-efficient configuration with Spot VMs and committed-use discounts.
Configure the chosen compute correctly for the requirements, balancing performance, scale, and cost via each service feature.
4.1.1Compute Engine and GKE
In Compute Engine, pick a fitting machine type (general/compute-optimized/memory-optimized) and scale/self-heal identical VMs in a MIG from an instance template. In GKE, choose Autopilot (Google manages nodes) or Standard (you configure nodes), mix machine configs via node pools, and run workloads (Deployments/Services). Map "let Google run nodes too = GKE Autopilot" and "fine node control = GKE Standard."
4.1.2Cloud Run and cost efficiency
In Cloud Run, each deploy creates a revision, and traffic splitting enables gradual rollout (canary) and rollback. For cost efficiency, combine Spot VMs (deep discount) for interruptible batch, committed-use discounts (CUDs) for steady workloads, and the automatic sustained-use discounts (SUDs) for long uninterrupted use. Map "interruptible = deep discount Spot VMs" and "commit 1–3 years = CUDs."
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.