How does implementing a Content Delivery Network (CDN) contribute to optimizing solution performance using geolocation?

Question

Options

• AIt ensures that compute resources are centrally located
• BIt reduces bandwidth costs by limiting data transfer
• CIt decreases latency by caching content closer to the user
• DIt simplifies application development by reducing the need for backend services

• A
  5% (1)
• B
  14% (3)
• C
  77% (17)
• D
  5% (1)

Explanation

Option C is correct because a CDN works by distributing cached copies of content across servers in multiple geographic locations (called "points of presence" or PoPs), so when a user makes a request, it's served from the nearest server rather than a distant origin - dramatically reducing round-trip latency. Option A is wrong because CDNs do the opposite of centralizing compute; their entire value comes from geographic distribution. Option B is a partial misconception - CDNs can reduce origin bandwidth costs, but that's a side effect, not the mechanism by which they use geolocation to improve performance. Option D is wrong because CDNs are purely a delivery/caching layer and don't simplify backend development in any meaningful way.

Memory tip: Think of a CDN like a chain of local convenience stores - instead of driving to one central warehouse every time you need something, you grab it from the nearest store. The "geo" in geolocation is the key: closer = faster.

No community discussion yet for this question.