Skip to content

SAP-C03 · Domain 4: Resilience, Migration, and Business Continuity · 15% of the exam

Task 4.2: Design disaster recovery architectures.

Recovering from a disaster: strategies chosen by RTO, RPO and cost, continuous replication with Elastic Disaster Recovery, assessments and runbooks, multi-Region failover with Route 53, Global Accelerator and Application Recovery Controller, tests, and multi-cluster containers.

Study it

Sample questions

Try each one before opening the answer. Every option is explained, with the AWS documentation page that proves it.

Question 1 · choose 1

A company runs a critical ERP system on 40 VMware virtual machines in its data center. It needs disaster recovery on AWS with an RPO of seconds and an RTO of under one hour. The application must not change, and the company wants to pay as little as possible for the recovery site while no disaster is in progress. Which solution meets these requirements?

  1. AReplicate the servers continuously with AWS Elastic Disaster Recovery and launch recovery instances only during a drill or disaster
  2. BBack up the virtual machines to AWS with AWS Backup every hour and restore them to Amazon EC2 during a disaster
  3. CRun a full-size copy of every server on Amazon EC2 at all times and keep the data in sync with database and file replication software
  4. DExport the virtual machines to Amazon Machine Images every night with VM Import/Export and launch them during a disaster
Show the answer and why
  • AReplicate the servers continuously with AWS Elastic Disaster Recovery and launch recovery instances only during a drill or disaster

    Correct

    Elastic Disaster Recovery replicates source servers continuously into a staging area that uses affordable storage and minimal compute, and it launches recovery instances only when needed. AWS states that it enables RPOs of seconds and RTOs of minutes.

  • BBack up the virtual machines to AWS with AWS Backup every hour and restore them to Amazon EC2 during a disaster

    Incorrect

    Scheduled backups give an RPO equal to the backup interval, an hour in this design, which misses an RPO of seconds.

  • CRun a full-size copy of every server on Amazon EC2 at all times and keep the data in sync with database and file replication software

    Incorrect

    Running the whole recovery site at full size all the time meets the objectives but is the most expensive option while no disaster is in progress.

  • DExport the virtual machines to Amazon Machine Images every night with VM Import/Export and launch them during a disaster

    Incorrect

    Nightly images give an RPO of up to a day, far from seconds, and importing large virtual machines takes time.

Seconds of RPO without a running copy of the site is what continuous block-level replication into a staging area gives. Backups and images are bound to their schedule.

Question 2 · choose 1

An order database runs on Amazon Aurora MySQL in us-west-2. If the Region becomes unavailable, the database must accept writes in us-east-1 within minutes and lose at most a few seconds of data. Until then, a reporting application in us-east-1 must read the data locally. Which solution meets these requirements?

  1. AAdd Aurora Replicas in two more Availability Zones of us-west-2 and point the reporting application at the reader endpoint
  2. BCopy automated snapshots to us-east-1 every hour with AWS Backup and restore the latest one during a Regional outage
  3. CConvert the cluster to an Aurora global database with a secondary cluster in us-east-1 and fail over to it
  4. DTurn on Aurora Backtrack with a 72-hour window and rewind the cluster after the Region recovers
Show the answer and why
  • AAdd Aurora Replicas in two more Availability Zones of us-west-2 and point the reporting application at the reader endpoint

    Incorrect

    Aurora Replicas protect against the loss of an instance or an Availability Zone within one Region. They do not help if us-west-2 is unavailable, and reads would cross Regions.

  • BCopy automated snapshots to us-east-1 every hour with AWS Backup and restore the latest one during a Regional outage

    Incorrect

    Restoring an hourly snapshot can lose up to an hour of data and takes longer than a promotion, so it misses both the RPO and the RTO.

  • CConvert the cluster to an Aurora global database with a secondary cluster in us-east-1 and fail over to it

    Correct

    A global database replicates to secondary Regions with typical lag under a second, secondary clusters serve local reads, and a secondary can be promoted to take writes when the primary Region is impaired.

  • DTurn on Aurora Backtrack with a 72-hour window and rewind the cluster after the Region recovers

    Incorrect

    Backtrack rewinds a cluster in place to an earlier point in time. It creates no copy in another Region, so it cannot keep the database writable during a Regional outage.

