You save $69.98
CRISC Premium Bundle
- Premium File 1105 Questions & Answers
- Last Update: Nov 10, 2026
- Training Course 64 Lectures
- Study Guide 498 Pages
You save $69.98
A risk owner seeks evidence following review of this situation: A retail app collects a customer's birth date for a discount feature that only needs proof of being over the required age. Which evidence would best demonstrate that the intended risk response is functioning?
Data mapping shows only necessary proof is collected and historic unneeded birth dates follow controlled deletion. This evidence addresses the stated risk rather than showing only that a control was configured. Data minimization reduces confidentiality and compliance exposure by limiting unnecessary personal data.
A controlled exercise restores uncompromised records from protected recovery points. That observation may help validate ransomware backup integrity, but it does not establish the acceptance condition for privacy-by-design minimization. Here, the decisive evidence is: Data mapping shows only necessary proof is collected and historic unneeded birth dates follow controlled deletion.
Reporting time and follow-up quality improve in simulation and real intake records. That observation may help validate security incident reporting culture, but it does not establish the acceptance condition for privacy-by-design minimization. Here, the decisive evidence is: Data mapping shows only necessary proof is collected and historic unneeded birth dates follow controlled deletion.
Responsibility mapping and control tests show the customer-managed access rules and provider evidence separately. That observation may help validate shared responsibility in cloud, but it does not establish the acceptance condition for privacy-by-design minimization. Here, the decisive evidence is: Data mapping shows only necessary proof is collected and historic unneeded birth dates follow controlled deletion.
A governance team is discussing the underlying cause in this situation: A retail app collects a customer's birth date for a discount feature that only needs proof of being over the required age. Which risk-management principle most directly explains the correct approach?
Data minimization reduces confidentiality and compliance exposure by limiting unnecessary personal data. The immediate management action is: Replace raw birth-date collection with a proportionate age-eligibility signal and review retention needs.
Framework value depends on correct applicability and coverage of material processing boundaries. That principle is relevant to control-framework applicability, not the mechanism implicated by the stated privacy-by-design minimization situation. In this case: Data minimization reduces confidentiality and compliance exposure by limiting unnecessary personal data.
Architecture governance helps control accumulated integration complexity and misconfiguration risk. That principle is relevant to hybrid network technical debt, not the mechanism implicated by the stated privacy-by-design minimization situation. In this case: Data minimization reduces confidentiality and compliance exposure by limiting unnecessary personal data.
Data classification and purpose limitation should govern how sensitive information is reused. That principle is relevant to sensitive analytics access, not the mechanism implicated by the stated privacy-by-design minimization situation. In this case: Data minimization reduces confidentiality and compliance exposure by limiting unnecessary personal data.
A risk committee is deciding whether an unresolved exposure can be tolerated: A retail app collects a customer's birth date for a discount feature that only needs proof of being over the required age. What is the most relevant avoidable consequence if the weakness remains unresolved?
Collecting unnecessary birth dates expands loss severity if the app is compromised. This consequence follows from the specific missing governance or technical safeguard. Data minimization reduces confidentiality and compliance exposure by limiting unnecessary personal data. The appropriate response is: Replace raw birth-date collection with a proportionate age-eligibility signal and review retention needs.
Completion rates alone may hide continuing exposure to business email compromise. That potential consequence concerns phishing awareness targeting, rather than the direct risk described by privacy-by-design minimization. Here the material exposure is: Collecting unnecessary birth dates expands loss severity if the app is compromised.
Raw copy proliferation expands confidentiality exposure beyond the original protected processing system. That potential consequence concerns sensitive analytics access, rather than the direct risk described by privacy-by-design minimization. Here the material exposure is: Collecting unnecessary birth dates expands loss severity if the app is compromised.
An artificially narrow scope can create misleading security attestation while data remains exposed. That potential consequence concerns control-framework applicability, rather than the direct risk described by privacy-by-design minimization. Here the material exposure is: Collecting unnecessary birth dates expands loss severity if the app is compromised.
Before making a treatment decision, an analyst is investigating this situation: A retail app collects a customer's birth date for a discount feature that only needs proof of being over the required age. Which targeted first investigation would best clarify the risk before action is approved?
Trace where birth dates are captured, used, copied and stored relative to the feature requirement. This isolates the relevant cause before changing unrelated controls. An appropriate follow-up is: Replace raw birth-date collection with a proportionate age-eligibility signal and review retention needs.
Trace administrator login, token issuance, command rights and session-event capture. That investigation concerns privileged authentication architecture and would not isolate the first implicated dependency here. The targeted check is: Trace where birth dates are captured, used, copied and stored relative to the feature requirement.
Trace the partner data flow and compare it with the declared control boundary. That investigation concerns control-framework applicability and would not isolate the first implicated dependency here. The targeted check is: Trace where birth dates are captured, used, copied and stored relative to the feature requirement.
Trace go-live prerequisites and supplier milestones to actual readiness evidence. That investigation concerns project dependency risk and would not isolate the first implicated dependency here. The targeted check is: Trace where birth dates are captured, used, copied and stored relative to the feature requirement.
An organization is preventing a recurrence of this risk pattern: A retail app collects a customer's birth date for a discount feature that only needs proof of being over the required age. Which ongoing safeguard would best prevent recurrence of this specific failure mode?
Require purpose-necessity review in new personal-data fields. This safeguard addresses the recurring failure rather than only the current event. The expected verification is: Data mapping shows only necessary proof is collected and historic unneeded birth dates follow controlled deletion.
Require security review gates at each material SDLC phase. That safeguard prevents failures associated with secure design stage and does not directly prevent this privacy-by-design minimization recurrence. The applicable continuing control is: Require purpose-necessity review in new personal-data fields.
Require architecture review for new site-to-cloud connectivity. That safeguard prevents failures associated with hybrid network technical debt and does not directly prevent this privacy-by-design minimization recurrence. The applicable continuing control is: Require purpose-necessity review in new personal-data fields.
Track recurrence metrics and require problem reviews for repeated incidents. That safeguard prevents failures associated with problem versus incident handling and does not directly prevent this privacy-by-design minimization recurrence. The applicable continuing control is: Require purpose-necessity review in new personal-data fields.
A risk leader is reviewing this situation: A customer asks a service to erase eligible profile data, but the support portal deletes only its local copy and leaves marketing replicas. Which next step would most directly treat or govern the risk in this situation?
Map the applicable erasure obligation and propagate authorized deletion across eligible dependent stores and processors. Privacy controls must address the full personal-data lifecycle and legitimate retention exceptions. Evidence that the action has worked would be: Deletion evidence covers permitted systems, exceptions and third-party confirmation where required.
Integrate policy-as-code validation and protected release approvals into the deployment pipeline. That change is aimed at devops security drift, whereas this decision must address data-subject request propagation. The relevant first comparison is: Trace data lineage and legal holds for the customer profile across processors.
Classify transcripts, define justified retention and secure deletion rules, and test their operation. That change is aimed at data retention lifecycle, whereas this decision must address data-subject request propagation. The relevant first comparison is: Trace data lineage and legal holds for the customer profile across processors.
Map zero-trust principles to actual identity, device, resource and continuous authorization control outcomes. That change is aimed at zero-trust program evaluation, whereas this decision must address data-subject request propagation. The relevant first comparison is: Trace data lineage and legal holds for the customer profile across processors.
A risk owner seeks evidence following review of this situation: A customer asks a service to erase eligible profile data, but the support portal deletes only its local copy and leaves marketing replicas. Which evidence would best demonstrate that the intended risk response is functioning?
Deletion evidence covers permitted systems, exceptions and third-party confirmation where required. This evidence addresses the stated risk rather than showing only that a control was configured. Privacy controls must address the full personal-data lifecycle and legitimate retention exceptions.
Scope records cover partner API data, accountable owners and tested safeguards. That observation may help validate control-framework applicability, but it does not establish the acceptance condition for data-subject request propagation. Here, the decisive evidence is: Deletion evidence covers permitted systems, exceptions and third-party confirmation where required.
Build evidence shows prohibited network exposure is blocked before release and exceptions tracked. That observation may help validate devops security drift, but it does not establish the acceptance condition for data-subject request propagation. Here, the decisive evidence is: Deletion evidence covers permitted systems, exceptions and third-party confirmation where required.
Retention schedules and deletion logs demonstrate expired chats are removed from primary and relevant secondary stores. That observation may help validate data retention lifecycle, but it does not establish the acceptance condition for data-subject request propagation. Here, the decisive evidence is: Deletion evidence covers permitted systems, exceptions and third-party confirmation where required.
A governance team is discussing the underlying cause in this situation: A customer asks a service to erase eligible profile data, but the support portal deletes only its local copy and leaves marketing replicas. Which risk-management principle most directly explains the correct approach?
Privacy controls must address the full personal-data lifecycle and legitimate retention exceptions. The immediate management action is: Map the applicable erasure obligation and propagate authorized deletion across eligible dependent stores and processors.
Key management must follow the data lifecycle and required retention or destruction periods. That principle is relevant to encryption key retirement, not the mechanism implicated by the stated data-subject request propagation situation. In this case: Privacy controls must address the full personal-data lifecycle and legitimate retention exceptions.
Software supply-chain exposure changes over time and should be monitored across the development lifecycle. That principle is relevant to third-party library in sdlc, not the mechanism implicated by the stated data-subject request propagation situation. In this case: Privacy controls must address the full personal-data lifecycle and legitimate retention exceptions.
Data lifecycle risk spans collection, use, storage, retention and disposal, including copies. That principle is relevant to data retention lifecycle, not the mechanism implicated by the stated data-subject request propagation situation. In this case: Privacy controls must address the full personal-data lifecycle and legitimate retention exceptions.
A risk committee is deciding whether an unresolved exposure can be tolerated: A customer asks a service to erase eligible profile data, but the support portal deletes only its local copy and leaves marketing replicas. What is the most relevant avoidable consequence if the weakness remains unresolved?
Local-only deletion can leave unmanaged personal data in downstream systems. This consequence follows from the specific missing governance or technical safeguard. Privacy controls must address the full personal-data lifecycle and legitimate retention exceptions. The appropriate response is: Map the applicable erasure obligation and propagate authorized deletion across eligible dependent stores and processors.
Treating a firewall purchase as strategy completion may leave trusted internal routes unprotected. That potential consequence concerns zero-trust program evaluation, rather than the direct risk described by data-subject request propagation. Here the material exposure is: Local-only deletion can leave unmanaged personal data in downstream systems.
A calendar-only replacement date can leave critical unsupported equipment at unacceptable exposure. That potential consequence concerns technology roadmap risk, rather than the direct risk described by data-subject request propagation. Here the material exposure is: Local-only deletion can leave unmanaged personal data in downstream systems.
A firewall-only remedy may still permit stolen credentials to execute untracked privileged commands. That potential consequence concerns privileged authentication architecture, rather than the direct risk described by data-subject request propagation. Here the material exposure is: Local-only deletion can leave unmanaged personal data in downstream systems.
Before making a treatment decision, an analyst is investigating this situation: A customer asks a service to erase eligible profile data, but the support portal deletes only its local copy and leaves marketing replicas. Which targeted first investigation would best clarify the risk before action is approved?
Trace data lineage and legal holds for the customer profile across processors. This isolates the relevant cause before changing unrelated controls. An appropriate follow-up is: Map the applicable erasure obligation and propagate authorized deletion across eligible dependent stores and processors.
Trace field-level data lineage and test effective access on the analytics replica. That investigation concerns sensitive analytics access and would not isolate the first implicated dependency here. The targeted check is: Trace data lineage and legal holds for the customer profile across processors.
Compare managed service documentation with actual customer configuration and contractual obligations. That investigation concerns shared responsibility in cloud and would not isolate the first implicated dependency here. The targeted check is: Trace data lineage and legal holds for the customer profile across processors.
Trace the partner data flow and compare it with the declared control boundary. That investigation concerns control-framework applicability and would not isolate the first implicated dependency here. The targeted check is: Trace data lineage and legal holds for the customer profile across processors.
An organization is preventing a recurrence of this risk pattern: A customer asks a service to erase eligible profile data, but the support portal deletes only its local copy and leaves marketing replicas. Which ongoing safeguard would best prevent recurrence of this specific failure mode?
Test request propagation when new data pipelines are introduced. This safeguard addresses the recurring failure rather than only the current event. The expected verification is: Deletion evidence covers permitted systems, exceptions and third-party confirmation where required.
Maintain testable security controls as versioned pipeline policies. That safeguard prevents failures associated with devops security drift and does not directly prevent this data-subject request propagation recurrence. The applicable continuing control is: Test request propagation when new data pipelines are introduced.
Embed masking and classification rules in dataset provisioning. That safeguard prevents failures associated with sensitive analytics access and does not directly prevent this data-subject request propagation recurrence. The applicable continuing control is: Test request propagation when new data pipelines are introduced.
Require integration acceptance criteria for identity changes. That safeguard prevents failures associated with production rollout safeguard and does not directly prevent this data-subject request propagation recurrence. The applicable continuing control is: Test request propagation when new data pipelines are introduced.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (1105 Questions, Last Updated on Nov 10, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.