Certified Data Engineer Associate Practice Test 67
Question 660
At a tax accounting service, regional sales teams can see one another’s customers from a shared Delta table despite a same-table analytics requirement. The dataset `invoice_lines` is in scope, and direct SQL queries must not bypass sensitivity protections. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Run only a normal, unchanged `invoice_lines` sample and review regional identity claims.
- Review a platform-level availability report for `invoice_lines` without testing whether ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
- Query the same table as two regions and verify disjoint authorized customer subsets
- Check that the intended configuration exists for `invoice_lines` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
C: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
A:Run only a normal, unchanged `invoice_lines` 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.
B:Review a platform-level availability report for `invoice_lines` 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 `invoice_lines` records. It cannot replace the direct exercise: query the same table as two regions and verify disjoint authorized customer subsets.
D: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 ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
Question 661
At a telecom operations group, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `baggage_scans` is in scope, and auditors require tested denials as well as approvals. What evidence should the engineer collect to establish the cause rather than a coincidental symptom?
- 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
- Examine only a normal successful run of `baggage_scans` and trend table grants without recreating the fault.
- Correlate table grants, masking function outputs by principal across affected and unaffected `R034-CASE-133` runs.
Explanation
Correct Answer
D:Correlate table grants, masking function outputs by principal across affected and unaffected `R034-CASE-133` 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 completed run status and aggregate cluster health without record-level correlation. 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 `baggage_scans` 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 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 `baggage_scans` 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 662
At a telecom operations group, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `baggage_scans` is in scope, and auditors require tested denials as well as approvals. Which platform configuration or data-engineering change is most defensible?
- Copy unmasked data to a new unrestricted support catalog; use that approach for `baggage_scans`.
- Apply a governed column mask that returns redacted identifiers for the support group while allowing authorized compliance roles
- Revoke table SELECT for every support analyst despite their approved ticket workload; use that approach for `baggage_scans`.
- Publish the full identifier column and ask analysts to hide it in dashboards; use that approach for `baggage_scans`.
Explanation
Correct Answer
B: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:Copy unmasked data to a new unrestricted support catalog; use that approach for `baggage_scans`. Additional unrestricted copies expand the exposure surface. For `baggage_scans`, this cannot remove the causal limitation: table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
C:Revoke table SELECT for every support analyst despite their approved ticket workload; use that approach for `baggage_scans`. Total denial blocks the required non-sensitive support data. For `baggage_scans`, this cannot remove the causal limitation: table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
D:Publish the full identifier column and ask analysts to hide it in dashboards; use that approach for `baggage_scans`. Dashboard hiding does not prevent direct SQL reads of the sensitive column. For `baggage_scans`, this cannot remove the causal limitation: table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
Question 663
At a telecom operations group, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `baggage_scans` is in scope, and auditors require tested denials as well as approvals. A teammate proposes: "Publish the full identifier column and ask analysts to hide it in dashboards." Which technical limitation is the decisive reason not to approve that specific proposal?
- Total denial blocks the required non-sensitive support data. This would apply to an alternative change for `baggage_scans`.
- Additional unrestricted copies expand the exposure surface. This would apply to another option for `baggage_scans`.
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
- Dashboard hiding does not prevent direct SQL reads of the sensitive column. The proposal does not repair `baggage_scans`.
Explanation
Correct Answer
D:Dashboard hiding does not prevent direct SQL reads of the sensitive column. The proposal does not repair `baggage_scans`. This identifies the known limitation of the exact proposed action. Dashboard hiding does not prevent direct SQL reads of the sensitive column. 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
A:Total denial blocks the required non-sensitive support data. This would apply to an alternative change for `baggage_scans`. This failure applies to the separate proposal "Revoke table SELECT for every support analyst despite their approved ticket workload".
B:Additional unrestricted copies expand the exposure surface. This would apply to another option for `baggage_scans`. This limitation belongs to the different alternative "Copy unmasked data to a new unrestricted support catalog". The stem calls for the specific failure of "Publish the full identifier column and ask analysts to hide it in dashboards".
C: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.
Question 664
At a telecom operations group, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `baggage_scans` is in scope, and auditors require tested denials as well as approvals. What risk-and-cost compromise should the owner accept instead of the proposed shortcuts?
- Allow functional table access while restricting sensitive fields by identity
- Publish the full identifier column and ask analysts to hide it in dashboards
- Copy unmasked data to a new unrestricted support catalog
- Revoke table SELECT for every support analyst despite their approved ticket workload; monitor results only after launch of `baggage_scans`.
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. 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 `baggage_scans`.
C:Copy unmasked data to a new unrestricted support catalog. Additional unrestricted copies expand the exposure surface. Monitoring after deployment does not make this approach a safe bounded tradeoff for `baggage_scans`.
D:Revoke table SELECT for every support analyst despite their approved ticket workload; monitor results only after launch of `baggage_scans`. Total denial blocks the required non-sensitive support data. Monitoring after deployment does not make this approach a safe bounded tradeoff for `baggage_scans`.
Question 665
At a telecom operations group, support analysts may inspect ticket records but must not see full national identifiers stored in one column. The dataset `baggage_scans` is in scope, and auditors require tested denials as well as approvals. Which direct test could falsify the proposed fix instead of only confirming deployment?
- Review a platform-level availability report for `baggage_scans` without testing whether table-wide SELECT gives access to sensitive column values unless masking restricts them at query time.
- Run only a normal, unchanged `baggage_scans` sample and review table grants.
- Check that the intended configuration exists for `baggage_scans` and that a healthy run succeeded, without inducing the earlier failure.
- Run the same query as support and compliance users and verify the intended masked and clear outputs
Explanation
Correct Answer
D: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:Review a platform-level availability report for `baggage_scans` 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 `baggage_scans` records. It cannot replace the direct exercise: run the same query as support and compliance users and verify the intended masked and clear outputs.
B:Run only a normal, unchanged `baggage_scans` 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.
C:Check that the intended configuration exists for `baggage_scans` 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.
Question 666
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. Which correlated observation is the strongest basis for the change decision?
- 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
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- Correlate regional identity claims, query results by role across affected and unaffected `R034-CASE-134` runs.
Explanation
Correct Answer
D:Correlate regional identity claims, query results by role across affected and unaffected `R034-CASE-134` runs.. By joining regional identity claims, query results by role, active row filter, and direct-table access test across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: ordinary table SELECT does not limit which region’s rows are returned without a row-level policy. It also sets a measurable baseline for query the same table as two regions and verify disjoint authorized customer subsets.
Incorrect Answers
A:Review completed run status and aggregate cluster health without record-level correlation. A successful aggregate platform state can coexist with ordinary table SELECT does not limit which region’s rows are returned without a row-level policy. This check never observes the affected `program_enrollments` 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 regional identity claims, query results by role, active row filter, and direct-table access test, the direct means of distinguishing ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
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 ordinary table SELECT does not limit which region’s rows are returned without a row-level policy. The failing-path regional identity claims, query results by role, active row filter, and direct-table access test has to be correlated before attributing cause.
Question 667
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 implementation should the engineer select for the failing workflow?
- Apply a row filter based on caller group or region entitlement so each team sees only authorized rows
- Remove SELECT entirely from all teams regardless of their authorized customers; use that approach for `program_enrollments`.
- Create a view with no WHERE clause and grant it to all regional teams; use that approach for `program_enrollments`.
- Filter rows only in the BI dashboard while leaving direct table queries unrestricted; use that approach for `program_enrollments`.
Explanation
Correct Answer
A:Apply a row filter based on caller group or region entitlement so each team sees only authorized rows. This directly addresses ordinary table SELECT does not limit which region’s rows are returned without a row-level policy. The design should be accepted only after query the same table as two regions and verify disjoint authorized customer subsets; the related operational boundary is to enforce regional entitlements centrally while retaining one shared dataset.
Incorrect Answers
B:Remove SELECT entirely from all teams regardless of their authorized customers; use that approach for `program_enrollments`. Full denial prevents the requested legitimate regional analytics. For `program_enrollments`, this cannot remove the causal limitation: ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
C:Create a view with no WHERE clause and grant it to all regional teams; use that approach for `program_enrollments`. An unrestricted view exposes the same cross-region data as the base table. For `program_enrollments`, this cannot remove the causal limitation: ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
D:Filter rows only in the BI dashboard while leaving direct table queries unrestricted; use that approach for `program_enrollments`. Dashboard-only filtering can be bypassed by direct SQL access. For `program_enrollments`, this cannot remove the causal limitation: ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
Question 668
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. A teammate proposes: "Filter rows only in the BI dashboard while leaving direct table queries unrestricted." Which technical limitation is the decisive reason not to approve that specific proposal?
- Dashboard-only filtering can be bypassed by direct SQL access. The proposal does not repair `program_enrollments`.
- Full denial prevents the requested legitimate regional analytics. This would apply to another option for `program_enrollments`.
- An unrestricted view exposes the same cross-region data as the base table. This would apply to an alternative change for `program_enrollments`.
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
Explanation
Correct Answer
A:Dashboard-only filtering can be bypassed by direct SQL access. The proposal does not repair `program_enrollments`. This identifies the known limitation of the exact proposed action. Dashboard-only filtering can be bypassed by direct SQL access. The underlying problem remains ordinary table SELECT does not limit which region’s rows are returned without a row-level policy; Apply a row filter based on caller group or region entitlement so each team sees only authorized rows instead targets that failure.
Incorrect Answers
B:Full denial prevents the requested legitimate regional analytics. This would apply to another option for `program_enrollments`. This limitation belongs to the different alternative "Remove SELECT entirely from all teams regardless of their authorized customers". The stem calls for the specific failure of "Filter rows only in the BI dashboard while leaving direct table queries unrestricted".
C:An unrestricted view exposes the same cross-region data as the base table. This would apply to an alternative change for `program_enrollments`. This failure applies to the separate proposal "Create a view with no WHERE clause and grant it to all regional teams".
D: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 ordinary table SELECT does not limit which region’s rows are returned without a row-level policy.
Question 669
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. Which decision preserves the stated data contract while keeping the change scope proportionate?
- Enforce regional entitlements centrally while retaining one shared dataset
- Remove SELECT entirely from all teams regardless of their authorized customers
- Create a view with no WHERE clause and grant it to all regional teams
- Filter rows only in the BI dashboard while leaving direct table queries unrestricted
Explanation
Correct Answer
A:Enforce regional entitlements centrally while retaining one shared dataset. This explicitly bounds the compromise while still addressing ordinary table SELECT does not limit which region’s rows are returned without a row-level policy. Acceptance relies on query the same table as two regions and verify disjoint authorized customer subsets rather than simply declaring the change complete.
Incorrect Answers
B:Remove SELECT entirely from all teams regardless of their authorized customers. Full denial prevents the requested legitimate regional analytics. Monitoring after deployment does not make this approach a safe bounded tradeoff for `program_enrollments`.
C:Create a view with no WHERE clause and grant it to all regional teams. An unrestricted view exposes the same cross-region data as the base table. Monitoring after deployment does not make this approach a safe bounded tradeoff for `program_enrollments`.
D:Filter rows only in the BI dashboard while leaving direct table queries unrestricted. Dashboard-only filtering can be bypassed by direct SQL access. Monitoring after deployment does not make this approach a safe bounded tradeoff for `program_enrollments`.
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.