A jurisdiction requiring an organization to place a link on the website that allows a consumer to opt-out of sharing is an example of what type of requirement?
Answer(s): A
JustificationFunctional (Correct) – The requirement specifies what the system must do : provide a consumer-facing link that enables opt-out of data sharing. This describes a distinct business/functionality function that the application must deliver, which is the definition of a functional requirement.Operational (Incorrect) – It would be operational only if the focus were on the process for handling opt-out requests (e.g., staff procedures, escalation workflows). The wording here targets the existence of a UI link, not the operational workflow.Technical (Incorrect) – A technical requirement would detail how the link is implemented (e.g., using a specific API, encryption standards, or server configuration). The statement does not reference any implementation specifics.Use case (Incorrect) – A use-case description narrates a scenario from the user’s perspective (“As a consumer, I click a link to opt out of sharing”). The question asks for the type of requirement in a regulatory context, which aligns with a functional requirement rather than a narrative use-case definition.Conclusion: The mandate to expose an opt-out link on a website is best classified as a functional requirement because it defines a concrete piece of functionality the system must provide.
International Association of Privacy Professionals (IAPP), Certified Information Privacy Technologist (CIPT) Body of Knowledge (2023). https://iapp.org/certified-privacy-technologist/ NIST Special Publication 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations (2020), Section PL-2 “Consent and Opt-Out”. https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final— End of response—
Which of the following is the LEAST effective at meeting the Fair Information Practice Principles (FIPPs) in the Systems Development Life Cycle (SDLC)?
Answer(s): D
Why option D is the least effective at supporting the Fair Information Practice Principles (FIPPs) during SDLCScope of impact – Conducting privacy threat modeling (A) directly addresses purpose limitation, data minimization, and security by identifying how personal data is collected, used, and shared. This activity embeds FIPPs early in design, ensuring that privacy considerations are baked into the system architecture. Compliance with coding standards (B) enforces data protection and security controls at the implementation level, helping to meet the security and integrity aspects of FIPPs through consistent, vetted development practices. Data-flow modeling (C) maps the movement of sensitive data across components, clarifying collection, use, retention, and transfer boundaries. This explicit mapping is a core technique for demonstrating compliance with purpose, minimization, and retention principles. OWASP Top 10 review (D) focuses primarily on technical vulnerabilities and attack surface reduction. While important for security, it does not systematically address the broader FIPPs such as purpose specification, user consent, data subject rights, or retention policies. Consequently, it offers the narrowest alignment with the holistic privacy objectives of FIPPs within the SDLC.Why the other options are more suitableA integrates privacy risk analysis into the design phase, directly supporting purpose and control principles. B ensures that secure coding mitigates data exposure, reinforcing security and integrity under FIPPs.C provides a visual, traceable map of data handling, enabling explicit management of collection, use, and retention obligations. D , though valuable for hardening security, is primarily a security-focused checklist and does not guarantee adherence to the full spectrum of privacy principles.Conclusion – Therefore, reviewing code against the OWASP Top 10 (option D) is the least effective method for ensuring FIPPs are met throughout the SDLC, as it lacks explicit linkage to purpose, consent, and data-subject rights that the other practices address.
IAPP CIPT Official Guide – Privacy in the Software Development Lifecycle: https://iapp.org/certify/cielt/CIPT/ NIST Privacy Framework – Managing Privacy Risks in New Technologies: https://www.nist.gov/itl/applied-cybersecurity-center/nist-privacy-frameworkThese documents provide detailed guidance on integrating privacy considerations (including threat modeling, data-flow analysis, and secure coding) into each phase of the SDLC, supporting the rationale above.
An organization is launching a smart watch which, in addition to alerts, will notify the wearer of incoming calls allowing them to answer on the device. This convenience also comes with privacy concerns and is an example of?
Answer(s): B
Why B – Ubiquitous computing is the best choiceThe smartwatch embeds computational capabilities directly into a personal, wearable item that the user interacts with throughout daily activities, illustrating the core idea of computing that is “everywhere” and seamlessly integrated into ordinary objects. This integration raises privacy concerns because the device continuously senses and communicates contextual data (e.g., call notifications) without requiring explicit user interaction, a hallmark of ubiquitous computing environments.Why the other options are less appropriateAnthropomorphism (C) – Refers to attributing human traits to non-human entities; a watch that simply delivers alerts does not personify itself. Value-Sensitive Design (A) – Describes a design methodology that incorporates stakeholder values into technology; it is a process, not the phenomenon described by the scenario. Coupling (D) – Pertains to the degree of interdependence between system components; the question does not address system architecture interrelations.Conclusion The described scenario exemplifies ubiquitous computing , where computational functions are woven into everyday artifacts, leading to pervasive data collection and privacy considerations.
“Ubiquitous Computing” – Wikipedia, https://en.wikipedia.org/wiki/Ubiquitous_computing NIST Definition of “Ubiquitous Computing” (NISTIR 7563), https://doi.org/10.6028/NIST.IR.7563
What is the main issue pertaining to data protection with the use of 'deep fakes'?
Answer(s): B – Non-conformity with the accuracy principleCore data-protection relevance – Under most modern privacy frameworks (e.g., GDPR Art. 5(1)(c), ISO 27701, APPI), personal data must be accurate and kept up-to-date. Deep-fake generation deliberately creates synthetic media that mimics real persons or events but is factually false. Because the fabricated content can be indistinguishable from genuine material, it fails the accuracy requirement and can be treated as inaccurate personal data (especially when it involves biometric or identifying data). Why “misinformation” (A) is secondary – While deep-fakes can spread misinformation, data-protection law does not evaluate truthfulness as a primary criterion; it focuses on whether the data subject’s personal information reflects reality. Misleading information may be a societal concern, but it does not directly breach a data-protection principle unless it compromises the accuracy obligation. Why “non-repudiation” (C) is not the primary issue – Non-repudiation pertains to proof of origin and integrity in transactional or legal contexts (e.g., digital signatures, audit trails). Deep-fakes may undermine evidentiary confidence, but that is a broader forensic or legal challenge rather than a direct violation of a data-protection principle. Why “confidentiality” (D) is unrelated – Confidentiality concerns unauthorized disclosure or access. Deep-fake production often relies on public or harvested data and does not inherently expose private information; the core protection gap lies elsewhere—namely, the fidelity of the data itself.Thus, the main data-protection issue with deep-fakes is their non-conformity with the accuracy principle, because they introduce deliberately false personal data that can misrepresent individuals and violate statutory obligations to keep personal data accurate.
EU General Data Protection Regulation (GDPR), Art. 5(1)(c) – Accuracy: https://eur-lex.europa.eu/eli/reg/2016/679/oj ENISA – “Artificial Intelligence and Personal Data Protection” (2023) – Chapter on data accuracy: https://www.enisa.europa.eu/publications/artificial-intelligence-and-data-protection(Both links are publicly accessible and provide the legal and guidance foundations for the analysis above.)
Which of the following best describes the basic concept of "Privacy by Design?”
Answer(s): C
Privacy by Design means embedding privacy safeguards into the very structure of a system, making them an inherent part of its architecture rather than an after-thought or separate add-on. Option C directly reflects this concept, describing the implementation of privacy protection through system architecture, which aligns with the core principle of building privacy into design from the outset. Option A focuses only on adopting privacy-enhancing technologies, which is a toolset but does not capture the broader architectural integration needed. Option B addresses integrating a privacy program across business functions, a governance activity that is important but not the foundational architectural notion. Option D refers to introducing business processes for privacy gap assessment, which is part of privacy program management but does not encompass the design-centric approach at the system level.References https://iapp.org/resources/article/privacy-by-design-an-essential-part-of-innovation/ https://www.nist.gov/publications/privacy-framework
Post your Comments and Discuss IAPP CIPT exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the CIPT content, but please register or login to continue.