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
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.