Question 540
To retire a failed SSD without exposing its previous confidential blocks, which measure best meets the requirement?
- Paper-document shredding
- Cryptographic erase validation
- Secure media sanitization
- Data retention legal hold
- Cloud object version cleanup
Explanation
Correct Answer
C:Appropriate purge or destruction methods consider flash remapping and device capability; this mechanism directly supports the requirement to retire a failed SSD without exposing its previous confidential blocks.
Incorrect Answers
A:Approved physical destruction addresses hard-copy material outside electronic deletion controls; that is useful when the task is to dispose of printed regulated reports so they cannot be reconstructed easily, not the stated requirement to retire a failed SSD without exposing its previous confidential blocks.
B:Secure key retirement can render ciphertext unusable only if backup and replicated keys are controlled; a team would select it to verify that encryption keys protecting discarded drives were actually destroyed, which does not provide the particular result to retire a failed SSD without exposing its previous confidential blocks.
D:Hold procedures preserve specified information despite normal disposal schedules; applying it would serve pause scheduled destruction of relevant records during litigation without directly satisfying the goal to retire a failed SSD without exposing its previous confidential blocks.
E:Version-aware lifecycle policies target previous copies, not just the current object view; it addresses the different need to remove sensitive historical revisions after an approved retention period, leaving the requested ability to retire a failed SSD without exposing its previous confidential blocks unresolved.
Question 541
To verify that encryption keys protecting discarded drives were actually destroyed, what control should be selected?
- Paper-document shredding
- Data subject deletion workflow
- Remanence verification
- Cryptographic erase validation
Explanation
Correct Answer
D:Secure key retirement can render ciphertext unusable only if backup and replicated keys are controlled; it supplies the specific control needed to verify that encryption keys protecting discarded drives were actually destroyed.
Incorrect Answers
A:Approved physical destruction addresses hard-copy material outside electronic deletion controls; it could help someone trying to dispose of printed regulated reports so they cannot be reconstructed easily, but the problem is instead to verify that encryption keys protecting discarded drives were actually destroyed.
B:Erasure handling tracks replicas, backups and legal exemptions rather than deleting one database row only; that is useful when the task is to coordinate removal of eligible personal records across connected systems, not the stated requirement to verify that encryption keys protecting discarded drives were actually destroyed.
C:Post-sanitization testing validates the chosen erase method for the actual storage technology; a team would select it to check that decommissioned media no longer exposes recoverable prior data, which does not provide the particular result to verify that encryption keys protecting discarded drives were actually destroyed.
Question 542
To pause scheduled destruction of relevant records during litigation, which security control is most appropriate?
- Remanence verification
- Paper-document shredding
- Cloud object version cleanup
- Data retention legal hold
Explanation
Correct Answer
D:Hold procedures preserve specified information despite normal disposal schedules; that is why it addresses the operational task to pause scheduled destruction of relevant records during litigation.
Incorrect Answers
A:Post-sanitization testing validates the chosen erase method for the actual storage technology; although relevant to check that decommissioned media no longer exposes recoverable prior data, it does not by itself achieve the required task to pause scheduled destruction of relevant records during litigation.
B:Approved physical destruction addresses hard-copy material outside electronic deletion controls; it could help someone trying to dispose of printed regulated reports so they cannot be reconstructed easily, but the problem is instead to pause scheduled destruction of relevant records during litigation.
C:Version-aware lifecycle policies target previous copies, not just the current object view; that is useful when the task is to remove sensitive historical revisions after an approved retention period, not the stated requirement to pause scheduled destruction of relevant records during litigation.
Question 543
To dispose of printed regulated reports so they cannot be reconstructed easily, what would a data protection engineer implement or use?
- Cryptographic erase validation
- Paper-document shredding
- Data subject deletion workflow
- Secure media sanitization
Explanation
Correct Answer
B:Approved physical destruction addresses hard-copy material outside electronic deletion controls; its relevant protective or investigative effect is to dispose of printed regulated reports so they cannot be reconstructed easily.
Incorrect Answers
A:Secure key retirement can render ciphertext unusable only if backup and replicated keys are controlled; the outcome it supports is to verify that encryption keys protecting discarded drives were actually destroyed, whereas this scenario asks defenders to dispose of printed regulated reports so they cannot be reconstructed easily.
C:Erasure handling tracks replicas, backups and legal exemptions rather than deleting one database row only; it could help someone trying to coordinate removal of eligible personal records across connected systems, but the problem is instead to dispose of printed regulated reports so they cannot be reconstructed easily.
D:Appropriate purge or destruction methods consider flash remapping and device capability; that is useful when the task is to retire a failed SSD without exposing its previous confidential blocks, not the stated requirement to dispose of printed regulated reports so they cannot be reconstructed easily.
Question 544
To remove sensitive historical revisions after an approved retention period, which practice addresses that objective?
- Data subject deletion workflow
- Data export approval
- Paper-document shredding
- Cloud object version cleanup
Explanation
Correct Answer
D:Version-aware lifecycle policies target previous copies, not just the current object view; the requested outcome is precisely to remove sensitive historical revisions after an approved retention period.
Incorrect Answers
A:Erasure handling tracks replicas, backups and legal exemptions rather than deleting one database row only; its mechanism supports coordinate removal of eligible personal records across connected systems, while the requested control must be able to remove sensitive historical revisions after an approved retention period.
B:Governed exports apply least privilege and traceability to high-impact transfer operations; the outcome it supports is to require authorization and logging before bulk extraction of employee records, whereas this scenario asks defenders to remove sensitive historical revisions after an approved retention period.
C:Approved physical destruction addresses hard-copy material outside electronic deletion controls; although relevant to dispose of printed regulated reports so they cannot be reconstructed easily, it does not by itself achieve the required task to remove sensitive historical revisions after an approved retention period.
Question 545
To coordinate removal of eligible personal records across connected systems, which tool, policy, or technique is appropriate?
- Audit-log retention protection
- Paper-document shredding
- Data subject deletion workflow
- Cloud object version cleanup
- Remanence verification
Explanation
Correct Answer
C:Erasure handling tracks replicas, backups and legal exemptions rather than deleting one database row only; this choice fits the scenario because the team must coordinate removal of eligible personal records across connected systems.
Incorrect Answers
A:Restricted append and retention permissions help preserve evidence against user-level manipulation; the technique works for situations involving keep sensitive data-access records intact for the investigation window, rather than this need to coordinate removal of eligible personal records across connected systems.
B:Approved physical destruction addresses hard-copy material outside electronic deletion controls; its mechanism supports dispose of printed regulated reports so they cannot be reconstructed easily, while the requested control must be able to coordinate removal of eligible personal records across connected systems.
D:Version-aware lifecycle policies target previous copies, not just the current object view; although relevant to remove sensitive historical revisions after an approved retention period, it does not by itself achieve the required task to coordinate removal of eligible personal records across connected systems.
E:Post-sanitization testing validates the chosen erase method for the actual storage technology; it could help someone trying to check that decommissioned media no longer exposes recoverable prior data, but the problem is instead to coordinate removal of eligible personal records across connected systems.
Question 546
To check that decommissioned media no longer exposes recoverable prior data, what safeguard would be most applicable?
- Remanence verification
- Cryptographic erase validation
- Database row-level security
- Data retention legal hold
Explanation
Correct Answer
A:Post-sanitization testing validates the chosen erase method for the actual storage technology; this mechanism directly supports the requirement to check that decommissioned media no longer exposes recoverable prior data.
Incorrect Answers
B:Secure key retirement can render ciphertext unusable only if backup and replicated keys are controlled; the technique works for situations involving verify that encryption keys protecting discarded drives were actually destroyed, rather than this need to check that decommissioned media no longer exposes recoverable prior data.
C:Row-level policy filters result visibility within a shared table according to request identity or attributes; its mechanism supports limit each regional analyst to records within assigned territories, while the requested control must be able to check that decommissioned media no longer exposes recoverable prior data.
D:Hold procedures preserve specified information despite normal disposal schedules; the outcome it supports is to pause scheduled destruction of relevant records during litigation, whereas this scenario asks defenders to check that decommissioned media no longer exposes recoverable prior data.
Question 547
To require authorization and logging before bulk extraction of employee records, what is the relevant defensive action?
- Data export approval
- Data integrity constraints
- Audit-log retention protection
- Data retention legal hold
Explanation
Correct Answer
A:Governed exports apply least privilege and traceability to high-impact transfer operations; it supplies the specific control needed to require authorization and logging before bulk extraction of employee records.
Incorrect Answers
B:Database constraints maintain permissible states but do not authenticate who submitted every transaction; it addresses the different need to reject invalid or inconsistent records before they enter a relational table, leaving the requested ability to require authorization and logging before bulk extraction of employee records unresolved.
C:Restricted append and retention permissions help preserve evidence against user-level manipulation; the technique works for situations involving keep sensitive data-access records intact for the investigation window, rather than this need to require authorization and logging before bulk extraction of employee records.
D:Hold procedures preserve specified information despite normal disposal schedules; its mechanism supports pause scheduled destruction of relevant records during litigation, while the requested control must be able to require authorization and logging before bulk extraction of employee records.
Question 548
To limit each regional analyst to records within assigned territories, which option most directly provides the capability?
- Data integrity constraints
- Paper-document shredding
- Database row-level security
- Audit-log retention protection
Explanation
Correct Answer
C:Row-level policy filters result visibility within a shared table according to request identity or attributes; that is why it addresses the operational task to limit each regional analyst to records within assigned territories.
Incorrect Answers
A:Database constraints maintain permissible states but do not authenticate who submitted every transaction; its operational purpose is to reject invalid or inconsistent records before they enter a relational table, not to achieve the specific requirement to limit each regional analyst to records within assigned territories.
B:Approved physical destruction addresses hard-copy material outside electronic deletion controls; applying it would serve dispose of printed regulated reports so they cannot be reconstructed easily without directly satisfying the goal to limit each regional analyst to records within assigned territories.
D:Restricted append and retention permissions help preserve evidence against user-level manipulation; the technique works for situations involving keep sensitive data-access records intact for the investigation window, rather than this need to limit each regional analyst to records within assigned territories.
Question 549
To reject invalid or inconsistent records before they enter a relational table, which control achieves the target outcome?
- Data subject deletion workflow
- Data export approval
- Data integrity constraints
- Cloud object version cleanup
Explanation
Correct Answer
C:Database constraints maintain permissible states but do not authenticate who submitted every transaction; its relevant protective or investigative effect is to reject invalid or inconsistent records before they enter a relational table.
Incorrect Answers
A:Erasure handling tracks replicas, backups and legal exemptions rather than deleting one database row only; a team would select it to coordinate removal of eligible personal records across connected systems, which does not provide the particular result to reject invalid or inconsistent records before they enter a relational table.
B:Governed exports apply least privilege and traceability to high-impact transfer operations; its operational purpose is to require authorization and logging before bulk extraction of employee records, not to achieve the specific requirement to reject invalid or inconsistent records before they enter a relational table.
D:Version-aware lifecycle policies target previous copies, not just the current object view; it addresses the different need to remove sensitive historical revisions after an approved retention period, leaving the requested ability to reject invalid or inconsistent records before they enter a relational table unresolved.
Question 550
To keep sensitive data-access records intact for the investigation window, which option is the direct technical match?
- Database row-level security
- Data export approval
- Data subject deletion workflow
- Data integrity constraints
- Audit-log retention protection
Explanation
Correct Answer
E:Restricted append and retention permissions help preserve evidence against user-level manipulation; the requested outcome is precisely to keep sensitive data-access records intact for the investigation window.
Incorrect Answers
A:Row-level policy filters result visibility within a shared table according to request identity or attributes; that is useful when the task is to limit each regional analyst to records within assigned territories, not the stated requirement to keep sensitive data-access records intact for the investigation window.
B:Governed exports apply least privilege and traceability to high-impact transfer operations; a team would select it to require authorization and logging before bulk extraction of employee records, which does not provide the particular result to keep sensitive data-access records intact for the investigation window.
C:Erasure handling tracks replicas, backups and legal exemptions rather than deleting one database row only; its operational purpose is to coordinate removal of eligible personal records across connected systems, not to achieve the specific requirement to keep sensitive data-access records intact for the investigation window.
D:Database constraints maintain permissible states but do not authenticate who submitted every transaction; applying it would serve reject invalid or inconsistent records before they enter a relational table without directly satisfying the goal to keep sensitive data-access records intact for the investigation window.