A Front Door/CDN rule caches /api/lock-status and a harbor contractor sees another operator’s payload. What cache behavior should the security engineer set?
Select an answer to reveal the explanation.
Short Explanation
Personalized or signed-in API payloads don’t belong in the CDN cookie jar. Bypass cache or honor cache-control for those routes; leave anonymous static files on the CDN.
Full Explanation
CDN/Front Door caching is a security concern when authenticated or user-specific responses are stored at the edge and served to other clients. Security engineers configure bypass-cache behavior or honor cache-control for those routes while still allowing CDN caching for anonymous static assets. Aggressive caching of all API responses creates cross-user data exposure. Bastion is unrelated to CDN static delivery. Treating the problem as only an AZ-204 Cache-Control coding exercise ignores Front Door rule configuration as a Domain 2 control.