A county publishes emergency-alert pages through a content delivery network. Architects worry that the origin is reachable directly and that poisoned cache objects could mislead the public. Which CDN design practice best addresses those concerns?
Select an answer to reveal the explanation.
Short Explanation
A CDN is a helpful megaphone—until someone talks to the stage door or slips a fake flyer into the stack. Lock the origin so only the CDN can fetch, and make sure cached alert pages can’t be quietly swapped for junk.
Full Explanation
CDN security for public emergency content requires protecting the origin from direct Internet abuse and hardening cache behavior against poisoning and unauthorized object insertion. Restricting origin connectivity to the CDN, authenticating pulls, and careful cache-key and validation design reduce both origin exposure and the risk that malicious or incorrect content is served at scale. Bypassing or fully disabling the CDN undermines the resilience goal without solving origin trust.