Exam Bundle

This signal belongs to the adjacent case “An ABAC policy applies to an entire schema but a new table is added,” whose remedy is Tag the new table/columns appropriately under the scoped policy. The observed result for the present requirement is Only columns with the intended classification are masked.

A new sensitive column receives the required mask before consumer access pertains to a different control (Add schema-evolution QA and governed-tag classification checks) and a different need (The team needs to prove masked columns remain protected after a new data column appears). It cannot establish that Refine the governed-tag match condition or classification met the stated goal.

Cross-tenant test rows are excluded according to the intended policy would demonstrate the separate action Fix the row-filter mapping to the authoritative tenant column, which addresses “One table has several different tenant columns and the wrong field was used for enforcement.” It does not verify the requirement “An overly broad ABAC rule unexpectedly masks low-risk columns” following Refine the governed-tag match condition or classification.

Aggregate or irreversibly anonymize allowed measurements before erasure belongs to the separate case “A source must keep anonymized trends after personal records are deleted,” where The trends remain while tested identifiers cannot be reconstructed would be expected. That differs from the condition in this stem: “A verified deletion request targets one customer's personal rows in an active Delta table.”

Perform supported data rewrites and retention-safe vacuum/purge as required belongs to the separate case “An erasure request requires removal from historical physical files after a compliant retention process,” where Approved verification cannot recover the erased values from retained table files would be expected. That differs from the condition in this stem: “A verified deletion request targets one customer's personal rows in an active Delta table.”

Use Delta-supported transactional deletion and verified physical cleanup is appropriate when “An analyst suggests overwriting Parquet files directly to purge Delta rows”; it would be verified by The Delta log remains consistent and erasure is reflected in queries. It does not directly satisfy “A verified deletion request targets one customer's personal rows in an active Delta table,” whose relevant acceptance evidence is The current table no longer returns the customer's rows.

The trends remain while tested identifiers cannot be reconstructed would demonstrate the separate action Aggregate or irreversibly anonymize allowed measurements before erasure, which addresses “A source must keep anonymized trends after personal records are deleted.” It does not verify the requirement “A verified deletion request targets one customer's personal rows in an active Delta table” following Apply a scoped transactional DELETE or supported erasure operation.

Approved verification cannot recover the erased values from retained table files pertains to a different control (Perform supported data rewrites and retention-safe vacuum/purge as required) and a different need (An erasure request requires removal from historical physical files after a compliant retention process). It cannot establish that Apply a scoped transactional DELETE or supported erasure operation met the stated goal.

The Delta log remains consistent and erasure is reflected in queries would demonstrate the separate action Use Delta-supported transactional deletion and verified physical cleanup, which addresses “An analyst suggests overwriting Parquet files directly to purge Delta rows.” It does not verify the requirement “A verified deletion request targets one customer's personal rows in an active Delta table” following Apply a scoped transactional DELETE or supported erasure operation.

Use Delta-supported transactional deletion and verified physical cleanup belongs to the separate case “An analyst suggests overwriting Parquet files directly to purge Delta rows,” where The Delta log remains consistent and erasure is reflected in queries would be expected. That differs from the condition in this stem: “An erasure request requires removal from historical physical files after a compliant retention process.”

This action solves a different issue: “A source must keep anonymized trends after personal records are deleted.” Its normal signal is The trends remain while tested identifiers cannot be reconstructed. Here the requested behavior is “An erasure request requires removal from historical physical files after a compliant retention process,” so that signal is not sufficient.

This action solves a different issue: “A verified deletion request targets one customer's personal rows in an active Delta table.” Its normal signal is The current table no longer returns the customer's rows. Here the requested behavior is “An erasure request requires removal from historical physical files after a compliant retention process,” so that signal is not sufficient.

That observation is a valid indicator for “A source must keep anonymized trends after personal records are deleted” when using Aggregate or irreversibly anonymize allowed measurements before erasure. The scenario instead tests “An erasure request requires removal from historical physical files after a compliant retention process”; the relevant result is Approved verification cannot recover the erased values from retained table files.

This signal belongs to the adjacent case “An analyst suggests overwriting Parquet files directly to purge Delta rows,” whose remedy is Use Delta-supported transactional deletion and verified physical cleanup. The observed result for the present requirement is Approved verification cannot recover the erased values from retained table files.

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 erasure request requires removal from historical physical files after a compliant retention process”; the relevant result is Approved verification cannot recover the erased values from retained table files.

