CIPP-E domain - 31% of the exam

European Data Protection Law and Regulation

European Data Protection Law and Regulation is 31% of the CIPP-E exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

103
Practice questions
6
Objectives
84
Medium
19
Hard

Where people go wrong

  • Treating pseudonymised data as anonymous

    The wrong answers treat data as anonymous once names are replaced by random tokens or codes, even though a lookup table or key survives. Some add that holding the key in a separate team or on a separate server takes the dataset outside the GDPR, or that a promise not to use it does. Pseudonymised data can still be attributed to a person using additional information kept separately, so it remains personal data. Only data that cannot reasonably be re-identified, once keys and raw records are destroyed, is anonymous.

    See it in a sample question
  • Letting the contract label fix controller or processor status

    The wrong answers treat a service contract as settling the role, so a vendor stays a processor, or owes only a contractual penalty, after it starts using client data for its own purposes. A processor that goes beyond instructions and determines its own purposes becomes a controller for that processing, with the matching obligations and liability. Controller and processor are functional roles, assigned by who actually decides the purposes and means, whatever the agreement says.

    See it in a sample question
  • Misplacing the defect in bundled consent

    The wrong answers locate the defect in bundled consent elsewhere: no explicit consent, an unnamed partner, no warning about withdrawal, no handwritten signature, an overlong declaration, or a supposed ban on third-party sharing. Some accept the tick box because it is an affirmative action. The defect is the bundling. Consent must be specific to each purpose, clearly distinguishable from other matters, and not made a condition of a service when the processing is unnecessary for that service.

    See it in a sample question
  • Swapping the breach notification and communication duties

    The wrong answers swap the two breach duties. They apply the high-risk threshold to the supervisory authority, treat notifying the authority as discharging the duty to tell individuals, or make communication to individuals wait for an order. Notification to the authority is required unless the breach is unlikely to result in a risk. Communication to data subjects is triggered by likely high risk and can fall away where measures such as encryption make the data unintelligible.

    See it in a sample question
  • Stretching portability to inferred data and legal-obligation records

    The wrong answers extend portability to everything held about the subscriber: analytics and play-count scores the controller derived, or billing records kept under a tax obligation. Portability covers personal data the data subject provided, including data observed from their use, processed by automated means on the basis of consent or a contract. Derived or inferred data falls outside it, as does data processed under a legal obligation, even though the access right may still reach it.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleEuropean Data Protection Law and Regulationmedium

A marketing analytics firm replaces every customer name in its dataset with a randomly generated token and stores the lookup table that links each token back to a name on a separate, access-controlled server it still owns. It tells a client that, because the working dataset now contains no names, that dataset is anonymous and falls outside the GDPR. Why is this conclusion incorrect?

  • AThe dataset is anonymous only if the lookup table is held by a third party rather than the firm itself, so ownership of the table is the deciding factor.
  • BThe dataset is anonymous because tokenisation is a recognised anonymisation technique under Article 4, so no further conditions need to be met.
  • CThe dataset becomes anonymous as soon as the firm contractually promises not to consult the lookup table, since the risk of re-identification is then removed.
  • DBecause the firm retains a key that can re-attribute the tokens to identified individuals, the data remains pseudonymous personal data and stays within the GDPR. Correct
Pseudonymous data remains personal data under the GDPR because a retained key makes re-identification reasonably possible, regardless of who holds it. The GDPR distinguishes anonymisation, which irreversibly prevents identification and removes data from scope, from pseudonymisation, where data can still be attributed to a person using separately kept additional information; retaining the lookup key means re-identification is reasonably likely, so the data stays personal.

Why A is wrong: It is tempting because separation of the key from the data is a genuine pseudonymisation safeguard, but who holds the key does not convert pseudonymous data into anonymous data; identifiability by means reasonably likely to be used is what matters.

Why B is wrong: This is a plausible confusion of two distinct concepts, but Article 4(5) treats tokenisation that retains a re-identification key as pseudonymisation, not anonymisation, so the GDPR continues to apply.

Why C is wrong: A promise not to use the key is appealing as a safeguard, but anonymisation depends on whether re-identification is reasonably possible, not on a policy commitment; the key still exists and can be used, so the data stays personal.

Why D is correct: Correct: Article 4(5) defines pseudonymisation as processing where data can still be attributed to an individual using additional information kept separately, and Recital 26 confirms pseudonymous data is personal data because re-identification remains reasonably possible.

Free sampleEuropean Data Protection Law and Regulationmedium

EDPB guidance warns that a processor which goes beyond its controller's instructions and starts determining its own purposes for the data changes its legal status. Conceptually, what does this principle illustrate about how the controller and processor roles are assigned?

  • AThe roles are fixed permanently at the start of the relationship by the contract and cannot change regardless of how the parties later behave.
  • BThe roles are assigned by the supervisory authority, which must formally re-designate a party before any change in status takes effect.
  • CThe roles are assigned by the factual circumstances of the processing, so they can change if a party's actual decision-making over purposes and means changes. Correct
  • DThe roles depend on the volume of data processed, so a party becomes a controller once it handles a large enough dataset.
Controller and processor are functional roles set by the factual reality of who decides purposes and means, so a party's status can change with its conduct. Under EDPB Guidelines 07/2020 the roles flow from the factual circumstances, not from a static label. A processor that determines its own purposes and means for the data steps outside its instructions and is treated as a controller for that processing, with the heavier obligations that follow under Article 28(10).

Why A is wrong: This contradicts the guidance. The contract documents but does not freeze the roles; if a processor later determines its own purposes the factual position overrides the original label, so treating the roles as permanently fixed is incorrect.

