A software architect has been asked to build a platform to distribute music to thousands of users on a global scale. The architect has been reading about content delivery networks (CDN). Which of the

SOA is an application integration and software design pattern focused on exposing business logic as services, and is not a principal concern when designing a CDN for media distribution.

The principal function of a CDN is to cache content-such as music files-at geographically distributed edge servers (Points of Presence), so that users receive content from a nearby node rather than a distant origin server. Establishing a media caching methodology defines how, where, and for how long content is stored at edge locations, which is the foundational design decision for any CDN-based distribution platform. Without a caching strategy, the CDN cannot effectively reduce latency or handle thousands of simultaneous global users.

CDN providers already have pre-established ISP relationships and peering agreements; an architect building a CDN-based platform does not need to individually negotiate with hundreds of ISPs, as this is handled by the CDN infrastructure layer.

Building a dedicated low-latency WAN is a network infrastructure undertaking that predates or bypasses CDN architecture; CDNs are specifically designed to deliver performance over the public internet without requiring a private WAN.