Certified Data Engineer Associate Practice Test 62
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.
Question 611
At a subscription media service, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `housing_applications` is in scope, and the underlying data retention policy must be preserved. Which investigation best tests the stated constraint with direct data?
- Correlate external location, storage credentials across affected and unaffected `R034-CASE-123` runs.
- Review aggregate cluster availability and job completion for `housing_applications` without correlating the observed error path.
- Examine only a normal successful run of `housing_applications` and trend external location without recreating the fault.
- Compare the saved configuration with the signed change ticket for `housing_applications` while omitting source and output records.
Explanation
Correct Answer
A:Correlate external location, storage credentials across affected and unaffected `R034-CASE-123` 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
B:Review aggregate cluster availability and job completion for `housing_applications` without correlating the observed error path. 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 `housing_applications` records or their causal path.
C:Examine only a normal successful run of `housing_applications` and trend external location without recreating the fault. 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.
D:Compare the saved configuration with the signed change ticket for `housing_applications` 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 612
At a subscription media service, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `housing_applications` is in scope, and the underlying data retention policy must be preserved. Which option targets the actual technical dependency rather than an incidental symptom?
- Drop and recreate the external cloud bucket whenever table metadata changes; use that approach for `housing_applications`.
- Register the approved external Delta location with the required Unity Catalog credentials and maintain external data ownership
- Convert it to a managed table by blindly moving files away from the regulated path; use that approach for `housing_applications`.
- Create an ungoverned temporary view over direct path reads for every analyst; use that approach for `housing_applications`.
Explanation
Correct Answer
B: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
A:Drop and recreate the external cloud bucket whenever table metadata changes; use that approach for `housing_applications`. Deleting the underlying storage is not required for registering or updating external table metadata. For `housing_applications`, 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 `housing_applications`. Unreviewed relocation may violate the required storage residency and retention controls. For `housing_applications`, this cannot remove the causal limitation: moving or deleting regulated files would violate the independent storage retention boundary.
D:Create an ungoverned temporary view over direct path reads for every analyst; use that approach for `housing_applications`. Per-user bypasses undermine shared object permissions and auditability. For `housing_applications`, this cannot remove the causal limitation: moving or deleting regulated files would violate the independent storage retention boundary.
Question 613
At a subscription media service, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `housing_applications` is in scope, and the underlying data retention policy must be preserved. A teammate proposes: "Convert it to a managed table by blindly moving files away from the regulated path." Which technical limitation is the decisive reason not to approve that specific proposal?
- Per-user bypasses undermine shared object permissions and auditability. This would apply to an alternative change for `housing_applications`.
- The failed query is caused only by a temporary notebook session, not catalog scope or security settings.
- Unreviewed relocation may violate the required storage residency and retention controls. The proposal does not repair `housing_applications`.
- Deleting the underlying storage is not required for registering or updating external table metadata. This would apply to another option for `housing_applications`.
Explanation
Correct Answer
C:Unreviewed relocation may violate the required storage residency and retention controls. The proposal does not repair `housing_applications`. This identifies the known limitation of the exact proposed action. Unreviewed relocation may violate the required storage residency and retention controls. 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:Per-user bypasses undermine shared object permissions and auditability. This would apply to an alternative change for `housing_applications`. This failure applies to the separate proposal "Create an ungoverned temporary view over direct path reads for every 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 moving or deleting regulated files would violate the independent storage retention boundary.
D:Deleting the underlying storage is not required for registering or updating external table metadata. This would apply to another option for `housing_applications`. This limitation belongs to the different alternative "Drop and recreate the external cloud bucket whenever table metadata changes". The stem calls for the specific failure of "Convert it to a managed table by blindly moving files away from the regulated path".
Question 614
At a subscription media service, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `housing_applications` is in scope, and the underlying data retention policy must be preserved. What operational boundary should be documented for approval?
- Drop and recreate the external cloud bucket whenever table metadata changes; monitor results only after launch of `housing_applications`.
- Convert it to a managed table by blindly moving files away from the regulated path; monitor results only after launch of `housing_applications`.
- Create an ungoverned temporary view over direct path reads for every analyst; monitor results only after launch of `housing_applications`.
- Preserve independent storage control while exposing a governed catalog object
Explanation
Correct Answer
D: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; monitor results only after launch of `housing_applications`. 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 `housing_applications`.
B:Convert it to a managed table by blindly moving files away from the regulated path; monitor results only after launch of `housing_applications`. Unreviewed relocation may violate the required storage residency and retention controls. Monitoring after deployment does not make this approach a safe bounded tradeoff for `housing_applications`.
C:Create an ungoverned temporary view over direct path reads for every analyst; monitor results only after launch of `housing_applications`. Per-user bypasses undermine shared object permissions and auditability. Monitoring after deployment does not make this approach a safe bounded tradeoff for `housing_applications`.
Question 615
At a subscription media service, an external Delta table must remain at a legally controlled cloud path while analysts query it through Unity Catalog. The dataset `housing_applications` is in scope, and the underlying data retention policy must be preserved. Which validation should be required in the release record?
- Review a platform-level availability report for `housing_applications` without testing whether moving or deleting regulated files would violate the independent storage retention boundary.
- Run only a normal, unchanged `housing_applications` sample and review external location.
- Check that the intended configuration exists for `housing_applications` and that a healthy run succeeded, without inducing the earlier failure.
- Register the existing Delta dataset without copying data and verify governed reads plus unchanged storage ownership
Explanation
Correct Answer
D: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
A:Review a platform-level availability report for `housing_applications` without testing whether moving or deleting regulated files would violate the independent storage retention boundary. Aggregate availability does not establish the behavior of affected `housing_applications` records. It cannot replace the direct exercise: register the existing Delta dataset without copying data and verify governed reads plus unchanged storage ownership.
B:Run only a normal, unchanged `housing_applications` sample and review external location. A normal sample does not challenge moving or deleting regulated files would violate the independent storage retention boundary.
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 moving or deleting regulated files would violate the independent storage retention boundary.
Question 616
At a regional banking group, 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 `cargo_visits` is in scope, and effective access must follow least privilege. Before choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Correlate table metadata, storage location across affected and unaffected `R034-CASE-124` 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 `cargo_visits` and trend table metadata without recreating the fault.
Explanation
Correct Answer
A:Correlate table metadata, storage location across affected and unaffected `R034-CASE-124` 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: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 `cargo_visits` 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 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.
D:Examine only a normal successful run of `cargo_visits` and trend table metadata without recreating the fault. 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.
Question 617
At a regional banking group, 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 `cargo_visits` is in scope, and effective access must follow least privilege. Which implementation best resolves the stated defect without breaking the business constraint?
- Assume DROP TABLE on an external table always deletes its cloud data files; use that approach for `cargo_visits`.
- Give every analyst write access to the raw external bucket; use that approach for `cargo_visits`.
- Copy the data into a personal workspace folder and call it a managed table; use that approach for `cargo_visits`.
- Create or convert to an eligible Unity Catalog managed Delta table with approved storage and ownership semantics
Explanation
Correct Answer
D: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:Assume DROP TABLE on an external table always deletes its cloud data files; use that approach for `cargo_visits`. External table metadata deletion does not guarantee deletion of externally owned data. For `cargo_visits`, this cannot remove the causal limitation: external table storage is separately administered and dropping the table does not necessarily remove underlying files.
B:Give every analyst write access to the raw external bucket; use that approach for `cargo_visits`. Broad storage writes bypass governed table lifecycle and least privilege. For `cargo_visits`, this cannot remove the causal limitation: external table storage is separately administered and dropping the table does not necessarily remove underlying files.
C:Copy the data into a personal workspace folder and call it a managed table; use that approach for `cargo_visits`. Workspace files do not establish governed managed Delta table storage and ownership. For `cargo_visits`, this cannot remove the causal limitation: external table storage is separately administered and dropping the table does not necessarily remove underlying files.
Question 618
At a regional banking group, 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 `cargo_visits` is in scope, and effective access must follow least privilege. A teammate proposes: "Copy the data into a personal workspace folder and call it a managed table." Which technical limitation is the decisive reason not to approve that specific proposal?
- Broad storage writes bypass governed table lifecycle and least privilege. 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.
- Workspace files do not establish governed managed Delta table storage and ownership. The proposal does not repair `cargo_visits`.
- External table metadata deletion does not guarantee deletion of externally owned data. This would apply to an alternative change for `cargo_visits`.
Explanation
Correct Answer
C:Workspace files do not establish governed managed Delta table storage and ownership. The proposal does not repair `cargo_visits`. This identifies the known limitation of the exact proposed action. Workspace files do not establish governed managed Delta table storage and ownership. 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:Broad storage writes bypass governed table lifecycle and least privilege. This would apply to another option for `cargo_visits`. This limitation belongs to the different alternative "Give every analyst write access to the raw external bucket". The stem calls for the specific failure of "Copy the data into a personal workspace folder and call it a managed table".
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 external table storage is separately administered and dropping the table does not necessarily remove underlying files.
D:External table metadata deletion does not guarantee deletion of externally owned data. This would apply to an alternative change for `cargo_visits`. This failure applies to the separate proposal "Assume DROP TABLE on an external table always deletes its cloud data files".
Question 619
At a regional banking group, 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 `cargo_visits` is in scope, and effective access must follow least privilege. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Give every analyst write access to the raw external bucket
- Use managed lifecycle where the platform should own storage while retaining external tables for independently controlled paths
- Copy the data into a personal workspace folder and call it a managed table
- Assume DROP TABLE on an external table always deletes its cloud data files; monitor results only after launch of `cargo_visits`.
Explanation
Correct Answer
B: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: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 `cargo_visits`.
C: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 `cargo_visits`.
D:Assume DROP TABLE on an external table always deletes its cloud data files; monitor results only after launch of `cargo_visits`. 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 `cargo_visits`.
Question 620
At a regional banking group, 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 `cargo_visits` is in scope, and effective access must follow least privilege. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Check that the intended configuration exists for `cargo_visits` and that a healthy run succeeded, without inducing the earlier failure.
- Run only a normal, unchanged `cargo_visits` sample and review table metadata.
- Create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy
- Review a platform-level availability report for `cargo_visits` without testing whether external table storage is separately administered and dropping the table does not necessarily remove underlying files.
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 `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 external table storage is separately administered and dropping the table does not necessarily remove underlying files.
B:Run only a normal, unchanged `cargo_visits` 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.
D:Review a platform-level availability report for `cargo_visits` 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 `cargo_visits` records. It cannot replace the direct exercise: create test managed and external tables, drop each, and confirm behavior of metadata and storage under policy.