Certified Data Engineer Associate Practice Test 12
Question 110
At a vehicle fleet operator, a streaming JSON feed added a new optional field and Auto Loader stopped at a schema evolution exception. The dataset `orders_bronze` is in scope, and bronze tables must remain governed by Unity Catalog. What verification provides evidence of correct behavior under the original adverse condition?
- Review a platform-level availability report for `orders_bronze` without testing whether Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
- Run only a normal, unchanged `orders_bronze` sample and review new file schema.
- Inject a JSON field not present in the first batch and confirm the restarted stream retains it without losing records
- Check that the intended configuration exists for `orders_bronze` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
C:Inject a JSON field not present in the first batch and confirm the restarted stream retains it without losing records. This reproduces the scenario-dependent condition, verifies new file schema, _schemas changes, stream exception, and post-restart bronze column count, and directly tests whether Auto Loader records the new field and may stop the stream so its schema change can be applied on restart is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `orders_bronze` without testing whether Auto Loader records the new field and may stop the stream so its schema change can be applied on restart. Aggregate availability does not establish the behavior of affected `orders_bronze` records. It cannot replace the direct exercise: inject a JSON field not present in the first batch and confirm the restarted stream retains it without losing records.
B:Run only a normal, unchanged `orders_bronze` sample and review new file schema. A normal sample does not challenge Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
D:Check that the intended configuration exists for `orders_bronze` 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 Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
Question 111
At a scientific imaging provider, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `shipment_status` is in scope, and an interrupted delivery must be recoverable without data loss. Which investigation best tests the stated constraint with direct data?
- Correlate connector supported source capabilities, change progress across affected and unaffected `R034-CASE-023` 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 supported source capabilities, change progress across affected and unaffected `R034-CASE-023` 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
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 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.
C: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 `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 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 112
At a scientific imaging provider, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `shipment_status` is in scope, and an interrupted delivery must be recoverable without data loss. Which option targets the actual technical dependency rather than an incidental symptom?
- Poll the SaaS dashboard HTML from a notebook as a replacement for change capture; use that approach for `shipment_status`.
- Create a table once from the first snapshot and never refresh it; use that approach for `shipment_status`.
- Append each daily SaaS snapshot without change keys; use that approach for `shipment_status`.
- Choose a compatible managed Lakeflow Connect ingestion connector with supported incremental change capture into Unity Catalog Delta
Explanation
Correct Answer
D: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 `shipment_status`. HTML scraping lacks an agreed change protocol and stable source semantics. For `shipment_status`, this cannot remove the causal limitation: snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
B:Create a table once from the first snapshot and never refresh it; use that approach for `shipment_status`. The destination becomes stale after the initial extract. For `shipment_status`, this cannot remove the causal limitation: snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
C:Append each daily SaaS snapshot without change keys; use that approach for `shipment_status`. Repeated snapshots multiply unchanged rows and cannot represent deletions reliably. For `shipment_status`, this cannot remove the causal limitation: snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
Question 113
At a scientific imaging provider, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `shipment_status` is in scope, and an interrupted delivery must be recoverable without data loss. A teammate proposes: "Create a table once from the first snapshot and never refresh it." Which technical limitation is the decisive reason not to approve that specific proposal?
- Repeated snapshots multiply unchanged rows and cannot represent deletions reliably. This would apply to an alternative change for `shipment_status`.
- The destination becomes stale after the initial extract. The proposal does not repair `shipment_status`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
- HTML scraping lacks an agreed change protocol and stable source semantics. This would apply to another option for `shipment_status`.
Explanation
Correct Answer
B:The destination becomes stale after the initial extract. The proposal does not repair `shipment_status`. This identifies the known limitation of the exact proposed action. The destination becomes stale after the initial extract. 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:Repeated snapshots multiply unchanged rows and cannot represent deletions reliably. This would apply to an alternative change for `shipment_status`. This failure applies to the separate proposal "Append each daily SaaS snapshot without change keys".
C: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.
D:HTML scraping lacks an agreed change protocol and stable source semantics. This would apply to another option for `shipment_status`. This limitation belongs to the different alternative "Poll the SaaS dashboard HTML from a notebook as a replacement for change capture". The stem calls for the specific failure of "Create a table once from the first snapshot and never refresh it".
Question 114
At a scientific imaging provider, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `shipment_status` is in scope, and an interrupted delivery must be recoverable without data loss. What operational boundary should be documented for approval?
- Poll the SaaS dashboard HTML from a notebook as a replacement for change capture
- Accept a supported managed connector lifecycle to avoid custom delete and schema logic
- Create a table once from the first snapshot and never refresh it
- Append each daily SaaS snapshot without change keys
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: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 `shipment_status`.
C: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 `shipment_status`.
D:Append each daily SaaS snapshot without change keys. Repeated snapshots multiply unchanged rows and cannot represent deletions reliably. Monitoring after deployment does not make this approach a safe bounded tradeoff for `shipment_status`.
Question 115
At a scientific imaging provider, an enterprise SaaS source needs incremental account updates and deletions, but nightly CSV export omits delete events. The dataset `shipment_status` is in scope, and an interrupted delivery must be recoverable without data loss. Which validation should be required in the release record?
- Update and delete a source record, run the connector, and reconcile the target’s final state and change latency
- Run only a normal, unchanged `shipment_status` sample and review connector supported source capabilities.
- 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 snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
Explanation
Correct Answer
A: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
B:Run only a normal, unchanged `shipment_status` 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 `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 snapshot-only exports do not convey an ordered delete/change feed needed for downstream state.
D:Review a platform-level availability report for `shipment_status` 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 `shipment_status` 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.
Question 116
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 choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Correlate connector authentication errors, secret rotation time across affected and unaffected `R034-CASE-024` runs.
- Compare the saved configuration with the signed change ticket for `image_metadata` while omitting source and output records.
- Examine only a normal successful run of `image_metadata` and trend connector authentication errors without recreating the fault.
- Review aggregate cluster availability and job completion for `image_metadata` without correlating the observed error path.
Explanation
Correct Answer
A:Correlate connector authentication errors, secret rotation time across affected and unaffected `R034-CASE-024` 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:Compare the saved configuration with the signed change ticket for `image_metadata` while omitting source and output records. 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.
C:Examine only a normal successful run of `image_metadata` and trend connector authentication errors without recreating the fault. 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.
D:Review aggregate cluster availability and job completion for `image_metadata` without correlating the observed error path. 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 `image_metadata` records or their causal path.
Question 117
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. Which implementation best resolves the stated defect without breaking the business constraint?
- Disable scheduled ingestion until the next monthly maintenance window; use that approach for `image_metadata`.
- Drop and recreate the target Delta table to reset the connector; use that approach for `image_metadata`.
- 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 `image_metadata`.
Explanation
Correct Answer
C: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 `image_metadata`. Stopping retries leaves an increasing data-freshness gap. For `image_metadata`, this cannot remove the causal limitation: a source connector cannot authenticate with rotated credentials even though source data is healthy.
B:Drop and recreate the target Delta table to reset the connector; use that approach for `image_metadata`. Deleting destination state is unrelated to source authentication and destroys history. For `image_metadata`, this cannot remove the causal limitation: a source connector cannot authenticate with rotated credentials even though source data is healthy.
D:Increase notebook executor memory without checking connector errors; use that approach for `image_metadata`. Compute memory is not the cause of a source authentication failure. For `image_metadata`, this cannot remove the causal limitation: a source connector cannot authenticate with rotated credentials even though source data is healthy.
Question 118
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. A teammate proposes: "Increase notebook executor memory without checking connector errors." Which technical limitation is the decisive reason not to approve that specific proposal?
- Stopping retries leaves an increasing data-freshness gap. This would apply to an alternative change for `image_metadata`.
- Deleting destination state is unrelated to source authentication and destroys history. This would apply to another option for `image_metadata`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
- Compute memory is not the cause of a source authentication failure. The proposal does not repair `image_metadata`.
Explanation
Correct Answer
D:Compute memory is not the cause of a source authentication failure. The proposal does not repair `image_metadata`. This identifies the known limitation of the exact proposed action. Compute memory is not the cause of a source authentication failure. 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
A:Stopping retries leaves an increasing data-freshness gap. This would apply to an alternative change for `image_metadata`. This failure applies to the separate proposal "Disable scheduled ingestion until the next monthly maintenance window".
B:Deleting destination state is unrelated to source authentication and destroys history. This would apply to another option for `image_metadata`. This limitation belongs to the different alternative "Drop and recreate the target Delta table to reset the connector". The stem calls for the specific failure of "Increase notebook executor memory without checking connector errors".
C: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 119
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. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Drop and recreate the target Delta table to reset the connector; monitor results only after launch of `image_metadata`.
- Disable scheduled ingestion until the next monthly maintenance window; monitor results only after launch of `image_metadata`.
- Restore least-privilege source access and durable incremental progress without widening entitlements
- Increase notebook executor memory without checking connector errors; monitor results only after launch of `image_metadata`.
Explanation
Correct Answer
C: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:Drop and recreate the target Delta table to reset the connector; monitor results only after launch of `image_metadata`. Deleting destination state is unrelated to source authentication and destroys history. Monitoring after deployment does not make this approach a safe bounded tradeoff for `image_metadata`.
B:Disable scheduled ingestion until the next monthly maintenance window; monitor results only after launch of `image_metadata`. Stopping retries leaves an increasing data-freshness gap. Monitoring after deployment does not make this approach a safe bounded tradeoff for `image_metadata`.
D:Increase notebook executor memory without checking connector errors; monitor results only after launch of `image_metadata`. Compute memory is not the cause of a source authentication failure. Monitoring after deployment does not make this approach a safe bounded tradeoff for `image_metadata`.
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.