What is a content delivery network (CDN) and when would you use it?

What is a content delivery network (CDN) and when would you use it?

• A. A CDN caches static content at edge locations to reduce latency and improve load times for users globally.
• B. A CDN stores database backups in a centralized data center.
• C. A CDN provides authentication services for users.
• D. A CDN converts dynamic content into static pages.

Answer: (A)

Caching static content at edge locations to reduce latency and improve load times for users globally. A CDN places copies of your static assets—like images, CSS, JavaScript, and video—on servers around the world. When someone requests a resource, it’s served from the nearest edge location rather than all the way from your origin server. This proximity lowers travel distance and round-trip time, so pages load faster, user experience improves, and your origin server handles less traffic, which can also reduce bandwidth costs. You’d use a CDN when you have a global audience or you serve large static assets and media. It’s especially helpful for sites that experience traffic spikes or need reliable performance across different regions. The other options describe different services or uses that aren’t the primary purpose of a CDN—storing backups, providing authentication, or transforming dynamic content into static pages.

Caching static content at edge locations to reduce latency and improve load times for users globally.

A CDN places copies of your static assets—like images, CSS, JavaScript, and video—on servers around the world. When someone requests a resource, it’s served from the nearest edge location rather than all the way from your origin server. This proximity lowers travel distance and round-trip time, so pages load faster, user experience improves, and your origin server handles less traffic, which can also reduce bandwidth costs.

You’d use a CDN when you have a global audience or you serve large static assets and media. It’s especially helpful for sites that experience traffic spikes or need reliable performance across different regions.

The other options describe different services or uses that aren’t the primary purpose of a CDN—storing backups, providing authentication, or transforming dynamic content into static pages.