Certified Data Engineer Associate Practice Test 17
Question 160
At a subscription media service, a supported CRM application offers a managed incremental connector, but the team plans to export full JSON snapshots hourly. The dataset `fraud_signals` 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 `fraud_signals` without testing whether custom snapshots add extraction maintenance and cannot reliably detect late deletions.
- Change, delete and re-create a source entity and verify incremental target convergence
- Check that the intended configuration exists for `fraud_signals` and that a healthy run succeeded, without inducing the earlier failure.
- Run only a normal, unchanged `fraud_signals` sample and review CRM connector support matrix.
Explanation
Correct Answer
B: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
A:Review a platform-level availability report for `fraud_signals` without testing whether custom snapshots add extraction maintenance and cannot reliably detect late deletions. Aggregate availability does not establish the behavior of affected `fraud_signals` records. It cannot replace the direct exercise: change, delete and re-create a source entity and verify incremental target convergence.
C:Check that the intended configuration exists for `fraud_signals` 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.
D:Run only a normal, unchanged `fraud_signals` sample and review CRM connector support matrix. A normal sample does not challenge custom snapshots add extraction maintenance and cannot reliably detect late deletions.
Question 161
At a regional banking group, a warehouse receives millions of newly arriving object-storage files each day and a SQL-only full scan has become slow. The dataset `claims_records` is in scope, and an interrupted delivery must be recoverable without data loss. What evidence should the engineer collect to establish the cause rather than a coincidental symptom?
- Examine only a normal successful run of `claims_records` and trend new-file arrival rate without recreating the fault.
- Compare the saved configuration with the signed change ticket for `claims_records` while omitting source and output records.
- Review aggregate cluster availability and job completion for `claims_records` without correlating the observed error path.
- Correlate new-file arrival rate, discovery latency across affected and unaffected `R034-CASE-033` runs.
Explanation
Correct Answer
D:Correlate new-file arrival rate, discovery latency across affected and unaffected `R034-CASE-033` runs.. By joining new-file arrival rate, discovery latency, listing overhead, and checkpoint progress across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: listing all historical objects for each run scales poorly under continual file arrival. It also sets a measurable baseline for double the arriving file count and verify sustained ingestion throughput without rereading historical files.
Incorrect Answers
A:Examine only a normal successful run of `claims_records` and trend new-file arrival rate without recreating the fault. A healthy-run trend can be useful, but it does not expose listing all historical objects for each run scales poorly under continual file arrival. The failing-path new-file arrival rate, discovery latency, listing overhead, and checkpoint progress has to be correlated before attributing cause.
B:Compare the saved configuration with the signed change ticket for `claims_records` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit new-file arrival rate, discovery latency, listing overhead, and checkpoint progress, the direct means of distinguishing listing all historical objects for each run scales poorly under continual file arrival.
C:Review aggregate cluster availability and job completion for `claims_records` without correlating the observed error path. A successful aggregate platform state can coexist with listing all historical objects for each run scales poorly under continual file arrival. This check never observes the affected `claims_records` records or their causal path.
Question 162
At a regional banking group, a warehouse receives millions of newly arriving object-storage files each day and a SQL-only full scan has become slow. The dataset `claims_records` is in scope, and an interrupted delivery must be recoverable without data loss. Which platform configuration or data-engineering change is most defensible?
- Favor a scalable Auto Loader or streaming-table ingestion path with file discovery and checkpointing rather than repeated whole-directory scans
- Collect files manually in a notebook driver directory before loading; use that approach for `claims_records`.
- Route the cloud files through an unrelated JDBC database first; use that approach for `claims_records`.
- Increase the frequency of complete directory scans without tracking seen files; use that approach for `claims_records`.
Explanation
Correct Answer
A:Favor a scalable Auto Loader or streaming-table ingestion path with file discovery and checkpointing rather than repeated whole-directory scans. This directly addresses listing all historical objects for each run scales poorly under continual file arrival. The design should be accepted only after double the arriving file count and verify sustained ingestion throughput without rereading historical files; the related operational boundary is to accept managed discovery and checkpoint state to meet large-scale freshness requirements.
Incorrect Answers
B:Collect files manually in a notebook driver directory before loading; use that approach for `claims_records`. Driver staging is not scalable or durable for millions of incoming objects. For `claims_records`, this cannot remove the causal limitation: listing all historical objects for each run scales poorly under continual file arrival.
C:Route the cloud files through an unrelated JDBC database first; use that approach for `claims_records`. An extra relational hop adds complexity without addressing file discovery scale. For `claims_records`, this cannot remove the causal limitation: listing all historical objects for each run scales poorly under continual file arrival.
D:Increase the frequency of complete directory scans without tracking seen files; use that approach for `claims_records`. More repeated scans increase object listing cost and duplicate ingestion risk. For `claims_records`, this cannot remove the causal limitation: listing all historical objects for each run scales poorly under continual file arrival.
Question 163
At a regional banking group, a warehouse receives millions of newly arriving object-storage files each day and a SQL-only full scan has become slow. The dataset `claims_records` is in scope, and an interrupted delivery must be recoverable without data loss. A teammate proposes: "Collect files manually in a notebook driver directory before loading." Which technical limitation is the decisive reason not to approve that specific proposal?
- Driver staging is not scalable or durable for millions of incoming objects. The proposal does not repair `claims_records`.
- An extra relational hop adds complexity without addressing file discovery scale. This would apply to another option for `claims_records`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
- More repeated scans increase object listing cost and duplicate ingestion risk. This would apply to an alternative change for `claims_records`.
Explanation
Correct Answer
A:Driver staging is not scalable or durable for millions of incoming objects. The proposal does not repair `claims_records`. This identifies the known limitation of the exact proposed action. Driver staging is not scalable or durable for millions of incoming objects. The underlying problem remains listing all historical objects for each run scales poorly under continual file arrival; Favor a scalable Auto Loader or streaming-table ingestion path with file discovery and checkpointing rather than repeated whole-directory scans instead targets that failure.
Incorrect Answers
B:An extra relational hop adds complexity without addressing file discovery scale. This would apply to another option for `claims_records`. This limitation belongs to the different alternative "Route the cloud files through an unrelated JDBC database first". The stem calls for the specific failure of "Collect files manually in a notebook driver directory before loading".
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 listing all historical objects for each run scales poorly under continual file arrival.
D:More repeated scans increase object listing cost and duplicate ingestion risk. This would apply to an alternative change for `claims_records`. This failure applies to the separate proposal "Increase the frequency of complete directory scans without tracking seen files".
Question 164
At a regional banking group, a warehouse receives millions of newly arriving object-storage files each day and a SQL-only full scan has become slow. The dataset `claims_records` is in scope, and an interrupted delivery must be recoverable without data loss. What risk-and-cost compromise should the owner accept instead of the proposed shortcuts?
- Collect files manually in a notebook driver directory before loading; monitor results only after launch of `claims_records`.
- Accept managed discovery and checkpoint state to meet large-scale freshness requirements
- Route the cloud files through an unrelated JDBC database first; monitor results only after launch of `claims_records`.
- Increase the frequency of complete directory scans without tracking seen files; monitor results only after launch of `claims_records`.
Explanation
Correct Answer
B:Accept managed discovery and checkpoint state to meet large-scale freshness requirements. This explicitly bounds the compromise while still addressing listing all historical objects for each run scales poorly under continual file arrival. Acceptance relies on double the arriving file count and verify sustained ingestion throughput without rereading historical files rather than simply declaring the change complete.
Incorrect Answers
A:Collect files manually in a notebook driver directory before loading; monitor results only after launch of `claims_records`. Driver staging is not scalable or durable for millions of incoming objects. Monitoring after deployment does not make this approach a safe bounded tradeoff for `claims_records`.
C:Route the cloud files through an unrelated JDBC database first; monitor results only after launch of `claims_records`. An extra relational hop adds complexity without addressing file discovery scale. Monitoring after deployment does not make this approach a safe bounded tradeoff for `claims_records`.
D:Increase the frequency of complete directory scans without tracking seen files; monitor results only after launch of `claims_records`. More repeated scans increase object listing cost and duplicate ingestion risk. Monitoring after deployment does not make this approach a safe bounded tradeoff for `claims_records`.
Question 165
At a regional banking group, a warehouse receives millions of newly arriving object-storage files each day and a SQL-only full scan has become slow. The dataset `claims_records` is in scope, and an interrupted delivery must be recoverable without data loss. Which direct test could falsify the proposed fix instead of only confirming deployment?
- Review a platform-level availability report for `claims_records` without testing whether listing all historical objects for each run scales poorly under continual file arrival.
- Double the arriving file count and verify sustained ingestion throughput without rereading historical files
- Run only a normal, unchanged `claims_records` sample and review new-file arrival rate.
- Check that the intended configuration exists for `claims_records` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
B:Double the arriving file count and verify sustained ingestion throughput without rereading historical files. This reproduces the scenario-dependent condition, verifies new-file arrival rate, discovery latency, listing overhead, and checkpoint progress, and directly tests whether listing all historical objects for each run scales poorly under continual file arrival is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `claims_records` without testing whether listing all historical objects for each run scales poorly under continual file arrival. Aggregate availability does not establish the behavior of affected `claims_records` records. It cannot replace the direct exercise: double the arriving file count and verify sustained ingestion throughput without rereading historical files.
C:Run only a normal, unchanged `claims_records` sample and review new-file arrival rate. A normal sample does not challenge listing all historical objects for each run scales poorly under continual file arrival.
D:Check that the intended configuration exists for `claims_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 listing all historical objects for each run scales poorly under continual file arrival.
Question 166
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. Which correlated observation is the strongest basis for the change decision?
- Correlate CRM connector support matrix, update/delete capture across affected and unaffected `R034-CASE-034` runs.
- Compare the current configuration and the signed change approval, without source-row evidence
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- Review aggregate cluster availability and job completion for `account_statements` without correlating the observed error path.
Explanation
Correct Answer
A:Correlate CRM connector support matrix, update/delete capture across affected and unaffected `R034-CASE-034` runs.. By joining CRM connector support matrix, update/delete capture, replication delay, and target governance across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: custom snapshots add extraction maintenance and cannot reliably detect late deletions. It also sets a measurable baseline for change, delete and re-create a source entity and verify incremental target convergence.
Incorrect Answers
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 CRM connector support matrix, update/delete capture, replication delay, and target governance, the direct means of distinguishing custom snapshots add extraction maintenance and cannot reliably detect late deletions.
C: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 custom snapshots add extraction maintenance and cannot reliably detect late deletions. The failing-path CRM connector support matrix, update/delete capture, replication delay, and target governance has to be correlated before attributing cause.
D:Review aggregate cluster availability and job completion for `account_statements` without correlating the observed error path. A successful aggregate platform state can coexist with custom snapshots add extraction maintenance and cannot reliably detect late deletions. This check never observes the affected `account_statements` records or their causal path.
Question 167
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 implementation should the engineer select for the failing workflow?
- Use SQL COPY INTO on the CRM REST URL directly; use that approach for `account_statements`.
- Use Auto Loader to monitor a folder that the CRM never exports into; use that approach for `account_statements`.
- Maintain hourly full snapshots without primary keys; use that approach for `account_statements`.
- Prefer a supported Lakeflow Connect managed connector for source-specific incremental updates and Unity Catalog delivery
Explanation
Correct Answer
D:Prefer a supported Lakeflow Connect managed connector for source-specific incremental updates and Unity Catalog delivery. This directly addresses custom snapshots add extraction maintenance and cannot reliably detect late deletions. The design should be accepted only after change, delete and re-create a source entity and verify incremental target convergence; the related operational boundary is to choose a managed source integration over custom polling while respecting connector limitations.
Incorrect Answers
A:Use SQL COPY INTO on the CRM REST URL directly; use that approach for `account_statements`. COPY INTO accepts supported file locations, not arbitrary CRM API requests. For `account_statements`, this cannot remove the causal limitation: custom snapshots add extraction maintenance and cannot reliably detect late deletions.
B:Use Auto Loader to monitor a folder that the CRM never exports into; use that approach for `account_statements`. A file-ingestion service cannot read data that is not delivered as files. For `account_statements`, this cannot remove the causal limitation: custom snapshots add extraction maintenance and cannot reliably detect late deletions.
C:Maintain hourly full snapshots without primary keys; use that approach for `account_statements`. Repeated full snapshots do not guarantee an accurate current-state target or deleted records. For `account_statements`, this cannot remove the causal limitation: custom snapshots add extraction maintenance and cannot reliably detect late deletions.
Question 168
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. A teammate proposes: "Use Auto Loader to monitor a folder that the CRM never exports into." 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.
- A file-ingestion service cannot read data that is not delivered as files. The proposal does not repair `account_statements`.
- Repeated full snapshots do not guarantee an accurate current-state target or deleted records. This would apply to another option for `account_statements`.
- COPY INTO accepts supported file locations, not arbitrary CRM API requests. This would apply to an alternative change for `account_statements`.
Explanation
Correct Answer
B:A file-ingestion service cannot read data that is not delivered as files. The proposal does not repair `account_statements`. This identifies the known limitation of the exact proposed action. A file-ingestion service cannot read data that is not delivered as files. The underlying problem remains custom snapshots add extraction maintenance and cannot reliably detect late deletions; Prefer a supported Lakeflow Connect managed connector for source-specific incremental updates and Unity Catalog delivery 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 custom snapshots add extraction maintenance and cannot reliably detect late deletions.
C:Repeated full snapshots do not guarantee an accurate current-state target or deleted records. This would apply to another option for `account_statements`. This limitation belongs to the different alternative "Maintain hourly full snapshots without primary keys". The stem calls for the specific failure of "Use Auto Loader to monitor a folder that the CRM never exports into".
D:COPY INTO accepts supported file locations, not arbitrary CRM API requests. This would apply to an alternative change for `account_statements`. This failure applies to the separate proposal "Use SQL COPY INTO on the CRM REST URL directly".
Question 169
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. Which decision preserves the stated data contract while keeping the change scope proportionate?
- Use Auto Loader to monitor a folder that the CRM never exports into
- Use SQL COPY INTO on the CRM REST URL directly
- Maintain hourly full snapshots without primary keys; monitor results only after launch of `account_statements`.
- Choose a managed source integration over custom polling while respecting connector limitations
Explanation
Correct Answer
D:Choose a managed source integration over custom polling while respecting connector limitations. This explicitly bounds the compromise while still addressing custom snapshots add extraction maintenance and cannot reliably detect late deletions. Acceptance relies on change, delete and re-create a source entity and verify incremental target convergence rather than simply declaring the change complete.
Incorrect Answers
A:Use Auto Loader to monitor a folder that the CRM never exports into. A file-ingestion service cannot read data that is not delivered as files. Monitoring after deployment does not make this approach a safe bounded tradeoff for `account_statements`.
B:Use SQL COPY INTO on the CRM REST URL directly. COPY INTO accepts supported file locations, not arbitrary CRM API requests. Monitoring after deployment does not make this approach a safe bounded tradeoff for `account_statements`.
C:Maintain hourly full snapshots without primary keys; monitor results only after launch of `account_statements`. Repeated full snapshots do not guarantee an accurate current-state target or deleted records. Monitoring after deployment does not make this approach a safe bounded tradeoff for `account_statements`.
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.