What's changed: Created Professional Cloud Database Engineer Chapter 2 (Domain 2 "Manage": access management and monitoring/troubleshooting = IAM/DB users, slow queries/locking/missing indexes, vitals/audit logs/Cloud Monitoring, quotas/contention/alerts; backup/recovery and optimization/automation = automatic scheduled backups/PITR/export/retention, scale up-out/read replicas/query optimization, index rebuilds/exports/upgrades/SLA-SLO automation).
2.2Backup/recovery, cost/performance optimization, and automation
Understand backup/recovery (automatic scheduled backups, export/import, RTO/RPO/PITR), data retention, optimizing cost/performance via scale up/out and replication strategies, query optimization, and automating common database tasks (index rebuilds, exports, upgrades, SLA/SLO monitoring).
Operate databases with protection (backup/recovery), efficiency (cost/performance), and automation of repetitive tasks.
2.2.1Backup and recovery
Configure automatic scheduled backups per requirements (RTO/RPO) and provide PITR to roll back to a point in time. Set up data export/import (migration, analytics, archival). Manage data retention by retention period and regulation. Map "reliable periodic backups = automatic scheduled backups" and "to a point in time = PITR."
2.2.2Cost/performance optimization and automation
Choose vertical scale-up and horizontal scale-out (read replicas distribute reads) by requirements and define a replication strategy. Improve cost/performance with query optimization (indexes, plans). Automate repetitive tasks: index rebuilds, scheduled exports, upgrades of managed DBs, and SLA/SLO monitoring. Map "scale reads = read replicas" and "routine tasks = automation."
Common: requirement → means. E.g., "reliable periodic backups" = automatic scheduled backups; "recover to a point in time" = PITR; "distribute read load" = read replicas (scale-out); "make queries fast/cheap" = index/plan optimization; "automate routine tasks" = automate index rebuilds/exports/upgrades; "monitor SLA/SLO" = SLO monitoring.
Watch the mix-ups: (1) Do not confuse scale-up (vertical) and scale-out (horizontal, read replicas). (2) Read replicas are for read scaling, distinct from the HA standby. (3) Backups need recovery testing, not just capture.
2.2.3Section summary
- Backup/recovery = automatic scheduled backups + PITR; retention per regulation
- Optimize = scale up/out, read replicas, query/index optimization
- Automate = index rebuilds/exports/upgrades/SLA-SLO monitoring
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. To reliably take periodic backups per requirements, which is best?
Q2. To distribute read load and improve performance, which is best?
Q3. To recover a database to a specific point in time, which feature?
Q4. To streamline routine tasks like index rebuilds, scheduled exports, and upgrades, which best fits?
Q5. Which correctly contrasts scale-up and scale-out?
Q6. To improve query cost and performance, which is the most direct action?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.