Certified Data Engineer Associate Practice Test 64
Question 630
At a wholesale pharmacy group, an analyst has SELECT on a Unity Catalog table but receives a permission error because catalog and schema usage were not granted. The dataset `vehicle_arrivals` is in scope, and the underlying data retention policy must be preserved. What verification provides evidence of correct behavior under the original adverse condition?
- Query as the analyst before and after the minimum grants and confirm unrelated schemas remain inaccessible
- Run only a normal, unchanged `vehicle_arrivals` sample and review effective grants on catalog.
- Review a platform-level availability report for `vehicle_arrivals` without testing whether table-level SELECT alone is insufficient without parent namespace usage privileges.
- Check that the intended configuration exists for `vehicle_arrivals` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
A:Query as the analyst before and after the minimum grants and confirm unrelated schemas remain inaccessible. This reproduces the scenario-dependent condition, verifies effective grants on catalog, schema and table, denied query error, and test principal identity, and directly tests whether table-level SELECT alone is insufficient without parent namespace usage privileges is resolved. Observed results, not intent, determine approval.
Incorrect Answers
B:Run only a normal, unchanged `vehicle_arrivals` sample and review effective grants on catalog. A normal sample does not challenge table-level SELECT alone is insufficient without parent namespace usage privileges.
C:Review a platform-level availability report for `vehicle_arrivals` without testing whether table-level SELECT alone is insufficient without parent namespace usage privileges. Aggregate availability does not establish the behavior of affected `vehicle_arrivals` records. It cannot replace the direct exercise: query as the analyst before and after the minimum grants and confirm unrelated schemas remain inaccessible.
D:Check that the intended configuration exists for `vehicle_arrivals` 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-level SELECT alone is insufficient without parent namespace usage privileges.
Question 631
At a marketplace risk team, a temporary contractor retains SELECT on a confidential table after project completion and access review flags the grant. The dataset `payment_decisions` is in scope, and effective access must follow least privilege. Which investigation best tests the stated constraint with direct data?
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- Correlate principal group membership, direct and inherited grants across affected and unaffected `R034-CASE-127` runs.
- Review completed run status and aggregate cluster health without record-level correlation
- Compare the saved configuration with the signed change ticket for `payment_decisions` while omitting source and output records.
Explanation
Correct Answer
B:Correlate principal group membership, direct and inherited grants across affected and unaffected `R034-CASE-127` runs.. By joining principal group membership, direct and inherited grants, query audit, and denied access after revocation across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: a stale direct or inherited grant can leave access after the intended authorization ends. It also sets a measurable baseline for revoke the relevant grants and verify the contractor cannot query while approved staff still can.
Incorrect Answers
A: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 a stale direct or inherited grant can leave access after the intended authorization ends. The failing-path principal group membership, direct and inherited grants, query audit, and denied access after revocation has to be correlated before attributing cause.
C:Review completed run status and aggregate cluster health without record-level correlation. A successful aggregate platform state can coexist with a stale direct or inherited grant can leave access after the intended authorization ends. This check never observes the affected `payment_decisions` records or their causal path.
D:Compare the saved configuration with the signed change ticket for `payment_decisions` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit principal group membership, direct and inherited grants, query audit, and denied access after revocation, the direct means of distinguishing a stale direct or inherited grant can leave access after the intended authorization ends.
Question 632
At a marketplace risk team, a temporary contractor retains SELECT on a confidential table after project completion and access review flags the grant. The dataset `payment_decisions` is in scope, and effective access must follow least privilege. Which option targets the actual technical dependency rather than an incidental symptom?
- Remove the contractor from one notebook share while leaving table privileges active; use that approach for `payment_decisions`.
- Change the table name but leave the same grants effective; use that approach for `payment_decisions`.
- Revoke the contractor group’s table SELECT and test the effective privilege path, including inherited grants
- Rely on a verbal instruction not to query the table; use that approach for `payment_decisions`.
Explanation
Correct Answer
C:Revoke the contractor group’s table SELECT and test the effective privilege path, including inherited grants. This directly addresses a stale direct or inherited grant can leave access after the intended authorization ends. The design should be accepted only after revoke the relevant grants and verify the contractor cannot query while approved staff still can; the related operational boundary is to restore least privilege with a tested denial rather than disrupting authorized users.
Incorrect Answers
A:Remove the contractor from one notebook share while leaving table privileges active; use that approach for `payment_decisions`. Notebook visibility does not determine underlying table SELECT authorization. For `payment_decisions`, this cannot remove the causal limitation: a stale direct or inherited grant can leave access after the intended authorization ends.
B:Change the table name but leave the same grants effective; use that approach for `payment_decisions`. Renaming an object does not reliably eliminate permissions or access. For `payment_decisions`, this cannot remove the causal limitation: a stale direct or inherited grant can leave access after the intended authorization ends.
D:Rely on a verbal instruction not to query the table; use that approach for `payment_decisions`. An unenforced request is not a revocation of access rights. For `payment_decisions`, this cannot remove the causal limitation: a stale direct or inherited grant can leave access after the intended authorization ends.
Question 633
At a marketplace risk team, a temporary contractor retains SELECT on a confidential table after project completion and access review flags the grant. The dataset `payment_decisions` is in scope, and effective access must follow least privilege. A teammate proposes: "Change the table name but leave the same grants effective." Which technical limitation is the decisive reason not to approve that specific proposal?
- Notebook visibility does not determine underlying table SELECT authorization. This would apply to an alternative change for `payment_decisions`.
- An unenforced request is not a revocation of access rights. This would apply to another option for `payment_decisions`.
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
- Renaming an object does not reliably eliminate permissions or access. The proposal does not repair `payment_decisions`.
Explanation
Correct Answer
D:Renaming an object does not reliably eliminate permissions or access. The proposal does not repair `payment_decisions`. This identifies the known limitation of the exact proposed action. Renaming an object does not reliably eliminate permissions or access. The underlying problem remains a stale direct or inherited grant can leave access after the intended authorization ends; Revoke the contractor group’s table SELECT and test the effective privilege path, including inherited grants instead targets that failure.
Incorrect Answers
A:Notebook visibility does not determine underlying table SELECT authorization. This would apply to an alternative change for `payment_decisions`. This failure applies to the separate proposal "Remove the contractor from one notebook share while leaving table privileges active".
B:An unenforced request is not a revocation of access rights. This would apply to another option for `payment_decisions`. This limitation belongs to the different alternative "Rely on a verbal instruction not to query the table". The stem calls for the specific failure of "Change the table name but leave the same grants effective".
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 a stale direct or inherited grant can leave access after the intended authorization ends.
Question 634
At a marketplace risk team, a temporary contractor retains SELECT on a confidential table after project completion and access review flags the grant. The dataset `payment_decisions` is in scope, and effective access must follow least privilege. What operational boundary should be documented for approval?
- Restore least privilege with a tested denial rather than disrupting authorized users
- Rely on a verbal instruction not to query the table
- Change the table name but leave the same grants effective
- Remove the contractor from one notebook share while leaving table privileges active; monitor results only after launch of `payment_decisions`.
Explanation
Correct Answer
A:Restore least privilege with a tested denial rather than disrupting authorized users. This explicitly bounds the compromise while still addressing a stale direct or inherited grant can leave access after the intended authorization ends. Acceptance relies on revoke the relevant grants and verify the contractor cannot query while approved staff still can rather than simply declaring the change complete.
Incorrect Answers
B:Rely on a verbal instruction not to query the table. An unenforced request is not a revocation of access rights. Monitoring after deployment does not make this approach a safe bounded tradeoff for `payment_decisions`.
C:Change the table name but leave the same grants effective. Renaming an object does not reliably eliminate permissions or access. Monitoring after deployment does not make this approach a safe bounded tradeoff for `payment_decisions`.
D:Remove the contractor from one notebook share while leaving table privileges active; monitor results only after launch of `payment_decisions`. Notebook visibility does not determine underlying table SELECT authorization. Monitoring after deployment does not make this approach a safe bounded tradeoff for `payment_decisions`.
Question 635
At a marketplace risk team, a temporary contractor retains SELECT on a confidential table after project completion and access review flags the grant. The dataset `payment_decisions` is in scope, and effective access must follow least privilege. Which validation should be required in the release record?
- Revoke the relevant grants and verify the contractor cannot query while approved staff still can
- Check that the intended configuration exists for `payment_decisions` and that a healthy run succeeded, without inducing the earlier failure.
- Run only a normal, unchanged `payment_decisions` sample and review principal group membership.
- Review a platform-level availability report for `payment_decisions` without testing whether a stale direct or inherited grant can leave access after the intended authorization ends.
Explanation
Correct Answer
A:Revoke the relevant grants and verify the contractor cannot query while approved staff still can. This reproduces the scenario-dependent condition, verifies principal group membership, direct and inherited grants, query audit, and denied access after revocation, and directly tests whether a stale direct or inherited grant can leave access after the intended authorization ends is resolved. Observed results, not intent, determine approval.
Incorrect Answers
B:Check that the intended configuration exists for `payment_decisions` 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 a stale direct or inherited grant can leave access after the intended authorization ends.
C:Run only a normal, unchanged `payment_decisions` sample and review principal group membership. A normal sample does not challenge a stale direct or inherited grant can leave access after the intended authorization ends.
D:Review a platform-level availability report for `payment_decisions` without testing whether a stale direct or inherited grant can leave access after the intended authorization ends. Aggregate availability does not establish the behavior of affected `payment_decisions` records. It cannot replace the direct exercise: revoke the relevant grants and verify the contractor cannot query while approved staff still can.
Question 636
At a public housing agency, an analyst has SELECT on a Unity Catalog table but receives a permission error because catalog and schema usage were not granted. The dataset `course_enrollments` is in scope, and the underlying data retention policy must be preserved. Before choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- 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 effective grants on catalog, schema and table across affected and unaffected `R034-CASE-128` runs.
Explanation
Correct Answer
D:Correlate effective grants on catalog, schema and table across affected and unaffected `R034-CASE-128` runs.. By joining effective grants on catalog, schema and table, denied query error, and test principal identity across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: table-level SELECT alone is insufficient without parent namespace usage privileges. It also sets a measurable baseline for query as the analyst before and after the minimum grants and confirm unrelated schemas remain inaccessible.
Incorrect Answers
A: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 table-level SELECT alone is insufficient without parent namespace usage privileges. The failing-path effective grants on catalog, schema and table, denied query error, and test principal identity has to be correlated before attributing cause.
B:Review completed run status and aggregate cluster health without record-level correlation. A successful aggregate platform state can coexist with table-level SELECT alone is insufficient without parent namespace usage privileges. This check never observes the affected `course_enrollments` records or their causal path.
C: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 effective grants on catalog, schema and table, denied query error, and test principal identity, the direct means of distinguishing table-level SELECT alone is insufficient without parent namespace usage privileges.
Question 637
At a public housing agency, an analyst has SELECT on a Unity Catalog table but receives a permission error because catalog and schema usage were not granted. The dataset `course_enrollments` is in scope, and the underlying data retention policy must be preserved. Which implementation best resolves the stated defect without breaking the business constraint?
- Grant the needed USE CATALOG and USE SCHEMA along the object hierarchy in addition to table SELECT
- Create a personal ungoverned copy of the table to bypass catalog checks; use that approach for `course_enrollments`.
- Transfer ownership of the table to the analyst; use that approach for `course_enrollments`.
- Grant ALL PRIVILEGES on the entire metastore to the analyst; use that approach for `course_enrollments`.
Explanation
Correct Answer
A:Grant the needed USE CATALOG and USE SCHEMA along the object hierarchy in addition to table SELECT. This directly addresses table-level SELECT alone is insufficient without parent namespace usage privileges. The design should be accepted only after query as the analyst before and after the minimum grants and confirm unrelated schemas remain inaccessible; the related operational boundary is to grant only the traversal and read permissions required for the approved data object.
Incorrect Answers
B:Create a personal ungoverned copy of the table to bypass catalog checks; use that approach for `course_enrollments`. Bypass copies defeat object-level governance and lineage. For `course_enrollments`, this cannot remove the causal limitation: table-level SELECT alone is insufficient without parent namespace usage privileges.
C:Transfer ownership of the table to the analyst; use that approach for `course_enrollments`. Ownership gives unwanted control and does not follow least privilege. For `course_enrollments`, this cannot remove the causal limitation: table-level SELECT alone is insufficient without parent namespace usage privileges.
D:Grant ALL PRIVILEGES on the entire metastore to the analyst; use that approach for `course_enrollments`. Global privileges are excessive for a single governed table read. For `course_enrollments`, this cannot remove the causal limitation: table-level SELECT alone is insufficient without parent namespace usage privileges.
Question 638
At a public housing agency, an analyst has SELECT on a Unity Catalog table but receives a permission error because catalog and schema usage were not granted. The dataset `course_enrollments` is in scope, and the underlying data retention policy must be preserved. A teammate proposes: "Transfer ownership of the table to the analyst." Which technical limitation is the decisive reason not to approve that specific proposal?
- Global privileges are excessive for a single governed table read. This would apply to another option for `course_enrollments`.
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
- Bypass copies defeat object-level governance and lineage. This would apply to an alternative change for `course_enrollments`.
- Ownership gives unwanted control and does not follow least privilege. The proposal does not repair `course_enrollments`.
Explanation
Correct Answer
D:Ownership gives unwanted control and does not follow least privilege. The proposal does not repair `course_enrollments`. This identifies the known limitation of the exact proposed action. Ownership gives unwanted control and does not follow least privilege. The underlying problem remains table-level SELECT alone is insufficient without parent namespace usage privileges; Grant the needed USE CATALOG and USE SCHEMA along the object hierarchy in addition to table SELECT instead targets that failure.
Incorrect Answers
A:Global privileges are excessive for a single governed table read. This would apply to another option for `course_enrollments`. This limitation belongs to the different alternative "Grant ALL PRIVILEGES on the entire metastore to the analyst". The stem calls for the specific failure of "Transfer ownership of the table to the analyst".
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-level SELECT alone is insufficient without parent namespace usage privileges.
C:Bypass copies defeat object-level governance and lineage. This would apply to an alternative change for `course_enrollments`. This failure applies to the separate proposal "Create a personal ungoverned copy of the table to bypass catalog checks".
Question 639
At a public housing agency, an analyst has SELECT on a Unity Catalog table but receives a permission error because catalog and schema usage were not granted. The dataset `course_enrollments` is in scope, and the underlying data retention policy must be preserved. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Transfer ownership of the table to the analyst
- Create a personal ungoverned copy of the table to bypass catalog checks
- Grant ALL PRIVILEGES on the entire metastore to the analyst
- Grant only the traversal and read permissions required for the approved data object
Explanation
Correct Answer
D:Grant only the traversal and read permissions required for the approved data object. This explicitly bounds the compromise while still addressing table-level SELECT alone is insufficient without parent namespace usage privileges. Acceptance relies on query as the analyst before and after the minimum grants and confirm unrelated schemas remain inaccessible rather than simply declaring the change complete.
Incorrect Answers
A:Transfer ownership of the table to the analyst. Ownership gives unwanted control and does not follow least privilege. Monitoring after deployment does not make this approach a safe bounded tradeoff for `course_enrollments`.
B:Create a personal ungoverned copy of the table to bypass catalog checks. Bypass copies defeat object-level governance and lineage. Monitoring after deployment does not make this approach a safe bounded tradeoff for `course_enrollments`.
C:Grant ALL PRIVILEGES on the entire metastore to the analyst. Global privileges are excessive for a single governed table read. Monitoring after deployment does not make this approach a safe bounded tradeoff for `course_enrollments`.
Question 640
At a public housing agency, an analyst has SELECT on a Unity Catalog table but receives a permission error because catalog and schema usage were not granted. The dataset `course_enrollments` is in scope, and the underlying data retention policy must be preserved. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Review a platform-level availability report for `course_enrollments` without testing whether table-level SELECT alone is insufficient without parent namespace usage privileges.
- Run only a normal, unchanged `course_enrollments` sample and review effective grants on catalog.
- Query as the analyst before and after the minimum grants and confirm unrelated schemas remain inaccessible
- Check that the intended configuration exists for `course_enrollments` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
C:Query as the analyst before and after the minimum grants and confirm unrelated schemas remain inaccessible. This reproduces the scenario-dependent condition, verifies effective grants on catalog, schema and table, denied query error, and test principal identity, and directly tests whether table-level SELECT alone is insufficient without parent namespace usage privileges is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `course_enrollments` without testing whether table-level SELECT alone is insufficient without parent namespace usage privileges. Aggregate availability does not establish the behavior of affected `course_enrollments` records. It cannot replace the direct exercise: query as the analyst before and after the minimum grants and confirm unrelated schemas remain inaccessible.
B:Run only a normal, unchanged `course_enrollments` sample and review effective grants on catalog. A normal sample does not challenge table-level SELECT alone is insufficient without parent namespace usage privileges.
D:Check that the intended configuration exists for `course_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 table-level SELECT alone is insufficient without parent namespace usage privileges.