Cross-Region writes within minutes with seconds of data loss and local reads meanwhile is the Aurora global database pattern.

Question 3 · choose 1

An enterprise has 80 applications with agreed resilience targets. Leaders want each application assessed against its targets, with recommendations based on AWS best practices, in one central place instead of spreadsheets. Which service fits?

  1. AAWS Fault Injection Service
  2. BAWS Trusted Advisor
  3. CAWS Resilience Hub
  4. DAmazon CloudWatch dashboards
Show the answer and why
  • AAWS Fault Injection Service

    Incorrect

    FIS runs fault experiments; it does not track targets and assessments for a portfolio.

  • BAWS Trusted Advisor

    Incorrect

    Trusted Advisor checks accounts against best practices but does not assess applications against their own resilience targets.

  • CAWS Resilience Hub

    Correct

    Resilience Hub lets you define resilience goals, assess applications against them and implement recommendations based on the Well-Architected Framework.

  • DAmazon CloudWatch dashboards

    Incorrect

    Dashboards show metrics, not assessments against resilience goals.

Central resilience assessment against goals is AWS Resilience Hub.

Question 4 · choose 1

A multi-account application fails over to a second Region with a long runbook: scale up compute, promote databases, and shift traffic, in a fixed order. Engineers make mistakes under pressure, and leaders want the recovery orchestrated and observable from one place. Which capability fits?

  1. ARegion switch in ARC with a plan for the application
  2. BZonal shift in ARC for the application's load balancers
  3. CRoute 53 failover records with health checks
  4. DAWS Backup restore jobs in the recovery Region
Show the answer and why
  • ARegion switch in ARC with a plan for the application

    Correct

    Region switch orchestrates large-scale, complex recovery tasks across accounts from a centralized, observable solution.

  • BZonal shift in ARC for the application's load balancers

    Incorrect

    Zonal shift moves traffic for a resource away from an impaired Availability Zone to healthy zones in the same Region. It does not orchestrate a failover to another Region.

  • CRoute 53 failover records with health checks

    Incorrect

    Health checks move DNS traffic but do not orchestrate scaling and database steps.

  • DAWS Backup restore jobs in the recovery Region

    Incorrect

    Restores recover data but do not orchestrate a whole Regional switch.

Orchestrated, observable Regional recovery is Region switch in ARC.

Question 5 · choose 1

A claims platform runs on Amazon ECS on AWS Fargate behind an Application Load Balancer in us-east-1. Its database is already an Aurora PostgreSQL global database with a secondary cluster in us-west-2. The disaster recovery targets for a Regional outage are an RPO of 1 minute and an RTO of 2 hours. Finance will not pay for application compute or load balancers in us-west-2 except during drills and real failovers. All infrastructure is defined in CloudFormation templates. Which disaster recovery strategy meets these requirements at the lowest cost?

  1. AMulti-site active/active: serve traffic from both Regions, and turn on write forwarding so the secondary cluster passes writes to the primary
  2. BBackup and restore: replace the secondary cluster with hourly AWS Backup copies in us-west-2, and rebuild the stack from templates after failover
  3. CWarm standby: run a scaled-down copy of the ECS services and the load balancer in us-west-2 at all times, and scale it out after failover
  4. DPilot light: keep the secondary cluster, and deploy the ECS services and load balancer from the same templates only when failing over to us-west-2
