What Is the Best Method to Protect Customer Data for Analysis?
What is the BEST method to protect customers’ personal data that is forwarded to a central system for analysis?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
What is tested is the difference between reversible de-identification (pseudonymization) and irreversible de-identification (anonymization), plus encryption's practical limits. The trap is confusing pseudonymization with anonymization or assuming encryption lets you analyze the data directly.
CDPSE candidates overwhelmingly select pseudonymization when protecting personal data forwarded for central-system analysis. This guide explains why pseudonymization balances privacy with analytical utility and why encryption, deletion, and anonymization are less appropriate in this scenario.
Choosing D (Anonymization) is a common mistake because anonymous data sounds strongest for privacy, but anonymization irreversibly severs the link to individual customers and often destroys the record-level utility the central system needs. Encryption may also be a tempting wrong answer because it is a familiar security control, but it prevents meaningful analysis without forcing costly decryption.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Pseudonymization (A) is the best method because it replaces direct identifiers with pseudonyms while preserving the data’s structure and usability for analysis. A central system can perform analytics and link records for a user without exposing the person’s actual identity. This matches the community consensus: comment [1] correctly explains that encrypted data cannot be practically analyzed, and comment [3] simply affirms with three likes that the answer is A.
Why the Other Options Are Wrong
Encryption (C) protects data at rest and in transit, but the server receiving the data must decrypt it before typical analysis, temporarily exposing the personal data. Deletion (B) defeats the entire purpose of forwarding data for analysis. Anonymization (D) is often confused with pseudonymization, but it irreversibly prevents identifying individuals, which can make certain per-customer and longitudinal analyses impossible. Comment [2] incorrectly lumps pseudonymization under anonymization, but GDPR and ISACA distinguish between pseudonymisation, which keeps data personal yet protected, and anonymisation, which removes it from the scope of data-protection regulation.
Community Comment Notes
The highest-voted comments clearly support A, with comment [3] scoring 3 likes and comment [1] scoring 2 likes and highlighting why encryption is not a workable analytics solution. Comment [2] presents a dissenting view, but it is based on a definitional misunderstanding. For CDPSE, remember that pseudonymization is not itself a form of anonymization; it is a separate privacy-enhancing technique with its own legal definitions and use cases.
Official Reference
Exam Strategy
When a data-protection question involves processing or analysis of personal data, look for the option that keeps the data functional while masking identity. Ask yourself whether the technique must be reversible and whether the data still has analytical value under that technique; pseudonymization is usually the right answer when you need to analyze records while protecting data subjects.
Related Analysis
Practice All CDPSE Questions
Access 229 questions with complete answers and detailed explanations.
View Full CDPSE Practice Test →