Examkin

Soru

Zorluk: OrtaEdge Caching and Content Delivery for Resilient Architectures

A company hosts a global web application in the us-east-1 Region. The application consists of static media assets stored in an Amazon S3 bucket and dynamic APIs served by Amazon EC2 instances behind an Application Load Balancer (ALB). To protect against regional outages and optimize performance, the company has duplicated its static assets to an S3 bucket in us-west-2 and deployed a standby backend service on EC2 instances behind an ALB in us-west-2. A solutions architect must design a content delivery and caching solution that ensures low latency for global users and automatically fails over to the standby resources in us-west-2 if the primary resources in us-east-1 fail or return server errors.

Which combination of actions should the solutions architect take to meet these requirements with the lowest latency and high resilience? (Select TWO.)

  1. Configure an Amazon CloudFront distribution with an origin group for static assets, specifying the us-east-1 S3 bucket as the primary origin and the us-west-2 S3 bucket as the secondary origin.Cevap
  2. Configure an Amazon CloudFront distribution with an origin group for dynamic APIs, specifying the us-east-1 Application Load Balancer as the primary origin and the us-west-2 Application Load Balancer as the secondary origin.Cevap
  3. C
    Configure Amazon Route 53 latency-based routing to resolve the domain directly to the Application Load Balancers in us-east-1 and us-west-2, relying on the routing policy to perform automatic failover during application server outages.
  4. D
    Deploy AWS Shield Standard and configure it to automatically fail over application traffic to the standby us-west-2 Region when HTTP 500 series errors are detected.
  5. E
    Configure Amazon CloudFront to set the Minimum TTL, Default TTL, and Maximum TTL to 0 seconds on all cache behaviors, ensuring that users always retrieve the latest failover content directly from the backup origins.

Cevap

Configure an Amazon CloudFront distribution with an origin group for static assets (with us-east-1 S3 as primary and us-west-2 S3 as secondary) and configure an origin group for dynamic APIs (with us-east-1 ALB as primary and us-west-2 ALB as secondary).
To build a resilient and low-latency architecture, Amazon CloudFront should be deployed in front of the origin servers. By setting up CloudFront origin groups, you can specify a primary origin and a secondary (standby) origin for both static assets (Amazon S3 buckets) and dynamic content (Application Load Balancers). If the primary origin in us-east-1 returns configured HTTP error codes (such as 500, 502, 503, or 504), CloudFront automatically fails over and routes subsequent requests to the secondary origin in us-west-2, ensuring high availability and low latency via edge caching.

Adım Adım Çözüm

1
Set up CloudFront origin groups for both static assets and dynamic APIs.
Two separate origin groups are created within the CloudFront distribution: one containing the S3 buckets in us-east-1 and us-west-2, and another containing the Application Load Balancers (ALBs) in us-east-1 and us-west-2.
Origin groups allow CloudFront to automatically handle origin failover when the primary origin is unavailable or returns specific HTTP errors.
2
Configure the cache behaviors to map static and dynamic paths to their respective origin groups.
Traffic for static media assets is routed to the S3 origin group, and traffic for dynamic APIs is routed to the ALB origin group.
This separation ensures that caching policies and failover behaviors are optimized for each content type.
3
Configure failover criteria for the origin groups.
Failover triggers are established for HTTP status codes such as 500, 502, 503, and 504.
This guarantees that if the primary resources in us-east-1 fail or return server errors, CloudFront instantly forwards the user requests to the standby resources in us-west-2.

Anahtar Kavram

Amazon CloudFront origin groups allow solutions architects to configure automatic origin failover for both Amazon S3 and custom origins (such as Application Load Balancers) to ensure high resilience and low latency.
Bu soruyu puanla

Konular

Edge Caching and Content Delivery for Resilient Architectures

Bu konudan daha fazla soru