Which strategies support compliance with data residency and sovereignty requirements in multicloud deployments? (Select two)

Question

Options

• AStoring all data in a single location to simplify management
• BIgnoring local and regional data protection laws
• CUtilizing cloud services that offer region-specific data storage options
• DImplementing data encryption both at rest and in transit

• A
  20% (10)
• B
  8% (4)
• C
  71% (35)

Explanation

C and D are correct because they directly address the two pillars of data residency compliance: knowing where data lives and protecting it wherever it goes. Cloud providers with region-specific storage options (C) let organizations keep data within legally required geographic boundaries - critical under regulations like GDPR, India's PDPB, or China's PIPL. Encryption at rest and in transit (D) satisfies data protection mandates that accompany most sovereignty laws, ensuring data is unreadable even if intercepted or stored on shared infrastructure.

A is wrong because consolidating all data in a single location directly violates residency requirements - data for EU citizens must stay in the EU, not wherever is "simplest." B is wrong for the obvious reason that ignoring local data protection laws exposes organizations to regulatory fines, legal action, and loss of operating licenses in those regions.

Memory tip: Think "WHERE it lives + HOW it's protected" - region-specific storage answers where, encryption answers how. Any strategy that ignores or consolidates location (A, B) is antithetical to the very definition of data sovereignty.

No community discussion yet for this question.