What's changed: Created DP-420 Chapter 5, completing the textbook (Domain 5: monitoring (Normalized RU Consumption hot-partition detection/status codes 429-449-503-408/server-side latency/Azure Monitor alerts/resource logs diagnostic settings→Log Analytics/cross-partition monitoring); backup and restore (periodic vs continuous/PITR/restore point/restore into a new account); security, data movement, DevOps (service-managed vs CMK Key Vault/Private Endpoint-IP-VNet/control-plane Azure RBAC-data-plane Entra ID RBAC/Always Encrypted/CORS/data movement ADF-Spark-Kafka-Stream Analytics-IoT Hub/DevOps declarative ARM-imperative PowerShell-CLI standard↔autoscale-failover)).
5.2Backup and restore
Understand choosing periodic vs continuous backup, configuring periodic backup, continuous backup and point-in-time restore (PITR), locating a restore point, and restoring a database/container.
Cosmos DB auto-backs up data, but there are two modes differing in restore flexibility and operations. Choosing the mode that fits requirements is a design point.
5.2.1Periodic and continuous backup
Periodic backup takes snapshots at intervals stored in geo-redundant storage worldwide (configure count/interval; restore is via Microsoft support into a new account). Continuous backup enables point-in-time restore (PITR), letting you self-service restore to any point in time (to the second) within the retention window—strong against accidental deletes/updates. For "roll back to a specific time / restore quickly yourself," use continuous backup + PITR.
5.2.2Restore points and restore operations
With continuous backup, locate the timestamp just before the mistake (the restore point) and restore the database or container into a new account at that state (you restore into a new account and switch over, not an in-place overwrite). Design the restore granularity/target (account/DB/container) and retention period (varies by mode/tier) to requirements.
Cues: "self-service restore to any point in time / undo accidental delete" = continuous backup + PITR. "interval snapshots, geo-redundant, restore via support" = periodic backup. Restore goes into a new account. Restore point = the timestamp just before the mistake.
Watch the mix-ups: (1) Periodic (snapshots, coarse, via support) vs continuous (any point, self-service). (2) Restore goes into a new account—not an in-place overwrite. (3) Continuous backup can cost more to operate than periodic—choose by requirement. (4) Retention periods differ by mode/tier.
5.2.3Section summary
- Periodic = interval snapshots/geo-redundant/restore via support; continuous = PITR self-service restore to any point
- Restore into a new account, returning the DB/container to the restore-point (pre-mistake) state
- Retention, granularity, and cost vary by mode/tier—choose by requirement
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. You want self-service restore to any point in time within retention to recover from accidental delete/update. Best backup mode?
Q2. Which backup mode takes interval snapshots in geo-redundant storage and restores via Microsoft support?
Q3. Which is correct about the Cosmos DB restore target?
Q4. With continuous backup, what should you first identify to roll back?
Q5. Which is a correct basis for choosing periodic vs continuous backup?
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.