DOP-C02 Practice Question 86: Secrets Manager Multi Region Replication
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 9 · question 6 of 10
An application currently runs only in us-east-1 and retrieves its database credentials from AWS Secrets Manager. The company is building a warm standby of the application in us-west-2 for disaster recovery and wants the standby to be able to read the same secret values locally, without the standby application making cross-Region calls to Secrets Manager during a failover, and without building custom synchronization logic. Updates made to the primary secret, including rotations, must propagate automatically. What should the team configure?
Show answer and explanation
Answer:
Secrets Manager's built-in multi-Region secret feature creates a read replica of a secret in one or more specified Regions; any update to the primary, including a value change from automatic rotation, is propagated to the replicas automatically, and applications in the replica Region read the secret locally with no cross-Region call and no custom sync code.
B is wrong because it requires building and maintaining custom synchronization logic, which the requirement explicitly rules out, and introduces sync lag and drift risk. C is wrong for the same reason, manual updates in two places are exactly the operational burden multi-Region replication removes, and Parameter Store SecureString has no native cross-Region replication of this kind. D is wrong because AWS Backup protects against accidental deletion or corruption on a periodic schedule, it is not designed for near-real-time propagation of secret updates for active-standby failover.
Reference: Replicate secrets across Regions