Certified Data Engineer Associate Practice Test 68
Question 670
At a city utilities office, regional sales teams can see one another’s customers from a shared Delta table despite a same-table analytics requirement. The dataset `program_enrollments` is in scope, and direct SQL queries must not bypass sensitivity protections. What verification provides evidence of correct behavior under the original adverse condition?
- Query the same table as two regions and verify disjoint authorized customer subsets
- Check that the intended configuration exists for `program_enrollments` and that a healthy run succeeded, without inducing the earlier failure.
- Run only a normal, unchanged `program_enrollments` sample and review regional identity claims.
- Review a platform-level availability report for `program_enrollments` without testing whether ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
Explanation
Correct Answer
A:Query the same table as two regions and verify disjoint authorized customer subsets. This reproduces the scenario-dependent condition, verifies regional identity claims, query results by role, active row filter, and direct-table access test, and directly tests whether ordinary table SELECT does not limit which region’s rows are returned without a row-level policy is resolved. Observed results, not intent, determine approval.
Incorrect Answers
B:Check that the intended configuration exists for `program_enrollments` 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 ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
C:Run only a normal, unchanged `program_enrollments` sample and review regional identity claims. A normal sample does not challenge ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
D:Review a platform-level availability report for `program_enrollments` without testing whether ordinary table SELECT does not limit which region’s rows are returned without a row-level policy. Aggregate availability does not establish the behavior of affected `program_enrollments` records. It cannot replace the direct exercise: query the same table as two regions and verify disjoint authorized customer subsets.
Question 671
At a ticketing marketplace, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `invoice_lines` is in scope, and auditors require tested denials as well as approvals. Which investigation best tests the stated constraint with direct data?
- Review aggregate cluster availability and job completion for `invoice_lines` without correlating the observed error path.
- Compare the saved configuration with the signed change ticket for `invoice_lines` while omitting source and output records.
- Examine only a normal successful run of `invoice_lines` and trend table grants without recreating the fault.
- Correlate table grants, masking function outputs by principal across affected and unaffected `R034-CASE-135` runs.
Explanation
Correct Answer
D:Correlate table grants, masking function outputs by principal across affected and unaffected `R034-CASE-135` runs.. By joining table grants, masking function outputs by principal, sensitive column tags, and audit queries across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: table-wide SELECT gives access to sensitive column values unless masking restricts them at query time. It also sets a measurable baseline for run the same query as support and compliance users and verify the intended masked and clear outputs.
Incorrect Answers
A:Review aggregate cluster availability and job completion for `invoice_lines` without correlating the observed error path. A successful aggregate platform state can coexist with table-wide SELECT gives access to sensitive column values unless masking restricts them at query time. This check never observes the affected `invoice_lines` records or their causal path.
B:Compare the saved configuration with the signed change ticket for `invoice_lines` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit table grants, masking function outputs by principal, sensitive column tags, and audit queries, the direct means of distinguishing table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
C:Examine only a normal successful run of `invoice_lines` and trend table grants without recreating the fault. A healthy-run trend can be useful, but it does not expose table-wide SELECT gives access to sensitive column values unless masking restricts them at query time. The failing-path table grants, masking function outputs by principal, sensitive column tags, and audit queries has to be correlated before attributing cause.
Question 672
At a ticketing marketplace, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `invoice_lines` is in scope, and auditors require tested denials as well as approvals. Which option targets the actual technical dependency rather than an incidental symptom?
- Revoke table SELECT for every support analyst despite their approved ticket workload; use that approach for `invoice_lines`.
- Publish the full identifier column and ask analysts to hide it in dashboards; use that approach for `invoice_lines`.
- Apply a governed column mask that returns redacted identifiers for the support group while allowing authorized compliance roles
- Copy unmasked data to a new unrestricted support catalog; use that approach for `invoice_lines`.
Explanation
Correct Answer
C:Apply a governed column mask that returns redacted identifiers for the support group while allowing authorized compliance roles. This directly addresses table-wide SELECT gives access to sensitive column values unless masking restricts them at query time. The design should be accepted only after run the same query as support and compliance users and verify the intended masked and clear outputs; the related operational boundary is to allow functional table access while restricting sensitive fields by identity.
Incorrect Answers
A:Revoke table SELECT for every support analyst despite their approved ticket workload; use that approach for `invoice_lines`. Total denial blocks the required non-sensitive support data. For `invoice_lines`, this cannot remove the causal limitation: table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
B:Publish the full identifier column and ask analysts to hide it in dashboards; use that approach for `invoice_lines`. Dashboard hiding does not prevent direct SQL reads of the sensitive column. For `invoice_lines`, this cannot remove the causal limitation: table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
D:Copy unmasked data to a new unrestricted support catalog; use that approach for `invoice_lines`. Additional unrestricted copies expand the exposure surface. For `invoice_lines`, this cannot remove the causal limitation: table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
Question 673
At a ticketing marketplace, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `invoice_lines` is in scope, and auditors require tested denials as well as approvals. A teammate proposes: "Revoke table SELECT for every support analyst despite their approved ticket workload." Which technical limitation is the decisive reason not to approve that specific proposal?
- Total denial blocks the required non-sensitive support data. The proposal does not repair `invoice_lines`.
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
- Additional unrestricted copies expand the exposure surface. This would apply to an alternative change for `invoice_lines`.
- Dashboard hiding does not prevent direct SQL reads of the sensitive column. This would apply to another option for `invoice_lines`.
Explanation
Correct Answer
A:Total denial blocks the required non-sensitive support data. The proposal does not repair `invoice_lines`. This identifies the known limitation of the exact proposed action. Total denial blocks the required non-sensitive support data. The underlying problem remains table-wide SELECT gives access to sensitive column values unless masking restricts them at query time; Apply a governed column mask that returns redacted identifiers for the support group while allowing authorized compliance roles instead targets that failure.
Incorrect Answers
B: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 table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
C:Additional unrestricted copies expand the exposure surface. This would apply to an alternative change for `invoice_lines`. This failure applies to the separate proposal "Copy unmasked data to a new unrestricted support catalog".
D:Dashboard hiding does not prevent direct SQL reads of the sensitive column. This would apply to another option for `invoice_lines`. This limitation belongs to the different alternative "Publish the full identifier column and ask analysts to hide it in dashboards". The stem calls for the specific failure of "Revoke table SELECT for every support analyst despite their approved ticket workload".
Question 674
At a ticketing marketplace, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `invoice_lines` is in scope, and auditors require tested denials as well as approvals. What operational boundary should be documented for approval?
- Allow functional table access while restricting sensitive fields by identity
- Publish the full identifier column and ask analysts to hide it in dashboards; monitor results only after launch of `invoice_lines`.
- Copy unmasked data to a new unrestricted support catalog; monitor results only after launch of `invoice_lines`.
- Revoke table SELECT for every support analyst despite their approved ticket workload; monitor results only after launch of `invoice_lines`.
Explanation
Correct Answer
A:Allow functional table access while restricting sensitive fields by identity. This explicitly bounds the compromise while still addressing table-wide SELECT gives access to sensitive column values unless masking restricts them at query time. Acceptance relies on run the same query as support and compliance users and verify the intended masked and clear outputs rather than simply declaring the change complete.
Incorrect Answers
B:Publish the full identifier column and ask analysts to hide it in dashboards; monitor results only after launch of `invoice_lines`. Dashboard hiding does not prevent direct SQL reads of the sensitive column. Monitoring after deployment does not make this approach a safe bounded tradeoff for `invoice_lines`.
C:Copy unmasked data to a new unrestricted support catalog; monitor results only after launch of `invoice_lines`. Additional unrestricted copies expand the exposure surface. Monitoring after deployment does not make this approach a safe bounded tradeoff for `invoice_lines`.
D:Revoke table SELECT for every support analyst despite their approved ticket workload; monitor results only after launch of `invoice_lines`. Total denial blocks the required non-sensitive support data. Monitoring after deployment does not make this approach a safe bounded tradeoff for `invoice_lines`.
Question 675
At a ticketing marketplace, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `invoice_lines` is in scope, and auditors require tested denials as well as approvals. Which validation should be required in the release record?
- Check that the intended configuration exists for `invoice_lines` and that a healthy run succeeded, without inducing the earlier failure.
- Run only a normal, unchanged `invoice_lines` sample and review table grants.
- Run the same query as support and compliance users and verify the intended masked and clear outputs
- Review a platform-level availability report for `invoice_lines` without testing whether table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
Explanation
Correct Answer
C:Run the same query as support and compliance users and verify the intended masked and clear outputs. This reproduces the scenario-dependent condition, verifies table grants, masking function outputs by principal, sensitive column tags, and audit queries, and directly tests whether table-wide SELECT gives access to sensitive column values unless masking restricts them at query time is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Check that the intended configuration exists for `invoice_lines` 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 table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
B:Run only a normal, unchanged `invoice_lines` sample and review table grants. A normal sample does not challenge table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
D:Review a platform-level availability report for `invoice_lines` without testing whether table-wide SELECT gives access to sensitive column values unless masking restricts them at query time. Aggregate availability does not establish the behavior of affected `invoice_lines` records. It cannot replace the direct exercise: run the same query as support and compliance users and verify the intended masked and clear outputs.
Question 676
At a regional banking group, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `patient_visits` 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?
- Correlate governed tag assignments, ABAC policy scope across affected and unaffected `R034-CASE-136` runs.
- Review completed run status and aggregate cluster health without record-level correlation
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- Compare the saved configuration with the signed change ticket for `patient_visits` while omitting source and output records.
Explanation
Correct Answer
A:Correlate governed tag assignments, ABAC policy scope across affected and unaffected `R034-CASE-136` 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
B: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 `patient_visits` records or their causal path.
C: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.
D:Compare the saved configuration with the signed change ticket for `patient_visits` while omitting source and output records. 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.
Question 677
At a regional banking group, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `patient_visits` 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 `patient_visits`.
- Use ungoverned text tags and expect them to enforce a security mask automatically; use that approach for `patient_visits`.
- Grant every consumer direct access then rely on application code to redact; use that approach for `patient_visits`.
- Use Unity Catalog ABAC with governed sensitive-data tags and a centrally scoped column mask policy on matching objects
Explanation
Correct Answer
D: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 `patient_visits`. Manual views do not automatically cover newly created sensitive tables. For `patient_visits`, this cannot remove the causal limitation: per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
B:Use ungoverned text tags and expect them to enforce a security mask automatically; use that approach for `patient_visits`. Descriptive tags alone do not create an active ABAC enforcement policy. For `patient_visits`, 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 `patient_visits`. Application-only masking can be bypassed by direct query access. For `patient_visits`, this cannot remove the causal limitation: per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
Question 678
At a regional banking group, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `patient_visits` is in scope, and effective access must follow least privilege. A teammate proposes: "Create one user-managed view for each current table and ignore new objects." 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.
- Application-only masking can be bypassed by direct query access. This would apply to an alternative change for `patient_visits`.
- Descriptive tags alone do not create an active ABAC enforcement policy. This would apply to another option for `patient_visits`.
- Manual views do not automatically cover newly created sensitive tables. The proposal does not repair `patient_visits`.
Explanation
Correct Answer
D:Manual views do not automatically cover newly created sensitive tables. The proposal does not repair `patient_visits`. This identifies the known limitation of the exact proposed action. Manual views do not automatically cover newly created sensitive tables. 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.
B:Application-only masking can be bypassed by direct query access. This would apply to an alternative change for `patient_visits`. This failure applies to the separate proposal "Grant every consumer direct access then rely on application code to redact".
C:Descriptive tags alone do not create an active ABAC enforcement policy. This would apply to another option for `patient_visits`. This limitation belongs to the different alternative "Use ungoverned text tags and expect them to enforce a security mask automatically". The stem calls for the specific failure of "Create one user-managed view for each current table and ignore new objects".
Question 679
At a regional banking group, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `patient_visits` 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
- Grant every consumer direct access then rely on application code to redact
- 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; monitor results only after launch of `patient_visits`.
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: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 `patient_visits`.
C: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 `patient_visits`.
D:Create one user-managed view for each current table and ignore new objects; monitor results only after launch of `patient_visits`. Manual views do not automatically cover newly created sensitive tables. Monitoring after deployment does not make this approach a safe bounded tradeoff for `patient_visits`.
Question 680
At a regional banking group, several catalogs contain newly created SSN columns, and manually attaching masks table by table leaves sensitive columns uncovered. The dataset `patient_visits` is in scope, and effective access must follow least privilege. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Check that the intended configuration exists for `patient_visits` and that a healthy run succeeded, without inducing the earlier failure.
- Review a platform-level availability report for `patient_visits` without testing whether per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
- Run only a normal, unchanged `patient_visits` sample and review governed tag assignments.
- Create a newly tagged SSN column in scope and confirm the central policy masks it for unauthorized users
Explanation
Correct Answer
D: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: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 per-table discretionary masking is hard to apply consistently as new tagged columns arrive.
B:Review a platform-level availability report for `patient_visits` 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 `patient_visits` 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 `patient_visits` 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.