Certified Data Engineer Associate Practice Test 10
Question 90
At a digital publishing service, a streaming JSON feed added a new optional field and Auto Loader stopped at a schema evolution exception. The dataset `maintenance_events` is in scope, and bronze tables must remain governed by Unity Catalog. What verification provides evidence of correct behavior under the original adverse condition?
- Check that the intended configuration exists for `maintenance_events` and that a healthy run succeeded, without inducing the earlier failure.
- Run only a normal, unchanged `maintenance_events` sample and review new file schema.
- Review a platform-level availability report for `maintenance_events` without testing whether Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
- Inject a JSON field not present in the first batch and confirm the restarted stream retains it without losing records
Explanation
Correct Answer
D: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:Check that the intended configuration exists for `maintenance_events` and that a healthy run succeeded, without inducing the earlier failure. Installed configuration and a healthy run are insufficient to prove the failure mode is gone. The original issue was Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
B:Run only a normal, unchanged `maintenance_events` 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.
C:Review a platform-level availability report for `maintenance_events` 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 `maintenance_events` 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.
Question 91
At a medical device company, semi-structured feeds contain occasional type mismatches that must be retained for later triage rather than dropped. The dataset `orders_bronze` is in scope, and repeat deliveries cannot silently double-count business records. Which investigation best tests the stated constraint with direct data?
- 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 saved configuration with the signed change ticket for `orders_bronze` while omitting source and output records.
- Correlate _rescued_data contents, original source path across affected and unaffected `R034-CASE-019` runs.
Explanation
Correct Answer
D:Correlate _rescued_data contents, original source path across affected and unaffected `R034-CASE-019` runs.. By joining _rescued_data contents, original source path, schema mismatch rate, and recovered values across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type. It also sets a measurable baseline for send a known type-mismatched JSON record and assert the original field survives in the rescued column.
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 the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type. The failing-path _rescued_data contents, original source path, schema mismatch rate, and recovered values 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 the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type. This check never observes the affected `orders_bronze` records or their causal path.
C:Compare the saved configuration with the signed change ticket for `orders_bronze` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit _rescued_data contents, original source path, schema mismatch rate, and recovered values, the direct means of distinguishing the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type.
Question 92
At a medical device company, semi-structured feeds contain occasional type mismatches that must be retained for later triage rather than dropped. The dataset `orders_bronze` is in scope, and repeat deliveries cannot silently double-count business records. Which option targets the actual technical dependency rather than an incidental symptom?
- Configure an Auto Loader rescued-data column and inspect its JSON payload for unparsed field values
- Turn off schema inference and rescued data then accept null values; use that approach for `orders_bronze`.
- Coerce every nested field to an integer at ingestion without validation; use that approach for `orders_bronze`.
- Use DROPMALFORMED and discard every row with an unexpected type; use that approach for `orders_bronze`.
Explanation
Correct Answer
A:Configure an Auto Loader rescued-data column and inspect its JSON payload for unparsed field values. This directly addresses the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type. The design should be accepted only after send a known type-mismatched JSON record and assert the original field survives in the rescued column; the related operational boundary is to retain anomalous source details in bronze while limiting automatic changes to trusted silver schemas.
Incorrect Answers
B:Turn off schema inference and rescued data then accept null values; use that approach for `orders_bronze`. Unrecognized information is lost rather than available for triage. For `orders_bronze`, this cannot remove the causal limitation: the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type.
C:Coerce every nested field to an integer at ingestion without validation; use that approach for `orders_bronze`. Invalid conversions either fail or misrepresent original payload content. For `orders_bronze`, this cannot remove the causal limitation: the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type.
D:Use DROPMALFORMED and discard every row with an unexpected type; use that approach for `orders_bronze`. Dropping the record loses evidence needed for later data quality repair. For `orders_bronze`, this cannot remove the causal limitation: the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type.
Question 93
At a medical device company, semi-structured feeds contain occasional type mismatches that must be retained for later triage rather than dropped. The dataset `orders_bronze` is in scope, and repeat deliveries cannot silently double-count business records. A teammate proposes: "Turn off schema inference and rescued data then accept null values." Which technical limitation is the decisive reason not to approve that specific proposal?
- Invalid conversions either fail or misrepresent original payload content. This would apply to another option for `orders_bronze`.
- Dropping the record loses evidence needed for later data quality repair. This would apply to an alternative change for `orders_bronze`.
- Unrecognized information is lost rather than available for triage. The proposal does not repair `orders_bronze`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
Explanation
Correct Answer
C:Unrecognized information is lost rather than available for triage. The proposal does not repair `orders_bronze`. This identifies the known limitation of the exact proposed action. Unrecognized information is lost rather than available for triage. The underlying problem remains the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type; Configure an Auto Loader rescued-data column and inspect its JSON payload for unparsed field values instead targets that failure.
Incorrect Answers
A:Invalid conversions either fail or misrepresent original payload content. This would apply to another option for `orders_bronze`. This limitation belongs to the different alternative "Coerce every nested field to an integer at ingestion without validation". The stem calls for the specific failure of "Turn off schema inference and rescued data then accept null values".
B:Dropping the record loses evidence needed for later data quality repair. This would apply to an alternative change for `orders_bronze`. This failure applies to the separate proposal "Use DROPMALFORMED and discard every row with an unexpected type".
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 the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type.
Question 94
At a medical device company, semi-structured feeds contain occasional type mismatches that must be retained for later triage rather than dropped. The dataset `orders_bronze` is in scope, and repeat deliveries cannot silently double-count business records. What operational boundary should be documented for approval?
- Use DROPMALFORMED and discard every row with an unexpected type
- Coerce every nested field to an integer at ingestion without validation
- Turn off schema inference and rescued data then accept null values; monitor results only after launch of `orders_bronze`.
- Retain anomalous source details in bronze while limiting automatic changes to trusted silver schemas
Explanation
Correct Answer
D:Retain anomalous source details in bronze while limiting automatic changes to trusted silver schemas. This explicitly bounds the compromise while still addressing the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type. Acceptance relies on send a known type-mismatched JSON record and assert the original field survives in the rescued column rather than simply declaring the change complete.
Incorrect Answers
A:Use DROPMALFORMED and discard every row with an unexpected type. Dropping the record loses evidence needed for later data quality repair. Monitoring after deployment does not make this approach a safe bounded tradeoff for `orders_bronze`.
B:Coerce every nested field to an integer at ingestion without validation. Invalid conversions either fail or misrepresent original payload content. Monitoring after deployment does not make this approach a safe bounded tradeoff for `orders_bronze`.
C:Turn off schema inference and rescued data then accept null values; monitor results only after launch of `orders_bronze`. Unrecognized information is lost rather than available for triage. Monitoring after deployment does not make this approach a safe bounded tradeoff for `orders_bronze`.
Question 95
At a medical device company, semi-structured feeds contain occasional type mismatches that must be retained for later triage rather than dropped. The dataset `orders_bronze` is in scope, and repeat deliveries cannot silently double-count business records. Which validation should be required in the release record?
- Run only a normal, unchanged `orders_bronze` sample and review _rescued_data contents.
- Send a known type-mismatched JSON record and assert the original field survives in the rescued column
- Review a platform-level availability report for `orders_bronze` without testing whether the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type.
- Check that the intended configuration exists for `orders_bronze` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
B:Send a known type-mismatched JSON record and assert the original field survives in the rescued column. This reproduces the scenario-dependent condition, verifies _rescued_data contents, original source path, schema mismatch rate, and recovered values, and directly tests whether the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `orders_bronze` sample and review _rescued_data contents. A normal sample does not challenge the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type.
C:Review a platform-level availability report for `orders_bronze` without testing whether the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type. Aggregate availability does not establish the behavior of affected `orders_bronze` records. It cannot replace the direct exercise: send a known type-mismatched JSON record and assert the original field survives in the rescued column.
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 the rescue path preserves unexpected or mismatched fields without pretending they conform to the declared type.
Question 96
At a manufacturing supplier, a streaming JSON feed added a new optional field and Auto Loader stopped at a schema evolution exception. The dataset `wind_turbine_events` is in scope, and bronze tables must remain governed by Unity Catalog. Before choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- Correlate new file schema, _schemas changes across affected and unaffected `R034-CASE-020` 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
Explanation
Correct Answer
B:Correlate new file schema, _schemas changes across affected and unaffected `R034-CASE-020` runs.. By joining new file schema, _schemas changes, stream exception, and post-restart bronze column count across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: Auto Loader records the new field and may stop the stream so its schema change can be applied on restart. It also sets a measurable baseline for inject a JSON field not present in the first batch and confirm the restarted stream retains it without losing records.
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 Auto Loader records the new field and may stop the stream so its schema change can be applied on restart. The failing-path new file schema, _schemas changes, stream exception, and post-restart bronze column count 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 Auto Loader records the new field and may stop the stream so its schema change can be applied on restart. This check never observes the affected `wind_turbine_events` 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 new file schema, _schemas changes, stream exception, and post-restart bronze column count, the direct means of distinguishing Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
Question 97
At a manufacturing supplier, a streaming JSON feed added a new optional field and Auto Loader stopped at a schema evolution exception. The dataset `wind_turbine_events` is in scope, and bronze tables must remain governed by Unity Catalog. Which implementation best resolves the stated defect without breaking the business constraint?
- Retain the schema location, use a supported add-new-columns evolution mode, and restart after Auto Loader updates the schema
- Delete both checkpoint and schema location and replay everything; use that approach for `wind_turbine_events`.
- Continue to parse only the previous schema and silently discard the new field; use that approach for `wind_turbine_events`.
- Use failOnNewColumns indefinitely while demanding automatic schema evolution; use that approach for `wind_turbine_events`.
Explanation
Correct Answer
A:Retain the schema location, use a supported add-new-columns evolution mode, and restart after Auto Loader updates the schema. This directly addresses Auto Loader records the new field and may stop the stream so its schema change can be applied on restart. The design should be accepted only after inject a JSON field not present in the first batch and confirm the restarted stream retains it without losing records; the related operational boundary is to accept a controlled stream restart for schema evolution rather than losing newly arriving attributes.
Incorrect Answers
B:Delete both checkpoint and schema location and replay everything; use that approach for `wind_turbine_events`. Erasing progress and inference history risks replay and inconsistent schema discovery. For `wind_turbine_events`, this cannot remove the causal limitation: Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
C:Continue to parse only the previous schema and silently discard the new field; use that approach for `wind_turbine_events`. Ignoring the new field violates the requirement to retain the source attribute. For `wind_turbine_events`, this cannot remove the causal limitation: Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
D:Use failOnNewColumns indefinitely while demanding automatic schema evolution; use that approach for `wind_turbine_events`. Failing on every unknown field does not deliver the requested automatic adaptation. For `wind_turbine_events`, this cannot remove the causal limitation: Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
Question 98
At a manufacturing supplier, a streaming JSON feed added a new optional field and Auto Loader stopped at a schema evolution exception. The dataset `wind_turbine_events` is in scope, and bronze tables must remain governed by Unity Catalog. A teammate proposes: "Use failOnNewColumns indefinitely while demanding automatic schema evolution." Which technical limitation is the decisive reason not to approve that specific proposal?
- Ignoring the new field violates the requirement to retain the source attribute. This would apply to an alternative change for `wind_turbine_events`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
- Erasing progress and inference history risks replay and inconsistent schema discovery. This would apply to another option for `wind_turbine_events`.
- Failing on every unknown field does not deliver the requested automatic adaptation. The proposal does not repair `wind_turbine_events`.
Explanation
Correct Answer
D:Failing on every unknown field does not deliver the requested automatic adaptation. The proposal does not repair `wind_turbine_events`. This identifies the known limitation of the exact proposed action. Failing on every unknown field does not deliver the requested automatic adaptation. The underlying problem remains Auto Loader records the new field and may stop the stream so its schema change can be applied on restart; Retain the schema location, use a supported add-new-columns evolution mode, and restart after Auto Loader updates the schema instead targets that failure.
Incorrect Answers
A:Ignoring the new field violates the requirement to retain the source attribute. This would apply to an alternative change for `wind_turbine_events`. This failure applies to the separate proposal "Continue to parse only the previous schema and silently discard the new field".
B: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 Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
C:Erasing progress and inference history risks replay and inconsistent schema discovery. This would apply to another option for `wind_turbine_events`. This limitation belongs to the different alternative "Delete both checkpoint and schema location and replay everything". The stem calls for the specific failure of "Use failOnNewColumns indefinitely while demanding automatic schema evolution".
Question 99
At a manufacturing supplier, a streaming JSON feed added a new optional field and Auto Loader stopped at a schema evolution exception. The dataset `wind_turbine_events` is in scope, and bronze tables must remain governed by Unity Catalog. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Use failOnNewColumns indefinitely while demanding automatic schema evolution
- Continue to parse only the previous schema and silently discard the new field
- Accept a controlled stream restart for schema evolution rather than losing newly arriving attributes
- Delete both checkpoint and schema location and replay everything
Explanation
Correct Answer
C:Accept a controlled stream restart for schema evolution rather than losing newly arriving attributes. This explicitly bounds the compromise while still addressing Auto Loader records the new field and may stop the stream so its schema change can be applied on restart. Acceptance relies on inject a JSON field not present in the first batch and confirm the restarted stream retains it without losing records rather than simply declaring the change complete.
Incorrect Answers
A:Use failOnNewColumns indefinitely while demanding automatic schema evolution. Failing on every unknown field does not deliver the requested automatic adaptation. Monitoring after deployment does not make this approach a safe bounded tradeoff for `wind_turbine_events`.
B:Continue to parse only the previous schema and silently discard the new field. Ignoring the new field violates the requirement to retain the source attribute. Monitoring after deployment does not make this approach a safe bounded tradeoff for `wind_turbine_events`.
D:Delete both checkpoint and schema location and replay everything. Erasing progress and inference history risks replay and inconsistent schema discovery. Monitoring after deployment does not make this approach a safe bounded tradeoff for `wind_turbine_events`.
Question 100
At a manufacturing supplier, a streaming JSON feed added a new optional field and Auto Loader stopped at a schema evolution exception. The dataset `wind_turbine_events` is in scope, and bronze tables must remain governed by Unity Catalog. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Run only a normal, unchanged `wind_turbine_events` sample and review new file schema.
- Review a platform-level availability report for `wind_turbine_events` without testing whether Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.
- Check that the intended configuration exists for `wind_turbine_events` and that a healthy run succeeded, without inducing the earlier failure.
- Inject a JSON field not present in the first batch and confirm the restarted stream retains it without losing records
Explanation
Correct Answer
D: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:Run only a normal, unchanged `wind_turbine_events` 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.
B:Review a platform-level availability report for `wind_turbine_events` 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 `wind_turbine_events` 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.
C:Check that the intended configuration exists for `wind_turbine_events` and that a healthy run succeeded, without inducing the earlier failure. Installed configuration and a healthy run are insufficient to prove the failure mode is gone. The original issue was Auto Loader records the new field and may stop the stream so its schema change can be applied on restart.