Certified Data Engineer Associate Practice Test 34
Question 330
At a census statistics agency, a silver customer dimension occasionally contains null customer IDs that should never reach billing gold tables. The dataset `payment_decisions` is in scope, and downstream dashboards cannot accept fabricated values. What verification provides evidence of correct behavior under the original adverse condition?
- Run only a normal, unchanged `payment_decisions` sample and review null key rate.
- Review a platform-level availability report for `payment_decisions` without testing whether a null business key breaks reliable joins and can create untraceable billing records.
- Check that the intended configuration exists for `payment_decisions` and that a healthy run succeeded, without inducing the earlier failure.
- Inject a null customer ID and verify the exception record is visible but absent from trusted gold
Explanation
Correct Answer
D:Inject a null customer ID and verify the exception record is visible but absent from trusted gold. This reproduces the scenario-dependent condition, verifies null key rate, rejected-record sample, silver-to-gold counts, and quality rule events, and directly tests whether a null business key breaks reliable joins and can create untraceable billing records is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `payment_decisions` sample and review null key rate. A normal sample does not challenge a null business key breaks reliable joins and can create untraceable billing records.
B:Review a platform-level availability report for `payment_decisions` without testing whether a null business key breaks reliable joins and can create untraceable billing records. Aggregate availability does not establish the behavior of affected `payment_decisions` records. It cannot replace the direct exercise: inject a null customer ID and verify the exception record is visible but absent from trusted gold.
C:Check that the intended configuration exists for `payment_decisions` 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 null business key breaks reliable joins and can create untraceable billing records.
Question 331
At a logistics carrier, a gold revenue table occasionally drifts from verified silver totals after a new transformation deployment. The dataset `course_enrollments` is in scope, and raw records must remain available for replay. 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 `course_enrollments` while omitting source and output records.
- Correlate source and gold aggregate totals, distinct business keys across affected and unaffected `R034-CASE-067` runs.
Explanation
Correct Answer
D:Correlate source and gold aggregate totals, distinct business keys across affected and unaffected `R034-CASE-067` runs.. By joining source and gold aggregate totals, distinct business keys, change timestamp, and quality assertion results across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: a successful job status alone cannot establish transformation correctness when totals have diverged. It also sets a measurable baseline for inject a duplicated invoice into silver and confirm the publication gate catches the changed revenue total.
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 a successful job status alone cannot establish transformation correctness when totals have diverged. The failing-path source and gold aggregate totals, distinct business keys, change timestamp, and quality assertion results 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 a successful job status alone cannot establish transformation correctness when totals have diverged. This check never observes the affected `course_enrollments` records or their causal path.
C:Compare the saved configuration with the signed change ticket for `course_enrollments` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit source and gold aggregate totals, distinct business keys, change timestamp, and quality assertion results, the direct means of distinguishing a successful job status alone cannot establish transformation correctness when totals have diverged.
Question 332
At a logistics carrier, a gold revenue table occasionally drifts from verified silver totals after a new transformation deployment. The dataset `course_enrollments` is in scope, and raw records must remain available for replay. Which option targets the actual technical dependency rather than an incidental symptom?
- Approve gold because the notebook task exited successfully; use that approach for `course_enrollments`.
- Round all totals aggressively until the difference disappears; use that approach for `course_enrollments`.
- Run reconciliations on key aggregates and row-level invariants, fail the affected publication on material mismatch
- Delete the previous gold snapshot before computing comparison metrics; use that approach for `course_enrollments`.
Explanation
Correct Answer
C:Run reconciliations on key aggregates and row-level invariants, fail the affected publication on material mismatch. This directly addresses a successful job status alone cannot establish transformation correctness when totals have diverged. The design should be accepted only after inject a duplicated invoice into silver and confirm the publication gate catches the changed revenue total; the related operational boundary is to block material mismatches while retaining diagnostic data to fix a broken transformation.
Incorrect Answers
A:Approve gold because the notebook task exited successfully; use that approach for `course_enrollments`. Successful execution does not prove that aggregate business measures reconcile. For `course_enrollments`, this cannot remove the causal limitation: a successful job status alone cannot establish transformation correctness when totals have diverged.
B:Round all totals aggressively until the difference disappears; use that approach for `course_enrollments`. Rounding can mask a genuine allocation or duplication defect. For `course_enrollments`, this cannot remove the causal limitation: a successful job status alone cannot establish transformation correctness when totals have diverged.
D:Delete the previous gold snapshot before computing comparison metrics; use that approach for `course_enrollments`. Removing a baseline makes it harder to identify and reverse the regression. For `course_enrollments`, this cannot remove the causal limitation: a successful job status alone cannot establish transformation correctness when totals have diverged.
Question 333
At a logistics carrier, a gold revenue table occasionally drifts from verified silver totals after a new transformation deployment. The dataset `course_enrollments` is in scope, and raw records must remain available for replay. A teammate proposes: "Delete the previous gold snapshot before computing comparison metrics." Which technical limitation is the decisive reason not to approve that specific proposal?
- The dashboard cached the prior result; no DataFrame operation or underlying data requires correction.
- Removing a baseline makes it harder to identify and reverse the regression. The proposal does not repair `course_enrollments`.
- Rounding can mask a genuine allocation or duplication defect. This would apply to another option for `course_enrollments`.
- Successful execution does not prove that aggregate business measures reconcile. This would apply to an alternative change for `course_enrollments`.
Explanation
Correct Answer
B:Removing a baseline makes it harder to identify and reverse the regression. The proposal does not repair `course_enrollments`. This identifies the known limitation of the exact proposed action. Removing a baseline makes it harder to identify and reverse the regression. The underlying problem remains a successful job status alone cannot establish transformation correctness when totals have diverged; Run reconciliations on key aggregates and row-level invariants, fail the affected publication on material mismatch instead targets that failure.
Incorrect Answers
A: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 a successful job status alone cannot establish transformation correctness when totals have diverged.
C:Rounding can mask a genuine allocation or duplication defect. This would apply to another option for `course_enrollments`. This limitation belongs to the different alternative "Round all totals aggressively until the difference disappears". The stem calls for the specific failure of "Delete the previous gold snapshot before computing comparison metrics".
D:Successful execution does not prove that aggregate business measures reconcile. This would apply to an alternative change for `course_enrollments`. This failure applies to the separate proposal "Approve gold because the notebook task exited successfully".
Question 334
At a logistics carrier, a gold revenue table occasionally drifts from verified silver totals after a new transformation deployment. The dataset `course_enrollments` is in scope, and raw records must remain available for replay. What operational boundary should be documented for approval?
- Round all totals aggressively until the difference disappears
- Approve gold because the notebook task exited successfully
- Delete the previous gold snapshot before computing comparison metrics; monitor results only after launch of `course_enrollments`.
- Block material mismatches while retaining diagnostic data to fix a broken transformation
Explanation
Correct Answer
D:Block material mismatches while retaining diagnostic data to fix a broken transformation. This explicitly bounds the compromise while still addressing a successful job status alone cannot establish transformation correctness when totals have diverged. Acceptance relies on inject a duplicated invoice into silver and confirm the publication gate catches the changed revenue total rather than simply declaring the change complete.
Incorrect Answers
A:Round all totals aggressively until the difference disappears. Rounding can mask a genuine allocation or duplication defect. Monitoring after deployment does not make this approach a safe bounded tradeoff for `course_enrollments`.
B:Approve gold because the notebook task exited successfully. Successful execution does not prove that aggregate business measures reconcile. Monitoring after deployment does not make this approach a safe bounded tradeoff for `course_enrollments`.
C:Delete the previous gold snapshot before computing comparison metrics; monitor results only after launch of `course_enrollments`. Removing a baseline makes it harder to identify and reverse the regression. Monitoring after deployment does not make this approach a safe bounded tradeoff for `course_enrollments`.
Question 335
At a logistics carrier, a gold revenue table occasionally drifts from verified silver totals after a new transformation deployment. The dataset `course_enrollments` is in scope, and raw records must remain available for replay. Which validation should be required in the release record?
- Run only a normal, unchanged `course_enrollments` sample and review source and gold aggregate totals.
- Inject a duplicated invoice into silver and confirm the publication gate catches the changed revenue total
- Review a platform-level availability report for `course_enrollments` without testing whether a successful job status alone cannot establish transformation correctness when totals have diverged.
- Check that the intended configuration exists for `course_enrollments` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
B:Inject a duplicated invoice into silver and confirm the publication gate catches the changed revenue total. This reproduces the scenario-dependent condition, verifies source and gold aggregate totals, distinct business keys, change timestamp, and quality assertion results, and directly tests whether a successful job status alone cannot establish transformation correctness when totals have diverged is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `course_enrollments` sample and review source and gold aggregate totals. A normal sample does not challenge a successful job status alone cannot establish transformation correctness when totals have diverged.
C:Review a platform-level availability report for `course_enrollments` without testing whether a successful job status alone cannot establish transformation correctness when totals have diverged. Aggregate availability does not establish the behavior of affected `course_enrollments` records. It cannot replace the direct exercise: inject a duplicated invoice into silver and confirm the publication gate catches the changed revenue total.
D:Check that the intended configuration exists for `course_enrollments` 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 successful job status alone cannot establish transformation correctness when totals have diverged.
Question 336
At a food delivery company, a silver customer dimension occasionally contains null customer IDs that should never reach billing gold tables. The dataset `vehicle_arrivals` is in scope, and downstream dashboards cannot accept fabricated values. 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 null key rate, rejected-record sample across affected and unaffected `R034-CASE-068` 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 null key rate, rejected-record sample across affected and unaffected `R034-CASE-068` runs.. By joining null key rate, rejected-record sample, silver-to-gold counts, and quality rule events across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: a null business key breaks reliable joins and can create untraceable billing records. It also sets a measurable baseline for inject a null customer ID and verify the exception record is visible but absent from trusted gold.
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 a null business key breaks reliable joins and can create untraceable billing records. The failing-path null key rate, rejected-record sample, silver-to-gold counts, and quality rule events has to be correlated before attributing cause.
C:Review completed run status and aggregate cluster health without record-level correlation. A successful aggregate platform state can coexist with a null business key breaks reliable joins and can create untraceable billing records. This check never observes the affected `vehicle_arrivals` 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 null key rate, rejected-record sample, silver-to-gold counts, and quality rule events, the direct means of distinguishing a null business key breaks reliable joins and can create untraceable billing records.
Question 337
At a food delivery company, a silver customer dimension occasionally contains null customer IDs that should never reach billing gold tables. The dataset `vehicle_arrivals` is in scope, and downstream dashboards cannot accept fabricated values. Which implementation best resolves the stated defect without breaking the business constraint?
- Allow the rows into gold and hope a later dashboard filter hides them; use that approach for `vehicle_arrivals`.
- Replace missing customer IDs with a common literal value; use that approach for `vehicle_arrivals`.
- Disable all quality checks when ingestion latency increases; use that approach for `vehicle_arrivals`.
- Enforce a non-null key quality expectation or validation rule and route rejected records for investigation before publishing gold
Explanation
Correct Answer
D:Enforce a non-null key quality expectation or validation rule and route rejected records for investigation before publishing gold. This directly addresses a null business key breaks reliable joins and can create untraceable billing records. The design should be accepted only after inject a null customer ID and verify the exception record is visible but absent from trusted gold; the related operational boundary is to keep a visible quarantine route instead of silently replacing missing identifiers.
Incorrect Answers
A:Allow the rows into gold and hope a later dashboard filter hides them; use that approach for `vehicle_arrivals`. A presentation filter does not protect downstream consumers or data contracts. For `vehicle_arrivals`, this cannot remove the causal limitation: a null business key breaks reliable joins and can create untraceable billing records.
B:Replace missing customer IDs with a common literal value; use that approach for `vehicle_arrivals`. A shared fabricated key merges unrelated customers into one identity. For `vehicle_arrivals`, this cannot remove the causal limitation: a null business key breaks reliable joins and can create untraceable billing records.
C:Disable all quality checks when ingestion latency increases; use that approach for `vehicle_arrivals`. Removing checks trades temporary performance for silent data corruption. For `vehicle_arrivals`, this cannot remove the causal limitation: a null business key breaks reliable joins and can create untraceable billing records.
Question 338
At a food delivery company, a silver customer dimension occasionally contains null customer IDs that should never reach billing gold tables. The dataset `vehicle_arrivals` is in scope, and downstream dashboards cannot accept fabricated values. A teammate proposes: "Replace missing customer IDs with a common literal value." Which technical limitation is the decisive reason not to approve that specific proposal?
- The dashboard cached the prior result; no DataFrame operation or underlying data requires correction.
- A presentation filter does not protect downstream consumers or data contracts. This would apply to another option for `vehicle_arrivals`.
- A shared fabricated key merges unrelated customers into one identity. The proposal does not repair `vehicle_arrivals`.
- Removing checks trades temporary performance for silent data corruption. This would apply to an alternative change for `vehicle_arrivals`.
Explanation
Correct Answer
C:A shared fabricated key merges unrelated customers into one identity. The proposal does not repair `vehicle_arrivals`. This identifies the known limitation of the exact proposed action. A shared fabricated key merges unrelated customers into one identity. The underlying problem remains a null business key breaks reliable joins and can create untraceable billing records; Enforce a non-null key quality expectation or validation rule and route rejected records for investigation before publishing gold instead targets that failure.
Incorrect Answers
A: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 a null business key breaks reliable joins and can create untraceable billing records.
B:A presentation filter does not protect downstream consumers or data contracts. This would apply to another option for `vehicle_arrivals`. This limitation belongs to the different alternative "Allow the rows into gold and hope a later dashboard filter hides them". The stem calls for the specific failure of "Replace missing customer IDs with a common literal value".
D:Removing checks trades temporary performance for silent data corruption. This would apply to an alternative change for `vehicle_arrivals`. This failure applies to the separate proposal "Disable all quality checks when ingestion latency increases".
Question 339
At a food delivery company, a silver customer dimension occasionally contains null customer IDs that should never reach billing gold tables. The dataset `vehicle_arrivals` is in scope, and downstream dashboards cannot accept fabricated values. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Disable all quality checks when ingestion latency increases
- Keep a visible quarantine route instead of silently replacing missing identifiers
- Allow the rows into gold and hope a later dashboard filter hides them
- Replace missing customer IDs with a common literal value
Explanation
Correct Answer
B:Keep a visible quarantine route instead of silently replacing missing identifiers. This explicitly bounds the compromise while still addressing a null business key breaks reliable joins and can create untraceable billing records. Acceptance relies on inject a null customer ID and verify the exception record is visible but absent from trusted gold rather than simply declaring the change complete.
Incorrect Answers
A:Disable all quality checks when ingestion latency increases. Removing checks trades temporary performance for silent data corruption. Monitoring after deployment does not make this approach a safe bounded tradeoff for `vehicle_arrivals`.
C:Allow the rows into gold and hope a later dashboard filter hides them. A presentation filter does not protect downstream consumers or data contracts. Monitoring after deployment does not make this approach a safe bounded tradeoff for `vehicle_arrivals`.
D:Replace missing customer IDs with a common literal value. A shared fabricated key merges unrelated customers into one identity. Monitoring after deployment does not make this approach a safe bounded tradeoff for `vehicle_arrivals`.
Question 340
At a food delivery company, a silver customer dimension occasionally contains null customer IDs that should never reach billing gold tables. The dataset `vehicle_arrivals` is in scope, and downstream dashboards cannot accept fabricated values. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Inject a null customer ID and verify the exception record is visible but absent from trusted gold
- Run only a normal, unchanged `vehicle_arrivals` sample and review null key rate.
- Review a platform-level availability report for `vehicle_arrivals` without testing whether a null business key breaks reliable joins and can create untraceable billing records.
- Check that the intended configuration exists for `vehicle_arrivals` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
A:Inject a null customer ID and verify the exception record is visible but absent from trusted gold. This reproduces the scenario-dependent condition, verifies null key rate, rejected-record sample, silver-to-gold counts, and quality rule events, and directly tests whether a null business key breaks reliable joins and can create untraceable billing records is resolved. Observed results, not intent, determine approval.
Incorrect Answers
B:Run only a normal, unchanged `vehicle_arrivals` sample and review null key rate. A normal sample does not challenge a null business key breaks reliable joins and can create untraceable billing records.
C:Review a platform-level availability report for `vehicle_arrivals` without testing whether a null business key breaks reliable joins and can create untraceable billing records. Aggregate availability does not establish the behavior of affected `vehicle_arrivals` records. It cannot replace the direct exercise: inject a null customer ID and verify the exception record is visible but absent from trusted gold.
D:Check that the intended configuration exists for `vehicle_arrivals` 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 null business key breaks reliable joins and can create untraceable billing records.