Why B is wrong: No regulator designation is needed for the status to change. The shift in role happens by operation of law once the facts change, so requiring a formal authority re-designation misunderstands how the roles arise.

Why C is correct: EDPB Guidelines 07/2020 treat controller and processor as functional concepts derived from the factual reality. A processor that begins determining purposes acts as a controller for that processing, showing the role follows the substance of decision-making rather than a fixed label.

Why D is wrong: Data volume affects obligations such as the need for a DPO or a DPIA, but it does not determine controller or processor status. The roles turn on who decides the purposes and means, not on how much data is involved.

Free sampleEuropean Data Protection Law and Regulationmedium

A subscription fitness app presents new users with a single tick box during sign-up that reads "I agree to the terms of service and to receiving personalised health and nutrition advertising from our partners". A user cannot complete registration without ticking it, and the partner advertising is not needed to deliver the core fitness tracking service. Under the GDPR, why is this most likely an invalid basis for processing personal data for the partner advertising?

  • AConsent is invalid because the controller failed to obtain explicit consent, which is the standard required for all marketing activities under the GDPR.
  • BConsent is invalid only because the user was not told the identity of every partner that would receive the data before ticking the box.
  • CConsent is valid because the user actively ticked the box and was therefore given a clear affirmative action that signals agreement.
  • DConsent has been bundled with acceptance of the terms of service, so it is not specific and is not freely given for the separate advertising purpose. Correct
Recognise that bundling consent for an unrelated purpose into a precondition of service makes that consent neither specific nor freely given. Valid consent under Article 7 and Recital 32 must be freely given and specific to each purpose. Tying advertising consent to a mandatory term of service removes genuine choice and merges distinct purposes, defeating both requirements regardless of the affirmative tick.

Why A is wrong: Tempting because explicit consent sounds like a higher and safer standard, but ordinary marketing does not require explicit consent under Article 9; the defect here is bundling and lack of free choice, not the absence of an explicit form of consent.

Why B is wrong: Tempting because transparency about recipients matters, but a missing recipient list is a separate information defect; even a fully informed user is denied a free and specific choice here because consent is tied to completing registration.

Why C is wrong: Tempting because a ticked box is an affirmative action, but an affirmative action alone does not cure the lack of freely given and specific consent when agreement is a non-negotiable condition of using an unrelated service.

Why D is correct: Correct: Article 7(2) requires a request for consent to be clearly distinguishable from other matters, and Recital 32 requires consent to be specific to each purpose, so bundling advertising consent into the terms of service makes it neither specific nor freely given.

Free sampleEuropean Data Protection Law and Regulationmedium

Under the GDPR, what is the risk threshold that triggers a controller's duty to notify the competent supervisory authority of a personal data breach, as distinct from the threshold for communicating to affected data subjects?

  • ANotification is required unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. Correct
  • BNotification is required only where the breach is likely to result in a high risk to the rights and freedoms of natural persons.
  • CNotification is required for every personal data breach without exception, regardless of the level of risk involved.
  • DNotification is required only where the breach involves special category data or data relating to criminal convictions.
Distinguish the 'unlikely to result in a risk' threshold for notifying the authority from the 'high risk' threshold for communicating to data subjects. Article 33 sets a low bar for reporting to the regulator, exempting only breaches unlikely to pose any risk, whereas Article 34 reserves data subject communication for breaches likely to result in a high risk, so the two duties operate at different thresholds.

Why A is correct: Article 33 requires notifying the supervisory authority unless the breach is unlikely to result in a risk, so any breach posing more than a negligible risk must be reported.

Why B is wrong: The 'high risk' threshold is the one that triggers communication to the affected data subjects, not the lower threshold that governs notification to the supervisory authority.

Why C is wrong: There is a risk-based exemption: a breach unlikely to result in any risk to individuals need not be notified to the authority, so a blanket duty overstates the obligation.

Why D is wrong: The trigger is the level of risk, not the category of data; ordinary personal data can give rise to a notifiable breach and special category data can occasionally fall below the risk threshold.

Free sampleEuropean Data Protection Law and Regulationhard

Under the GDPR, the right to data portability is narrower than the right of access. Which condition must be met for data to fall within the scope of the portability right?

  • AThe data must concern the data subject and be processed for any lawful basis, provided it is held in a structured electronic file.
  • BThe data must include inferences and profiles the controller has derived, as long as they relate to the data subject.
  • CThe data must have been provided by the data subject and be processed by automated means on the basis of consent or a contract. Correct
  • DThe data must be processed on the basis of a legal obligation and held in a commonly used machine-readable format.
Data portability covers only data provided by the subject, processed by automated means, on the basis of consent or contract. Article 20 deliberately confines portability to a subset of access: the data must be provided by the data subject, processed automatically, and rest on consent or contract, which excludes inferred data and other lawful bases.

Why A is wrong: This describes the broad reach of the access right rather than portability; portability does not extend to every lawful basis, as legitimate interests and legal obligation are excluded.

Why B is wrong: Derived or inferred data such as profiles is not 'provided by' the data subject, so the EDPB treats it as outside the portability right even though it relates to the person.

Why C is correct: Article 20 limits portability to personal data the data subject has provided, where processing is carried out by automated means and is based on consent or on a contract, so all three elements must coincide.

Why D is wrong: A legal-obligation basis is expressly excluded from portability; the machine-readable format describes how data is delivered, not which data qualifies.

Other domains in this exam

See also the CIPP-E cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by IAPP. Original, blueprint-aligned practice material only.