When designing solutions for data residency in a multicloud environment, which strategy ensures compliance with local regulations?

Question

Options

• AStoring all data in a single location to simplify compliance
• BIgnoring local regulations in favor of a unified global approach
• CDistributing data across multiple regions according to data sovereignty laws
• DEncrypting data without regard to its storage location

• A
  9% (3)
• B
  3% (1)
• C
  76% (26)
• D
  12% (4)

Explanation

Distributing data across multiple regions according to data sovereignty laws (C) directly addresses data residency requirements by ensuring each country's or jurisdiction's data remains within its legally mandated boundaries - this is the foundation of compliance in multicloud architectures.

Why the distractors fail:

• A - Centralizing all data in one location violates data residency laws for any jurisdiction whose regulations require local storage.
• B - Ignoring local regulations is a compliance violation, not a strategy; regulators don't make exceptions for convenience.
• D - Encryption protects data confidentiality but doesn't satisfy residency laws, which govern where data is stored physically, not how it's protected.

Memory tip: Think of data sovereignty like a passport - data must "live" in the country whose laws govern it, regardless of how it's secured or how convenient consolidation would be.

No community discussion yet for this question.