Live-updating banners behind a shared edge need a split policy: content-hashed versions can ride long immutable TTLs under a stable host-path key, while the live pointer or unversioned banner path stays on short s-maxage or a tagged invalidation so a creative swap does not wait for natural expiry across every POP. Keep Cookie and Authorization out of the public key, and prefer replacing the object under a new fingerprint rather than overwriting one key that every region still holds warm.
Ops prove-out after a banner cutover: fetch the pointer path twice from a clean client and confirm Age plus X-Cache move MISS then HIT only while the body is still the intended creative; publish a new fingerprint, purge or wait out the short TTL on the pointer, and re-check until every sampled POP returns the new bytes. If one region keeps the old creative, inventory which key variants still exist — an un-normalized query or leftover cookie in the key looks like a sticky POP when the real issue is cache-key cardinality.