Certified Data Engineer Associate Practice Test 6
Question 50
At a municipal transit operator, a point-of-sale application continuously emits order events that downstream fraud monitors must see within minutes. The dataset `housing_applications` is in scope, and an interrupted delivery must be recoverable without data loss. What verification provides evidence of correct behavior under the original adverse condition?
- Check that the intended configuration exists for `housing_applications` and that a healthy run succeeded, without inducing the earlier failure.
- Force a restart during ingestion and confirm bounded end-to-end latency with no unaccounted source events
- Review a platform-level availability report for `housing_applications` without testing whether an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
- Run only a normal, unchanged `housing_applications` sample and review event arrival timestamps.
Explanation
Correct Answer
B:Force a restart during ingestion and confirm bounded end-to-end latency with no unaccounted source events. This reproduces the scenario-dependent condition, verifies event arrival timestamps, source offsets/files, checkpoint state, and bronze freshness lag, and directly tests whether an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Check that the intended configuration exists for `housing_applications` 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 end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
C:Review a platform-level availability report for `housing_applications` without testing whether an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling. Aggregate availability does not establish the behavior of affected `housing_applications` records. It cannot replace the direct exercise: force a restart during ingestion and confirm bounded end-to-end latency with no unaccounted source events.
D:Run only a normal, unchanged `housing_applications` sample and review event arrival timestamps. A normal sample does not challenge an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
Question 51
At a subscription media service, an archive of weekly invoice CSV files is appended once per week, but the team proposes an always-running stream. The dataset `cargo_visits` is in scope, and the target must retain every valid late-arriving event. Which investigation best tests the stated constraint with direct data?
- 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
- Correlate weekly file manifest, ingestion run watermark across affected and unaffected `R034-CASE-011` runs.
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
Explanation
Correct Answer
C:Correlate weekly file manifest, ingestion run watermark across affected and unaffected `R034-CASE-011` runs.. By joining weekly file manifest, ingestion run watermark, inserted row count, and duplicate invoice IDs across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: the source arrives in bounded weekly batches and has no continuous low-latency requirement. It also sets a measurable baseline for run the weekly ingestion twice with no new files and confirm the second run adds zero rows.
Incorrect Answers
A:Review completed run status and aggregate cluster health without record-level correlation. A successful aggregate platform state can coexist with the source arrives in bounded weekly batches and has no continuous low-latency requirement. This check never observes the affected `cargo_visits` records or their causal path.
B: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 weekly file manifest, ingestion run watermark, inserted row count, and duplicate invoice IDs, the direct means of distinguishing the source arrives in bounded weekly batches and has no continuous low-latency requirement.
D: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 source arrives in bounded weekly batches and has no continuous low-latency requirement. The failing-path weekly file manifest, ingestion run watermark, inserted row count, and duplicate invoice IDs has to be correlated before attributing cause.
Question 52
At a subscription media service, an archive of weekly invoice CSV files is appended once per week, but the team proposes an always-running stream. The dataset `cargo_visits` is in scope, and the target must retain every valid late-arriving event. Which option targets the actual technical dependency rather than an incidental symptom?
- Use repeatable scheduled incremental file ingestion to a governed Delta bronze table and record the processed-file boundary
- Overwrite the bronze table on every delivery; use that approach for `cargo_visits`.
- Keep a 24-hour streaming cluster polling an unchanged folder; use that approach for `cargo_visits`.
- Re-read and append the entire historical folder every week; use that approach for `cargo_visits`.
Explanation
Correct Answer
A:Use repeatable scheduled incremental file ingestion to a governed Delta bronze table and record the processed-file boundary. This directly addresses the source arrives in bounded weekly batches and has no continuous low-latency requirement. The design should be accepted only after run the weekly ingestion twice with no new files and confirm the second run adds zero rows; the related operational boundary is to favor scheduled execution and recorded incremental progress over permanent streaming infrastructure.
Incorrect Answers
B:Overwrite the bronze table on every delivery; use that approach for `cargo_visits`. Overwrites discard historical rows that incremental consumers still require. For `cargo_visits`, this cannot remove the causal limitation: the source arrives in bounded weekly batches and has no continuous low-latency requirement.
C:Keep a 24-hour streaming cluster polling an unchanged folder; use that approach for `cargo_visits`. Continuous polling consumes capacity without increasing the weekly delivery frequency. For `cargo_visits`, this cannot remove the causal limitation: the source arrives in bounded weekly batches and has no continuous low-latency requirement.
D:Re-read and append the entire historical folder every week; use that approach for `cargo_visits`. Unbounded reprocessing creates duplicate invoices unless separately deduplicated. For `cargo_visits`, this cannot remove the causal limitation: the source arrives in bounded weekly batches and has no continuous low-latency requirement.
Question 53
At a subscription media service, an archive of weekly invoice CSV files is appended once per week, but the team proposes an always-running stream. The dataset `cargo_visits` is in scope, and the target must retain every valid late-arriving event. A teammate proposes: "Re-read and append the entire historical folder every week." 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.
- Unbounded reprocessing creates duplicate invoices unless separately deduplicated. The proposal does not repair `cargo_visits`.
- Overwrites discard historical rows that incremental consumers still require. This would apply to an alternative change for `cargo_visits`.
- Continuous polling consumes capacity without increasing the weekly delivery frequency. This would apply to another option for `cargo_visits`.
Explanation
Correct Answer
B:Unbounded reprocessing creates duplicate invoices unless separately deduplicated. The proposal does not repair `cargo_visits`. This identifies the known limitation of the exact proposed action. Unbounded reprocessing creates duplicate invoices unless separately deduplicated. The underlying problem remains the source arrives in bounded weekly batches and has no continuous low-latency requirement; Use repeatable scheduled incremental file ingestion to a governed Delta bronze table and record the processed-file boundary 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 the source arrives in bounded weekly batches and has no continuous low-latency requirement.
C:Overwrites discard historical rows that incremental consumers still require. This would apply to an alternative change for `cargo_visits`. This failure applies to the separate proposal "Overwrite the bronze table on every delivery".
D:Continuous polling consumes capacity without increasing the weekly delivery frequency. This would apply to another option for `cargo_visits`. This limitation belongs to the different alternative "Keep a 24-hour streaming cluster polling an unchanged folder". The stem calls for the specific failure of "Re-read and append the entire historical folder every week".
Question 54
At a subscription media service, an archive of weekly invoice CSV files is appended once per week, but the team proposes an always-running stream. The dataset `cargo_visits` is in scope, and the target must retain every valid late-arriving event. What operational boundary should be documented for approval?
- Overwrite the bronze table on every delivery
- Keep a 24-hour streaming cluster polling an unchanged folder
- Favor scheduled execution and recorded incremental progress over permanent streaming infrastructure
- Re-read and append the entire historical folder every week
Explanation
Correct Answer
C:Favor scheduled execution and recorded incremental progress over permanent streaming infrastructure. This explicitly bounds the compromise while still addressing the source arrives in bounded weekly batches and has no continuous low-latency requirement. Acceptance relies on run the weekly ingestion twice with no new files and confirm the second run adds zero rows rather than simply declaring the change complete.
Incorrect Answers
A:Overwrite the bronze table on every delivery. Overwrites discard historical rows that incremental consumers still require. Monitoring after deployment does not make this approach a safe bounded tradeoff for `cargo_visits`.
B:Keep a 24-hour streaming cluster polling an unchanged folder. Continuous polling consumes capacity without increasing the weekly delivery frequency. Monitoring after deployment does not make this approach a safe bounded tradeoff for `cargo_visits`.
D:Re-read and append the entire historical folder every week. Unbounded reprocessing creates duplicate invoices unless separately deduplicated. Monitoring after deployment does not make this approach a safe bounded tradeoff for `cargo_visits`.
Question 55
At a subscription media service, an archive of weekly invoice CSV files is appended once per week, but the team proposes an always-running stream. The dataset `cargo_visits` is in scope, and the target must retain every valid late-arriving event. Which validation should be required in the release record?
- Run only a normal, unchanged `cargo_visits` sample and review weekly file manifest.
- Run the weekly ingestion twice with no new files and confirm the second run adds zero rows
- Review a platform-level availability report for `cargo_visits` without testing whether the source arrives in bounded weekly batches and has no continuous low-latency requirement.
- Check that the intended configuration exists for `cargo_visits` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
B:Run the weekly ingestion twice with no new files and confirm the second run adds zero rows. This reproduces the scenario-dependent condition, verifies weekly file manifest, ingestion run watermark, inserted row count, and duplicate invoice IDs, and directly tests whether the source arrives in bounded weekly batches and has no continuous low-latency requirement is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `cargo_visits` sample and review weekly file manifest. A normal sample does not challenge the source arrives in bounded weekly batches and has no continuous low-latency requirement.
C:Review a platform-level availability report for `cargo_visits` without testing whether the source arrives in bounded weekly batches and has no continuous low-latency requirement. Aggregate availability does not establish the behavior of affected `cargo_visits` records. It cannot replace the direct exercise: run the weekly ingestion twice with no new files and confirm the second run adds zero rows.
D:Check that the intended configuration exists for `cargo_visits` 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 source arrives in bounded weekly batches and has no continuous low-latency requirement.
Question 56
At a regional banking group, a point-of-sale application continuously emits order events that downstream fraud monitors must see within minutes. The dataset `population_records` is in scope, and an interrupted delivery must be recoverable without data loss. Before choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Review aggregate cluster availability and job completion for `population_records` without correlating the observed error path.
- Correlate event arrival timestamps, source offsets/files across affected and unaffected `R034-CASE-012` runs.
- Compare the saved configuration with the signed change ticket for `population_records` while omitting source and output records.
- Examine only a normal successful run of `population_records` and trend event arrival timestamps without recreating the fault.
Explanation
Correct Answer
B:Correlate event arrival timestamps, source offsets/files across affected and unaffected `R034-CASE-012` runs.. By joining event arrival timestamps, source offsets/files, checkpoint state, and bronze freshness lag across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling. It also sets a measurable baseline for force a restart during ingestion and confirm bounded end-to-end latency with no unaccounted source events.
Incorrect Answers
A:Review aggregate cluster availability and job completion for `population_records` without correlating the observed error path. A successful aggregate platform state can coexist with an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling. This check never observes the affected `population_records` records or their causal path.
C:Compare the saved configuration with the signed change ticket for `population_records` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit event arrival timestamps, source offsets/files, checkpoint state, and bronze freshness lag, the direct means of distinguishing an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
D:Examine only a normal successful run of `population_records` and trend event arrival timestamps without recreating the fault. A healthy-run trend can be useful, but it does not expose an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling. The failing-path event arrival timestamps, source offsets/files, checkpoint state, and bronze freshness lag has to be correlated before attributing cause.
Question 57
At a regional banking group, a point-of-sale application continuously emits order events that downstream fraud monitors must see within minutes. The dataset `population_records` is in scope, and an interrupted delivery must be recoverable without data loss. Which implementation best resolves the stated defect without breaking the business constraint?
- Disable stream checkpoint persistence after a clean run; use that approach for `population_records`.
- Use a supported incremental streaming ingestion path with durable checkpointing and a governed Delta landing table
- Write directly to an ungoverned notebook cache; use that approach for `population_records`.
- Schedule one full source scan after business closes; use that approach for `population_records`.
Explanation
Correct Answer
B:Use a supported incremental streaming ingestion path with durable checkpointing and a governed Delta landing table. This directly addresses an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling. The design should be accepted only after force a restart during ingestion and confirm bounded end-to-end latency with no unaccounted source events; the related operational boundary is to pay for incremental processing while maintaining durable recovery and governance.
Incorrect Answers
A:Disable stream checkpoint persistence after a clean run; use that approach for `population_records`. Without durable progress, restarts can replay events or lose processing state. For `population_records`, this cannot remove the causal limitation: an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
C:Write directly to an ungoverned notebook cache; use that approach for `population_records`. Ephemeral cache data loses durable progress and access controls. For `population_records`, this cannot remove the causal limitation: an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
D:Schedule one full source scan after business closes; use that approach for `population_records`. An end-of-day scan misses the required near-real-time freshness objective. For `population_records`, this cannot remove the causal limitation: an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
Question 58
At a regional banking group, a point-of-sale application continuously emits order events that downstream fraud monitors must see within minutes. The dataset `population_records` is in scope, and an interrupted delivery must be recoverable without data loss. A teammate proposes: "Schedule one full source scan after business closes." Which technical limitation is the decisive reason not to approve that specific proposal?
- Without durable progress, restarts can replay events or lose processing state. This would apply to another option for `population_records`.
- An end-of-day scan misses the required near-real-time freshness objective. The proposal does not repair `population_records`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
- Ephemeral cache data loses durable progress and access controls. This would apply to an alternative change for `population_records`.
Explanation
Correct Answer
B:An end-of-day scan misses the required near-real-time freshness objective. The proposal does not repair `population_records`. This identifies the known limitation of the exact proposed action. An end-of-day scan misses the required near-real-time freshness objective. The underlying problem remains an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling; Use a supported incremental streaming ingestion path with durable checkpointing and a governed Delta landing table instead targets that failure.
Incorrect Answers
A:Without durable progress, restarts can replay events or lose processing state. This would apply to another option for `population_records`. This limitation belongs to the different alternative "Disable stream checkpoint persistence after a clean run". The stem calls for the specific failure of "Schedule one full source scan after business closes".
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 end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
D:Ephemeral cache data loses durable progress and access controls. This would apply to an alternative change for `population_records`. This failure applies to the separate proposal "Write directly to an ungoverned notebook cache".
Question 59
At a regional banking group, a point-of-sale application continuously emits order events that downstream fraud monitors must see within minutes. The dataset `population_records` is in scope, and an interrupted delivery must be recoverable without data loss. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Pay for incremental processing while maintaining durable recovery and governance
- Write directly to an ungoverned notebook cache; monitor results only after launch of `population_records`.
- Disable stream checkpoint persistence after a clean run; monitor results only after launch of `population_records`.
- Schedule one full source scan after business closes; monitor results only after launch of `population_records`.
Explanation
Correct Answer
A:Pay for incremental processing while maintaining durable recovery and governance. This explicitly bounds the compromise while still addressing an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling. Acceptance relies on force a restart during ingestion and confirm bounded end-to-end latency with no unaccounted source events rather than simply declaring the change complete.
Incorrect Answers
B:Write directly to an ungoverned notebook cache; monitor results only after launch of `population_records`. Ephemeral cache data loses durable progress and access controls. Monitoring after deployment does not make this approach a safe bounded tradeoff for `population_records`.
C:Disable stream checkpoint persistence after a clean run; monitor results only after launch of `population_records`. Without durable progress, restarts can replay events or lose processing state. Monitoring after deployment does not make this approach a safe bounded tradeoff for `population_records`.
D:Schedule one full source scan after business closes; monitor results only after launch of `population_records`. An end-of-day scan misses the required near-real-time freshness objective. Monitoring after deployment does not make this approach a safe bounded tradeoff for `population_records`.
Question 60
At a regional banking group, a point-of-sale application continuously emits order events that downstream fraud monitors must see within minutes. The dataset `population_records` is in scope, and an interrupted delivery must be recoverable without data loss. Before release, which acceptance test would actually demonstrate that the root problem is controlled?
- Force a restart during ingestion and confirm bounded end-to-end latency with no unaccounted source events
- Review a platform-level availability report for `population_records` without testing whether an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
- Check that the intended configuration exists for `population_records` and that a healthy run succeeded, without inducing the earlier failure.
- Run only a normal, unchanged `population_records` sample and review event arrival timestamps.
Explanation
Correct Answer
A:Force a restart during ingestion and confirm bounded end-to-end latency with no unaccounted source events. This reproduces the scenario-dependent condition, verifies event arrival timestamps, source offsets/files, checkpoint state, and bronze freshness lag, and directly tests whether an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling is resolved. Observed results, not intent, determine approval.
Incorrect Answers
B:Review a platform-level availability report for `population_records` without testing whether an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling. Aggregate availability does not establish the behavior of affected `population_records` records. It cannot replace the direct exercise: force a restart during ingestion and confirm bounded end-to-end latency with no unaccounted source events.
C:Check that the intended configuration exists for `population_records` 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 end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.
D:Run only a normal, unchanged `population_records` sample and review event arrival timestamps. A normal sample does not challenge an end-of-day whole-directory batch cannot satisfy the event-latency bound or robust replay handling.