An application stores its static assets in a source Amazon S3 bucket and uses an Amazon RDS for MySQL DB instance. A SysOps Administrator must configure automatic replication of the static assets to a backup S3 bucket in a different Region. The database must also support automatic failover to another Availability Zone without requiring any manual updates to the application configuration. Which configuration satisfies these requirements?
- AEnable versioning on both the source and backup S3 buckets, configure S3 Cross-Region Replication (CRR), and configure a Route 53 DNS CNAME record at the zone apex pointing to the RDS instance endpoint for automatic failover.
- BConfigure S3 Cross-Region Replication (CRR) from the source S3 bucket to the backup S3 bucket without enabling bucket versioning, and configure the RDS DB instance as a Multi-AZ deployment.
- Enable versioning on both the source and backup S3 buckets, configure S3 Cross-Region Replication (CRR), and configure the RDS DB instance as a Multi-AZ deployment.Answer
- DEnable versioning on both the source and backup S3 buckets, configure S3 Cross-Region Replication (CRR), and create a Read Replica of the RDS instance in a different Availability Zone to act as the automatic failover target.
Answer
To meet the requirements, enable versioning on both the source and backup S3 buckets, configure S3 Cross-Region Replication (CRR), and configure the RDS DB instance as a Multi-AZ deployment.
The correct configuration enables S3 Versioning on both the source and backup buckets, which is a mandatory prerequisite for S3 Cross-Region Replication (CRR). Additionally, configuring RDS Multi-AZ ensures a synchronous standby instance is available in another Availability Zone, and RDS automatically updates the DNS record to point to this standby during a failover without requiring any endpoint updates in the application.
Step-by-Step Solution
Key Concept
Integrating S3 Cross-Region Replication (which requires versioning) with RDS Multi-AZ deployment (which provides automatic failover without endpoint changes).