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.2Configuring data and operating/monitoring
Understand configuring managed databases (Cloud SQL HA and read replicas, Spanner scaling), Cloud Storage lifecycle and access control, and operations via Cloud Monitoring, Cloud Logging, and alerts with SLO-based reliability management.
Data-tier configuration and post-launch operations/monitoring determine system reliability. Design managed-service availability features and observability.
4.2.1Configuring managed databases
In Cloud SQL, raise availability with an HA configuration (auto-failover to a standby in another zone) and distribute read load via read replicas. To scale globally, Spanner scales by adding nodes. For storage, Cloud Storage lifecycle rules move/delete old data to cheaper classes, and uniform bucket-level access keeps permissions simple and safe. Map "scale reads = read replicas" and "DB that tolerates zone failure = Cloud SQL HA."
4.2.2Operations, monitoring, and reliability
After launch, observe with Cloud Monitoring (metrics, dashboards, alerts) and Cloud Logging (log collection/search). Manage reliability via SLOs and error budgets, throttling releases when nearing the limit. Use Cloud Trace (distributed tracing) to track issues. Map "metric monitoring/alerts = Cloud Monitoring," "log investigation = Cloud Logging," and "reliability targets = SLOs/error budgets."
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.