Active-active edge config replication
Design an active-active geo-replicated key-value store for edge configuration (routing rules, WAF policies, rate-limit configs) served from 200+ edge POPs. Operators in any region can update config, all edges must converge to the same final state within seconds, and an edge must keep serving its last-known config even if fully partitioned from the control plane. Updates are infrequent but correctness of the final converged state is critical. How do you replicate and resolve concurrent edits?
What a strong answer looks like
Clarify scale and constraints first. Propose a clean component breakdown, then go deep on the hard parts (data model, bottlenecks, consistency, failure modes) and name the trade-offs you are making.
Clarify5:30 left
Estimate5:30 planned
Design16:30 planned
Deep dive13:30 planned
Failure9:00 planned
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.