# Content Delivery Network

A Content Delivery Network is a distributed network of edge servers that delivers content closer to users, often by caching responses from an origin.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/content-delivery-network

> A CDN reduces delivery latency and origin workload by serving reusable content from geographically distributed edge locations. It helps applications handle large audiences and traffic spikes, but its effectiveness depends on cache configuration, content freshness requirements, and origin resilience.

Practice exams covering Content Delivery Network: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of Content Delivery Network

Effective CDN design combines distributed delivery, correct cache keys, controlled freshness, secure access, and origins that remain resilient when caching cannot help.

1. **Distributed edge delivery**: Requests are handled through geographically distributed edge locations to reduce network round trips. Routing selects an appropriate edge, which is not necessarily the geographically closest location.
2. **Cache keys and reuse**: A cache key defines which requests can reuse the same stored response. Include inputs that change the response, but avoid unnecessary cookies, headers, and query parameters that reduce cache efficiency.
3. **Freshness management**: Expiration settings and cache-control policies balance content freshness against origin offload. Use versioned asset names for predictable releases and invalidation when cached content must be removed early.
4. **Origin offload and resilience**: Cache hits reduce origin requests and help absorb bursts of demand. Cache misses and uncached operations still require origin capacity, while failover and stale-content behavior must be explicitly designed.
5. **Secure delivery**: HTTPS protects content in transit, while signed requests or tokens can restrict viewer access. Restricting direct origin access helps prevent bypass of CDN security controls.
6. **Workload-specific acceleration**: Reusable assets and media segments are strong caching candidates; personalized responses require more careful policies. Dynamic HTTP delivery may benefit from optimized connections, but a CDN is not a substitute for a TCP or UDP network accelerator.

## Cloud services for Content Delivery Network

CloudFront, Cloud CDN, and Azure Front Door are alternative CDN implementations rather than components that must be deployed together. Each places an edge delivery layer in front of configured origins. In an AWS architecture, CloudFront can serve static paths from a private S3 bucket and forward application paths to an Application Load Balancer. Cache policies determine which responses are reused and which requests reach the origins. Origin access restrictions, redundant application targets, and appropriate authorization complement the CDN; caching alone does not provide application failover or protect private content.

- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: CloudFront implements CDN delivery through edge locations, configurable cache behaviors, and integration with AWS and external origins. It supports signed URLs and cookies, origin access control for supported origins, and origin failover for supported request methods.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon S3 commonly acts as a durable origin for assets delivered through a CDN. With CloudFront, a private S3 bucket can use origin access control so viewers retrieve objects through the distribution rather than directly from the bucket.

## Content Delivery Network exam questions

Real practice exam questions on Content Delivery Network, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A conference organizer distributes a public event schedule through an AWS service that caches files at edge locations worldwide. The organizer replaces the schedule on the origin server, but attendees still receive the previous version from cached copies. The schedule's URL must remain unchanged. Which action should the organizer take to allow attendees to receive the updated schedule before the cached copies expire?

**Correct answer:** Create an Amazon CloudFront invalidation for the schedule's file path.

**Explanation:** A CloudFront invalidation removes the specified file from edge caches before its normal expiration. Subsequent requests can retrieve the updated file from the origin without changing its URL.

### Question 2 (SAA-C03)

**Question:**

An engineering company distributes public reference archives from an HTTPS server in its on-premises data center. Customers worldwide repeatedly download the same archives, especially after weekly announcements. Published archives never change. The company's internet provider charges for outbound data, and download spikes frequently saturate the data center's internet connection.

The company must keep the authoritative files on premises. It wants to reduce data center outbound traffic and improve download performance without operating additional download servers.

Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Create an Amazon CloudFront distribution with the on-premises HTTPS server as a custom origin. Configure caching with a long TTL for the archive paths and direct customers to the distribution.

**Explanation:** CloudFront supports publicly accessible HTTPS servers outside AWS as custom origins. Edge caches can reuse the immutable archives for subsequent downloads, reducing data center outbound traffic and improving global performance without moving the authoritative files or managing more servers.

## Practice Content Delivery Network in a full exam

Questions on Content Delivery Network in each practice exam, with every answer option and an explanation for each:

- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 1 question

## What is Content Delivery Network

A content delivery network places a distributed delivery layer between clients and an application's origin, such as object storage, a load balancer, or a web server. Requests reach an edge location selected through the provider's routing mechanisms, typically based on network conditions and proximity rather than geographic distance alone. When an eligible response is cached there, the edge can serve it without fetching the content from the origin.

For a cache miss, the CDN retrieves the requested content from an upstream cache or the origin and may store it for subsequent requests. This reduces repeated origin work and long-distance transfers. For example, an online retailer can deliver product images, stylesheets, and JavaScript through a CDN while its application servers handle shopping carts and checkout. During a promotion, repeated requests for the same images are largely absorbed by the delivery layer rather than reaching the application infrastructure.

Cache behavior is controlled through expiration settings, HTTP headers, and CDN-specific policies. The cache key determines which requests share a cached response; it commonly includes the URL path and may include selected query parameters, headers, or cookies. Including unnecessary values fragments the cache and reduces the cache hit ratio. Omitting values that genuinely change a response can serve incorrect content or expose one user's information to another. Personalized pages and authenticated API responses therefore need explicit caching and authorization decisions.

Freshness is a deliberate trade-off. Long time-to-live values reduce origin traffic but allow cached content to remain unchanged longer. Versioned asset names, such as an application bundle containing a build identifier, allow long caching periods without delaying releases. Invalidations can remove cached objects before expiration, but propagation takes time and may incur charges. Sensitive responses should use appropriate cache-control directives and policies that prevent unintended shared caching.

CDNs support resilient architectures by distributing request handling and reducing pressure on origins. Some offer origin failover and configurable stale-content serving when an origin fails. However, a CDN does not automatically make a single-region application highly available. Cache misses, expired content, and uncached operations still depend on functioning origins, so critical applications may also require redundant origin capacity and tested failover. A cold cache after a deployment or invalidation can produce a sudden increase in origin traffic.

Security controls commonly include HTTPS, request filtering, and signed URLs or cookies for restricted downloads. Where supported, restrict origin access so users cannot bypass the CDN's controls. An AWS example is allowing a private S3 origin to be accessed through CloudFront origin access control. Viewer authorization and permission for the CDN to access the origin solve different problems and may both be necessary.

A CDN is not limited to static websites: it can deliver media segments and proxy dynamic HTTP traffic, potentially improving connection handling even when responses are not cached. Nevertheless, it is not equivalent to a general-purpose network accelerator. For exam scenarios, choose a CDN when requirements emphasize HTTP-based content delivery, caching, and origin offload. An accelerator such as AWS Global Accelerator addresses network routing for TCP or UDP applications without caching content. Measure cache hit ratio, origin request rate, latency, errors, and total delivery costs to validate the design rather than assuming every workload benefits equally.

## Learn Content Delivery Network in lessons

3 short lessons on Content Delivery Network in 2 certification courses.

- CLF-C02: Content Delivery Network: cache reuse and freshness (Premium), https://app.blowstack.com/lessons/content-delivery-network-cache-reuse-and-freshness-clf-c02
- SAA-C03: Content Delivery Network: edge caching and origin offload (Premium), https://app.blowstack.com/lessons/content-delivery-network-edge-caching-and-origin-offload-saa-c03
- CLF-C02: Content Delivery Network and Load Balancing: offloading versus distributing requests (Premium), https://app.blowstack.com/lessons/content-delivery-network-and-load-balancing-offloading-versus-distributing-requests-clf-c02
