Exam Bundle

Rows older than the approved retention period are no longer queryable would demonstrate the separate action Implement a scheduled retention filter and controlled deletion operation, which addresses “A policy requires deleting raw PII after a specified retention age.” It does not verify the requirement “An analyst suggests overwriting Parquet files directly to purge Delta rows” following Use Delta-supported transactional deletion and verified physical cleanup.

That observation is a valid indicator for “A verified deletion request targets one customer's personal rows in an active Delta table” when using Apply a scoped transactional DELETE or supported erasure operation. The scenario instead tests “An analyst suggests overwriting Parquet files directly to purge Delta rows”; the relevant result is The Delta log remains consistent and erasure is reflected in queries.

This signal belongs to the adjacent case “An erasure request requires removal from historical physical files after a compliant retention process,” whose remedy is Perform supported data rewrites and retention-safe vacuum/purge as required. The observed result for the present requirement is The Delta log remains consistent and erasure is reflected in queries.

This action solves a different issue: “A nonreversible representation is required for equality matching without a secret table.” Its normal signal is Matching source IDs yield consistent digests without a published mapping table. Here the requested behavior is “The same customer should map consistently across datasets without revealing the original ID,” so that signal is not sufficient.

Suppress the sensitive column in the approved projection is appropriate when “A field must be completely omitted from a downstream partner dataset”; it would be verified by The exported schema contains no sensitive field. It does not directly satisfy “The same customer should map consistently across datasets without revealing the original ID,” whose relevant acceptance evidence is Joined records match on pseudonyms while raw identities remain protected.

Generalize precise dates into approved age ranges is appropriate when “A birth date should be coarsened to an age band to reduce identification risk”; it would be verified by The partner sees only the allowed age band rather than full date. It does not directly satisfy “The same customer should map consistently across datasets without revealing the original ID,” whose relevant acceptance evidence is Joined records match on pseudonyms while raw identities remain protected.

Only the trusted service role can resolve tokens to the original identifier pertains to a different control (Use controlled reversible tokenization with a restricted mapping vault) and a different need (Authorized internal reidentification is necessary for customer service support). It cannot establish that Use controlled keyed tokenization or HMAC pseudonymization met the stated goal.

The partner sees only the allowed age band rather than full date would demonstrate the separate action Generalize precise dates into approved age ranges, which addresses “A birth date should be coarsened to an age band to reduce identification risk.” It does not verify the requirement “The same customer should map consistently across datasets without revealing the original ID” following Use controlled keyed tokenization or HMAC pseudonymization.

This signal belongs to the adjacent case “A nonreversible representation is required for equality matching without a secret table,” whose remedy is Use a suitable cryptographic one-way keyed hash with secret management. The observed result for the present requirement is Joined records match on pseudonyms while raw identities remain protected.

The alternative Use controlled reversible tokenization with a restricted mapping vault has a distinct purpose—Authorized internal reidentification is necessary for customer service support. It would not establish the required outcome (A field must be completely omitted from a downstream partner dataset); the necessary verification concerns The exported schema contains no sensitive field.

This action solves a different issue: “The same customer should map consistently across datasets without revealing the original ID.” Its normal signal is Joined records match on pseudonyms while raw identities remain protected. Here the requested behavior is “A field must be completely omitted from a downstream partner dataset,” so that signal is not sufficient.

Use a suitable cryptographic one-way keyed hash with secret management is appropriate when “A nonreversible representation is required for equality matching without a secret table”; it would be verified by Matching source IDs yield consistent digests without a published mapping table. It does not directly satisfy “A field must be completely omitted from a downstream partner dataset,” whose relevant acceptance evidence is The exported schema contains no sensitive field.

Joined records match on pseudonyms while raw identities remain protected would demonstrate the separate action Use controlled keyed tokenization or HMAC pseudonymization, which addresses “The same customer should map consistently across datasets without revealing the original ID.” It does not verify the requirement “A field must be completely omitted from a downstream partner dataset” following Suppress the sensitive column in the approved projection.

That observation is a valid indicator for “A nonreversible representation is required for equality matching without a secret table” when using Use a suitable cryptographic one-way keyed hash with secret management. The scenario instead tests “A field must be completely omitted from a downstream partner dataset”; the relevant result is The exported schema contains no sensitive field.

This signal belongs to the adjacent case “A birth date should be coarsened to an age band to reduce identification risk,” whose remedy is Generalize precise dates into approved age ranges. The observed result for the present requirement is The exported schema contains no sensitive field.

The alternative Use controlled keyed tokenization or HMAC pseudonymization has a distinct purpose—The same customer should map consistently across datasets without revealing the original ID. It would not establish the required outcome (A birth date should be coarsened to an age band to reduce identification risk); the necessary verification concerns The partner sees only the allowed age band rather than full date.

