Certified Data Engineer Associate Practice Test 61
Question 600
At a scientific imaging provider, a curated Delta table is meant to be fully platform-managed, but its owner uses an external storage path with separate lifecycle policies. The dataset `housing_applications` is in scope, and effective access must follow least privilege. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Run only a normal, unchanged `housing_applications` sample and review table metadata.
- Create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy
- Check that the intended configuration exists for `housing_applications` and that a healthy run succeeded, without inducing the earlier failure.
- Review a platform-level availability report for `housing_applications` without testing whether external table storage is separately administered and dropping the table does not necessarily remove underlying files.
Explanation
Correct Answer
B:Create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy. This reproduces the scenario-dependent condition, verifies table metadata, storage location, table type, object ownership, and file retention after drop, and directly tests whether external table storage is separately administered and dropping the table does not necessarily remove underlying files is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `housing_applications` sample and review table metadata. A normal sample does not challenge external table storage is separately administered and dropping the table does not necessarily remove underlying files.
C:Check that the intended configuration exists for `housing_applications` 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 external table storage is separately administered and dropping the table does not necessarily remove underlying files.
D:Review a platform-level availability report for `housing_applications` without testing whether external table storage is separately administered and dropping the table does not necessarily remove underlying files. Aggregate availability does not establish the behavior of affected `housing_applications` records. It cannot replace the direct exercise: create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy.
Question 601
At an agricultural sensor program, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `cargo_visits` is in scope, and the underlying data retention policy must be preserved. What evidence should the engineer collect to establish the cause rather than a coincidental symptom?
- 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
- Correlate external location, storage credentials across affected and unaffected `R034-CASE-121` runs.
- Compare the saved configuration with the signed change ticket for `cargo_visits` while omitting source and output records.
Explanation
Correct Answer
C:Correlate external location, storage credentials across affected and unaffected `R034-CASE-121` runs.. By joining external location, storage credentials, underlying path owner, SELECT grants, and file continuity across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: moving or deleting regulated files would violate the independent storage retention boundary. It also sets a measurable baseline for register the existing Delta dataset without copying data and verify governed reads plus unchanged storage ownership.
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 moving or deleting regulated files would violate the independent storage retention boundary. The failing-path external location, storage credentials, underlying path owner, SELECT grants, and file continuity 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 moving or deleting regulated files would violate the independent storage retention boundary. This check never observes the affected `cargo_visits` records or their causal path.
D:Compare the saved configuration with the signed change ticket for `cargo_visits` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit external location, storage credentials, underlying path owner, SELECT grants, and file continuity, the direct means of distinguishing moving or deleting regulated files would violate the independent storage retention boundary.
Question 602
At an agricultural sensor program, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `cargo_visits` is in scope, and the underlying data retention policy must be preserved. Which platform configuration or data-engineering change is most defensible?
- Register the approved external Delta location with the required Unity Catalog credentials and maintain external data ownership
- Create an ungoverned temporary view over direct path reads for every analyst; use that approach for `cargo_visits`.
- Convert it to a managed table by blindly moving files away from the regulated path; use that approach for `cargo_visits`.
- Drop and recreate the external cloud bucket whenever table metadata changes; use that approach for `cargo_visits`.
Explanation
Correct Answer
A:Register the approved external Delta location with the required Unity Catalog credentials and maintain external data ownership. This directly addresses moving or deleting regulated files would violate the independent storage retention boundary. The design should be accepted only after register the existing Delta dataset without copying data and verify governed reads plus unchanged storage ownership; the related operational boundary is to preserve independent storage control while exposing a governed catalog object.
Incorrect Answers
B:Create an ungoverned temporary view over direct path reads for every analyst; use that approach for `cargo_visits`. Per-user bypasses undermine shared object permissions and auditability. For `cargo_visits`, this cannot remove the causal limitation: moving or deleting regulated files would violate the independent storage retention boundary.
C:Convert it to a managed table by blindly moving files away from the regulated path; use that approach for `cargo_visits`. Unreviewed relocation may violate the required storage residency and retention controls. For `cargo_visits`, this cannot remove the causal limitation: moving or deleting regulated files would violate the independent storage retention boundary.
D:Drop and recreate the external cloud bucket whenever table metadata changes; use that approach for `cargo_visits`. Deleting the underlying storage is not required for registering or updating external table metadata. For `cargo_visits`, this cannot remove the causal limitation: moving or deleting regulated files would violate the independent storage retention boundary.
Question 603
At an agricultural sensor program, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `cargo_visits` is in scope, and the underlying data retention policy must be preserved. A teammate proposes: "Drop and recreate the external cloud bucket whenever table metadata changes." Which technical limitation is the decisive reason not to approve that specific proposal?
- Unreviewed relocation may violate the required storage residency and retention controls. This would apply to an alternative change for `cargo_visits`.
- Per-user bypasses undermine shared object permissions and auditability. This would apply to another option for `cargo_visits`.
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
- Deleting the underlying storage is not required for registering or updating external table metadata. The proposal does not repair `cargo_visits`.
Explanation
Correct Answer
D:Deleting the underlying storage is not required for registering or updating external table metadata. The proposal does not repair `cargo_visits`. This identifies the known limitation of the exact proposed action. Deleting the underlying storage is not required for registering or updating external table metadata. The underlying problem remains moving or deleting regulated files would violate the independent storage retention boundary; Register the approved external Delta location with the required Unity Catalog credentials and maintain external data ownership instead targets that failure.
Incorrect Answers
A:Unreviewed relocation may violate the required storage residency and retention controls. This would apply to an alternative change for `cargo_visits`. This failure applies to the separate proposal "Convert it to a managed table by blindly moving files away from the regulated path".
B:Per-user bypasses undermine shared object permissions and auditability. This would apply to another option for `cargo_visits`. This limitation belongs to the different alternative "Create an ungoverned temporary view over direct path reads for every analyst". The stem calls for the specific failure of "Drop and recreate the external cloud bucket whenever table metadata changes".
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 moving or deleting regulated files would violate the independent storage retention boundary.
Question 604
At an agricultural sensor program, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `cargo_visits` is in scope, and the underlying data retention policy must be preserved. What risk-and-cost compromise should the owner accept instead of the proposed shortcuts?
- Drop and recreate the external cloud bucket whenever table metadata changes
- Create an ungoverned temporary view over direct path reads for every analyst
- Preserve independent storage control while exposing a governed catalog object
- Convert it to a managed table by blindly moving files away from the regulated path; monitor results only after launch of `cargo_visits`.
Explanation
Correct Answer
C:Preserve independent storage control while exposing a governed catalog object. This explicitly bounds the compromise while still addressing moving or deleting regulated files would violate the independent storage retention boundary. Acceptance relies on register the existing Delta dataset without copying data and verify governed reads plus unchanged storage ownership rather than simply declaring the change complete.
Incorrect Answers
A:Drop and recreate the external cloud bucket whenever table metadata changes. Deleting the underlying storage is not required for registering or updating external table metadata. Monitoring after deployment does not make this approach a safe bounded tradeoff for `cargo_visits`.
B:Create an ungoverned temporary view over direct path reads for every analyst. Per-user bypasses undermine shared object permissions and auditability. Monitoring after deployment does not make this approach a safe bounded tradeoff for `cargo_visits`.
D:Convert it to a managed table by blindly moving files away from the regulated path; monitor results only after launch of `cargo_visits`. Unreviewed relocation may violate the required storage residency and retention controls. Monitoring after deployment does not make this approach a safe bounded tradeoff for `cargo_visits`.
Question 605
At an agricultural sensor program, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `cargo_visits` is in scope, and the underlying data retention policy must be preserved. Which direct test could falsify the proposed fix instead of only confirming deployment?
- Register the existing Delta dataset without copying data and verify governed reads plus unchanged storage ownership
- Run only a normal, unchanged `cargo_visits` sample and review external location.
- Review a platform-level availability report for `cargo_visits` without testing whether moving or deleting regulated files would violate the independent storage retention boundary.
- Check that the intended configuration exists for `cargo_visits` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
A:Register the existing Delta dataset without copying data and verify governed reads plus unchanged storage ownership. This reproduces the scenario-dependent condition, verifies external location, storage credentials, underlying path owner, SELECT grants, and file continuity, and directly tests whether moving or deleting regulated files would violate the independent storage retention boundary is resolved. Observed results, not intent, determine approval.
Incorrect Answers
B:Run only a normal, unchanged `cargo_visits` sample and review external location. A normal sample does not challenge moving or deleting regulated files would violate the independent storage retention boundary.
C:Review a platform-level availability report for `cargo_visits` without testing whether moving or deleting regulated files would violate the independent storage retention boundary. Aggregate availability does not establish the behavior of affected `cargo_visits` records. It cannot replace the direct exercise: register the existing Delta dataset without copying data and verify governed reads plus unchanged storage ownership.
D:Check that the intended configuration exists for `cargo_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 moving or deleting regulated files would violate the independent storage retention boundary.
Question 606
At a municipal transit operator, a curated Delta table is meant to be fully platform-managed, but its owner uses an external storage path with separate lifecycle policies. The dataset `population_records` is in scope, and effective access must follow least privilege. Which correlated observation is the strongest basis for the change decision?
- Correlate table metadata, storage location across affected and unaffected `R034-CASE-122` runs.
- 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
Explanation
Correct Answer
A:Correlate table metadata, storage location across affected and unaffected `R034-CASE-122` runs.. By joining table metadata, storage location, table type, object ownership, and file retention after drop across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: external table storage is separately administered and dropping the table does not necessarily remove underlying files. It also sets a measurable baseline for create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy.
Incorrect Answers
B: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 external table storage is separately administered and dropping the table does not necessarily remove underlying files. The failing-path table metadata, storage location, table type, object ownership, and file retention after drop 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 external table storage is separately administered and dropping the table does not necessarily remove underlying files. This check never observes the affected `population_records` records or their causal path.
D: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 metadata, storage location, table type, object ownership, and file retention after drop, the direct means of distinguishing external table storage is separately administered and dropping the table does not necessarily remove underlying files.
Question 607
At a municipal transit operator, a curated Delta table is meant to be fully platform-managed, but its owner uses an external storage path with separate lifecycle policies. The dataset `population_records` is in scope, and effective access must follow least privilege. What implementation should the engineer select for the failing workflow?
- Copy the data into a personal workspace folder and call it a managed table; use that approach for `population_records`.
- Create or convert to an eligible Unity Catalog managed Delta table with approved storage and ownership semantics
- Assume DROP TABLE on an external table always deletes its cloud data files; use that approach for `population_records`.
- Give every analyst write access to the raw external bucket; use that approach for `population_records`.
Explanation
Correct Answer
B:Create or convert to an eligible Unity Catalog managed Delta table with approved storage and ownership semantics. This directly addresses external table storage is separately administered and dropping the table does not necessarily remove underlying files. The design should be accepted only after create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy; the related operational boundary is to use managed lifecycle where the platform should own storage while retaining external tables for independently controlled paths.
Incorrect Answers
A:Copy the data into a personal workspace folder and call it a managed table; use that approach for `population_records`. Workspace files do not establish governed managed Delta table storage and ownership. For `population_records`, this cannot remove the causal limitation: external table storage is separately administered and dropping the table does not necessarily remove underlying files.
C:Assume DROP TABLE on an external table always deletes its cloud data files; use that approach for `population_records`. External table metadata deletion does not guarantee deletion of externally owned data. For `population_records`, this cannot remove the causal limitation: external table storage is separately administered and dropping the table does not necessarily remove underlying files.
D:Give every analyst write access to the raw external bucket; use that approach for `population_records`. Broad storage writes bypass governed table lifecycle and least privilege. For `population_records`, this cannot remove the causal limitation: external table storage is separately administered and dropping the table does not necessarily remove underlying files.
Question 608
At a municipal transit operator, a curated Delta table is meant to be fully platform-managed, but its owner uses an external storage path with separate lifecycle policies. The dataset `population_records` is in scope, and effective access must follow least privilege. A teammate proposes: "Give every analyst write access to the raw external bucket." Which technical limitation is the decisive reason not to approve that specific proposal?
- External table metadata deletion does not guarantee deletion of externally owned data. This would apply to another option for `population_records`.
- Broad storage writes bypass governed table lifecycle and least privilege. The proposal does not repair `population_records`.
- Workspace files do not establish governed managed Delta table storage and ownership. This would apply to an alternative change for `population_records`.
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
Explanation
Correct Answer
B:Broad storage writes bypass governed table lifecycle and least privilege. The proposal does not repair `population_records`. This identifies the known limitation of the exact proposed action. Broad storage writes bypass governed table lifecycle and least privilege. The underlying problem remains external table storage is separately administered and dropping the table does not necessarily remove underlying files; Create or convert to an eligible Unity Catalog managed Delta table with approved storage and ownership semantics instead targets that failure.
Incorrect Answers
A:External table metadata deletion does not guarantee deletion of externally owned data. This would apply to another option for `population_records`. This limitation belongs to the different alternative "Assume DROP TABLE on an external table always deletes its cloud data files". The stem calls for the specific failure of "Give every analyst write access to the raw external bucket".
C:Workspace files do not establish governed managed Delta table storage and ownership. This would apply to an alternative change for `population_records`. This failure applies to the separate proposal "Copy the data into a personal workspace folder and call it a managed table".
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 external table storage is separately administered and dropping the table does not necessarily remove underlying files.
Question 609
At a municipal transit operator, a curated Delta table is meant to be fully platform-managed, but its owner uses an external storage path with separate lifecycle policies. The dataset `population_records` is in scope, and effective access must follow least privilege. Which decision preserves the stated data contract while keeping the change scope proportionate?
- Copy the data into a personal workspace folder and call it a managed table
- Give every analyst write access to the raw external bucket
- Assume DROP TABLE on an external table always deletes its cloud data files
- Use managed lifecycle where the platform should own storage while retaining external tables for independently controlled paths
Explanation
Correct Answer
D:Use managed lifecycle where the platform should own storage while retaining external tables for independently controlled paths. This explicitly bounds the compromise while still addressing external table storage is separately administered and dropping the table does not necessarily remove underlying files. Acceptance relies on create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy rather than simply declaring the change complete.
Incorrect Answers
A:Copy the data into a personal workspace folder and call it a managed table. Workspace files do not establish governed managed Delta table storage and ownership. Monitoring after deployment does not make this approach a safe bounded tradeoff for `population_records`.
B:Give every analyst write access to the raw external bucket. Broad storage writes bypass governed table lifecycle and least privilege. Monitoring after deployment does not make this approach a safe bounded tradeoff for `population_records`.
C:Assume DROP TABLE on an external table always deletes its cloud data files. External table metadata deletion does not guarantee deletion of externally owned data. Monitoring after deployment does not make this approach a safe bounded tradeoff for `population_records`.
Question 610
At a municipal transit operator, a curated Delta table is meant to be fully platform-managed, but its owner uses an external storage path with separate lifecycle policies. The dataset `population_records` is in scope, and effective access must follow least privilege. What verification provides evidence of correct behavior under the original adverse condition?
- Check that the intended configuration exists for `population_records` and that a healthy run succeeded, without inducing the earlier failure.
- Review a platform-level availability report for `population_records` without testing whether external table storage is separately administered and dropping the table does not necessarily remove underlying files.
- Create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy
- Run only a normal, unchanged `population_records` sample and review table metadata.
Explanation
Correct Answer
C:Create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy. This reproduces the scenario-dependent condition, verifies table metadata, storage location, table type, object ownership, and file retention after drop, and directly tests whether external table storage is separately administered and dropping the table does not necessarily remove underlying files is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Check that the intended configuration exists for `population_records` 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 external table storage is separately administered and dropping the table does not necessarily remove underlying files.
B:Review a platform-level availability report for `population_records` without testing whether external table storage is separately administered and dropping the table does not necessarily remove underlying files. Aggregate availability does not establish the behavior of affected `population_records` records. It cannot replace the direct exercise: create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy.
D:Run only a normal, unchanged `population_records` sample and review table metadata. A normal sample does not challenge external table storage is separately administered and dropping the table does not necessarily remove underlying files.