Question 320
Employees attach confidential spreadsheets to personal email and the organization needs content-aware detection and blocking. Which data protection approach meets the information's lifecycle need?
- Encryption in transit
- Tokenization
- Database column masking
- Data loss prevention
- Encryption at rest
Explanation
Correct Answer
D:DLP policies recognize sensitive information and govern transfers across channels such as mail, endpoints and storage. Classification accuracy influences results.
Incorrect Answers
A:Transport encryption such as TLS protects data while crossing network links when the underlying evidence concerns confidentiality and integrity across network path rather than the stated controls on outbound sensitive documents.
B:Tokenization replaces sensitive values with references mapped in a protected system for the specific concern of surrogate references for payment data, not the requirement involving controls on outbound sensitive documents.
C:Masking obscures specified fields in a presented view according to access context when analysts encounter limited exposure of sensitive field values; this question instead describes controls on outbound sensitive documents.
E:At-rest encryption protects stored ciphertext against unauthorized offline access when keys remain secure; the operational difference is confidentiality of stored backup contents versus the scenario's controls on outbound sensitive documents.
Question 321
A team downloads a firmware image and wants to compare its calculated checksum with a digest obtained from a trusted authenticated source. Which integrity or authentication mechanism is needed?
- Asymmetric digital signature
- SHA-256 digest verification
- HMAC integrity protection
- Write-once protected logs
Explanation
Correct Answer
B:A SHA-256 digest detects accidental or malicious content changes when the expected hash is trustworthy. It does not itself prove who created the image.
Incorrect Answers
A:A digital signature offers verifiable integrity and signer attribution when public-key trust is established for situations characterized by independently verifiable signed records; the case points instead to detection of byte changes with trusted hash.
C:HMAC uses a secret key with a cryptographic hash to provide message integrity and shared-key authenticity; its distinguishing scope is keyed integrity for shared-secret messages, not the reported detection of byte changes with trusted hash.
D:WORM or immutable storage can prevent modification within configured retention boundaries, subject to correct access and governance settings for situations characterized by protection against rewriting archived events; the case points instead to detection of byte changes with trusted hash.
Question 322
Two trusted services share a secret and need to detect tampering with API messages while authenticating their origin to each other. Which integrity or authentication mechanism is needed?
- Asymmetric digital signature
- Database transaction constraints
- HMAC integrity protection
- Write-once protected logs
Explanation
Correct Answer
C:HMAC uses a secret key with a cryptographic hash to provide message integrity and shared-key authenticity. Both sides can generate valid tags.
Incorrect Answers
A:A digital signature offers verifiable integrity and signer attribution when public-key trust is established; this characterizes independently verifiable signed records, whereas the reported condition is keyed integrity for shared-secret messages.
B:Unique and referential constraints enforce structural data integrity in the database engine when analysts encounter integrity of stored relational records; this question instead describes keyed integrity for shared-secret messages.
D:WORM or immutable storage can prevent modification within configured retention boundaries, subject to correct access and governance settings; this characterizes protection against rewriting archived events, whereas the reported condition is keyed integrity for shared-secret messages.
Question 323
Audit records must be signed by one party and verified by independent recipients without sharing the signer's private key. Which integrity or authentication mechanism is needed?
- SHA-256 digest verification
- Asymmetric digital signature
- Write-once protected logs
- Database transaction constraints
Explanation
Correct Answer
B:A digital signature offers verifiable integrity and signer attribution when public-key trust is established. Key compromise undermines confidence.
Incorrect Answers
A:A SHA-256 digest detects accidental or malicious content changes when the expected hash is trustworthy; this characterizes detection of byte changes with trusted hash, whereas the reported condition is independently verifiable signed records.
C:WORM or immutable storage can prevent modification within configured retention boundaries, subject to correct access and governance settings; this characterizes protection against rewriting archived events, whereas the reported condition is independently verifiable signed records.
D:Unique and referential constraints enforce structural data integrity in the database engine; its distinguishing scope is integrity of stored relational records, not the reported independently verifiable signed records.
Question 324
An application must prevent duplicate invoice IDs and invalid cross-table relationships even when clients submit conflicting writes. Which integrity or authentication mechanism is needed?
- Write-once protected logs
- Database transaction constraints
- Asymmetric digital signature
- SHA-256 digest verification
Explanation
Correct Answer
B:Unique and referential constraints enforce structural data integrity in the database engine. They complement application-side checks.
Incorrect Answers
A:WORM or immutable storage can prevent modification within configured retention boundaries, subject to correct access and governance settings for situations characterized by protection against rewriting archived events; the case points instead to integrity of stored relational records.
C:A digital signature offers verifiable integrity and signer attribution when public-key trust is established; that is relevant to independently verifiable signed records but does not directly account for integrity of stored relational records.
D:A SHA-256 digest detects accidental or malicious content changes when the expected hash is trustworthy; that is relevant to detection of byte changes with trusted hash but does not directly account for integrity of stored relational records.
Question 325
Attackers with operational access may attempt to edit historic security records, and auditors require tamper-resistant retention. Which integrity or authentication mechanism is needed?
- Write-once protected logs
- Asymmetric digital signature
- SHA-256 digest verification
- HMAC integrity protection
- Database transaction constraints
Explanation
Correct Answer
A:WORM or immutable storage can prevent modification within configured retention boundaries, subject to correct access and governance settings.
Incorrect Answers
B:A digital signature offers verifiable integrity and signer attribution when public-key trust is established; that is relevant to independently verifiable signed records but does not directly account for protection against rewriting archived events.
C:A SHA-256 digest detects accidental or malicious content changes when the expected hash is trustworthy; that is relevant to detection of byte changes with trusted hash but does not directly account for protection against rewriting archived events.
D:HMAC uses a secret key with a cryptographic hash to provide message integrity and shared-key authenticity for the specific concern of keyed integrity for shared-secret messages, not the requirement involving protection against rewriting archived events.
E:Unique and referential constraints enforce structural data integrity in the database engine when the underlying evidence concerns integrity of stored relational records rather than the stated protection against rewriting archived events.
Question 326
Regional analysts may query a shared database but must retrieve only rows belonging to their assigned region. Which access or privacy control should the data team select?
- Row-level security
- Least-privilege data access review
- Column-level authorization
- Data anonymization
Explanation
Correct Answer
A:Row-level security evaluates user or session context to filter accessible records in database queries. Correct identity mapping is critical.
Incorrect Answers
B:Regular entitlement review removes unjustified data permissions and detects privilege creep when the underlying evidence concerns removal of stale access to restricted datasets rather than the stated database filtering per allowed record ownership.
C:Column-specific grants restrict access to sensitive fields even when row access exists; that is relevant to limiting selected database attributes but does not directly account for database filtering per allowed record ownership.
D:Effective anonymization removes or transforms identifying information so subjects cannot reasonably be reidentified in a setting defined by public statistical data without identifiable people; the observed issue is database filtering per allowed record ownership.
Question 327
Customer support may read contact fields but must not retrieve salary or government-ID columns from the same records. Which access or privacy control should the data team select?
- Pseudonymization
- Data anonymization
- Column-level authorization
- Row-level security
Explanation
Correct Answer
C:Column-specific grants restrict access to sensitive fields even when row access exists. Views can help implement the exposure boundary.
Incorrect Answers
A:Pseudonymization reduces direct identifiability while retaining the possibility of reidentification using additional protected information for the specific concern of linkable records without direct identities, not the requirement involving limiting selected database attributes.
B:Effective anonymization removes or transforms identifying information so subjects cannot reasonably be reidentified; it handles public statistical data without identifiable people, while the decisive evidence in the question is limiting selected database attributes.
D:Row-level security evaluates user or session context to filter accessible records in database queries; its distinguishing scope is database filtering per allowed record ownership, not the reported limiting selected database attributes.
Question 328
Researchers need linkable customer records for trend analysis, but direct identity fields must be replaced with separately controlled identifiers. Which access or privacy control should the data team select?
- Least-privilege data access review
- Row-level security
- Pseudonymization
- Column-level authorization
Explanation
Correct Answer
C:Pseudonymization reduces direct identifiability while retaining the possibility of reidentification using additional protected information. It is not full anonymization.
Incorrect Answers
A:Regular entitlement review removes unjustified data permissions and detects privilege creep; the operational difference is removal of stale access to restricted datasets versus the scenario's linkable records without direct identities.
B:Row-level security evaluates user or session context to filter accessible records in database queries in a setting defined by database filtering per allowed record ownership; the observed issue is linkable records without direct identities.
D:Column-specific grants restrict access to sensitive fields even when row access exists in a setting defined by limiting selected database attributes; the observed issue is linkable records without direct identities.
Question 329
An open research dataset should be released without a reasonably feasible path to identify the source individuals under the applicable threat model. Which access or privacy control should the data team select?
- Row-level security
- Least-privilege data access review
- Column-level authorization
- Data anonymization
Explanation
Correct Answer
D:Effective anonymization removes or transforms identifying information so subjects cannot reasonably be reidentified. Reidentification risk needs assessment.
Incorrect Answers
A:Row-level security evaluates user or session context to filter accessible records in database queries in a setting defined by database filtering per allowed record ownership; the observed issue is public statistical data without identifiable people.
B:Regular entitlement review removes unjustified data permissions and detects privilege creep; that is relevant to removal of stale access to restricted datasets but does not directly account for public statistical data without identifiable people.
C:Column-specific grants restrict access to sensitive fields even when row access exists in a setting defined by limiting selected database attributes; the observed issue is public statistical data without identifiable people.
Question 330
A former finance employee retains access to payroll tables months after transferring departments. Which access or privacy control should the data team select?
- Row-level security
- Least-privilege data access review
- Data anonymization
- Pseudonymization
- Column-level authorization
Explanation
Correct Answer
B:Regular entitlement review removes unjustified data permissions and detects privilege creep. Classification informs which accesses require the strongest controls.
Incorrect Answers
A:Row-level security evaluates user or session context to filter accessible records in database queries; its distinguishing scope is database filtering per allowed record ownership, not the reported removal of stale access to restricted datasets.
C:Effective anonymization removes or transforms identifying information so subjects cannot reasonably be reidentified; this characterizes public statistical data without identifiable people, whereas the reported condition is removal of stale access to restricted datasets.
D:Pseudonymization reduces direct identifiability while retaining the possibility of reidentification using additional protected information for situations characterized by linkable records without direct identities; the case points instead to removal of stale access to restricted datasets.
E:Column-specific grants restrict access to sensitive fields even when row access exists; this characterizes limiting selected database attributes, whereas the reported condition is removal of stale access to restricted datasets.