Examkin

Soru

Zorluk: OrtaEnhancing Reliability and Disaster Recovery

A company operates a critical telemetry analytics platform across multiple AWS accounts. The primary ingestion workload runs in a VPC in the us-west-2 Region, containing Amazon EKS clusters that write to an Amazon Aurora PostgreSQL DB cluster. The database contains proprietary configurations encrypted with an AWS KMS customer managed key. The disaster recovery (DR) target is the us-east-1 Region. The company needs to configure a DR solution that meets an RPO of less than 1 minute and an RTO of less than 15 minutes. Additionally, internal EKS microservices in both regions must resolve the internal database endpoint using a shared Route 53 Private Hosted Zone (PHZ) named corp.internal. Which TWO actions should the Solutions Architect take to meet these requirements? (Select TWO.)

  1. Configure Amazon Aurora Global Database with the primary cluster in us-west-2 and a secondary cluster in us-east-1, performing a managed failover to the secondary region during an outage.Cevap
  2. Associate the Route 53 Private Hosted Zone corp.internal from the primary account with the VPCs in both us-west-2 and us-east-1 using cross-account VPC association authorization.Cevap
  3. C
    Configure AWS Backup to take hourly snapshots of the Aurora PostgreSQL database in us-west-2, copy them to us-east-1, and restore them during a disaster.
  4. D
    Create a separate Route 53 Private Hosted Zone named corp.internal in the us-east-1 account, and configure a custom synchronization lambda function to mirror DNS records.
  5. E
    Configure a Route 53 failover routing policy pointing to database endpoints in both regions, omitting health checks to allow default connection-drop failover routing.

Cevap

Configure Amazon Aurora Global Database with the primary cluster in us-west-2 and a secondary cluster in us-east-1, and associate the Route 53 Private Hosted Zone corp.internal from the primary account with the VPCs in both regions.
The correct configuration integrates Amazon Aurora Global Database to achieve low-latency replication (sub-second lag) and quick promotion capability during disaster recovery. This satisfies the RPO of less than 1 minute and RTO of less than 15 minutes. To allow microservices in both EKS clusters to resolve internal endpoints consistently, the Solutions Architect associates the primary Private Hosted Zone with the VPCs in both regions, leveraging AWS cross-account and cross-region PHZ sharing capabilities.

Adım Adım Çözüm

1
Evaluate replication technologies that can support the target RPO and RTO constraints.
Aurora Global Database is selected because it provides replication latencies under 1 second (meeting the RPO of < 1 minute) and failover/promotion speeds under 15 minutes (meeting the RTO of < 15 minutes). AWS Backup and snapshot replication are eliminated as they fail these target metrics.
Aligning database replication strategy with business recovery objectives is critical for disaster recovery planning.
2
Establish cross-region and cross-account DNS resolution configuration for internal workloads.
The existing Route 53 Private Hosted Zone is associated with the VPCs in both regions using cross-account VPC association authorization.
This allows EKS workloads in both regions to resolve internal resource names directly and securely without maintaining redundant zones or custom sync tools.

Anahtar Kavram

Enhancing Disaster Recovery and Multi-Region DNS Resolution using Aurora Global Database and Route 53 Private Hosted Zone Association
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Enhancing Reliability and Disaster Recovery