This action solves a different issue: “Authorized internal reidentification is necessary for customer service support.” Its normal signal is Only the trusted service role can resolve tokens to the original identifier. Here the requested behavior is “A birth date should be coarsened to an age band to reduce identification risk,” so that signal is not sufficient.

Use a suitable cryptographic one-way keyed hash with secret management is appropriate when “A nonreversible representation is required for equality matching without a secret table”; it would be verified by Matching source IDs yield consistent digests without a published mapping table. It does not directly satisfy “A birth date should be coarsened to an age band to reduce identification risk,” whose relevant acceptance evidence is The partner sees only the allowed age band rather than full date.

Matching source IDs yield consistent digests without a published mapping table would demonstrate the separate action Use a suitable cryptographic one-way keyed hash with secret management, which addresses “A nonreversible representation is required for equality matching without a secret table.” It does not verify the requirement “A birth date should be coarsened to an age band to reduce identification risk” following Generalize precise dates into approved age ranges.

That observation is a valid indicator for “A field must be completely omitted from a downstream partner dataset” when using Suppress the sensitive column in the approved projection. The scenario instead tests “A birth date should be coarsened to an age band to reduce identification risk”; the relevant result is The partner sees only the allowed age band rather than full date.

That observation is a valid indicator for “The same customer should map consistently across datasets without revealing the original ID” when using Use controlled keyed tokenization or HMAC pseudonymization. The scenario instead tests “A birth date should be coarsened to an age band to reduce identification risk”; the relevant result is The partner sees only the allowed age band rather than full date.

Generalize precise dates into approved age ranges is appropriate when “A birth date should be coarsened to an age band to reduce identification risk”; it would be verified by The partner sees only the allowed age band rather than full date. It does not directly satisfy “A nonreversible representation is required for equality matching without a secret table,” whose relevant acceptance evidence is Matching source IDs yield consistent digests without a published mapping table.

This action solves a different issue: “A field must be completely omitted from a downstream partner dataset.” Its normal signal is The exported schema contains no sensitive field. Here the requested behavior is “A nonreversible representation is required for equality matching without a secret table,” so that signal is not sufficient.

The alternative Use controlled keyed tokenization or HMAC pseudonymization has a distinct purpose—The same customer should map consistently across datasets without revealing the original ID. It would not establish the required outcome (A nonreversible representation is required for equality matching without a secret table); the necessary verification concerns Matching source IDs yield consistent digests without a published mapping table.

That observation is a valid indicator for “Authorized internal reidentification is necessary for customer service support” when using Use controlled reversible tokenization with a restricted mapping vault. The scenario instead tests “A nonreversible representation is required for equality matching without a secret table”; the relevant result is Matching source IDs yield consistent digests without a published mapping table.

The partner sees only the allowed age band rather than full date pertains to a different control (Generalize precise dates into approved age ranges) and a different need (A birth date should be coarsened to an age band to reduce identification risk). It cannot establish that Use a suitable cryptographic one-way keyed hash with secret management met the stated goal.

This signal belongs to the adjacent case “A field must be completely omitted from a downstream partner dataset,” whose remedy is Suppress the sensitive column in the approved projection. The observed result for the present requirement is Matching source IDs yield consistent digests without a published mapping table.

Use a suitable cryptographic one-way keyed hash with secret management is appropriate when “A nonreversible representation is required for equality matching without a secret table”; it would be verified by Matching source IDs yield consistent digests without a published mapping table. It does not directly satisfy “Authorized internal reidentification is necessary for customer service support,” whose relevant acceptance evidence is Only the trusted service role can resolve tokens to the original identifier.

The alternative Suppress the sensitive column in the approved projection has a distinct purpose—A field must be completely omitted from a downstream partner dataset. It would not establish the required outcome (Authorized internal reidentification is necessary for customer service support); the necessary verification concerns Only the trusted service role can resolve tokens to the original identifier.

The alternative Generalize precise dates into approved age ranges has a distinct purpose—A birth date should be coarsened to an age band to reduce identification risk. It would not establish the required outcome (Authorized internal reidentification is necessary for customer service support); the necessary verification concerns Only the trusted service role can resolve tokens to the original identifier.

The partner sees only the allowed age band rather than full date would demonstrate the separate action Generalize precise dates into approved age ranges, which addresses “A birth date should be coarsened to an age band to reduce identification risk.” It does not verify the requirement “Authorized internal reidentification is necessary for customer service support” following Use controlled reversible tokenization with a restricted mapping vault.

Matching source IDs yield consistent digests without a published mapping table pertains to a different control (Use a suitable cryptographic one-way keyed hash with secret management) and a different need (A nonreversible representation is required for equality matching without a secret table). It cannot establish that Use controlled reversible tokenization with a restricted mapping vault met the stated goal.

This signal belongs to the adjacent case “The same customer should map consistently across datasets without revealing the original ID,” whose remedy is Use controlled keyed tokenization or HMAC pseudonymization. The observed result for the present requirement is Only the trusted service role can resolve tokens to the original identifier.