Vital records require a documented RPO that automated database protection must meet across Regions. Which approach best fits?
Select an answer to reveal the explanation.
Short Explanation
Vital records care about how much history you can lose, not just that a box exists. Cross-Region RDS replicas and backups keep the RPO promise when a whole Region goes dark.
Full Explanation
Vital records demand a documented RPO that automated database protection must meet across Regions, not merely within one Availability Zone. Configuring automated cross-Region RDS replication and backup aligns recovery points so restored or promoted databases retain recent commits within policy for birth, death, and related records. Infrequent local snapshots without cross-Region copy leave Region events able to exceed RPO. Backups only on the same instance's ephemeral disk offer almost no durability. Disabling automated backups to save storage contradicts vital-records stewardship. Exam caveat: replication lag and backup frequency jointly determine achievable RPO—publish measured lag, not just diagram intent. Operational check: review automated backup retention and cross-Region replica or copy status, simulate promotion or restore, and compare the recovered timestamp against the documented RPO. In municipal cloud governance, record the owners, success metrics, and rollback or restore contacts beside this technical choice so the next incident, budget review, or audit does not rediscover the decision from scratch under time pressure. In municipal cloud governance, record the owners, success metrics, and rollback or restore contacts beside this technical choice so the next incident, budget review, or audit does not rediscover the decision from scratch under time pressure.