Which statement about a CDN is true?

Which statement about a CDN is true?

• A. It caches static assets globally to reduce latency, improve load times, and handle traffic spikes.
• B. It stores the entire database on edge servers.
• C. It replaces the origin server for all requests.
• D. It can only deliver images.

Answer: (A)

The main idea tested here is how a CDN improves delivery by caching content close to users. A CDN places edge servers around the world and keeps copies of static assets there so when a user requests a page, those files can be served from a nearby location rather than always traveling back to the original server. This proximity lowers latency, speeds up page loads, and helps absorb traffic spikes by distributing requests across many edge locations. That's why the statement about caching static assets globally to reduce latency, improve load times, and handle traffic spikes is the best description of what a CDN does. It encapsulates the core benefit: bringing content closer to users to speed up delivery and manage high traffic. The other ideas don’t fit the typical CDN role. A CDN does not store the entire database on edge servers, since databases are dynamic and central to data integrity; they’re not meant to be cached wholesale at edge locations. It also doesn’t replace the origin server for all requests—the origin still serves content that isn’t cached or is dynamic, with the CDN acting as a fast front door. And a CDN isn’t limited to delivering only images; it handles many types of content, including scripts, styles, fonts, videos, and more.

The main idea tested here is how a CDN improves delivery by caching content close to users. A CDN places edge servers around the world and keeps copies of static assets there so when a user requests a page, those files can be served from a nearby location rather than always traveling back to the original server. This proximity lowers latency, speeds up page loads, and helps absorb traffic spikes by distributing requests across many edge locations.

That's why the statement about caching static assets globally to reduce latency, improve load times, and handle traffic spikes is the best description of what a CDN does. It encapsulates the core benefit: bringing content closer to users to speed up delivery and manage high traffic.

The other ideas don’t fit the typical CDN role. A CDN does not store the entire database on edge servers, since databases are dynamic and central to data integrity; they’re not meant to be cached wholesale at edge locations. It also doesn’t replace the origin server for all requests—the origin still serves content that isn’t cached or is dynamic, with the CDN acting as a fast front door. And a CDN isn’t limited to delivering only images; it handles many types of content, including scripts, styles, fonts, videos, and more.