A regional shared-services proposal would store citizen identity attributes in a cloud region outside the jurisdiction’s residency rules. How should architecture treat that constraint?
Select an answer to reveal the explanation.
Short Explanation
Where the filing cabinet sits is part of the design, not a footnote. Residency rules are hard constraints—architecture has to place citizen data where the law allows.
Full Explanation
Cross-border and residency requirements constrain eligible regions, processors, and replication topologies. Treating them as first-class architecture inputs early prevents non-compliant designs and expensive rework. Latency or cost optimizations cannot override legal and policy placement constraints for regulated citizen data.