What is the purpose of data masking when granting CX data access?

• A. To obfuscate sensitive information in datasets accessed by users with limited privileges.
• B. To encrypt data at rest.
• C. To delete data.
• D. To accelerate processing.

Answer: (A)

Data masking is about protecting sensitive information by altering or hiding values in datasets that users with limited privileges can access. The goal is to let analysts work with realistic-looking data—same structure, formats, and data types—while preventing exposure of real, sensitive values such as personal identifiers or payment details. By masking, you can surface meaningful patterns and test or report accurately without risking privacy or compliance violations. For example, customer names might appear as initials, phone numbers could show only the last few digits, or sensitive fields might be replaced with tokens. This approach contrasts with encrypting data at rest, which protects stored data from unauthorized access but doesn’t limit what a user sees when querying data; masking operates at the access layer to ensure restricted visibility. Deleting data would remove necessary information, and masking is not primarily intended to speed up processing. Overall, masking enables safe data access for roles with limited privileges by hiding sensitive parts of the data while preserving its usability.