Certified Data Engineer Associate Practice Test 2
Question 10
At a city utilities office, teams have copied the same customer table into several workspaces and cannot explain which analyst accessed which field. The dataset `supplier_orders` is in scope, and the control board requires an auditable data lineage. What verification provides evidence of correct behavior under the original adverse condition?
- Query as an approved analyst and an unauthorized analyst, then trace the shared table lineage after a write
- Run only a normal, unchanged `supplier_orders` sample and review table ownership.
- Review a platform-level availability report for `supplier_orders` without testing whether workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
- Check that the intended configuration exists for `supplier_orders` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
A:Query as an approved analyst and an unauthorized analyst, then trace the shared table lineage after a write. This reproduces the scenario-dependent condition, verifies table ownership, catalog lineage, actual effective grants, and sample cross-workspace access, and directly tests whether workspace-specific copies and ACLs prevent coherent governance and lineage across teams is resolved. Observed results, not intent, determine approval.
Incorrect Answers
B:Run only a normal, unchanged `supplier_orders` sample and review table ownership. A normal sample does not challenge workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
C:Review a platform-level availability report for `supplier_orders` without testing whether workspace-specific copies and ACLs prevent coherent governance and lineage across teams. Aggregate availability does not establish the behavior of affected `supplier_orders` records. It cannot replace the direct exercise: query as an approved analyst and an unauthorized analyst, then trace the shared table lineage after a write.
D:Check that the intended configuration exists for `supplier_orders` 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 workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
Question 11
At a ticketing marketplace, a shared analytics estate keeps writing Parquet files directly, and a failed overwrite left BI readers with inconsistent versions. The dataset `research_events` is in scope, and workspace users must retain least-privilege access. Which investigation best tests the stated constraint with direct data?
- Correlate transaction history, concurrent-reader consistency across affected and unaffected `R034-CASE-003` runs.
- Compare the saved configuration with the signed change ticket for `research_events` while omitting source and output records.
- Review aggregate cluster availability and job completion for `research_events` without correlating the observed error path.
- Examine only a normal successful run of `research_events` and trend transaction history without recreating the fault.
Explanation
Correct Answer
A:Correlate transaction history, concurrent-reader consistency across affected and unaffected `R034-CASE-003` runs.. By joining transaction history, concurrent-reader consistency, recovery version, and Unity Catalog grants across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges. It also sets a measurable baseline for interrupt a write and verify readers see one committed version; restore the previous Delta version and test a denied user.
Incorrect Answers
B:Compare the saved configuration with the signed change ticket for `research_events` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit transaction history, concurrent-reader consistency, recovery version, and Unity Catalog grants, the direct means of distinguishing bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges.
C:Review aggregate cluster availability and job completion for `research_events` without correlating the observed error path. A successful aggregate platform state can coexist with bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges. This check never observes the affected `research_events` records or their causal path.
D:Examine only a normal successful run of `research_events` and trend transaction history without recreating the fault. A healthy-run trend can be useful, but it does not expose bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges. The failing-path transaction history, concurrent-reader consistency, recovery version, and Unity Catalog grants has to be correlated before attributing cause.
Question 12
At a ticketing marketplace, a shared analytics estate keeps writing Parquet files directly, and a failed overwrite left BI readers with inconsistent versions. The dataset `research_events` is in scope, and workspace users must retain least-privilege access. Which option targets the actual technical dependency rather than an incidental symptom?
- Copy the files to a temporary notebook directory before every query; use that approach for `research_events`.
- Add Unity Catalog grants to files but do not convert the data to Delta; use that approach for `research_events`.
- Keep unversioned Parquet and rely on a nightly folder backup; use that approach for `research_events`.
- Use Delta Lake transactional tables for reliable commits and recovery, with Unity Catalog governing access and discovery
Explanation
Correct Answer
D:Use Delta Lake transactional tables for reliable commits and recovery, with Unity Catalog governing access and discovery. This directly addresses bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges. The design should be accepted only after interrupt a write and verify readers see one committed version; restore the previous Delta version and test a denied user; the related operational boundary is to accept the Delta migration and controlled catalog privileges rather than cheaper but unversioned file copies.
Incorrect Answers
A:Copy the files to a temporary notebook directory before every query; use that approach for `research_events`. A transient notebook copy fragments the source of truth and is not a durable commit protocol. For `research_events`, this cannot remove the causal limitation: bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges.
B:Add Unity Catalog grants to files but do not convert the data to Delta; use that approach for `research_events`. Governance metadata cannot supply ACID commits or Delta time travel to untransactional files. For `research_events`, this cannot remove the causal limitation: bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges.
C:Keep unversioned Parquet and rely on a nightly folder backup; use that approach for `research_events`. A nightly copy cannot provide a consistent transactional snapshot to concurrent readers. For `research_events`, this cannot remove the causal limitation: bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges.
Question 13
At a ticketing marketplace, a shared analytics estate keeps writing Parquet files directly, and a failed overwrite left BI readers with inconsistent versions. The dataset `research_events` is in scope, and workspace users must retain least-privilege access. A teammate proposes: "Copy the files to a temporary notebook directory before every query." Which technical limitation is the decisive reason not to approve that specific proposal?
- A nightly copy cannot provide a consistent transactional snapshot to concurrent readers. This would apply to an alternative change for `research_events`.
- The anomaly is entirely a compute sizing problem; the file format and catalog design are not involved.
- A transient notebook copy fragments the source of truth and is not a durable commit protocol. The proposal does not repair `research_events`.
- Governance metadata cannot supply ACID commits or Delta time travel to untransactional files. This would apply to another option for `research_events`.
Explanation
Correct Answer
C:A transient notebook copy fragments the source of truth and is not a durable commit protocol. The proposal does not repair `research_events`. This identifies the known limitation of the exact proposed action. A transient notebook copy fragments the source of truth and is not a durable commit protocol. The underlying problem remains bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges; Use Delta Lake transactional tables for reliable commits and recovery, with Unity Catalog governing access and discovery instead targets that failure.
Incorrect Answers
A:A nightly copy cannot provide a consistent transactional snapshot to concurrent readers. This would apply to an alternative change for `research_events`. This failure applies to the separate proposal "Keep unversioned Parquet and rely on a nightly folder backup".
B:The anomaly is entirely a compute sizing problem; the file format and catalog design are not involved. The case provides a concrete failing data or control path; a mere alternate theory does not address bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges.
D:Governance metadata cannot supply ACID commits or Delta time travel to untransactional files. This would apply to another option for `research_events`. This limitation belongs to the different alternative "Add Unity Catalog grants to files but do not convert the data to Delta". The stem calls for the specific failure of "Copy the files to a temporary notebook directory before every query".
Question 14
At a ticketing marketplace, a shared analytics estate keeps writing Parquet files directly, and a failed overwrite left BI readers with inconsistent versions. The dataset `research_events` is in scope, and workspace users must retain least-privilege access. What operational boundary should be documented for approval?
- Accept the Delta migration and controlled catalog privileges rather than cheaper but unversioned file copies
- Keep unversioned Parquet and rely on a nightly folder backup; monitor results only after launch of `research_events`.
- Add Unity Catalog grants to files but do not convert the data to Delta; monitor results only after launch of `research_events`.
- Copy the files to a temporary notebook directory before every query; monitor results only after launch of `research_events`.
Explanation
Correct Answer
A:Accept the Delta migration and controlled catalog privileges rather than cheaper but unversioned file copies. This explicitly bounds the compromise while still addressing bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges. Acceptance relies on interrupt a write and verify readers see one committed version; restore the previous Delta version and test a denied user rather than simply declaring the change complete.
Incorrect Answers
B:Keep unversioned Parquet and rely on a nightly folder backup; monitor results only after launch of `research_events`. A nightly copy cannot provide a consistent transactional snapshot to concurrent readers. Monitoring after deployment does not make this approach a safe bounded tradeoff for `research_events`.
C:Add Unity Catalog grants to files but do not convert the data to Delta; monitor results only after launch of `research_events`. Governance metadata cannot supply ACID commits or Delta time travel to untransactional files. Monitoring after deployment does not make this approach a safe bounded tradeoff for `research_events`.
D:Copy the files to a temporary notebook directory before every query; monitor results only after launch of `research_events`. A transient notebook copy fragments the source of truth and is not a durable commit protocol. Monitoring after deployment does not make this approach a safe bounded tradeoff for `research_events`.
Question 15
At a ticketing marketplace, a shared analytics estate keeps writing Parquet files directly, and a failed overwrite left BI readers with inconsistent versions. The dataset `research_events` is in scope, and workspace users must retain least-privilege access. Which validation should be required in the release record?
- Check that the intended configuration exists for `research_events` and that a healthy run succeeded, without inducing the earlier failure.
- Review a platform-level availability report for `research_events` without testing whether bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges.
- Interrupt a write and verify readers see one committed version; restore the previous Delta version and test a denied user
- Run only a normal, unchanged `research_events` sample and review transaction history.
Explanation
Correct Answer
C:Interrupt a write and verify readers see one committed version; restore the previous Delta version and test a denied user. This reproduces the scenario-dependent condition, verifies transaction history, concurrent-reader consistency, recovery version, and Unity Catalog grants, and directly tests whether bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Check that the intended configuration exists for `research_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 bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges.
B:Review a platform-level availability report for `research_events` without testing whether bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges. Aggregate availability does not establish the behavior of affected `research_events` records. It cannot replace the direct exercise: interrupt a write and verify readers see one committed version; restore the previous Delta version and test a denied user.
D:Run only a normal, unchanged `research_events` sample and review transaction history. A normal sample does not challenge bare Parquet overwrites provide neither the coordinated Delta commit log nor centrally governed object privileges.
Question 16
At a university research service, teams have copied the same customer table into several workspaces and cannot explain which analyst accessed which field. The dataset `experiment_samples` is in scope, and the control board requires an auditable data lineage. Before choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Correlate table ownership, catalog lineage across affected and unaffected `R034-CASE-004` runs.
- 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 `experiment_samples` and trend table ownership without recreating the fault.
Explanation
Correct Answer
A:Correlate table ownership, catalog lineage across affected and unaffected `R034-CASE-004` runs.. By joining table ownership, catalog lineage, actual effective grants, and sample cross-workspace access across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: workspace-specific copies and ACLs prevent coherent governance and lineage across teams. It also sets a measurable baseline for query as an approved analyst and an unauthorized analyst, then trace the shared table lineage after a write.
Incorrect Answers
B:Review completed run status and aggregate cluster health without record-level correlation. A successful aggregate platform state can coexist with workspace-specific copies and ACLs prevent coherent governance and lineage across teams. This check never observes the affected `experiment_samples` 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 table ownership, catalog lineage, actual effective grants, and sample cross-workspace access, the direct means of distinguishing workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
D:Examine only a normal successful run of `experiment_samples` and trend table ownership without recreating the fault. A healthy-run trend can be useful, but it does not expose workspace-specific copies and ACLs prevent coherent governance and lineage across teams. The failing-path table ownership, catalog lineage, actual effective grants, and sample cross-workspace access has to be correlated before attributing cause.
Question 17
At a university research service, teams have copied the same customer table into several workspaces and cannot explain which analyst accessed which field. The dataset `experiment_samples` is in scope, and the control board requires an auditable data lineage. Which implementation best resolves the stated defect without breaking the business constraint?
- Use Delta transaction logs alone as the user entitlement mechanism; use that approach for `experiment_samples`.
- Register governed tables in Unity Catalog and apply least-privilege grants while preserving one discoverable data lineage
- Create more copies in each workspace with local access lists; use that approach for `experiment_samples`.
- Give all analysts metastore administrator rights to make discovery easier; use that approach for `experiment_samples`.
Explanation
Correct Answer
B:Register governed tables in Unity Catalog and apply least-privilege grants while preserving one discoverable data lineage. This directly addresses workspace-specific copies and ACLs prevent coherent governance and lineage across teams. The design should be accepted only after query as an approved analyst and an unauthorized analyst, then trace the shared table lineage after a write; the related operational boundary is to centralize governance while allowing approved teams self-service discovery without copying sensitive data.
Incorrect Answers
A:Use Delta transaction logs alone as the user entitlement mechanism; use that approach for `experiment_samples`. Delta commit history does not replace Unity Catalog identity and object privileges. For `experiment_samples`, this cannot remove the causal limitation: workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
C:Create more copies in each workspace with local access lists; use that approach for `experiment_samples`. Local copies multiply uncontrolled policy surfaces and obscure common lineage. For `experiment_samples`, this cannot remove the causal limitation: workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
D:Give all analysts metastore administrator rights to make discovery easier; use that approach for `experiment_samples`. Administrative rights exceed read requirements and defeat least-privilege access. For `experiment_samples`, this cannot remove the causal limitation: workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
Question 18
At a university research service, teams have copied the same customer table into several workspaces and cannot explain which analyst accessed which field. The dataset `experiment_samples` is in scope, and the control board requires an auditable data lineage. A teammate proposes: "Use Delta transaction logs alone as the user entitlement mechanism." Which technical limitation is the decisive reason not to approve that specific proposal?
- Administrative rights exceed read requirements and defeat least-privilege access. This would apply to an alternative change for `experiment_samples`.
- The anomaly is entirely a compute sizing problem; the file format and catalog design are not involved.
- Local copies multiply uncontrolled policy surfaces and obscure common lineage. This would apply to another option for `experiment_samples`.
- Delta commit history does not replace Unity Catalog identity and object privileges. The proposal does not repair `experiment_samples`.
Explanation
Correct Answer
D:Delta commit history does not replace Unity Catalog identity and object privileges. The proposal does not repair `experiment_samples`. This identifies the known limitation of the exact proposed action. Delta commit history does not replace Unity Catalog identity and object privileges. The underlying problem remains workspace-specific copies and ACLs prevent coherent governance and lineage across teams; Register governed tables in Unity Catalog and apply least-privilege grants while preserving one discoverable data lineage instead targets that failure.
Incorrect Answers
A:Administrative rights exceed read requirements and defeat least-privilege access. This would apply to an alternative change for `experiment_samples`. This failure applies to the separate proposal "Give all analysts metastore administrator rights to make discovery easier".
B:The anomaly is entirely a compute sizing problem; the file format and catalog design are not involved. The case provides a concrete failing data or control path; a mere alternate theory does not address workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
C:Local copies multiply uncontrolled policy surfaces and obscure common lineage. This would apply to another option for `experiment_samples`. This limitation belongs to the different alternative "Create more copies in each workspace with local access lists". The stem calls for the specific failure of "Use Delta transaction logs alone as the user entitlement mechanism".
Question 19
At a university research service, teams have copied the same customer table into several workspaces and cannot explain which analyst accessed which field. The dataset `experiment_samples` is in scope, and the control board requires an auditable data lineage. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Create more copies in each workspace with local access lists
- Give all analysts metastore administrator rights to make discovery easier
- Use Delta transaction logs alone as the user entitlement mechanism; monitor results only after launch of `experiment_samples`.
- Centralize governance while allowing approved teams self-service discovery without copying sensitive data
Explanation
Correct Answer
D:Centralize governance while allowing approved teams self-service discovery without copying sensitive data. This explicitly bounds the compromise while still addressing workspace-specific copies and ACLs prevent coherent governance and lineage across teams. Acceptance relies on query as an approved analyst and an unauthorized analyst, then trace the shared table lineage after a write rather than simply declaring the change complete.
Incorrect Answers
A:Create more copies in each workspace with local access lists. Local copies multiply uncontrolled policy surfaces and obscure common lineage. Monitoring after deployment does not make this approach a safe bounded tradeoff for `experiment_samples`.
B:Give all analysts metastore administrator rights to make discovery easier. Administrative rights exceed read requirements and defeat least-privilege access. Monitoring after deployment does not make this approach a safe bounded tradeoff for `experiment_samples`.
C:Use Delta transaction logs alone as the user entitlement mechanism; monitor results only after launch of `experiment_samples`. Delta commit history does not replace Unity Catalog identity and object privileges. Monitoring after deployment does not make this approach a safe bounded tradeoff for `experiment_samples`.
Question 20
At a university research service, teams have copied the same customer table into several workspaces and cannot explain which analyst accessed which field. The dataset `experiment_samples` is in scope, and the control board requires an auditable data lineage. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Review a platform-level availability report for `experiment_samples` without testing whether workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
- Check that the intended configuration exists for `experiment_samples` and that a healthy run succeeded, without inducing the earlier failure.
- Run only a normal, unchanged `experiment_samples` sample and review table ownership.
- Query as an approved analyst and an unauthorized analyst, then trace the shared table lineage after a write
Explanation
Correct Answer
D:Query as an approved analyst and an unauthorized analyst, then trace the shared table lineage after a write. This reproduces the scenario-dependent condition, verifies table ownership, catalog lineage, actual effective grants, and sample cross-workspace access, and directly tests whether workspace-specific copies and ACLs prevent coherent governance and lineage across teams is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `experiment_samples` without testing whether workspace-specific copies and ACLs prevent coherent governance and lineage across teams. Aggregate availability does not establish the behavior of affected `experiment_samples` records. It cannot replace the direct exercise: query as an approved analyst and an unauthorized analyst, then trace the shared table lineage after a write.
B:Check that the intended configuration exists for `experiment_samples` 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 workspace-specific copies and ACLs prevent coherent governance and lineage across teams.
C:Run only a normal, unchanged `experiment_samples` sample and review table ownership. A normal sample does not challenge workspace-specific copies and ACLs prevent coherent governance and lineage across teams.