Certified Data Engineer Associate Practice Test 18
Question 170
At a census statistics agency, a supported CRM application offers a managed incremental connector, but the team plans to export full JSON snapshots hourly. The dataset `account_statements` 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?
- Change, delete and re-create a source entity and verify incremental target convergence
- Run only a normal, unchanged `account_statements` sample and review CRM connector support matrix.
- Review a platform-level availability report for `account_statements` without testing whether custom snapshots add extraction maintenance and cannot reliably detect late deletions.
- Check that the intended configuration exists for `account_statements` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
A:Change, delete and re-create a source entity and verify incremental target convergence. This reproduces the scenario-dependent condition, verifies CRM connector support matrix, update/delete capture, replication delay, and target governance, and directly tests whether custom snapshots add extraction maintenance and cannot reliably detect late deletions is resolved. Observed results, not intent, determine approval.
Incorrect Answers
B:Run only a normal, unchanged `account_statements` sample and review CRM connector support matrix. A normal sample does not challenge custom snapshots add extraction maintenance and cannot reliably detect late deletions.
C:Review a platform-level availability report for `account_statements` without testing whether custom snapshots add extraction maintenance and cannot reliably detect late deletions. Aggregate availability does not establish the behavior of affected `account_statements` records. It cannot replace the direct exercise: change, delete and re-create a source entity and verify incremental target convergence.
D:Check that the intended configuration exists for `account_statements` 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 custom snapshots add extraction maintenance and cannot reliably detect late deletions.
Question 171
At a parcel sorting company, e-commerce events contain an array of purchased items, but the reporting table stores the array as a raw opaque string. The dataset `route_updates` is in scope, and an interrupted delivery must be recoverable without data loss. Which investigation best tests the stated constraint with direct data?
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- Correlate nested array length, event count across affected and unaffected `R034-CASE-035` 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 nested array length, event count across affected and unaffected `R034-CASE-035` runs.. By joining nested array length, event count, exploded item count, and item-level schema across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: an array-valued field is not automatically one row per element in the relational reporting model. It also sets a measurable baseline for ingest an order with three line items and assert exactly three correctly associated silver item rows.
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 an array-valued field is not automatically one row per element in the relational reporting model. The failing-path nested array length, event count, exploded item count, and item-level schema 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 an array-valued field is not automatically one row per element in the relational reporting model. This check never observes the affected `route_updates` 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 nested array length, event count, exploded item count, and item-level schema, the direct means of distinguishing an array-valued field is not automatically one row per element in the relational reporting model.
Question 172
At a parcel sorting company, e-commerce events contain an array of purchased items, but the reporting table stores the array as a raw opaque string. The dataset `route_updates` 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?
- Apply a top-level COUNT to JSON event rows and call it an item count; use that approach for `route_updates`.
- Discard the nested item array and keep only the event identifier; use that approach for `route_updates`.
- Split the raw JSON string at every comma to create item records; use that approach for `route_updates`.
- Preserve nested JSON in bronze and use explode on the item array when producing one silver row per purchased item
Explanation
Correct Answer
D:Preserve nested JSON in bronze and use explode on the item array when producing one silver row per purchased item. This directly addresses an array-valued field is not automatically one row per element in the relational reporting model. The design should be accepted only after ingest an order with three line items and assert exactly three correctly associated silver item rows; the related operational boundary is to retain original nested payload for audit while normalizing item-level silver records.
Incorrect Answers
A:Apply a top-level COUNT to JSON event rows and call it an item count; use that approach for `route_updates`. Counting event rows ignores multiple items embedded in one event. For `route_updates`, this cannot remove the causal limitation: an array-valued field is not automatically one row per element in the relational reporting model.
B:Discard the nested item array and keep only the event identifier; use that approach for `route_updates`. Dropping the array removes the item-level facts required downstream. For `route_updates`, this cannot remove the causal limitation: an array-valued field is not automatically one row per element in the relational reporting model.
C:Split the raw JSON string at every comma to create item records; use that approach for `route_updates`. String splitting breaks escaped strings and nested JSON structures. For `route_updates`, this cannot remove the causal limitation: an array-valued field is not automatically one row per element in the relational reporting model.
Question 173
At a parcel sorting company, e-commerce events contain an array of purchased items, but the reporting table stores the array as a raw opaque string. The dataset `route_updates` is in scope, and an interrupted delivery must be recoverable without data loss. A teammate proposes: "Discard the nested item array and keep only the event identifier." Which technical limitation is the decisive reason not to approve that specific proposal?
- Dropping the array removes the item-level facts required downstream. The proposal does not repair `route_updates`.
- Counting event rows ignores multiple items embedded in one event. This would apply to an alternative change for `route_updates`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
- String splitting breaks escaped strings and nested JSON structures. This would apply to another option for `route_updates`.
Explanation
Correct Answer
A:Dropping the array removes the item-level facts required downstream. The proposal does not repair `route_updates`. This identifies the known limitation of the exact proposed action. Dropping the array removes the item-level facts required downstream. The underlying problem remains an array-valued field is not automatically one row per element in the relational reporting model; Preserve nested JSON in bronze and use explode on the item array when producing one silver row per purchased item instead targets that failure.
Incorrect Answers
B:Counting event rows ignores multiple items embedded in one event. This would apply to an alternative change for `route_updates`. This failure applies to the separate proposal "Apply a top-level COUNT to JSON event rows and call it an item count".
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 an array-valued field is not automatically one row per element in the relational reporting model.
D:String splitting breaks escaped strings and nested JSON structures. This would apply to another option for `route_updates`. This limitation belongs to the different alternative "Split the raw JSON string at every comma to create item records". The stem calls for the specific failure of "Discard the nested item array and keep only the event identifier".
Question 174
At a parcel sorting company, e-commerce events contain an array of purchased items, but the reporting table stores the array as a raw opaque string. The dataset `route_updates` is in scope, and an interrupted delivery must be recoverable without data loss. What operational boundary should be documented for approval?
- Discard the nested item array and keep only the event identifier
- Split the raw JSON string at every comma to create item records
- Apply a top-level COUNT to JSON event rows and call it an item count
- Retain original nested payload for audit while normalizing item-level silver records
Explanation
Correct Answer
D:Retain original nested payload for audit while normalizing item-level silver records. This explicitly bounds the compromise while still addressing an array-valued field is not automatically one row per element in the relational reporting model. Acceptance relies on ingest an order with three line items and assert exactly three correctly associated silver item rows rather than simply declaring the change complete.
Incorrect Answers
A:Discard the nested item array and keep only the event identifier. Dropping the array removes the item-level facts required downstream. Monitoring after deployment does not make this approach a safe bounded tradeoff for `route_updates`.
B:Split the raw JSON string at every comma to create item records. String splitting breaks escaped strings and nested JSON structures. Monitoring after deployment does not make this approach a safe bounded tradeoff for `route_updates`.
C:Apply a top-level COUNT to JSON event rows and call it an item count. Counting event rows ignores multiple items embedded in one event. Monitoring after deployment does not make this approach a safe bounded tradeoff for `route_updates`.
Question 175
At a parcel sorting company, e-commerce events contain an array of purchased items, but the reporting table stores the array as a raw opaque string. The dataset `route_updates` is in scope, and an interrupted delivery must be recoverable without data loss. Which validation should be required in the release record?
- Run only a normal, unchanged `route_updates` sample and review nested array length.
- Review a platform-level availability report for `route_updates` without testing whether an array-valued field is not automatically one row per element in the relational reporting model.
- Ingest an order with three line items and assert exactly three correctly associated silver item rows
- Check that the intended configuration exists for `route_updates` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
C:Ingest an order with three line items and assert exactly three correctly associated silver item rows. This reproduces the scenario-dependent condition, verifies nested array length, event count, exploded item count, and item-level schema, and directly tests whether an array-valued field is not automatically one row per element in the relational reporting model is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `route_updates` sample and review nested array length. A normal sample does not challenge an array-valued field is not automatically one row per element in the relational reporting model.
B:Review a platform-level availability report for `route_updates` without testing whether an array-valued field is not automatically one row per element in the relational reporting model. Aggregate availability does not establish the behavior of affected `route_updates` records. It cannot replace the direct exercise: ingest an order with three line items and assert exactly three correctly associated silver item rows.
D: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 an array-valued field is not automatically one row per element in the relational reporting model.
Question 176
At a hospital analytics group, semi-structured sensor payloads add optional nested attributes that vary by device firmware. The dataset `shipment_status` 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?
- Compare the saved configuration with the signed change ticket for `shipment_status` while omitting source and output records.
- Correlate firmware variant, rescued/optional nested paths across affected and unaffected `R034-CASE-036` runs.
- Examine only a normal successful run of `shipment_status` and trend firmware variant without recreating the fault.
- Review aggregate cluster availability and job completion for `shipment_status` without correlating the observed error path.
Explanation
Correct Answer
B:Correlate firmware variant, rescued/optional nested paths across affected and unaffected `R034-CASE-036` runs.. By joining firmware variant, rescued/optional nested paths, parse error counts, and downstream schema conformance across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions. It also sets a measurable baseline for replay two firmware versions with different optional fields and check bronze fidelity plus silver validation.
Incorrect Answers
A:Compare the saved configuration with the signed change ticket for `shipment_status` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit firmware variant, rescued/optional nested paths, parse error counts, and downstream schema conformance, the direct means of distinguishing premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.
C:Examine only a normal successful run of `shipment_status` and trend firmware variant without recreating the fault. A healthy-run trend can be useful, but it does not expose premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions. The failing-path firmware variant, rescued/optional nested paths, parse error counts, and downstream schema conformance has to be correlated before attributing cause.
D:Review aggregate cluster availability and job completion for `shipment_status` without correlating the observed error path. A successful aggregate platform state can coexist with premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions. This check never observes the affected `shipment_status` records or their causal path.
Question 177
At a hospital analytics group, semi-structured sensor payloads add optional nested attributes that vary by device firmware. The dataset `shipment_status` 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?
- Land the raw nested payload in a governed Delta bronze table and selectively project validated nested fields into silver
- Cast the entire JSON object to a single numeric column; use that approach for `shipment_status`.
- Store JSON in user workspace files without Unity Catalog metadata; use that approach for `shipment_status`.
- Reject every payload without all optional fields; use that approach for `shipment_status`.
Explanation
Correct Answer
A:Land the raw nested payload in a governed Delta bronze table and selectively project validated nested fields into silver. This directly addresses premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions. The design should be accepted only after replay two firmware versions with different optional fields and check bronze fidelity plus silver validation; the related operational boundary is to allow flexible bronze ingestion while enforcing stable downstream typed attributes.
Incorrect Answers
B:Cast the entire JSON object to a single numeric column; use that approach for `shipment_status`. A nested structure cannot be represented as one numeric measurement. For `shipment_status`, this cannot remove the causal limitation: premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.
C:Store JSON in user workspace files without Unity Catalog metadata; use that approach for `shipment_status`. Ungoverned workspace copies bypass the required catalog access boundary. For `shipment_status`, this cannot remove the causal limitation: premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.
D:Reject every payload without all optional fields; use that approach for `shipment_status`. Optional fields should not cause the whole valid device event to be dropped. For `shipment_status`, this cannot remove the causal limitation: premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.
Question 178
At a hospital analytics group, semi-structured sensor payloads add optional nested attributes that vary by device firmware. The dataset `shipment_status` is in scope, and the target must retain every valid late-arriving event. A teammate proposes: "Cast the entire JSON object to a single numeric column." Which technical limitation is the decisive reason not to approve that specific proposal?
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
- Ungoverned workspace copies bypass the required catalog access boundary. This would apply to an alternative change for `shipment_status`.
- A nested structure cannot be represented as one numeric measurement. The proposal does not repair `shipment_status`.
- Optional fields should not cause the whole valid device event to be dropped. This would apply to another option for `shipment_status`.
Explanation
Correct Answer
C:A nested structure cannot be represented as one numeric measurement. The proposal does not repair `shipment_status`. This identifies the known limitation of the exact proposed action. A nested structure cannot be represented as one numeric measurement. The underlying problem remains premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions; Land the raw nested payload in a governed Delta bronze table and selectively project validated nested fields into silver instead targets that failure.
Incorrect Answers
A: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 premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.
B:Ungoverned workspace copies bypass the required catalog access boundary. This would apply to an alternative change for `shipment_status`. This failure applies to the separate proposal "Store JSON in user workspace files without Unity Catalog metadata".
D:Optional fields should not cause the whole valid device event to be dropped. This would apply to another option for `shipment_status`. This limitation belongs to the different alternative "Reject every payload without all optional fields". The stem calls for the specific failure of "Cast the entire JSON object to a single numeric column".
Question 179
At a hospital analytics group, semi-structured sensor payloads add optional nested attributes that vary by device firmware. The dataset `shipment_status` 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?
- Store JSON in user workspace files without Unity Catalog metadata; monitor results only after launch of `shipment_status`.
- Reject every payload without all optional fields; monitor results only after launch of `shipment_status`.
- Cast the entire JSON object to a single numeric column; monitor results only after launch of `shipment_status`.
- Allow flexible bronze ingestion while enforcing stable downstream typed attributes
Explanation
Correct Answer
D:Allow flexible bronze ingestion while enforcing stable downstream typed attributes. This explicitly bounds the compromise while still addressing premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions. Acceptance relies on replay two firmware versions with different optional fields and check bronze fidelity plus silver validation rather than simply declaring the change complete.
Incorrect Answers
A:Store JSON in user workspace files without Unity Catalog metadata; monitor results only after launch of `shipment_status`. Ungoverned workspace copies bypass the required catalog access boundary. Monitoring after deployment does not make this approach a safe bounded tradeoff for `shipment_status`.
B:Reject every payload without all optional fields; monitor results only after launch of `shipment_status`. Optional fields should not cause the whole valid device event to be dropped. Monitoring after deployment does not make this approach a safe bounded tradeoff for `shipment_status`.
C:Cast the entire JSON object to a single numeric column; monitor results only after launch of `shipment_status`. A nested structure cannot be represented as one numeric measurement. Monitoring after deployment does not make this approach a safe bounded tradeoff for `shipment_status`.
Question 180
At a hospital analytics group, semi-structured sensor payloads add optional nested attributes that vary by device firmware. The dataset `shipment_status` 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 `shipment_status` without testing whether premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.
- Replay two firmware versions with different optional fields and check bronze fidelity plus silver validation
- Run only a normal, unchanged `shipment_status` sample and review firmware variant.
- Check that the intended configuration exists for `shipment_status` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
B:Replay two firmware versions with different optional fields and check bronze fidelity plus silver validation. This reproduces the scenario-dependent condition, verifies firmware variant, rescued/optional nested paths, parse error counts, and downstream schema conformance, and directly tests whether premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `shipment_status` without testing whether premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions. Aggregate availability does not establish the behavior of affected `shipment_status` records. It cannot replace the direct exercise: replay two firmware versions with different optional fields and check bronze fidelity plus silver validation.
C:Run only a normal, unchanged `shipment_status` sample and review firmware variant. A normal sample does not challenge premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.
D: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 premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.