Browse Certification Practice Tests by Exam Family

IAPP CIPT Sample Questions & Practice Test

Try 12 Certified Information Privacy Technologist (CIPT) sample questions on privacy engineering, data minimization, security controls, identity, telemetry, and privacy by design.

Certified Information Privacy Technologist (CIPT) preparation focuses on how privacy requirements become technical design choices: minimization, identity, consent, telemetry, access control, retention, security, and privacy by design.

Use these 12 original sample questions for initial self-assessment. They are not official IAPP questions and do not reproduce a live exam.

What this route should test

  • privacy by design, data minimization, secure engineering, and lifecycle thinking
  • technical controls for collection, use, sharing, retention, deletion, identity, and telemetry
  • translating privacy requirements into system and product decisions

Official-source check

Verify current certification names, exam policies, and requirements with the IAPP certification page .

Sample Exam Questions

Question 1

Topic: privacy by design

Which design choice best reflects privacy by design?

  • A. Collect every possible field because storage is cheap
  • B. Add privacy review only after launch
  • C. Define privacy requirements early, collect only needed data, and build controls into the workflow
  • D. Treat privacy as only a legal notice

Best answer: C

Explanation: Privacy by design means privacy requirements are part of architecture, data flows, controls, and product decisions from the start.


Question 2

Topic: minimization

A mobile app requests location access even though its core function does not require location. What is the best privacy engineering concern?

  • A. The request may violate data minimization and purpose limitation expectations
  • B. The app will always be faster
  • C. Location data is never personal data
  • D. The request eliminates security risk

Best answer: A

Explanation: Privacy engineering should challenge unnecessary collection and align data with a defined purpose.


Question 3

Topic: retention

What is a strong technical support for retention limits?

  • A. Keeping all personal data forever
  • B. Asking engineers to remember manually
  • C. Removing all metadata
  • D. Automated retention rules, deletion workflows, audit logs, and exception handling

Best answer: D

Explanation: Retention requirements are stronger when systems enforce lifecycle rules and record exceptions.


Question 4

Topic: access control

Which control best supports least privilege for personal data?

  • A. Shared administrator passwords
  • B. Role-based access, periodic access review, and logging of sensitive data access
  • C. Public database exports
  • D. Access granted by default to every employee

Best answer: B

Explanation: Least privilege requires appropriate access, review, and monitoring.


Question 5

Topic: de-identification

Why is pseudonymization not the same as anonymization?

  • A. Pseudonymized data is always public
  • B. Pseudonymized data may still be linkable to a person with additional information
  • C. Anonymization keeps direct identifiers intact
  • D. There is no privacy difference

Best answer: B

Explanation: Pseudonymization reduces direct identifiability but may remain personal data depending on re-identification risk.


Question 6

Topic: telemetry

A product team wants to collect detailed user telemetry. What should privacy engineering ask first?

  • A. Whether the dashboard colors are attractive
  • B. How to collect more fields than needed
  • C. What purpose requires the data, what granularity is necessary, and how long it will be retained
  • D. How to avoid documentation

Best answer: C

Explanation: Telemetry should be purpose-bound, minimized, protected, and governed through retention and access controls.


Question 7

Topic: consent implementation

What makes a consent preference center technically useful?

  • A. Preferences are captured, honored across systems, auditable, and easy to change
  • B. Preferences are stored but ignored
  • C. Users cannot withdraw choices
  • D. The system loses the source of consent

Best answer: A

Explanation: Consent systems must operationalize choices across downstream systems and preserve evidence.


Question 8

Topic: secure transmission

Why encrypt personal data in transit?

  • A. To eliminate the need for authentication
  • B. To make retention unnecessary
  • C. To make data anonymous
  • D. To reduce interception risk while data moves between systems or users

Best answer: D

Explanation: Encryption in transit protects confidentiality during communication but does not replace other privacy controls.


Question 9

Topic: data mapping

Why do engineers need data-flow maps for privacy work?

  • A. To understand collection points, storage, processors, transfers, APIs, retention, and deletion dependencies
  • B. To avoid documenting systems
  • C. To remove all product requirements
  • D. To make databases slower

Best answer: A

Explanation: Data-flow maps reveal where privacy controls must operate.


Question 10

Topic: logging

Which logging approach is most privacy-aware?

  • A. Log full personal records for every event
  • B. Make logs publicly searchable
  • C. Log only necessary fields, protect logs, limit retention, and avoid sensitive values when possible
  • D. Keep logs forever with no access control

Best answer: C

Explanation: Logs are useful for security and operations but can become privacy risk if over-collected or under-protected.


Question 11

Topic: deletion

A user deletion request is approved. Which technical issue most often creates risk?

  • A. The user’s spelling preference
  • B. The color of the delete button
  • C. The lack of a marketing slogan
  • D. Downstream replicas, backups, analytics stores, and vendors may still hold data

Best answer: D

Explanation: Privacy engineering must account for distributed data copies and deletion dependencies.


Question 12

Topic: threat modeling

How does privacy threat modeling help product teams?

  • A. It replaces legal review
  • B. It identifies misuse, exposure, inference, collection, retention, and user-harm scenarios before release
  • C. It proves all risks are impossible
  • D. It focuses only on interface colors

Best answer: B

Explanation: Privacy threat modeling extends security thinking to privacy harms and system misuse.

Revised on Thursday, May 21, 2026