Certified Data Engineer Associate Practice Test 13
Question 120
At an agricultural sensor program, a managed connector stopped after a credential rotation while the source continues accepting new orders. The dataset `image_metadata` is in scope, and the target must retain every valid late-arriving event. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Review a platform-level availability report for `image_metadata` without testing whether a source connector cannot authenticate with rotated credentials even though source data is healthy.
- Check that the intended configuration exists for `image_metadata` and that a healthy run succeeded, without inducing the earlier failure.
- Run only a normal, unchanged `image_metadata` sample and review connector authentication errors.
- Rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes
Explanation
Correct Answer
D:Rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes. This reproduces the scenario-dependent condition, verifies connector authentication errors, secret rotation time, source permissions, and last processed update, and directly tests whether a source connector cannot authenticate with rotated credentials even though source data is healthy is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `image_metadata` without testing whether a source connector cannot authenticate with rotated credentials even though source data is healthy. Aggregate availability does not establish the behavior of affected `image_metadata` records. It cannot replace the direct exercise: rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes.
B:Check that the intended configuration exists for `image_metadata` 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 source connector cannot authenticate with rotated credentials even though source data is healthy.
C:Run only a normal, unchanged `image_metadata` sample and review connector authentication errors. A normal sample does not challenge a source connector cannot authenticate with rotated credentials even though source data is healthy.
Question 121
At a municipal transit operator, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `route_updates` is in scope, and an interrupted delivery must be recoverable without data loss. 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 connector supported source capabilities, change progress across affected and unaffected `R034-CASE-025` runs.
- Compare the saved configuration with the signed change ticket for `route_updates` while omitting source and output records.
Explanation
Correct Answer
C:Correlate connector supported source capabilities, change progress across affected and unaffected `R034-CASE-025` runs.. By joining connector supported source capabilities, change progress, delete-event handling, and Delta target state across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: snapshot-only exports do not convey an ordered delete/change feed needed for downstream state. It also sets a measurable baseline for update and delete a source record, run the connector, and reconcile the target’s final state and change latency.
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 snapshot-only exports do not convey an ordered delete/change feed needed for downstream state. The failing-path connector supported source capabilities, change progress, delete-event handling, and Delta target state 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 snapshot-only exports do not convey an ordered delete/change feed needed for downstream state. This check never observes the affected `route_updates` records or their causal path.
D:Compare the saved configuration with the signed change ticket for `route_updates` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit connector supported source capabilities, change progress, delete-event handling, and Delta target state, the direct means of distinguishing snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
Question 122
At a municipal transit operator, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `route_updates` is in scope, and an interrupted delivery must be recoverable without data loss. Which platform configuration or data-engineering change is most defensible?
- Poll the SaaS dashboard HTML from a notebook as a replacement for change capture; use that approach for `route_updates`.
- Append each daily SaaS snapshot without change keys; use that approach for `route_updates`.
- Choose a compatible managed Lakeflow Connect ingestion connector with supported incremental change capture into Unity Catalog Delta
- Create a table once from the first snapshot and never refresh it; use that approach for `route_updates`.
Explanation
Correct Answer
C:Choose a compatible managed Lakeflow Connect ingestion connector with supported incremental change capture into Unity Catalog Delta. This directly addresses snapshot-only exports do not convey an ordered delete/change feed needed for downstream state. The design should be accepted only after update and delete a source record, run the connector, and reconcile the target’s final state and change latency; the related operational boundary is to accept a supported managed connector lifecycle to avoid custom delete and schema logic.
Incorrect Answers
A:Poll the SaaS dashboard HTML from a notebook as a replacement for change capture; use that approach for `route_updates`. HTML scraping lacks an agreed change protocol and stable source semantics. For `route_updates`, this cannot remove the causal limitation: snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
B:Append each daily SaaS snapshot without change keys; use that approach for `route_updates`. Repeated snapshots multiply unchanged rows and cannot represent deletions reliably. For `route_updates`, this cannot remove the causal limitation: snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
D:Create a table once from the first snapshot and never refresh it; use that approach for `route_updates`. The destination becomes stale after the initial extract. For `route_updates`, this cannot remove the causal limitation: snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
Question 123
At a municipal transit operator, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `route_updates` is in scope, and an interrupted delivery must be recoverable without data loss. A teammate proposes: "Append each daily SaaS snapshot without change keys." Which technical limitation is the decisive reason not to approve that specific proposal?
- HTML scraping lacks an agreed change protocol and stable source semantics. This would apply to an alternative change for `route_updates`.
- Repeated snapshots multiply unchanged rows and cannot represent deletions reliably. The proposal does not repair `route_updates`.
- The destination becomes stale after the initial extract. This would apply to another option for `route_updates`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
Explanation
Correct Answer
B:Repeated snapshots multiply unchanged rows and cannot represent deletions reliably. The proposal does not repair `route_updates`. This identifies the known limitation of the exact proposed action. Repeated snapshots multiply unchanged rows and cannot represent deletions reliably. The underlying problem remains snapshot-only exports do not convey an ordered delete/change feed needed for downstream state; Choose a compatible managed Lakeflow Connect ingestion connector with supported incremental change capture into Unity Catalog Delta instead targets that failure.
Incorrect Answers
A:HTML scraping lacks an agreed change protocol and stable source semantics. This would apply to an alternative change for `route_updates`. This failure applies to the separate proposal "Poll the SaaS dashboard HTML from a notebook as a replacement for change capture".
C:The destination becomes stale after the initial extract. This would apply to another option for `route_updates`. This limitation belongs to the different alternative "Create a table once from the first snapshot and never refresh it". The stem calls for the specific failure of "Append each daily SaaS snapshot without change keys".
D:Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct. The case provides a concrete failing data or control path; a mere alternate theory does not address snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
Question 124
At a municipal transit operator, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `route_updates` is in scope, and an interrupted delivery must be recoverable without data loss. What risk-and-cost compromise should the owner accept instead of the proposed shortcuts?
- Create a table once from the first snapshot and never refresh it
- Accept a supported managed connector lifecycle to avoid custom delete and schema logic
- Poll the SaaS dashboard HTML from a notebook as a replacement for change capture
- Append each daily SaaS snapshot without change keys; monitor results only after launch of `route_updates`.
Explanation
Correct Answer
B:Accept a supported managed connector lifecycle to avoid custom delete and schema logic. This explicitly bounds the compromise while still addressing snapshot-only exports do not convey an ordered delete/change feed needed for downstream state. Acceptance relies on update and delete a source record, run the connector, and reconcile the target’s final state and change latency rather than simply declaring the change complete.
Incorrect Answers
A:Create a table once from the first snapshot and never refresh it. The destination becomes stale after the initial extract. Monitoring after deployment does not make this approach a safe bounded tradeoff for `route_updates`.
C:Poll the SaaS dashboard HTML from a notebook as a replacement for change capture. HTML scraping lacks an agreed change protocol and stable source semantics. Monitoring after deployment does not make this approach a safe bounded tradeoff for `route_updates`.
D:Append each daily SaaS snapshot without change keys; monitor results only after launch of `route_updates`. Repeated snapshots multiply unchanged rows and cannot represent deletions reliably. Monitoring after deployment does not make this approach a safe bounded tradeoff for `route_updates`.
Question 125
At a municipal transit operator, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `route_updates` is in scope, and an interrupted delivery must be recoverable without data loss. Which direct test could falsify the proposed fix instead of only confirming deployment?
- Review a platform-level availability report for `route_updates` without testing whether snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
- Run only a normal, unchanged `route_updates` sample and review connector supported source capabilities.
- Check that the intended configuration exists for `route_updates` and that a healthy run succeeded, without inducing the earlier failure.
- Update and delete a source record, run the connector, and reconcile the target’s final state and change latency
Explanation
Correct Answer
D:Update and delete a source record, run the connector, and reconcile the target’s final state and change latency. This reproduces the scenario-dependent condition, verifies connector supported source capabilities, change progress, delete-event handling, and Delta target state, and directly tests whether snapshot-only exports do not convey an ordered delete/change feed needed for downstream state is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `route_updates` without testing whether snapshot-only exports do not convey an ordered delete/change feed needed for downstream state. Aggregate availability does not establish the behavior of affected `route_updates` records. It cannot replace the direct exercise: update and delete a source record, run the connector, and reconcile the target’s final state and change latency.
B:Run only a normal, unchanged `route_updates` sample and review connector supported source capabilities. A normal sample does not challenge snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
C:Check that the intended configuration exists for `route_updates` 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 snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
Question 126
At a subscription media service, a managed connector stopped after a credential rotation while the source continues accepting new orders. The dataset `shipment_status` is in scope, and the target must retain every valid late-arriving event. Which correlated observation is the strongest basis for the change decision?
- Correlate connector authentication errors, secret rotation time across affected and unaffected `R034-CASE-026` 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 connector authentication errors, secret rotation time across affected and unaffected `R034-CASE-026` runs.. By joining connector authentication errors, secret rotation time, source permissions, and last processed update across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: a source connector cannot authenticate with rotated credentials even though source data is healthy. It also sets a measurable baseline for rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes.
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 a source connector cannot authenticate with rotated credentials even though source data is healthy. The failing-path connector authentication errors, secret rotation time, source permissions, and last processed update 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 source connector cannot authenticate with rotated credentials even though source data is healthy. This check never observes the affected `shipment_status` 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 connector authentication errors, secret rotation time, source permissions, and last processed update, the direct means of distinguishing a source connector cannot authenticate with rotated credentials even though source data is healthy.
Question 127
At a subscription media service, a managed connector stopped after a credential rotation while the source continues accepting new orders. The dataset `shipment_status` is in scope, and the target must retain every valid late-arriving event. What implementation should the engineer select for the failing workflow?
- Disable scheduled ingestion until the next monthly maintenance window; use that approach for `shipment_status`.
- Repair the connector authentication and permissions, validate its ingestion state, and resume from retained progress
- Increase notebook executor memory without checking connector errors; use that approach for `shipment_status`.
- Drop and recreate the target Delta table to reset the connector; use that approach for `shipment_status`.
Explanation
Correct Answer
B:Repair the connector authentication and permissions, validate its ingestion state, and resume from retained progress. This directly addresses a source connector cannot authenticate with rotated credentials even though source data is healthy. The design should be accepted only after rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes; the related operational boundary is to restore least-privilege source access and durable incremental progress without widening entitlements.
Incorrect Answers
A:Disable scheduled ingestion until the next monthly maintenance window; use that approach for `shipment_status`. Stopping retries leaves an increasing data-freshness gap. For `shipment_status`, this cannot remove the causal limitation: a source connector cannot authenticate with rotated credentials even though source data is healthy.
C:Increase notebook executor memory without checking connector errors; use that approach for `shipment_status`. Compute memory is not the cause of a source authentication failure. For `shipment_status`, this cannot remove the causal limitation: a source connector cannot authenticate with rotated credentials even though source data is healthy.
D:Drop and recreate the target Delta table to reset the connector; use that approach for `shipment_status`. Deleting destination state is unrelated to source authentication and destroys history. For `shipment_status`, this cannot remove the causal limitation: a source connector cannot authenticate with rotated credentials even though source data is healthy.
Question 128
At a subscription media service, a managed connector stopped after a credential rotation while the source continues accepting new orders. The dataset `shipment_status` is in scope, and the target must retain every valid late-arriving event. A teammate proposes: "Disable scheduled ingestion until the next monthly maintenance window." Which technical limitation is the decisive reason not to approve that specific proposal?
- Stopping retries leaves an increasing data-freshness gap. The proposal does not repair `shipment_status`.
- Deleting destination state is unrelated to source authentication and destroys history. This would apply to an alternative change for `shipment_status`.
- Compute memory is not the cause of a source authentication failure. This would apply to another option for `shipment_status`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
Explanation
Correct Answer
A:Stopping retries leaves an increasing data-freshness gap. The proposal does not repair `shipment_status`. This identifies the known limitation of the exact proposed action. Stopping retries leaves an increasing data-freshness gap. The underlying problem remains a source connector cannot authenticate with rotated credentials even though source data is healthy; Repair the connector authentication and permissions, validate its ingestion state, and resume from retained progress instead targets that failure.
Incorrect Answers
B:Deleting destination state is unrelated to source authentication and destroys history. This would apply to an alternative change for `shipment_status`. This failure applies to the separate proposal "Drop and recreate the target Delta table to reset the connector".
C:Compute memory is not the cause of a source authentication failure. This would apply to another option for `shipment_status`. This limitation belongs to the different alternative "Increase notebook executor memory without checking connector errors". The stem calls for the specific failure of "Disable scheduled ingestion until the next monthly maintenance window".
D:Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct. The case provides a concrete failing data or control path; a mere alternate theory does not address a source connector cannot authenticate with rotated credentials even though source data is healthy.
Question 129
At a subscription media service, a managed connector stopped after a credential rotation while the source continues accepting new orders. The dataset `shipment_status` is in scope, and the target must retain every valid late-arriving event. Which decision preserves the stated data contract while keeping the change scope proportionate?
- Increase notebook executor memory without checking connector errors
- Restore least-privilege source access and durable incremental progress without widening entitlements
- Disable scheduled ingestion until the next monthly maintenance window
- Drop and recreate the target Delta table to reset the connector
Explanation
Correct Answer
B:Restore least-privilege source access and durable incremental progress without widening entitlements. This explicitly bounds the compromise while still addressing a source connector cannot authenticate with rotated credentials even though source data is healthy. Acceptance relies on rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes rather than simply declaring the change complete.
Incorrect Answers
A:Increase notebook executor memory without checking connector errors. Compute memory is not the cause of a source authentication failure. Monitoring after deployment does not make this approach a safe bounded tradeoff for `shipment_status`.
C:Disable scheduled ingestion until the next monthly maintenance window. Stopping retries leaves an increasing data-freshness gap. Monitoring after deployment does not make this approach a safe bounded tradeoff for `shipment_status`.
D:Drop and recreate the target Delta table to reset the connector. Deleting destination state is unrelated to source authentication and destroys history. Monitoring after deployment does not make this approach a safe bounded tradeoff for `shipment_status`.
Question 130
At a subscription media service, a managed connector stopped after a credential rotation while the source continues accepting new orders. The dataset `shipment_status` is in scope, and the target must retain every valid late-arriving event. What verification provides evidence of correct behavior under the original adverse condition?
- Check that the intended configuration exists for `shipment_status` and that a healthy run succeeded, without inducing the earlier failure.
- Review a platform-level availability report for `shipment_status` without testing whether a source connector cannot authenticate with rotated credentials even though source data is healthy.
- Run only a normal, unchanged `shipment_status` sample and review connector authentication errors.
- Rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes
Explanation
Correct Answer
D:Rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes. This reproduces the scenario-dependent condition, verifies connector authentication errors, secret rotation time, source permissions, and last processed update, and directly tests whether a source connector cannot authenticate with rotated credentials even though source data is healthy is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Check that the intended configuration exists for `shipment_status` 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 source connector cannot authenticate with rotated credentials even though source data is healthy.
B:Review a platform-level availability report for `shipment_status` without testing whether a source connector cannot authenticate with rotated credentials even though source data is healthy. Aggregate availability does not establish the behavior of affected `shipment_status` records. It cannot replace the direct exercise: rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes.
C:Run only a normal, unchanged `shipment_status` sample and review connector authentication errors. A normal sample does not challenge a source connector cannot authenticate with rotated credentials even though source data is healthy.