Question

Difficulty: MediumMulti-AZ, Multi-Region Architectures and Disaster Recovery (DR)

A financial services company hosts an invoice processing platform in the us-west-2 Region. The application architecture consists of Amazon EC2 instances behind an Application Load Balancer (ALB), an Amazon RDS for PostgreSQL database for invoice metadata, and an Amazon S3 bucket for storing scanned invoice documents. The company needs to design a disaster recovery (DR) solution in the us-east-1 Region. The solution must support a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 2 hours while keeping ongoing standby costs as low as possible. Which combination of database and storage configurations will meet these requirements? (Select TWO.)

  1. Configure Amazon S3 Cross-Region Replication (CRR) to asynchronously copy invoice documents from the us-west-2 bucket to a destination bucket in us-east-1.Answer
  2. Create an Amazon RDS for PostgreSQL cross-region read replica in us-east-1 to serve as the standby database.Answer
  3. C
    Set up an Amazon S3 Lifecycle rule on the us-west-2 bucket to transition objects directly to an Amazon S3 Glacier Flexible Retrieval vault in us-east-1.
  4. D
    Create a daily AWS Backup plan to copy database snapshots to us-east-1, and restore the snapshots to a new RDS instance when a failover is initiated.
  5. E
    Configure Amazon Route 53 with a latency-based routing policy to automatically promote the replica and redirect database write traffic to us-east-1 during an outage.

Answer

Configure Amazon S3 Cross-Region Replication (CRR) to asynchronously copy invoice documents from the us-west-2 bucket to a destination bucket in us-east-1, and create an Amazon RDS for PostgreSQL cross-region read replica in us-east-1 to serve as the standby database.
To meet a 15-minute RPO and a 2-hour RTO cost-effectively, a Pilot Light DR pattern is appropriate. The correct configurations include using Amazon S3 Cross-Region Replication (CRR) to copy scanned invoices from us-west-2 to us-east-1, ensuring that newly uploaded documents are replicated asynchronously within minutes. For the database tier, creating an Amazon RDS for PostgreSQL cross-region read replica ensures the metadata is continuously replicated asynchronously with low lag (satisfying the 15-minute RPO) and can be promoted to primary status within minutes during a failover event (satisfying the 2-hour RTO).

Step-by-Step Solution

1
Analyze the storage replication requirements for the RPO of 15 minutes.
Identify that Amazon S3 Cross-Region Replication (CRR) provides automated, asynchronous replication of new objects to another region, satisfying the RPO for the document storage.
S3 Lifecycle rules alone cannot copy data across regions directly into S3 Glacier without replication, and Glacier retrieval times would violate the RTO.
2
Analyze the database replication requirements for the RPO of 15 minutes and RTO of 2 hours.
Determine that an Amazon RDS for PostgreSQL cross-region read replica keeps the standby database updated asynchronously with minimal lag, satisfying the 15-minute RPO, and can be promoted to a standalone primary database quickly, satisfying the 2-hour RTO.
Daily database snapshots via AWS Backup only guarantee a 24-hour RPO and require a lengthy restore process, which violates the 15-minute RPO and 2-hour RTO requirements.
3
Evaluate the routing and failover automation options.
Discard options attempting to use Route 53 latency routing to automate RDS promotion, as Route 53 is a DNS service and cannot perform database-level operations or promote read replicas.
RDS read replicas require explicit promotion to become writeable, and Route 53 does not manage database failover.

Key Concept

Designing a pilot light multi-region disaster recovery architecture utilizing Amazon S3 Cross-Region Replication and Amazon RDS cross-region read replicas to meet stringent RTO and RPO constraints cost-effectively.
Estimated Time:2m 0s
Rate this question