Study guide
2.6 Structuring the Privacy Team: DPO, CPO, Representatives & Resourcing
Certified Information Privacy Manager CIPM
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 CIPM Exam Facts & Format 1.2 The CIPM Body of Knowledge: Six Domains & How the Exam Is Built 1.3 Study Strategy, Timeline & How to Use This Guide
2 Domain I: Developing a Privacy Program Framework
2.1 Program Scope, Strategy & Governance Model 2.2 Stakeholders, Privacy Team Structure & Common Vocabulary 2.3 Applicable Regulations, Oversight Agencies & Non-Compliance Impact 2.4 Personal Information Sources, Cross-Border Operations & AI Privacy Risk 2.5 Business Model, Operating Environment & Risk Appetite 2.6 Structuring the Privacy Team: DPO, CPO, Representatives & Resourcing 2.7 Vision, Mission & the Privacy Program Communication Plan 2.8 Policy Access, Version Control & Role-Relevant Updates 2.9 Codes of Conduct, Certifications & Self-Certification Mechanisms
3 Domain II: Establishing Program Governance
3.1 Privacy Policies & Life-Cycle Processes 3.2 Breach, Complaint, DSR & Retention Plans 3.3 Roles, Responsibilities, Metrics & Continuous Legal Monitoring 3.4 Training & Awareness Activities 3.5 Governance Bodies, Program Charter & Escalation Paths 3.6 Governing Internal & External Data Sharing and Disclosure 3.7 Retention Schedules & Defensible Disposal 3.8 Regulatory Change Monitoring & Enforcement Systems
4 Domain III: Operational Life Cycle — Assessing Data
4.1 Data Inventories, Flows & Life-Cycle Mapping 4.2 Data Discovery, System Integrations & Keeping the Inventory Current 4.3 Policy Compliance Measurement & Gap Analysis 4.4 Processor/Vendor Evaluation & Physical/Environmental Controls 4.5 Third-Party Risk Life Cycle & Sub-Processor Chains
5 Domain III (continued): Assessing Data — Technical & Physical Controls, M&A Risk
4.6 Technical Controls, Use/Retention Limits & Data Location 4.7 Physical & Environmental Controls in Depth 4.8 Mergers, Acquisitions & Divestitures Data Risk
6 Domain IV: Operational Life Cycle — Protecting Personal Data
5.1 Information Security Practices, Data Classification & Access Controls 5.2 Privacy by Design Principles & the SDLC 5.3 Organizational Guidelines for Data Use & Secondary-Use Governance 5.4 Privacy-Enhancing Technologies & Technical Control Enforcement 5.5 Technical, Administrative & Organizational Measures 5.6 Access Reviews, Monitoring & Enforcing Technical Controls
7 Domain V: Operational Life Cycle — Sustaining Program Performance
6.1 Privacy Metrics for Program Performance 6.2 Auditing the Privacy Program 6.3 Continuous Assessment: PIA, DPIA, TIA, LIA & PTA 6.4 Risk Mitigation, Post-M&A Assessment & Ethical AI Use
8 Domain VI: Operational Life Cycle — Responding to Requests & Incidents
7.1 Data Subject Access Requests & Consent/Rights Processes 7.2 Global Privacy Legislation on Data Subject Rights 7.3 Incident Handling, Breach Response & Records 7.4 Post-Incident Review & IR Plan Improvement 7.5 Privacy Notices & Transparency Obligations 7.6 Complaint Handling & Regulator Interaction 7.7 Breach Communications to Regulators, Individuals & Other Stakeholders
9 Final Review & Exam Strategy
8.1 Mixed-Domain Scenarios & Common Exam Traps 8.2 Test-Day Logistics, Score Strategy & Credential Maintenance
2.6 Structuring the Privacy Team: DPO, CPO, Representatives & Resourcing
Key Takeaways Explain This Topic AI
GDPR Article 37 makes a DPO mandatory in three cases: public authority processing, core activities requiring regular and systematic large-scale monitoring, and core activities involving large-scale special-category or criminal-conviction data.
Articles 38-39 protect DPO independence: no instructions on how to perform the role, no dismissal or penalty for performing it, direct reporting to the highest management level, and no conflicting duties.
A CPO is a business leadership role that owns the program and budget; a DPO is a statutory advisory and monitoring role. One person can hold both only if no conflict of interest exists.
Article 27 requires a written-mandated EU representative for non-EU controllers caught by Article 3(2), with a parallel UK representative requirement under the UK GDPR.
Privacy team capacity should scale with processing complexity — jurisdictions, systems, vendors, rights volume — not with total headcount, and a privacy champion network extends reach without extending headcount.
Last updated: August 2026
Roles the Exam Expects You to Tell Apart
Performance indicator I.A.4 — define the structure of the privacy team — is tested less as an org-chart question than as a role-confusion question. The CIPM repeatedly offers distractors that assign a statutory duty to a business role, or a business decision to a statutory one.
DPO versus CPO versus privacy manager
Role Nature Core duty Who can hold it
Data Protection Officer (DPO) Statutory role under GDPR Arts. 37-39 Inform and advise, monitor compliance, advise on DPIAs, cooperate with and act as contact point for the supervisory authority Employee or external contractor; must be independent and conflict-free
Chief Privacy Officer (CPO) Business leadership role Owns the privacy program, its strategy, budget, staffing and executive relationships An executive; may sit over the DPO
Privacy manager Operational role — the CIPM's own subject Runs the operational life cycle: assessments, vendor reviews, rights workflows, incidents, metrics Reports into the CPO or DPO
Privacy champion / liaison Part-time embedded role Extends the program into a business unit; first-line triage and escalation A business-unit employee, not a privacy specialist
The most common exam trap is treating the DPO as "the person in charge of privacy." A DPO advises and monitors ; the DPO does not own the decisions being monitored. That is precisely why the roles must be separable.
When a DPO is mandatory
GDPR Article 37(1) requires a DPO in exactly three circumstances:
Processing is carried out by a public authority or body (except courts acting judicially).
Core activities consist of processing operations that, by their nature, scope or purposes, require regular and systematic monitoring of data subjects on a large scale .
Core activities consist of large-scale processing of special categories of data (Art. 9) or personal data relating to criminal convictions and offences (Art. 10).
Two words carry the weight. Core activities means the processing is part of what the organization does to achieve its purpose — a hospital's patient records are core; the hospital's own payroll is not. Large scale is not defined numerically in the regulation; regulators look at the number of data subjects, the volume and range of data, duration, and geographic extent. Note also that member-state law can impose additional DPO requirements, and Germany's threshold is famously broader than the GDPR baseline.
DPO independence — the protections that get tested
Article 38 is where scenario items live:
The DPO must be involved properly and in a timely manner in all issues relating to personal data protection.
The organization must provide the resources and access necessary, and support the DPO's ongoing expertise.
The DPO must receive no instructions regarding the exercise of their tasks.
The DPO cannot be dismissed or penalised for performing their tasks.
The DPO reports directly to the highest management level .
The DPO may hold other tasks and duties only where they create no conflict of interest .
That last clause is the classic item. A DPO who is also the Head of IT, Head of Marketing, CISO, or General Counsel is determining the purposes and means of processing they are supposed to monitor. Regulators have fined organizations over exactly this conflict. The safe structures are a standalone DPO, or an outsourced/fractional DPO for smaller organizations that cannot justify a full-time hire.
Representatives for organizations outside the EU
Article 27 requires a controller or processor not established in the Union but caught by Article 3(2) to designate, in writing , a representative established in a member state where the relevant data subjects are. The representative is the addressee for supervisory authorities and data subjects, must be identified in the privacy notice, and must maintain a copy of the record of processing activities. The narrow exemptions cover occasional processing that does not involve large-scale special-category data and is unlikely to result in risk, and public authorities. The UK GDPR imposes a parallel UK-representative requirement, so a US company selling into both the EU and the UK generally needs two representatives, not one. A representative is not a DPO — the roles, duties and appointment tests are entirely separate.
Sizing and extending the team
Privacy capacity tracks processing complexity , not headcount. The practical drivers are the number of jurisdictions, the number of in-scope systems, the vendor population, monthly rights-request volume, the release cadence that needs assessment, and the M&A pipeline.
Because headcount rarely keeps pace, the standard answer on the exam is a privacy champion network : named part-time liaisons embedded in each business unit, given targeted training, a defined escalation path, and time formally allocated by their manager. Champions triage early, flag new processing before launch, and localize training. The three failure modes are equally testable — appointing champions without allocating time, without training them, or without an escalation route to a real decision-maker.