CloudFront caches a citizen portal's JavaScript aggressively, so releases sometimes leave browsers on stale bundles. How should the build artifact address this?
Select an answer to reveal the explanation.
Short Explanation
Same filename, same cache key—citizens keep yesterday's portal. Fingerprint the JS in the build so CloudFront treats each release as a new object. Disabling the CDN or emailing "please hard refresh" is not a deployment strategy.
Full Explanation
Versioned static assets (content hashes in filenames) allow long CDN TTLs while guaranteeing clients fetch new code after a release. This is a core front-end packaging concern for CloudFront-backed civic portals. Disabling CloudFront, relying on user education, or misusing DynamoDB for script delivery does not solve cache busting cleanly.