nerdexam
Amazon

SAP-C02 · Question #637

A company has a website that serves many visitors. The company deploys a backend service for the website in a primary AWS Region and a disaster recovery (DR) Region. A single Amazon CloudFront…

The correct answer is D. Create a CloudFront origin group that includes two origins, one for each backend service Region. To achieve the fastest failover time for a CloudFront-backed website with primary and DR regions, use a CloudFront origin group that automatically fails over between origins based on their health status.

Submitted by priya_blr· Mar 6, 2026Continuous Improvement for Existing Solutions

Question

A company has a website that serves many visitors. The company deploys a backend service for the website in a primary AWS Region and a disaster recovery (DR) Region. A single Amazon CloudFront distribution is deployed for the website. The company creates an Amazon Route 53 record set with health checks and a failover routing policy for the primary Region's backend service. The company configures the Route 53 record set as an origin for the CloudFront distribution. The company configures another record set that points to the backend service's endpoint in the DR Region as a secondary failover record type. The TTL for both record sets is 60 seconds. Currently, failover takes more than 1 minute. A solutions architect must design a solution that will provide the fastest failover time. Which solution will achieve this goal?

Options

  • ADeploy an additional CloudFront distribution. Create a new Route 53 failover record set with
  • BSet the TTL to 4 second for the existing Route 53 record sets that are used for the backend
  • CCreate new record sets for the backend services by using a latency routing policy. Use the record
  • DCreate a CloudFront origin group that includes two origins, one for each backend service Region.

How the community answered

(30 responses)
  • A
    3% (1)
  • B
    20% (6)
  • C
    10% (3)
  • D
    67% (20)

Why each option

To achieve the fastest failover time for a CloudFront-backed website with primary and DR regions, use a CloudFront origin group that automatically fails over between origins based on their health status.

ADeploy an additional CloudFront distribution. Create a new Route 53 failover record set with

Deploying an additional CloudFront distribution adds complexity and cost without directly addressing the failover speed issue for a single website; CloudFront origin groups are the specific feature for fast origin failover within a distribution.

BSet the TTL to 4 second for the existing Route 53 record sets that are used for the backend

While a lower Route 53 TTL can speed up DNS resolution, CloudFront often caches DNS responses for origins, and its own internal origin health checks and failover mechanisms (like origin groups) are more effective at reducing failover time when CloudFront is in front.

CCreate new record sets for the backend services by using a latency routing policy. Use the record

A latency routing policy directs users to the region with the lowest latency, which is not designed for primary/secondary failover based on health checks to maximize availability during a failure event.

DCreate a CloudFront origin group that includes two origins, one for each backend service Region.Correct

A CloudFront origin group enables CloudFront to perform automatic origin failover between a primary and a secondary origin based on origin response, providing significantly faster failover (typically within seconds) than relying on DNS TTLs or Route 53 failover alone when CloudFront is the distribution point.

Concept tested: CloudFront origin group failover, disaster recovery

Source: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/high-availability-origin-failover.html

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full SAP-C02 Practice