What is the difference between data sovereignty and data residency?
Residency is where data is stored. Sovereignty is which country's laws govern it, and the two are often used together.

Exam objectiveCompare and contrast concepts and strategies to protect data
Objective 3.3 covers the concepts and strategies for protecting data through its life: what kind of data it is, how it is classified, what state it is in, where it may legally live, and which techniques protect it.
Types and classifications. Data types include regulated data (governed by law or an industry rule), trade secrets, intellectual property, legal information, financial information, and human-readable versus non-human-readable data. A binary file is not secure just because a person cannot read it. Classification labels say how carefully data must be handled: public, private, sensitive, confidential, restricted, and critical. They are not one ranked scale; critical is about availability and integrity, and sensitive is a general term that covers several others.
States and location. Data at rest is stored, data in transit is moving, and data in use is loaded in memory and usually decrypted. Data sovereignty is which country's laws govern data, and geolocation measures where something is.
Protection methods. Encryption and hashing change data mathematically: encryption can be reversed with a key, hashing cannot. Masking hides part of a value, on display or in a masked copy, tokenization swaps the value for a token mapped back only through a vault, and obfuscation makes data hard to understand but protects it far less than encryption if the method becomes known. Segmentation decides which systems can reach data at all, permission restrictions decide what a signed-in account may do, and geographic restrictions act on where access comes from.
Exam questions give a data scenario, such as card numbers in a test database or backups in another country, and ask for the classification, the data state, or the technique that fits.
This page is the map. Knotch is where you drill it until it sticks.
Tokenization removes the real value from the system and keeps it in a vault. Masking hides part of the value, either on screen or in a masked copy such as a test database, and the hidden part cannot be recovered from the masked data.
Confidential material goes to authorized groups, such as a team or department. Restricted material goes only to a short list of named people with a need to know.
Data at rest is stored on disks, databases, backups, or removable media and is protected with storage encryption. Data in use is loaded in memory and usually decrypted, so it relies on access control, enclaves, and endpoint defenses.
Segmentation decides which systems can reach the data at all. Permissions decide what an authenticated user may do once connected.
The full set of look-alike pairs for this objective is inside Knotch.
A call-center application shows agents only the last four digits of a customer's card number. The full number remains in the database for billing.
Which method does the screen use?
Masking replaces part of a value with placeholders so viewers see only what they need.
Masking limits what a viewer sees while the original can still exist elsewhere.
Why not B: Encryption changes the stored data and needs a key to read it; here the viewer simply sees a partial value.
Why not C: Tokenization replaces the value with a random token whose real value lives in a separate vault.
Why not D: A hash is one-way and could not be turned back into digits for billing.
Residency is where data is stored. Sovereignty is which country's laws govern it, and the two are often used together.
The six labels are public, private, sensitive, confidential, restricted, and critical. Real organizations use different names and levels and map them to their own scheme.
Encrypted data can be reversed with a key. A vault-based token has no key; it is mapped back to the real value through the vault.
