CDPSE By Design Principles 4 — Questions and Answers
Question 1: Under GDPR Article 25, Privacy by Design is legally required. Which action best demonstrates compliance with this obligation during product development?
- Conducting a privacy impact assessment only after product launch
- Documenting privacy controls considered and integrated during the design phase (Correct answer)
- Referring all privacy decisions to the legal department after development
- Adding a privacy policy page to the product website
Correct answer: Documenting privacy controls considered and integrated during the design phase
GDPR Article 25 requires controllers to implement appropriate technical and organizational measures at the time of design, which must be documented as evidence of compliance.
Question 2: A company wants to analyze customer purchase trends without exposing individual customer data. Which Privacy by Design technique achieves both business and privacy goals (positive-sum)?
- Storing raw transaction records indefinitely
- Using differential privacy to add statistical noise to aggregate outputs (Correct answer)
- Sharing individual purchase histories with analysts under NDA
- Removing names from records but keeping all other identifiers
Correct answer: Using differential privacy to add statistical noise to aggregate outputs
Differential privacy allows meaningful statistical analysis while mathematically limiting the ability to infer any individual's data, achieving both functionality and privacy.
Question 3: Which Privacy by Design principle is most directly supported by publishing an organization's privacy architecture and data flow documentation to stakeholders?
- Full Lifecycle Protection
- Privacy as the Default
- Visibility and Transparency — Keep it Open (Correct answer)
- Proactive not Reactive
Correct answer: Visibility and Transparency — Keep it Open
Visibility and Transparency requires that organizations openly communicate their privacy practices, architectures, and policies so stakeholders can verify claims.
Question 4: An organization uses a single system to process both highly sensitive health data and general marketing preferences. A privacy architect proposes separating these into distinct systems. This addresses which risk?
- Lack of data minimization
- Insufficient user consent mechanisms
- Aggregation risk and data contamination across contexts (Correct answer)
- Inadequate access logging
Correct answer: Aggregation risk and data contamination across contexts
Separating systems prevents aggregation risk, where combining disparate data types creates a more sensitive profile than any single dataset would represent.
Question 5: When implementing Privacy by Design in a microservices architecture, which approach best supports the 'Embedded into Design' principle?
- Adding a centralized privacy proxy in front of all services post-deployment
- Defining privacy contracts and data handling rules within each service's API specification (Correct answer)
- Requiring all services to log to a central compliance database
- Auditing services quarterly for privacy compliance
Correct answer: Defining privacy contracts and data handling rules within each service's API specification
Defining privacy handling within each service's API specification makes privacy a first-class architectural concern rather than an external enforcement layer.
Question 6: A privacy engineer is evaluating two database architectures: one stores full PII for analytics, the other stores only hashed identifiers with separate re-identification keys held by a different team. Which principle does the second architecture embody?
- End-to-End Security
- Separation of Duties combined with Pseudonymization (Correct answer)
- Full Functionality
- Visibility and Transparency
Correct answer: Separation of Duties combined with Pseudonymization
Pseudonymization combined with separation of duties ensures that no single team can re-identify individuals, reducing insider threat and unauthorized linkage.
Question 7: Which statement best describes how Privacy by Design addresses the tension between innovation and privacy compliance?
- Privacy by Design slows innovation by mandating compliance reviews before any development
- Privacy by Design resolves the tension by proving both can be achieved simultaneously through positive-sum design (Correct answer)
- Privacy by Design prioritizes compliance over functionality in all cases
- Privacy by Design defers privacy requirements to post-launch regulatory review
Correct answer: Privacy by Design resolves the tension by proving both can be achieved simultaneously through positive-sum design
The Positive-Sum principle explicitly rejects false trade-offs, showing that innovative and privacy-respecting systems are mutually achievable.
CDPSE By Design Principles 4
Under GDPR Article 25, Privacy by Design is legally required.
Which action best demonstrates compliance with this obligation during product development?