1. Edge Data Consistency advanced

    A mobility platform wants to place data close to users in many regions. Which data can be replicated and which cannot?

    2 min answer olafly-ioedgereplication
  2. Edge Data Consistency advanced

    A social platform serves user profiles from edge caches worldwide. A user updates their profile and still sees the old one. How should this be handled?

    1 min answer edgeconsistencyinvalidationread-your-writes
  3. Edge Data Consistency advanced

    After a price change you issue a CDN purge and every point of presence returns 200. Twenty minutes later customers in one region still see the old price, and a hard refresh fixes it for some of them. Where do you look and in what order?

    2 min answer cdnpurgecache-variantsvary
  4. Edge Data Consistency intermediate

    Review this design. A streaming platform resolves three things in an edge function on every playback request: the active feature-flag set written from CI and read 200000 times a second; the regional price shown in the paywall; and whether this account's subscription is still active. All three live in a globally replicated edge key-value store with roughly 10-second propagation, writable from any location with last-writer-wins. What would you remove, what would you change, and what would you leave alone?

    3 min answer edge-data-consistencyreplicationentitlementsigned-tokens
  5. Edge Data Consistency advanced

    You enforce a rate limit of 100 requests per minute per user at the edge, across 40 locations. Abuse monitoring shows a user making 3,000. Explain.

    2 min answer edgerate-limitingconsistency