Certified Data Engineer Associate Practice Test 70
Question 690
At a logistics carrier, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `soil_measurements` is in scope, and effective access must follow least privilege. What verification provides evidence of correct behavior under the original adverse condition?
- Review a platform-level availability report for `soil_measurements` without testing whether per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
- Create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users
- Run only a normal, unchanged `soil_measurements` sample and review governed tag assignments.
- Check that the intended configuration exists for `soil_measurements` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
B:Create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users. This reproduces the scenario-dependent condition, verifies governed tag assignments, ABAC policy scope, runtime support, and masked query results by user, and directly tests whether per-table discretionary masking is hard to apply consistently as new tagged columns arrive is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `soil_measurements` without testing whether per-table discretionary masking is hard to apply consistently as new tagged columns arrive. Aggregate availability does not establish the behavior of affected `soil_measurements` records. It cannot replace the direct exercise: create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users.
C:Run only a normal, unchanged `soil_measurements` sample and review governed tag assignments. A normal sample does not challenge per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
D:Check that the intended configuration exists for `soil_measurements` and that a healthy run succeeded, without inducing the earlier failure. Installed configuration and a healthy run are insufficient to prove the failure mode is gone. The original issue was per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
Question 691
At a food delivery company, a government data lake applies a central region row filter but one new table lacks the governed region tag and is unexpectedly visible. The dataset `patient_visits` is in scope, and the underlying data retention policy must be preserved. Which investigation best tests the stated constraint with direct data?
- Compare the current configuration and the signed change approval, without source-row evidence
- Correlate governed tag key/value, effective policy definitions across affected and unaffected `R034-CASE-139` runs.
- Review completed run status and aggregate cluster health without record-level correlation
- Examine only a normal successful run of `patient_visits` and trend governed tag key/value without recreating the fault.
Explanation
Correct Answer
B:Correlate governed tag key/value, effective policy definitions across affected and unaffected `R034-CASE-139` runs.. By joining governed tag key/value, effective policy definitions, allowed group identities, and row filter query results across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: ABAC policy matching depends on the governed attributes attached to the intended target objects. It also sets a measurable baseline for query as two regional principals before and after tagging and confirm only their permitted rows are visible.
Incorrect Answers
A:Compare the current configuration and the signed change approval, without source-row evidence. A desired configuration and approval ticket are not runtime proof. In this case they omit governed tag key/value, effective policy definitions, allowed group identities, and row filter query results, the direct means of distinguishing ABAC policy matching depends on the governed attributes attached to the intended target objects.
C:Review completed run status and aggregate cluster health without record-level correlation. A successful aggregate platform state can coexist with ABAC policy matching depends on the governed attributes attached to the intended target objects. This check never observes the affected `patient_visits` records or their causal path.
D:Examine only a normal successful run of `patient_visits` and trend governed tag key/value without recreating the fault. A healthy-run trend can be useful, but it does not expose ABAC policy matching depends on the governed attributes attached to the intended target objects. The failing-path governed tag key/value, effective policy definitions, allowed group identities, and row filter query results has to be correlated before attributing cause.
Question 692
At a food delivery company, a government data lake applies a central region row filter but one new table lacks the governed region tag and is unexpectedly visible. The dataset `patient_visits` is in scope, and the underlying data retention policy must be preserved. Which option targets the actual technical dependency rather than an incidental symptom?
- Rewrite every analyst notebook query to add its own region predicate; use that approach for `patient_visits`.
- Assign the required governed tag and verify the centrally scoped ABAC row filter applies to the table
- Remove the ABAC policy because one table was not matched; use that approach for `patient_visits`.
- Assign an arbitrary ungoverned label without testing policy matching; use that approach for `patient_visits`.
Explanation
Correct Answer
B:Assign the required governed tag and verify the centrally scoped ABAC row filter applies to the table. This directly addresses ABAC policy matching depends on the governed attributes attached to the intended target objects. The design should be accepted only after query as two regional principals before and after tagging and confirm only their permitted rows are visible; the related operational boundary is to retain central policy ownership while making onboarding checks require correct tags.
Incorrect Answers
A:Rewrite every analyst notebook query to add its own region predicate; use that approach for `patient_visits`. Client-side WHERE clauses are bypassable and do not repair central policy coverage. For `patient_visits`, this cannot remove the causal limitation: ABAC policy matching depends on the governed attributes attached to the intended target objects.
C:Remove the ABAC policy because one table was not matched; use that approach for `patient_visits`. Disabling the guardrail broadens access and ignores the missing attribute. For `patient_visits`, this cannot remove the causal limitation: ABAC policy matching depends on the governed attributes attached to the intended target objects.
D:Assign an arbitrary ungoverned label without testing policy matching; use that approach for `patient_visits`. A free-text label may not satisfy governed tag policy predicates. For `patient_visits`, this cannot remove the causal limitation: ABAC policy matching depends on the governed attributes attached to the intended target objects.
Question 693
At a food delivery company, a government data lake applies a central region row filter but one new table lacks the governed region tag and is unexpectedly visible. The dataset `patient_visits` is in scope, and the underlying data retention policy must be preserved. A teammate proposes: "Remove the ABAC policy because one table was not matched." Which technical limitation is the decisive reason not to approve that specific proposal?
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
- A free-text label may not satisfy governed tag policy predicates. This would apply to an alternative change for `patient_visits`.
- Disabling the guardrail broadens access and ignores the missing attribute. The proposal does not repair `patient_visits`.
- Client-side WHERE clauses are bypassable and do not repair central policy coverage. This would apply to another option for `patient_visits`.
Explanation
Correct Answer
C:Disabling the guardrail broadens access and ignores the missing attribute. The proposal does not repair `patient_visits`. This identifies the known limitation of the exact proposed action. Disabling the guardrail broadens access and ignores the missing attribute. The underlying problem remains ABAC policy matching depends on the governed attributes attached to the intended target objects; Assign the required governed tag and verify the centrally scoped ABAC row filter applies to the table instead targets that failure.
Incorrect Answers
A:The failed query is caused only by a temporary notebook session, not catalog scope or security settings. The case provides a concrete failing data or control path; a mere alternate theory does not address ABAC policy matching depends on the governed attributes attached to the intended target objects.
B:A free-text label may not satisfy governed tag policy predicates. This would apply to an alternative change for `patient_visits`. This failure applies to the separate proposal "Assign an arbitrary ungoverned label without testing policy matching".
D:Client-side WHERE clauses are bypassable and do not repair central policy coverage. This would apply to another option for `patient_visits`. This limitation belongs to the different alternative "Rewrite every analyst notebook query to add its own region predicate". The stem calls for the specific failure of "Remove the ABAC policy because one table was not matched".
Question 694
At a food delivery company, a government data lake applies a central region row filter but one new table lacks the governed region tag and is unexpectedly visible. The dataset `patient_visits` is in scope, and the underlying data retention policy must be preserved. What operational boundary should be documented for approval?
- Retain central policy ownership while making onboarding checks require correct tags
- Assign an arbitrary ungoverned label without testing policy matching
- Remove the ABAC policy because one table was not matched
- Rewrite every analyst notebook query to add its own region predicate; monitor results only after launch of `patient_visits`.
Explanation
Correct Answer
A:Retain central policy ownership while making onboarding checks require correct tags. This explicitly bounds the compromise while still addressing ABAC policy matching depends on the governed attributes attached to the intended target objects. Acceptance relies on query as two regional principals before and after tagging and confirm only their permitted rows are visible rather than simply declaring the change complete.
Incorrect Answers
B:Assign an arbitrary ungoverned label without testing policy matching. A free-text label may not satisfy governed tag policy predicates. Monitoring after deployment does not make this approach a safe bounded tradeoff for `patient_visits`.
C:Remove the ABAC policy because one table was not matched. Disabling the guardrail broadens access and ignores the missing attribute. Monitoring after deployment does not make this approach a safe bounded tradeoff for `patient_visits`.
D:Rewrite every analyst notebook query to add its own region predicate; monitor results only after launch of `patient_visits`. Client-side WHERE clauses are bypassable and do not repair central policy coverage. Monitoring after deployment does not make this approach a safe bounded tradeoff for `patient_visits`.
Question 695
At a food delivery company, a government data lake applies a central region row filter but one new table lacks the governed region tag and is unexpectedly visible. The dataset `patient_visits` is in scope, and the underlying data retention policy must be preserved. Which validation should be required in the release record?
- Review a platform-level availability report for `patient_visits` without testing whether ABAC policy matching depends on the governed attributes attached to the intended target objects.
- Run only a normal, unchanged `patient_visits` sample and review governed tag key/value.
- Query as two regional principals before and after tagging and confirm only their permitted rows are visible
- Check that the intended configuration exists for `patient_visits` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
C:Query as two regional principals before and after tagging and confirm only their permitted rows are visible. This reproduces the scenario-dependent condition, verifies governed tag key/value, effective policy definitions, allowed group identities, and row filter query results, and directly tests whether ABAC policy matching depends on the governed attributes attached to the intended target objects is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `patient_visits` without testing whether ABAC policy matching depends on the governed attributes attached to the intended target objects. Aggregate availability does not establish the behavior of affected `patient_visits` records. It cannot replace the direct exercise: query as two regional principals before and after tagging and confirm only their permitted rows are visible.
B:Run only a normal, unchanged `patient_visits` sample and review governed tag key/value. A normal sample does not challenge ABAC policy matching depends on the governed attributes attached to the intended target objects.
D:Check that the intended configuration exists for `patient_visits` and that a healthy run succeeded, without inducing the earlier failure. Installed configuration and a healthy run are insufficient to prove the failure mode is gone. The original issue was ABAC policy matching depends on the governed attributes attached to the intended target objects.
Question 696
At an education technology firm, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `courier_events` is in scope, and effective access must follow least privilege. Before choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Review completed run status and aggregate cluster health without record-level correlation
- Compare the current configuration and the signed change approval, without source-row evidence
- Correlate governed tag assignments, ABAC policy scope across affected and unaffected `R034-CASE-140` runs.
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
Explanation
Correct Answer
C:Correlate governed tag assignments, ABAC policy scope across affected and unaffected `R034-CASE-140` runs.. By joining governed tag assignments, ABAC policy scope, runtime support, and masked query results by user across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: per-table discretionary masking is hard to apply consistently as new tagged columns arrive. It also sets a measurable baseline for create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users.
Incorrect Answers
A:Review completed run status and aggregate cluster health without record-level correlation. A successful aggregate platform state can coexist with per-table discretionary masking is hard to apply consistently as new tagged columns arrive. This check never observes the affected `courier_events` records or their causal path.
B:Compare the current configuration and the signed change approval, without source-row evidence. A desired configuration and approval ticket are not runtime proof. In this case they omit governed tag assignments, ABAC policy scope, runtime support, and masked query results by user, the direct means of distinguishing per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
D:Inspect normal-period success metrics for the stated dataset without reproducing the source error. A healthy-run trend can be useful, but it does not expose per-table discretionary masking is hard to apply consistently as new tagged columns arrive. The failing-path governed tag assignments, ABAC policy scope, runtime support, and masked query results by user has to be correlated before attributing cause.
Question 697
At an education technology firm, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `courier_events` is in scope, and effective access must follow least privilege. Which implementation best resolves the stated defect without breaking the business constraint?
- Create one user-managed view for each current table and ignore new objects; use that approach for `courier_events`.
- Use Unity Catalog ABAC with governed sensitive-data tags and a centrally scoped column mask policy on matching objects
- Grant every consumer direct access then rely on application code to redact; use that approach for `courier_events`.
- Use ungoverned text tags and expect them to enforce a security mask automatically; use that approach for `courier_events`.
Explanation
Correct Answer
B:Use Unity Catalog ABAC with governed sensitive-data tags and a centrally scoped column mask policy on matching objects. This directly addresses per-table discretionary masking is hard to apply consistently as new tagged columns arrive. The design should be accepted only after create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users; the related operational boundary is to manage the security rule once at the catalog or schema scope rather than ad hoc user-managed copies.
Incorrect Answers
A:Create one user-managed view for each current table and ignore new objects; use that approach for `courier_events`. Manual views do not automatically cover newly created sensitive tables. For `courier_events`, this cannot remove the causal limitation: per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
C:Grant every consumer direct access then rely on application code to redact; use that approach for `courier_events`. Application-only masking can be bypassed by direct query access. For `courier_events`, this cannot remove the causal limitation: per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
D:Use ungoverned text tags and expect them to enforce a security mask automatically; use that approach for `courier_events`. Descriptive tags alone do not create an active ABAC enforcement policy. For `courier_events`, this cannot remove the causal limitation: per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
Question 698
At an education technology firm, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `courier_events` is in scope, and effective access must follow least privilege. A teammate proposes: "Use ungoverned text tags and expect them to enforce a security mask automatically." Which technical limitation is the decisive reason not to approve that specific proposal?
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
- Descriptive tags alone do not create an active ABAC enforcement policy. The proposal does not repair `courier_events`.
- Manual views do not automatically cover newly created sensitive tables. This would apply to an alternative change for `courier_events`.
- Application-only masking can be bypassed by direct query access. This would apply to another option for `courier_events`.
Explanation
Correct Answer
B:Descriptive tags alone do not create an active ABAC enforcement policy. The proposal does not repair `courier_events`. This identifies the known limitation of the exact proposed action. Descriptive tags alone do not create an active ABAC enforcement policy. The underlying problem remains per-table discretionary masking is hard to apply consistently as new tagged columns arrive; Use Unity Catalog ABAC with governed sensitive-data tags and a centrally scoped column mask policy on matching objects instead targets that failure.
Incorrect Answers
A:The failed query is caused only by a temporary notebook session, not catalog scope or security settings. The case provides a concrete failing data or control path; a mere alternate theory does not address per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
C:Manual views do not automatically cover newly created sensitive tables. This would apply to an alternative change for `courier_events`. This failure applies to the separate proposal "Create one user-managed view for each current table and ignore new objects".
D:Application-only masking can be bypassed by direct query access. This would apply to another option for `courier_events`. This limitation belongs to the different alternative "Grant every consumer direct access then rely on application code to redact". The stem calls for the specific failure of "Use ungoverned text tags and expect them to enforce a security mask automatically".
Question 699
At an education technology firm, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `courier_events` is in scope, and effective access must follow least privilege. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Manage the security rule once at the catalog or schema scope rather than ad hoc user-managed copies
- Use ungoverned text tags and expect them to enforce a security mask automatically
- Create one user-managed view for each current table and ignore new objects
- Grant every consumer direct access then rely on application code to redact
Explanation
Correct Answer
A:Manage the security rule once at the catalog or schema scope rather than ad hoc user-managed copies. This explicitly bounds the compromise while still addressing per-table discretionary masking is hard to apply consistently as new tagged columns arrive. Acceptance relies on create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users rather than simply declaring the change complete.
Incorrect Answers
B:Use ungoverned text tags and expect them to enforce a security mask automatically. Descriptive tags alone do not create an active ABAC enforcement policy. Monitoring after deployment does not make this approach a safe bounded tradeoff for `courier_events`.
C:Create one user-managed view for each current table and ignore new objects. Manual views do not automatically cover newly created sensitive tables. Monitoring after deployment does not make this approach a safe bounded tradeoff for `courier_events`.
D:Grant every consumer direct access then rely on application code to redact. Application-only masking can be bypassed by direct query access. Monitoring after deployment does not make this approach a safe bounded tradeoff for `courier_events`.
Question 700
At an education technology firm, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `courier_events` is in scope, and effective access must follow least privilege. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Run only a normal, unchanged `courier_events` sample and review governed tag assignments.
- Create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users
- Review a platform-level availability report for `courier_events` without testing whether per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
- Check that the intended configuration exists for `courier_events` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
B:Create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users. This reproduces the scenario-dependent condition, verifies governed tag assignments, ABAC policy scope, runtime support, and masked query results by user, and directly tests whether per-table discretionary masking is hard to apply consistently as new tagged columns arrive is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `courier_events` sample and review governed tag assignments. A normal sample does not challenge per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
C:Review a platform-level availability report for `courier_events` without testing whether per-table discretionary masking is hard to apply consistently as new tagged columns arrive. Aggregate availability does not establish the behavior of affected `courier_events` records. It cannot replace the direct exercise: create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users.
D:Check that the intended configuration exists for `courier_events` and that a healthy run succeeded, without inducing the earlier failure. Installed configuration and a healthy run are insufficient to prove the failure mode is gone. The original issue was per-table discretionary masking is hard to apply consistently as new tagged columns arrive.