Examkin

Soru

Zorluk: KolayDisaster Recovery Strategies

A company is designing a disaster recovery (DR) strategy for a non-critical internal administration application. The business requires a Recovery Point Objective (RPO) of 2424 hours and a Recovery Time Objective (RTO) of 2424 hours. The primary objective is to minimize cost. Which of the following actions should a SysOps Administrator take to meet these requirements? (Choose two.)

  1. Configure AWS Backup to perform daily cross-region backups of the database to the secondary Region.Cevap
  2. Store infrastructure definitions as AWS CloudFormation templates to provision the compute resources in the secondary Region only during a disaster recovery event.Cevap
  3. C
    Configure an Amazon RDS Read Replica in the secondary Region to provide automatic synchronous failover of the database layer.
  4. D
    Set up Amazon S3 Cross-Region Replication (CRR) for application assets without enabling S3 Versioning on either the source or destination buckets.
  5. E
    Configure an Amazon Route 53 active-active failover routing policy to route all traffic to the secondary Region even when the primary Region is fully healthy.

Cevap

Configure AWS Backup to perform daily cross-region backups of the database to the secondary Region, and store infrastructure definitions as AWS CloudFormation templates to provision the compute resources in the secondary Region only during a disaster recovery event.
The correct options align with the Backup and Restore disaster recovery strategy. With an RTO and RPO of 2424 hours, the company does not need warm resources running in the secondary Region. Using AWS Backup for daily cross-region replication ensures that database backups are under 2424 hours old, meeting the RPO. Deploying resources on-demand using AWS CloudFormation templates during a disaster allows recovery well within the 2424-hour RTO while avoiding the cost of maintaining running compute capacity.

Adım Adım Çözüm

1
Analyze the business requirements for RTO, RPO, and budget.
Identify that both RTO and RPO are 2424 hours, and the primary driver is cost optimization, which points to a Backup and Restore disaster recovery strategy.
Determining the correct recovery strategy category limits the set of appropriate AWS services.
2
Evaluate options for the database tier that satisfy the 2424-hour RPO at minimal cost.
Select daily cross-region backups using AWS Backup because they satisfy the 2424-hour RPO without the high cost of active replication like read replicas or global databases.
Ensures the database recovery point meets business requirements without exceeding the cost envelope.
3
Evaluate compute and infrastructure provisioning options that satisfy the 2424-hour RTO at minimal cost.
Select AWS CloudFormation templates to provision resources on-demand during a failover event, avoiding running idle instances in the disaster recovery Region.
Ensures the compute resources can be deployed within the 2424-hour recovery window without incurring passive compute charges.

Anahtar Kavram

Disaster Recovery Strategies
Bu soruyu puanla

Konular

Disaster Recovery Strategies

Bu konudan daha fazla soru