Ensure the Successful Operation of a Cloud Solution
What this domain really tests
Day-two operations: monitoring and logging (Cloud Monitoring, Cloud Logging), alerting, autoscaling, backups, and cost control. Expect questions on how to detect, diagnose, and remediate operational issues.
Concepts to master
- Observability: metrics via Cloud Monitoring, logs via Cloud Logging; log sinks route logs to destinations like Cloud Storage or BigQuery.
- Alerting: alerting policies on metric thresholds; uptime checks for availability.
- Autoscaling: managed instance groups scale on CPU/utilization or custom metrics; Cloud Run scales on concurrency/requests.
- Backups and snapshots: persistent disk snapshots, Cloud SQL automated backups and point-in-time recovery.
- Cost: budgets with alerts, committed use discounts, and rightsizing.
Traps
- Confusing logs (events) with metrics (numeric time series) - alerts fire on metrics, not raw logs.
- Assuming snapshots are incremental per-disk and region-scoped; cross-region copies need explicit configuration.
- Forgetting that a log sink needs a destination and a writer identity with permissions.
- Believing budgets stop spending - they only alert.
Rule of thumb
For "detect and notify," use an alerting policy on a metric with a notification channel; for "diagnose after the fact," query logs via Logging or a sink to BigQuery.
Worked example
To alert when a VM's CPU exceeds 80% for 5 minutes: create an alerting policy on the CPU utilization metric with a 5-minute condition and a notification channel.