This action solves a different issue: “An erasure request requires removal from historical physical files after a compliant retention process.” Its normal signal is Approved verification cannot recover the erased values from retained table files. Here the requested behavior is “A policy requires deleting raw PII after a specified retention age,” so that signal is not sufficient.

The alternative Use Delta-supported transactional deletion and verified physical cleanup has a distinct purpose—An analyst suggests overwriting Parquet files directly to purge Delta rows. It would not establish the required outcome (A policy requires deleting raw PII after a specified retention age); the necessary verification concerns Rows older than the approved retention period are no longer queryable.

This action solves a different issue: “A source must keep anonymized trends after personal records are deleted.” Its normal signal is The trends remain while tested identifiers cannot be reconstructed. Here the requested behavior is “A policy requires deleting raw PII after a specified retention age,” so that signal is not sufficient.

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 Rows older than the approved retention period are no longer queryable.

The trends remain while tested identifiers cannot be reconstructed pertains to a different control (Aggregate or irreversibly anonymize allowed measurements before erasure) and a different need (A source must keep anonymized trends after personal records are deleted). It cannot establish that Implement a scheduled retention filter and controlled deletion operation met the stated goal.

The Delta log remains consistent and erasure is reflected in queries would demonstrate the separate action Use Delta-supported transactional deletion and verified physical cleanup, which addresses “An analyst suggests overwriting Parquet files directly to purge Delta rows.” It does not verify the requirement “A policy requires deleting raw PII after a specified retention age” following Implement a scheduled retention filter and controlled deletion operation.

The alternative Perform supported data rewrites and retention-safe vacuum/purge as required has a distinct purpose—An erasure request requires removal from historical physical files after a compliant retention process. It would not establish the required outcome (A source must keep anonymized trends after personal records are deleted); the necessary verification concerns The trends remain while tested identifiers cannot be reconstructed.

The alternative Implement a scheduled retention filter and controlled deletion operation has a distinct purpose—A policy requires deleting raw PII after a specified retention age. It would not establish the required outcome (A source must keep anonymized trends after personal records are deleted); the necessary verification concerns The trends remain while tested identifiers cannot be reconstructed.

The alternative Use Delta-supported transactional deletion and verified physical cleanup has a distinct purpose—An analyst suggests overwriting Parquet files directly to purge Delta rows. It would not establish the required outcome (A source must keep anonymized trends after personal records are deleted); the necessary verification concerns The trends remain while tested identifiers cannot be reconstructed.

This signal belongs to the adjacent case “A verified deletion request targets one customer's personal rows in an active Delta table,” whose remedy is Apply a scoped transactional DELETE or supported erasure operation. The observed result for the present requirement is The trends remain while tested identifiers cannot be reconstructed.

The Delta log remains consistent and erasure is reflected in queries pertains to a different control (Use Delta-supported transactional deletion and verified physical cleanup) and a different need (An analyst suggests overwriting Parquet files directly to purge Delta rows). It cannot establish that Aggregate or irreversibly anonymize allowed measurements before erasure met the stated goal.

That observation is a valid indicator for “An erasure request requires removal from historical physical files after a compliant retention process” when using Perform supported data rewrites and retention-safe vacuum/purge as required. The scenario instead tests “A source must keep anonymized trends after personal records are deleted”; the relevant result is The trends remain while tested identifiers cannot be reconstructed.

Perform supported data rewrites and retention-safe vacuum/purge as required belongs to the separate case “An erasure request requires removal from historical physical files after a compliant retention process,” where Approved verification cannot recover the erased values from retained table files would be expected. That differs from the condition in this stem: “An analyst suggests overwriting Parquet files directly to purge Delta rows.”

Aggregate or irreversibly anonymize allowed measurements before erasure is appropriate when “A source must keep anonymized trends after personal records are deleted”; it would be verified by The trends remain while tested identifiers cannot be reconstructed. It does not directly satisfy “An analyst suggests overwriting Parquet files directly to purge Delta rows,” whose relevant acceptance evidence is The Delta log remains consistent and erasure is reflected in queries.

This action solves a different issue: “A policy requires deleting raw PII after a specified retention age.” Its normal signal is Rows older than the approved retention period are no longer queryable. Here the requested behavior is “An analyst suggests overwriting Parquet files directly to purge Delta rows,” so that signal is not sufficient.

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.