A city emergency-alert API must stay available if a single data-center event occurs, while callers need low latency and data residency in one geography. Which application-level placement approach best fits that goal on OCI?
Select an answer to reveal the explanation.
Short Explanation
Think of availability domains like separate fire stations in the same city and fault domains like different truck bays—so one maintenance event does not take every responder. Pick a region for latency and residency, spread replicas, and remember some OCI resources are regional while others are AD-local.
Full Explanation
Developers choose a region for caller latency and data residency, then design so one data-center event is not a total outage. Spreading stateless replicas and using fault domains for anti-affinity reduces correlated failure. Some resources are regional while compute instances and block volumes are availability-domain local. Collapsing everything into one AD or one instance maximizes blast radius; this is app-level placement thinking, not Foundations trivia or hub-spoke DR architecture.