Show the answer and why
  • AMulti-site active/active: serve traffic from both Regions, and turn on write forwarding so the secondary cluster passes writes to the primary

    Incorrect

    Active/active runs the full workload in both Regions all the time, which costs the most and breaks the rule against running compute in us-west-2 outside drills. Write forwarding is useful when secondary Regions must accept writes, which this design does not need.

  • BBackup and restore: replace the secondary cluster with hourly AWS Backup copies in us-west-2, and rebuild the stack from templates after failover

    Incorrect

    AWS Backup can copy recovery points to another Region on a schedule, but with hourly copies up to an hour of committed data can be lost, which breaks the 1-minute RPO. Continuous replication is what keeps the RPO that low.

  • CWarm standby: run a scaled-down copy of the ECS services and the load balancer in us-west-2 at all times, and scale it out after failover

    Incorrect

    Warm standby keeps a scaled-down but fully functional copy of production running in the recovery Region, so it pays for exactly the compute and load balancers that finance refuses to fund outside drills.

  • DPilot light: keep the secondary cluster, and deploy the ECS services and load balancer from the same templates only when failing over to us-west-2

    Correct

    In a pilot light, the data stores stay always on and replicated while application servers are not deployed until a drill or failover. Aurora replicates to the secondary cluster with latency typically under a second, which covers the 1-minute RPO, and redeploying the stateless ECS tier from IaC fits within 2 hours.

Read the cost rule as the deciding constraint: nothing that serves traffic may run in us-west-2 until a drill or disaster. Warm standby and active/active both break it. Backup and restore would satisfy the cost rule but loses up to an hour of data with hourly copies. Pilot light keeps only the replicated data always on and switches the rest on from the same templates, which meets the 1-minute RPO and the 2-hour RTO at the lowest cost.

Question 6 · choose 1

An internal API runs in a primary and a standby Region behind internal Application Load Balancers in private subnets. Clients resolve api.corp.internal from a Route 53 private hosted zone. When the primary Region's error-rate CloudWatch alarm goes off, DNS must send clients to the standby Region automatically. What should a solutions architect configure?

  1. AFailover records whose primary has a Route 53 health check that probes the private IP addresses of the primary load balancer
  2. BLoad balancer health checks on the primary targets, with the standby load balancer registered as an extra target
  3. CMultivalue answer records for both load balancers so that clients retry the other address when one fails
  4. DFailover records whose primary is associated with a Route 53 health check that monitors the state of the CloudWatch alarm
Show the answer and why
  • AFailover records whose primary has a Route 53 health check that probes the private IP addresses of the primary load balancer

    Incorrect

    Route 53 health checkers run outside your VPCs and cannot reach private IP addresses, so a health check on a private endpoint cannot report its state.

  • BLoad balancer health checks on the primary targets, with the standby load balancer registered as an extra target

    Incorrect

    Load balancer health checks decide which targets of that load balancer receive traffic. They do not change DNS answers to another Region.

  • CMultivalue answer records for both load balancers so that clients retry the other address when one fails

    Incorrect

    Without health checks, multivalue answers keep returning the failed Region, and nothing reacts to the CloudWatch alarm.

  • DFailover records whose primary is associated with a Route 53 health check that monitors the state of the CloudWatch alarm

    Correct

    For resources Route 53 cannot reach, such as private endpoints, a health check can be based on a CloudWatch alarm, and failover routing then answers with the secondary record while that check is unhealthy.

Private endpoints cannot be probed by Route 53 health checkers, so the health check watches a CloudWatch alarm instead and drives failover routing.

Question 7 · choose 1

A new application will run active-passive in us-east-1 and us-west-2 on an Aurora PostgreSQL global database. Its database credentials are a Secrets Manager secret in us-east-1 that rotates every 30 days. If us-east-1 is down, the application in us-west-2 must read the current credentials from its own Region, the credentials must stay identical in both Regions after every rotation, and the team will not write or run code that copies secrets. Which solution meets these requirements?

  1. AKeep a SecureString parameter in us-west-2 and update it from a Lambda function that runs after each rotation in us-east-1
  2. BReplicate the secret to us-west-2 and keep the 30-day rotation configured on the primary secret in us-east-1
  3. CCreate a second secret in us-west-2 for the same database user with its own 30-day rotation schedule
  4. DLet the us-west-2 application read the secret from the us-east-1 endpoint through an IAM policy that allows the cross-Region call
