Certified Data Engineer Associate Practice Test 20
Question 190
At a wholesale pharmacy group, semi-structured sensor payloads add optional nested attributes that vary by device firmware. The dataset `route_updates` 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 `route_updates` and that a healthy run succeeded, without inducing the earlier failure.
- Review a platform-level availability report for `route_updates` without testing whether premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.
- Run only a normal, unchanged `route_updates` sample and review firmware variant.
- Replay two firmware versions with different optional fields and check bronze fidelity plus silver validation
Explanation
Correct Answer
D: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: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 premature rigid flattening loses attributes that are absent or newly introduced in some firmware versions.
B:Review a platform-level availability report for `route_updates` 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 `route_updates` 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 `route_updates` 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.
Question 191
At a vehicle fleet operator, bronze orders arrive with currency totals as strings and null order dates, producing incorrect daily financial summaries. The dataset `booking_changes` is in scope, and the release must preserve the original source evidence. Which investigation best tests the stated constraint with direct data?
- Examine only a normal successful run of `booking_changes` and trend source field types without recreating the fault.
- Review aggregate cluster availability and job completion for `booking_changes` without correlating the observed error path.
- Correlate source field types, invalid-row sample across affected and unaffected `R034-CASE-039` runs.
- Compare the saved configuration with the signed change ticket for `booking_changes` while omitting source and output records.
Explanation
Correct Answer
C:Correlate source field types, invalid-row sample across affected and unaffected `R034-CASE-039` runs.. By joining source field types, invalid-row sample, cast success count, and silver numeric reconciliation across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: string amounts can aggregate incorrectly and missing business dates are not safe grouping keys. It also sets a measurable baseline for load zero, null and malformed amounts, then reconcile silver totals and quarantined rejects to bronze input.
Incorrect Answers
A:Examine only a normal successful run of `booking_changes` and trend source field types without recreating the fault. A healthy-run trend can be useful, but it does not expose string amounts can aggregate incorrectly and missing business dates are not safe grouping keys. The failing-path source field types, invalid-row sample, cast success count, and silver numeric reconciliation has to be correlated before attributing cause.
B:Review aggregate cluster availability and job completion for `booking_changes` without correlating the observed error path. A successful aggregate platform state can coexist with string amounts can aggregate incorrectly and missing business dates are not safe grouping keys. This check never observes the affected `booking_changes` records or their causal path.
D:Compare the saved configuration with the signed change ticket for `booking_changes` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit source field types, invalid-row sample, cast success count, and silver numeric reconciliation, the direct means of distinguishing string amounts can aggregate incorrectly and missing business dates are not safe grouping keys.
Question 192
At a vehicle fleet operator, bronze orders arrive with currency totals as strings and null order dates, producing incorrect daily financial summaries. The dataset `booking_changes` is in scope, and the release must preserve the original source evidence. Which option targets the actual technical dependency rather than an incidental symptom?
- Validate and cast amounts to a numeric type, quarantine invalid dates, and write typed clean records to a silver Delta table
- Aggregate the raw string amount without conversion and skip null checks; use that approach for `booking_changes`.
- Overwrite the original bronze payload with only accepted rows; use that approach for `booking_changes`.
- Replace every missing date with today without provenance; use that approach for `booking_changes`.
Explanation
Correct Answer
A:Validate and cast amounts to a numeric type, quarantine invalid dates, and write typed clean records to a silver Delta table. This directly addresses string amounts can aggregate incorrectly and missing business dates are not safe grouping keys. The design should be accepted only after load zero, null and malformed amounts, then reconcile silver totals and quarantined rejects to bronze input; the related operational boundary is to preserve immutable raw events but enforce typed, validated silver records for consumption.
Incorrect Answers
B:Aggregate the raw string amount without conversion and skip null checks; use that approach for `booking_changes`. String comparison or implicit casts can corrupt arithmetic and let invalid dates pass. For `booking_changes`, this cannot remove the causal limitation: string amounts can aggregate incorrectly and missing business dates are not safe grouping keys.
C:Overwrite the original bronze payload with only accepted rows; use that approach for `booking_changes`. Destructive cleaning loses the raw evidence needed to replay and audit rejected records. For `booking_changes`, this cannot remove the causal limitation: string amounts can aggregate incorrectly and missing business dates are not safe grouping keys.
D:Replace every missing date with today without provenance; use that approach for `booking_changes`. Inventing transaction dates changes business facts and misstates historical revenue. For `booking_changes`, this cannot remove the causal limitation: string amounts can aggregate incorrectly and missing business dates are not safe grouping keys.
Question 193
At a vehicle fleet operator, bronze orders arrive with currency totals as strings and null order dates, producing incorrect daily financial summaries. The dataset `booking_changes` is in scope, and the release must preserve the original source evidence. A teammate proposes: "Aggregate the raw string amount without conversion and skip null checks." Which technical limitation is the decisive reason not to approve that specific proposal?
- Destructive cleaning loses the raw evidence needed to replay and audit rejected records. This would apply to another option for `booking_changes`.
- The dashboard cached the prior result; no DataFrame operation or underlying data requires correction.
- String comparison or implicit casts can corrupt arithmetic and let invalid dates pass. The proposal does not repair `booking_changes`.
- Inventing transaction dates changes business facts and misstates historical revenue. This would apply to an alternative change for `booking_changes`.
Explanation
Correct Answer
C:String comparison or implicit casts can corrupt arithmetic and let invalid dates pass. The proposal does not repair `booking_changes`. This identifies the known limitation of the exact proposed action. String comparison or implicit casts can corrupt arithmetic and let invalid dates pass. The underlying problem remains string amounts can aggregate incorrectly and missing business dates are not safe grouping keys; Validate and cast amounts to a numeric type, quarantine invalid dates, and write typed clean records to a silver Delta table instead targets that failure.
Incorrect Answers
A:Destructive cleaning loses the raw evidence needed to replay and audit rejected records. This would apply to another option for `booking_changes`. This limitation belongs to the different alternative "Overwrite the original bronze payload with only accepted rows". The stem calls for the specific failure of "Aggregate the raw string amount without conversion and skip null checks".
B:The dashboard cached the prior result; no DataFrame operation or underlying data requires correction. The case provides a concrete failing data or control path; a mere alternate theory does not address string amounts can aggregate incorrectly and missing business dates are not safe grouping keys.
D:Inventing transaction dates changes business facts and misstates historical revenue. This would apply to an alternative change for `booking_changes`. This failure applies to the separate proposal "Replace every missing date with today without provenance".
Question 194
At a vehicle fleet operator, bronze orders arrive with currency totals as strings and null order dates, producing incorrect daily financial summaries. The dataset `booking_changes` is in scope, and the release must preserve the original source evidence. What operational boundary should be documented for approval?
- Preserve immutable raw events but enforce typed, validated silver records for consumption
- Overwrite the original bronze payload with only accepted rows; monitor results only after launch of `booking_changes`.
- Replace every missing date with today without provenance; monitor results only after launch of `booking_changes`.
- Aggregate the raw string amount without conversion and skip null checks; monitor results only after launch of `booking_changes`.
Explanation
Correct Answer
A:Preserve immutable raw events but enforce typed, validated silver records for consumption. This explicitly bounds the compromise while still addressing string amounts can aggregate incorrectly and missing business dates are not safe grouping keys. Acceptance relies on load zero, null and malformed amounts, then reconcile silver totals and quarantined rejects to bronze input rather than simply declaring the change complete.
Incorrect Answers
B:Overwrite the original bronze payload with only accepted rows; monitor results only after launch of `booking_changes`. Destructive cleaning loses the raw evidence needed to replay and audit rejected records. Monitoring after deployment does not make this approach a safe bounded tradeoff for `booking_changes`.
C:Replace every missing date with today without provenance; monitor results only after launch of `booking_changes`. Inventing transaction dates changes business facts and misstates historical revenue. Monitoring after deployment does not make this approach a safe bounded tradeoff for `booking_changes`.
D:Aggregate the raw string amount without conversion and skip null checks; monitor results only after launch of `booking_changes`. String comparison or implicit casts can corrupt arithmetic and let invalid dates pass. Monitoring after deployment does not make this approach a safe bounded tradeoff for `booking_changes`.
Question 195
At a vehicle fleet operator, bronze orders arrive with currency totals as strings and null order dates, producing incorrect daily financial summaries. The dataset `booking_changes` is in scope, and the release must preserve the original source evidence. Which validation should be required in the release record?
- Run only a normal, unchanged `booking_changes` sample and review source field types.
- Review a platform-level availability report for `booking_changes` without testing whether string amounts can aggregate incorrectly and missing business dates are not safe grouping keys.
- Load zero, null and malformed amounts, then reconcile silver totals and quarantined rejects to bronze input
- Check that the intended configuration exists for `booking_changes` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
C:Load zero, null and malformed amounts, then reconcile silver totals and quarantined rejects to bronze input. This reproduces the scenario-dependent condition, verifies source field types, invalid-row sample, cast success count, and silver numeric reconciliation, and directly tests whether string amounts can aggregate incorrectly and missing business dates are not safe grouping keys is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `booking_changes` sample and review source field types. A normal sample does not challenge string amounts can aggregate incorrectly and missing business dates are not safe grouping keys.
B:Review a platform-level availability report for `booking_changes` without testing whether string amounts can aggregate incorrectly and missing business dates are not safe grouping keys. Aggregate availability does not establish the behavior of affected `booking_changes` records. It cannot replace the direct exercise: load zero, null and malformed amounts, then reconcile silver totals and quarantined rejects to bronze input.
D:Check that the intended configuration exists for `booking_changes` 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 string amounts can aggregate incorrectly and missing business dates are not safe grouping keys.
Question 196
At a tax accounting service, bronze shipping events use mixed timezone strings and inconsistent carrier codes, making downstream shipment durations misleading. The dataset `meter_readings` is in scope, and a finance audit requires reproducible aggregated figures. 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 timestamp offsets, normalized UTC values across affected and unaffected `R034-CASE-040` runs.
- Review completed run status and aggregate cluster health without record-level correlation
- Compare the saved configuration with the signed change ticket for `meter_readings` while omitting source and output records.
Explanation
Correct Answer
B:Correlate timestamp offsets, normalized UTC values across affected and unaffected `R034-CASE-040` runs.. By joining timestamp offsets, normalized UTC values, reference lookups, and rejected code counts across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: heterogeneous timestamps and code names cannot be compared or joined consistently without standardization. It also sets a measurable baseline for replay two events at the same instant with different offsets and verify equal canonical time plus mapped carrier identity.
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 heterogeneous timestamps and code names cannot be compared or joined consistently without standardization. The failing-path timestamp offsets, normalized UTC values, reference lookups, and rejected code counts 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 heterogeneous timestamps and code names cannot be compared or joined consistently without standardization. This check never observes the affected `meter_readings` records or their causal path.
D:Compare the saved configuration with the signed change ticket for `meter_readings` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit timestamp offsets, normalized UTC values, reference lookups, and rejected code counts, the direct means of distinguishing heterogeneous timestamps and code names cannot be compared or joined consistently without standardization.
Question 197
At a tax accounting service, bronze shipping events use mixed timezone strings and inconsistent carrier codes, making downstream shipment durations misleading. The dataset `meter_readings` is in scope, and a finance audit requires reproducible aggregated figures. Which implementation best resolves the stated defect without breaking the business constraint?
- Strip the timezone suffix and compare all timestamps as local wall-clock time; use that approach for `meter_readings`.
- Set all invalid carrier codes to the most common valid carrier; use that approach for `meter_readings`.
- Group the unnormalized carrier strings as distinct carriers; use that approach for `meter_readings`.
- Normalize timestamps to a documented timezone and map carrier codes through a validated reference table before silver writes
Explanation
Correct Answer
D:Normalize timestamps to a documented timezone and map carrier codes through a validated reference table before silver writes. This directly addresses heterogeneous timestamps and code names cannot be compared or joined consistently without standardization. The design should be accepted only after replay two events at the same instant with different offsets and verify equal canonical time plus mapped carrier identity; the related operational boundary is to permit auditable quarantine for unknown codes rather than introducing fabricated mappings.
Incorrect Answers
A:Strip the timezone suffix and compare all timestamps as local wall-clock time; use that approach for `meter_readings`. Removing offsets can reorder events across sites and distort elapsed time. For `meter_readings`, this cannot remove the causal limitation: heterogeneous timestamps and code names cannot be compared or joined consistently without standardization.
B:Set all invalid carrier codes to the most common valid carrier; use that approach for `meter_readings`. Guessing categorical values silently changes real shipment ownership. For `meter_readings`, this cannot remove the causal limitation: heterogeneous timestamps and code names cannot be compared or joined consistently without standardization.
C:Group the unnormalized carrier strings as distinct carriers; use that approach for `meter_readings`. Aliases create duplicate carrier categories instead of one standardized code. For `meter_readings`, this cannot remove the causal limitation: heterogeneous timestamps and code names cannot be compared or joined consistently without standardization.
Question 198
At a tax accounting service, bronze shipping events use mixed timezone strings and inconsistent carrier codes, making downstream shipment durations misleading. The dataset `meter_readings` is in scope, and a finance audit requires reproducible aggregated figures. A teammate proposes: "Set all invalid carrier codes to the most common valid carrier." Which technical limitation is the decisive reason not to approve that specific proposal?
- Removing offsets can reorder events across sites and distort elapsed time. This would apply to an alternative change for `meter_readings`.
- Guessing categorical values silently changes real shipment ownership. The proposal does not repair `meter_readings`.
- Aliases create duplicate carrier categories instead of one standardized code. This would apply to another option for `meter_readings`.
- The dashboard cached the prior result; no DataFrame operation or underlying data requires correction.
Explanation
Correct Answer
B:Guessing categorical values silently changes real shipment ownership. The proposal does not repair `meter_readings`. This identifies the known limitation of the exact proposed action. Guessing categorical values silently changes real shipment ownership. The underlying problem remains heterogeneous timestamps and code names cannot be compared or joined consistently without standardization; Normalize timestamps to a documented timezone and map carrier codes through a validated reference table before silver writes instead targets that failure.
Incorrect Answers
A:Removing offsets can reorder events across sites and distort elapsed time. This would apply to an alternative change for `meter_readings`. This failure applies to the separate proposal "Strip the timezone suffix and compare all timestamps as local wall-clock time".
C:Aliases create duplicate carrier categories instead of one standardized code. This would apply to another option for `meter_readings`. This limitation belongs to the different alternative "Group the unnormalized carrier strings as distinct carriers". The stem calls for the specific failure of "Set all invalid carrier codes to the most common valid carrier".
D:The dashboard cached the prior result; no DataFrame operation or underlying data requires correction. The case provides a concrete failing data or control path; a mere alternate theory does not address heterogeneous timestamps and code names cannot be compared or joined consistently without standardization.
Question 199
At a tax accounting service, bronze shipping events use mixed timezone strings and inconsistent carrier codes, making downstream shipment durations misleading. The dataset `meter_readings` is in scope, and a finance audit requires reproducible aggregated figures. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Permit auditable quarantine for unknown codes rather than introducing fabricated mappings
- Group the unnormalized carrier strings as distinct carriers
- Strip the timezone suffix and compare all timestamps as local wall-clock time
- Set all invalid carrier codes to the most common valid carrier; monitor results only after launch of `meter_readings`.
Explanation
Correct Answer
A:Permit auditable quarantine for unknown codes rather than introducing fabricated mappings. This explicitly bounds the compromise while still addressing heterogeneous timestamps and code names cannot be compared or joined consistently without standardization. Acceptance relies on replay two events at the same instant with different offsets and verify equal canonical time plus mapped carrier identity rather than simply declaring the change complete.
Incorrect Answers
B:Group the unnormalized carrier strings as distinct carriers. Aliases create duplicate carrier categories instead of one standardized code. Monitoring after deployment does not make this approach a safe bounded tradeoff for `meter_readings`.
C:Strip the timezone suffix and compare all timestamps as local wall-clock time. Removing offsets can reorder events across sites and distort elapsed time. Monitoring after deployment does not make this approach a safe bounded tradeoff for `meter_readings`.
D:Set all invalid carrier codes to the most common valid carrier; monitor results only after launch of `meter_readings`. Guessing categorical values silently changes real shipment ownership. Monitoring after deployment does not make this approach a safe bounded tradeoff for `meter_readings`.
Question 200
At a tax accounting service, bronze shipping events use mixed timezone strings and inconsistent carrier codes, making downstream shipment durations misleading. The dataset `meter_readings` is in scope, and a finance audit requires reproducible aggregated figures. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Review a platform-level availability report for `meter_readings` without testing whether heterogeneous timestamps and code names cannot be compared or joined consistently without standardization.
- Run only a normal, unchanged `meter_readings` sample and review timestamp offsets.
- Replay two events at the same instant with different offsets and verify equal canonical time plus mapped carrier identity
- Check that the intended configuration exists for `meter_readings` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
C:Replay two events at the same instant with different offsets and verify equal canonical time plus mapped carrier identity. This reproduces the scenario-dependent condition, verifies timestamp offsets, normalized UTC values, reference lookups, and rejected code counts, and directly tests whether heterogeneous timestamps and code names cannot be compared or joined consistently without standardization is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `meter_readings` without testing whether heterogeneous timestamps and code names cannot be compared or joined consistently without standardization. Aggregate availability does not establish the behavior of affected `meter_readings` records. It cannot replace the direct exercise: replay two events at the same instant with different offsets and verify equal canonical time plus mapped carrier identity.
B:Run only a normal, unchanged `meter_readings` sample and review timestamp offsets. A normal sample does not challenge heterogeneous timestamps and code names cannot be compared or joined consistently without standardization.
D:Check that the intended configuration exists for `meter_readings` 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 heterogeneous timestamps and code names cannot be compared or joined consistently without standardization.