Soru

Zorluk: KolayEdge Caching and Content Delivery for Resilient Architectures

An online education company stores popular static media assets, such as course images and stylesheets, in an Amazon S3 bucket. During peak enrollment periods, the S3 bucket experiences performance degradation due to high request volumes from global users. The company wants to reduce latency for users, protect the S3 bucket from overloading, and minimize operational complexity. Which configuration should the solutions architect choose?

  1. Configure an Amazon CloudFront distribution with the Amazon S3 bucket as the origin, caching the static assets at edge locations with default Time to Live (TTL) settings.Cevap
  2. B
    Create an Amazon CloudFront distribution with the Amazon S3 bucket as the origin, and set the default Time to Live (TTL) to zero to ensure content is always fetched from the source.
  3. C
    Configure Amazon Route 53 with a latency-based routing policy to resolve the website's domain name directly to the S3 bucket endpoint.
  4. D
    Deploy AWS Shield Advanced directly on the S3 bucket to inspect Layer 7 web traffic and prevent request spikes from degrading performance.

Cevap

Configure an Amazon CloudFront distribution with the Amazon S3 bucket as the origin, caching the static assets at edge locations with default Time to Live (TTL) settings.
Configuring Amazon CloudFront with the S3 bucket as the origin allows CloudFront to cache static assets (like images and stylesheets) at global edge locations. This reduces latency for users worldwide by serving content from the nearest edge location and protects the origin S3 bucket from high request volumes by serving cached copies, thereby increasing resiliency and reliability.

Adım Adım Çözüm

1
Identify the primary requirements: reduce latency for global users accessing static S3 assets and protect the origin bucket from request overload.
A caching mechanism at edge locations is needed to serve content closer to users and offload traffic from the S3 bucket.
Serving cached static content at edge locations reduces network round-trip time and prevents origin degradation.
2
Evaluate the capabilities of Amazon CloudFront.
Amazon CloudFront is a content delivery network that caches files at edge locations when non-zero TTL settings are active.
CloudFront acts as an edge caching layer that directly solves latency issues and shields the origin S3 bucket from high request volumes.
3
Compare CloudFront options against Route 53 and AWS Shield alternatives.
CloudFront with default TTL settings meets the requirement, whereas setting TTL to zero disables caching. Route 53 latency routing and AWS Shield do not cache content.
This step eliminates incorrect architectures that fail to provide edge caching.

Anahtar Kavram

Edge caching with Amazon CloudFront
Bu soruyu puanla