An existing citizen portal still serves CSS, JavaScript, and images directly from a single-Region origin, causing slow loads for distant residents. Which managed performance adoption should architects propose?
Select an answer to reveal the explanation.
Short Explanation
Hauling every stylesheet from one Region origin is like mailing library books from a single warehouse for every request. CloudFront parks copies at the edge so phones stop waiting on cross-country hops. Static assets love CDNs; give them one.
Full Explanation
Proposing managed services for performance commonly includes CloudFront for static portal assets, reducing origin load and improving latency for geographically dispersed residents. Keeping assets only on-prem near city hall, disabling caching, or using self-signed browser hacks does not provide global edge acceleration. Continuous improvement of existing portals adopts edge caching without rewriting the entire application tier.