How do data sovereignty requirements influence cloud provider selection and data architecture?

• A. Data sovereignty has no impact on provider selection.
• B. Data sovereignty only affects data at rest.
• C. Laws may require data to reside in specific regions, impacting provider selection and data architecture.
• D. Data sovereignty requires always using the same provider globally.

Answer: (C)

Data sovereignty means laws require data to be stored and processed within specific borders. That directly influences cloud provider selection and how you design data architecture. When choosing a provider, you look for those that offer data residency options in the required region and that provide contracts, audits, and controls that align with local regulations. For the data architecture, you must design to keep data in the permitted region, which may involve regional data stores, regional backups and disaster recovery, and limiting cross-border data transfers. You might also manage encryption keys within the same region or under a jurisdiction-approved key management approach, and you’ll need to assess whether regional replication is allowed and how it impacts latency and privacy obligations. In short, data sovereignty drives both where you host data and how you structure data flows and protections across regions.