IT Cert Ready

ISACA

CDPSE

Certified Data Privacy Solutions Engineer

Start practicing

About this certification

CDPSE (Certified Data Privacy Solutions Engineer) is a ISACA certification. IT Cert Ready offers 1,644 practice questions with domain quizzes, full mock exams, and detailed explanations. Practice by official domain with 4 blueprint-aligned domains.

Official exam domain weights

Verified blueprint weights from the official exam outline.

  • Domain 1 · Privacy Governance · 20%
  • Domain 2 · Privacy Risk Management and Compliance · 18%
  • Domain 3 · Data Life Cycle Management · 23%
  • Domain 4 · Privacy Engineering · 39%

Sample CDPSE practice questions

Preview realistic multiple-choice items from the IT Cert Ready question bank. Expand each answer for the correct choice and explanation—the same format used in domain quizzes and mock exams.

  1. Sample question 1 · Data Life Cycle Management (23%)

    Vantara Media Group, a mid-sized digital news publisher operating across the EU and UK, collects granular audience behavioral data—including article dwell time, scroll depth, device fingerprints, and inferred political interests—to power its programmatic advertising platform. Following a routine internal review, the privacy engineering team discovers that anonymized audience analytics datasets retained for 36 months still contain quasi-identifiers (postal district, device type, and inferred age bracket) that, when combined, re-identify approximately 12% of records against a publicly available voter registry. The analytics vendor contract requires 30 days' notice before any dataset schema changes. The Chief Revenue Officer argues that removing the quasi-identifiers will degrade ad-targeting revenue by an estimated 18% and requests a 90-day delay before any remediation. The privacy team must decide on an immediate course of action. As the privacy engineer at Vantara Media Group, what should you do FIRST in response to this finding?

    • A. Accept the Chief Revenue Officer's 90-day delay request and document the business justification in the risk register while monitoring for any regulatory inquiries.
    • B. Immediately suppress the re-identifiable records from active analytics processing, escalate the re-identification risk to the Data Protection Officer and senior leadership, and initiate a formal data minimization remediation plan with defined milestones.
    • C. Notify the analytics vendor of the schema change requirement and wait for the 30-day contractual notice period to expire before taking any action on the datasets.
    • D. Apply pseudonymization tokens to the quasi-identifier fields and continue using the datasets for ad targeting while the longer-term remediation plan is developed.
    View answer & explanation

    Correct answer: B. Immediately suppress the re-identifiable records from active analytics processing, escalate the re-identification risk to the Data Protection Officer and senior leadership, and initiate a formal data minimization remediation plan with defined milestones.

    [Domain 3 - Data Life Cycle Management, Subtopic 3B - Data Persistence and Destruction - Area 1 - Data Minimization] Core Concept: Data minimization requires that personal data be adequate, relevant, and limited to what is necessary for the specified purpose. When retained analytics data is found to enable re-identification of individuals, the organization has a continuing obligation under GDPR Article 5(1)(c) to remediate the over-retention immediately, and accountability principles (Article 5(2)) require that the risk be escalated and documented with appropriate governance oversight rather than deferred for commercial reasons. Correct Answer (B): Suppressing re-identifiable records from active processing stops ongoing harm while the remediation plan is formalized. Escalating to the DPO and senior leadership satisfies the accountability and transparency obligations under GDPR and ensures that the privacy risk is not subordinated to revenue considerations without proper governance sign-off. Correct Answer (B): Correct Answer (B): Establishing a remediation plan with milestones demonstrates proactive compliance and supports defensibility with regulators. Why the other options are incorrect: Why the other options are incorrect: Why the other options are incorrect: Option A: : : Accepting a 90-day delay without halting active use of re-identifiable data allows continued processing that likely violates GDPR's data minimization and purpose limitation principles; documenting a business justification does not cure an ongoing legal non-compliance. Option C: : : Waiting for the vendor's contractual notice period to expire before acting conflates a vendor change-management clause with the organization's own legal obligation to stop unlawful processing; the contract does not override data protection law. Option D: : : Applying pseudonymization to quasi-identifiers while continuing ad-targeting use does not address the root cause—the datasets already enable re-identification—and continuing to use them for behavioral profiling without remediation perpetuates the minimization violation.

  2. Sample question 2 · Data Life Cycle Management (23%)

    Nexaform Systems, a large South Korean electronics manufacturer with operations in the EU and Southeast Asia, deploys IoT-connected quality control cameras on its production lines. Camera footage is processed by an AI-based defect detection engine operated by a local vendor, Daewon Analytics. Under the processing agreement, footage is retained for 90 days for model retraining purposes. During a scheduled vendor audit, the privacy engineer discovers that Daewon Analytics has been archiving footage beyond the 90-day window—some files dating back 22 months—citing a contractual ambiguity around 'model improvement cycles.' Three days after the audit finding is documented, a ransomware attack encrypts Daewon Analytics' archive servers, potentially affecting the over-retained footage. The privacy engineer must determine the escalation sequence and whether the incident triggers notification obligations under the EU GDPR, given that the manufacturer's EU subsidiary is the data controller. As the privacy engineer for Nexaform Systems' EU subsidiary, what is the MOST appropriate escalation and notification sequence following the ransomware attack on Daewon Analytics' servers containing over-retained production footage?

    • A. Delay supervisory authority notification until Daewon Analytics completes its internal forensic investigation, as the controller cannot confirm the scope of affected data without vendor findings.
    • B. Notify all data subjects depicted in the production footage immediately, as GDPR Article 34 requires individual notification whenever encrypted personal data is involved in a ransomware attack.
    • C. Notify the lead supervisory authority within 72 hours of the ransomware attack becoming known to the controller, document the over-retention as an aggravating factor in the breach record, instruct Daewon Analytics to isolate affected systems and provide a forensic impact assessment, and initiate contract remediation to eliminate the retention ambiguity.
    • D. Treat the incident as a vendor operational matter and require Daewon Analytics to manage all regulatory notifications independently, since the breach occurred on the processor's infrastructure.
    View answer & explanation

    Correct answer: C. Notify the lead supervisory authority within 72 hours of the ransomware attack becoming known to the controller, document the over-retention as an aggravating factor in the breach record, instruct Daewon Analytics to isolate affected systems and provide a forensic impact assessment, and initiate contract remediation to eliminate the retention ambiguity.

    [Domain 3 - Data Life Cycle Management, Subtopic 3B - Data Persistence and Destruction - Area 1 - Data Minimization] Core Concept: GDPR Article 33 requires the data controller to notify the competent supervisory authority within 72 hours of becoming aware of a personal data breach, unless the breach is unlikely to result in a risk to individuals' rights and freedoms. The over-retention of footage beyond the agreed 90-day window is itself a data minimization and storage limitation violation under Article 5(1)(e), and it directly amplifies the scope and risk of the ransomware breach. Controllers remain accountable for processor conduct and cannot delegate regulatory notification obligations to processors. Correct Answer (C): Notifying the lead supervisory authority within 72 hours of the controller becoming aware of the breach satisfies GDPR Article 33, even if the full scope is not yet known—the notification can be phased. Documenting the over-retention as an aggravating factor ensures transparency and fairness in the breach record, and directing Daewon Analytics to isolate systems and provide forensic findings supports the controller's accountability obligation. Correct Answer (C): Correct Answer (C): Initiating contract remediation addresses the root cause of the retention ambiguity that enabled the over-retention. Why the other options are incorrect: Why the other options are incorrect: Why the other options are incorrect: Option A: : : GDPR Article 33 does not permit the controller to delay supervisory authority notification pending completion of a processor's internal investigation; the 72-hour clock runs from when the controller becomes aware, and initial notification can be submitted with incomplete information. Option B: : : GDPR Article 34 requires individual notification only when the breach is likely to result in a high risk to individuals' rights and freedoms; this determination requires a risk assessment and is not automatic simply because encrypted data is involved in a ransomware attack. Option D: : : As the data controller, Nexaform's EU subsidiary bears primary regulatory accountability under GDPR and cannot transfer notification obligations to the processor; the processor's role is to assist the controller, not to independently manage supervisory authority communications on the controller's behalf.

  3. Sample question 3 · Data Life Cycle Management (23%)

    Prismwave Digital, a small independent podcast network based in the Netherlands with approximately 40 employees, uses a third-party audience analytics platform called ListenMetrics to process listener engagement data. ListenMetrics anonymizes listener records by stripping direct identifiers and retaining hashed device IDs, episode completion percentages, and geographic region at the city level. Prismwave's privacy engineer learns from an industry alert that ListenMetrics suffered a configuration error six weeks ago that caused raw, un-anonymized listener records—including IP addresses and email addresses from newsletter sign-ups—to be written to a shared analytics export bucket accessible to all ListenMetrics customers. Prismwave's own listener data was included in the exposed bucket for approximately 11 days before ListenMetrics corrected the error. ListenMetrics notified Prismwave only after the privacy engineer independently discovered the alert. Prismwave's DPA notification obligation under GDPR Article 33 requires reporting within 72 hours of becoming aware of a personal data breach. The privacy engineer must determine the appropriate escalation and disclosure path. As the privacy engineer at Prismwave Digital, which course of action BEST fulfills your accountability, transparency, and data life cycle obligations given the delayed vendor notification?

    • A. Treat the incident as the vendor's responsibility since ListenMetrics caused the exposure, and wait for ListenMetrics to file the regulatory notification on Prismwave's behalf before taking further action.
    • B. Immediately assess the scope of Prismwave listener data exposed, escalate to the DPO and senior management, and submit a GDPR Article 33 notification to the Dutch Autoriteit Persoonsgegevens within 72 hours of Prismwave's own discovery of the breach, documenting the vendor's delayed notification as a contributing factor.
    • C. Conduct a full internal investigation over the next two weeks to precisely quantify the number of affected listeners before filing any regulatory notification, to ensure the report is complete and accurate.
    • D. Notify affected listeners directly via email before filing any regulatory notification, to demonstrate transparency and good faith to the Dutch supervisory authority.
    View answer & explanation

    Correct answer: B. Immediately assess the scope of Prismwave listener data exposed, escalate to the DPO and senior management, and submit a GDPR Article 33 notification to the Dutch Autoriteit Persoonsgegevens within 72 hours of Prismwave's own discovery of the breach, documenting the vendor's delayed notification as a contributing factor.

    [Domain 3 - Data Life Cycle Management, Subtopic 3B - Data Persistence and Destruction - Area 1 - Data Minimization] Core Concept: Accountability and transparency throughout the data life cycle extend to breach incidents involving third-party processors: as the data controller, Prismwave Digital retains full regulatory responsibility for personal data processed on its behalf, regardless of which party caused the exposure. GDPR Article 33 requires the controller to notify the competent supervisory authority within 72 hours of becoming aware of a breach, and Article 28 requires that processors notify controllers without undue delay—a requirement ListenMetrics violated. The 72-hour clock runs from the controller's own awareness, not from when the processor chooses to notify. Correct Answer (B): Prismwave's 72-hour notification obligation under GDPR Article 33 began when the privacy engineer independently discovered the breach, not when ListenMetrics eventually notified them. Immediately assessing scope, escalating internally, and filing with the Autoriteit Persoonsgegevens within the statutory window—while documenting the vendor's delayed notification—fulfills the controller's accountability obligations and creates a defensible record. Correct Answer (B): Correct Answer (B): The notification may be submitted with information available at the time and supplemented later if the full scope is not yet known. Why the other options are incorrect: Why the other options are incorrect: Why the other options are incorrect: Option A: : : As the data controller, Prismwave cannot delegate its GDPR Article 33 notification obligation to its processor; ListenMetrics is a processor and has no authority to file a supervisory authority notification on the controller's behalf, and waiting for the vendor to act would almost certainly result in a missed statutory deadline. Option C: : : Waiting two weeks to complete a full investigation before notifying the supervisory authority directly violates the 72-hour requirement under GDPR Article 33; the regulation explicitly permits phased notifications when complete information is not yet available, making a delay for completeness unjustifiable. Option D: : : Notifying affected individuals directly before the supervisory authority is not the prescribed sequence under GDPR; Article 33 notification to the supervisory authority takes precedence, and Article 34 notification to data subjects is a separate, subsequent obligation triggered only when the breach is likely to result in a high risk to individuals' rights and freedoms.

  4. Sample question 4 · Data Life Cycle Management (23%)

    Nordex Freight, a small regional logistics operator in Norway with 85 employees, recently onboarded a cloud-based fleet management SaaS provider called TrackNow Ltd., incorporated in Ireland. The contract was executed as a standard click-through SaaS agreement with no negotiated data processing addendum. TrackNow's default terms state that customer data is retained for the lifetime of the subscription plus five years post-termination for 'audit and dispute resolution purposes.' Nordex's drivers are subject to Norwegian working environment regulations that restrict continuous electronic monitoring, and the company's own internal policy commits to deleting location data after 60 days. A privacy engineer joining Nordex discovers this misalignment during an onboarding review. TrackNow has not provided a record of processing activities (RoPA) entry or a sub-processor list to Nordex. Which action should the privacy engineer at Nordex Freight take to MOST effectively promote accountability and transparency in the data life cycle with respect to the TrackNow vendor relationship?

    • A. Instruct Nordex's IT team to configure TrackNow's data export feature to pull and locally delete all driver data every 60 days, treating this as equivalent to vendor-side deletion.
    • B. Negotiate and execute a GDPR-compliant data processing agreement with TrackNow that specifies a 60-day retention limit aligned with Nordex's policy, requires disclosure of sub-processors, and obligates TrackNow to support Nordex's RoPA obligations.
    • C. File a complaint with Datatilsynet (the Norwegian DPA) regarding TrackNow's non-compliant default retention terms before attempting to renegotiate the contract.
    • D. Migrate to a different SaaS provider that offers a pre-negotiated DPA, as click-through agreements cannot be modified and therefore cannot satisfy GDPR Article 28 requirements.
    View answer & explanation

    Correct answer: B. Negotiate and execute a GDPR-compliant data processing agreement with TrackNow that specifies a 60-day retention limit aligned with Nordex's policy, requires disclosure of sub-processors, and obligates TrackNow to support Nordex's RoPA obligations.

    [Domain 3 - Data Life Cycle Management, Subtopic 3B - Data Persistence and Destruction - Area 1 - Data Minimization] Core Concept: GDPR Article 28 mandates that controllers engage processors only under a binding contract that sets out the subject matter, duration, nature, and purpose of processing, including specific retention obligations. A standard click-through SaaS agreement without a negotiated DPA does not satisfy this requirement. Accountability and transparency throughout the data life cycle require that vendor contracts explicitly govern retention periods, sub-processor disclosure, and support for the controller's own compliance obligations such as maintaining a RoPA. Correct Answer (B): Negotiating a GDPR-compliant DPA with TrackNow is the most effective action because it directly establishes the legal framework required under Article 28, aligns vendor retention to Nordex's 60-day policy, and creates enforceable obligations around sub-processor transparency and RoPA support. Correct Answer (B): Correct Answer (B): This approach addresses the accountability gap at its root — the absence of a binding processor agreement — and promotes transparency by ensuring all parties understand their data life cycle obligations. Why the other options are incorrect: Why the other options are incorrect: Why the other options are incorrect: Option A: : : Exporting data locally every 60 days does not delete data from TrackNow's servers; it only creates a local copy. TrackNow would continue to retain the data under its five-year default term, leaving the minimization and accountability gap unresolved on the vendor side. Option C: : : Filing a regulatory complaint before attempting contractual remediation is premature and disproportionate for a gap that can be addressed through negotiation. Regulators generally expect controllers to first take reasonable steps to achieve compliance before escalating to enforcement bodies. Option D: : : Click-through agreements can be supplemented or replaced with negotiated DPAs; many SaaS vendors, including those operating under Irish law, offer DPA addenda upon request. Migrating to a new provider without first attempting negotiation is an unnecessarily disruptive and costly response to a contractual gap that is routinely resolved through standard procurement processes.

  5. Sample question 5 · Data Life Cycle Management (23%)

    Orbitex Cloud, a European-headquartered technology firm with operations in Germany and the Netherlands, uses a U.S.-based SaaS payroll platform called PaySphere to process employee personal data including salary, tax identifiers, and bank account details. Orbitex's privacy engineer is reviewing PaySphere's SLA and discovers that PaySphere's contract guarantees data deletion within 180 days of contract termination but does not address backup media containing personal data. PaySphere's standard SLA also lacks any provision for data subjects to request deletion of their records during the active contract period. Orbitex is subject to GDPR and must ensure its vendor relationships uphold data subject rights and transparent data handling. Which contractual gap presents the GREATEST risk to Orbitex's ability to promote fairness and transparency under GDPR, and what should the privacy engineer prioritize addressing first?

    • A. The 180-day post-termination deletion window, which should be shortened to 30 days to align with GDPR storage limitation principles.
    • B. The absence of a provision enabling Orbitex to pass through data subject erasure requests to PaySphere during the active contract, which directly undermines GDPR Article 17 rights and Orbitex's accountability as a data controller.
    • C. The lack of a data breach notification clause in the SLA, which must be added before any other contractual deficiency is addressed.
    • D. PaySphere's status as a U.S.-based processor, which requires Orbitex to immediately suspend data transfers until Standard Contractual Clauses are signed.
    View answer & explanation

    Correct answer: B. The absence of a provision enabling Orbitex to pass through data subject erasure requests to PaySphere during the active contract, which directly undermines GDPR Article 17 rights and Orbitex's accountability as a data controller.

    [Domain 3 - Data Life Cycle Management, Subtopic 3B - Data Persistence and Destruction - Area 1 - Data Minimization] Core Concept: Fairness and transparency under GDPR require that data controllers ensure processors can operationally support data subject rights, including the right to erasure under Article 17. A processor contract that does not include a mechanism for the controller to submit and track erasure requests creates a structural accountability failure: the controller cannot fulfill its legal obligations to data subjects even if it wishes to do so. GDPR Article 28(3)(e) explicitly requires processor agreements to assist the controller in responding to data subject requests. Correct Answer (B): The absence of an erasure request pass-through mechanism is the most critical gap because it directly prevents Orbitex from fulfilling its GDPR obligations to data subjects during the active contract period — a continuous, ongoing risk rather than a post-termination concern. Correct Answer (B): Correct Answer (B): Without this provision, Orbitex cannot demonstrate accountability or fairness to employees whose data is processed by PaySphere, making this the highest-priority remediation item. Why the other options are incorrect: Why the other options are incorrect: Why the other options are incorrect: Option A: : : While 180 days may be longer than ideal, GDPR does not prescribe a specific post-termination deletion window; the more urgent gap is the inability to honor active data subject rights, which is a continuous compliance failure rather than a one-time end-of-contract issue. Option C: : : A breach notification clause is important but is a separate GDPR Article 33 obligation; it does not directly affect the fairness and transparency of ongoing data subject rights management, which is the scenario's focal concern. Option D: : : Suspending data transfers immediately is a disproportionate response without first confirming whether a transfer mechanism already exists; the scenario does not state that SCCs are absent, and suspension would disrupt payroll operations without resolving the identified contractual gap.

CDPSE exam prep FAQ

What is the passing score for the CDPSE exam?
Passing scores for CDPSE are set by ISACA and can change between exam versions. Check the latest official exam outline on the ISACA website for the current passing standard.
How many questions are on the CDPSE certification exam?
Official CDPSE exam length and item types are defined by ISACA. Review the current exam blueprint for the latest question counts and timing.
How do domain quizzes help with CDPSE exam prep?
Domain quizzes on IT Cert Ready let you practice CDPSE one blueprint domain at a time across 4 official exam domains. You get immediate feedback, detailed explanations, and can revisit weak areas before taking a full timed mock exam.
How many CDPSE practice questions are on IT Cert Ready?
IT Cert Ready includes 1,644 published CDPSE practice questions with domain quizzes, full-length mock exams, and answer explanations mapped to the official outline.