Show the answer and why
  • AKeep a SecureString parameter in us-west-2 and update it from a Lambda function that runs after each rotation in us-east-1

    Incorrect

    A parameter in us-west-2 would be readable during the outage, but the Lambda function is copy code the team refuses to run, and AWS recommends Secrets Manager rather than Parameter Store for database credentials.

  • BReplicate the secret to us-west-2 and keep the 30-day rotation configured on the primary secret in us-east-1

    Correct

    Replica secrets hold the same secret data in other Regions. Secrets Manager rotates the primary secret and propagates the new value to every replica, so rotation is not managed per Region, and a replica can be promoted to a standalone secret if needed.

  • CCreate a second secret in us-west-2 for the same database user with its own 30-day rotation schedule

    Incorrect

    A local secret is readable during the outage, but two independent rotations would each set their own password for the same database user, so the values in the two Regions would not stay identical.

  • DLet the us-west-2 application read the secret from the us-east-1 endpoint through an IAM policy that allows the cross-Region call

    Incorrect

    A cross-Region read works only while us-east-1 is reachable. During the outage the application could not fetch the credentials at all.

Three constraints decide it: a local copy during the outage, identical values after rotation, and no copy code. A cross-Region read fails in the outage, a separately rotated secret drifts, and a parameter kept in sync by a function is the code the team will not run. A replica secret receives every rotated value from the primary automatically.

Question 8 · choose 1

A CI pipeline in a tools account pushes container images to Amazon ECR in us-east-1. Production runs on Amazon ECS in a separate production account in us-east-1 and fails over to us-west-2 in the same account. During an outage of us-east-1, ECS in us-west-2 must be able to pull every production image, including images it has never pulled before. Only repositories whose names start with prod/ may leave the tools account, and the team will not change the pipeline or write code that copies images. Which solution meets these requirements?

  1. AAdd a step to the pipeline that also pushes each production image to a registry in us-west-2 in the production account
  2. BConfigure ECR replication of the prod/ prefix from the tools account to the production account's registry in us-west-2
  3. CCreate an ECR pull through cache rule in us-west-2 in the production account with the tools account registry as its upstream
  4. DTurn on tag immutability for the prod/ repositories so that the image tags that ECS uses can never be overwritten
Show the answer and why
  • AAdd a step to the pipeline that also pushes each production image to a registry in us-west-2 in the production account

    Incorrect

    Pushing twice would place every image in us-west-2 before an outage, but it is the pipeline change that the team has ruled out.

  • BConfigure ECR replication of the prod/ prefix from the tools account to the production account's registry in us-west-2

    Correct

    ECR private image replication works across Regions and accounts once the destination registry's permissions policy allows it, and a repository prefix filter limits which repositories are replicated. Each new image is copied when it is pushed, without code.

  • CCreate an ECR pull through cache rule in us-west-2 in the production account with the tools account registry as its upstream

    Incorrect

    Pull through cache supports an ECR upstream, but an image is fetched from the upstream the first time it is pulled and served from the cache only after that. Images never pulled before the outage would be unavailable.

  • DTurn on tag immutability for the prod/ repositories so that the image tags that ECS uses can never be overwritten

    Incorrect

    Tag immutability prevents image tags from being overwritten. It makes deployments more predictable, but every image still exists only in us-east-1.

The constraints are images available in us-west-2 before any pull, only the prod/ repositories crossing accounts, and no pipeline or code changes. A second push changes the pipeline, a pull through cache fills only on demand, and tag immutability copies nothing. ECR replication with a prefix filter to the production account in us-west-2 meets all of them.

Practice domain 4 →Practice all domains →