Certified Data Engineer Associate Practice Test 14
Question 130
At a subscription media service, a managed connector stopped after a credential rotation while the source continues accepting new orders. The dataset `shipment_status` 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 `shipment_status` and that a healthy run succeeded, without inducing the earlier failure.
- Review a platform-level availability report for `shipment_status` without testing whether a source connector cannot authenticate with rotated credentials even though source data is healthy.
- Run only a normal, unchanged `shipment_status` sample and review connector authentication errors.
- Rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes
Explanation
Correct Answer
D:Rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes. This reproduces the scenario-dependent condition, verifies connector authentication errors, secret rotation time, source permissions, and last processed update, and directly tests whether a source connector cannot authenticate with rotated credentials even though source data is healthy is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Check that the intended configuration exists for `shipment_status` and that a healthy run succeeded, without inducing the earlier failure. Installed configuration and a healthy run are insufficient to prove the failure mode is gone. The original issue was a source connector cannot authenticate with rotated credentials even though source data is healthy.
B:Review a platform-level availability report for `shipment_status` without testing whether a source connector cannot authenticate with rotated credentials even though source data is healthy. Aggregate availability does not establish the behavior of affected `shipment_status` records. It cannot replace the direct exercise: rotate the test secret, repair access, resume ingestion, and reconcile the previously missed source changes.
C:Run only a normal, unchanged `shipment_status` sample and review connector authentication errors. A normal sample does not challenge a source connector cannot authenticate with rotated credentials even though source data is healthy.
Question 131
At a regional insurer, a REST customer API imposes strict page limits and throttles large pulls, leaving the daily bronze dataset incomplete. The dataset `payment_decisions` is in scope, and an interrupted delivery must be recoverable without data loss. Which investigation best tests the stated constraint with direct data?
- Examine only a normal successful run of `payment_decisions` and trend pagination tokens without recreating the fault.
- Review aggregate cluster availability and job completion for `payment_decisions` without correlating the observed error path.
- Correlate pagination tokens, 429 responses across affected and unaffected `R034-CASE-027` runs.
- Compare the saved configuration with the signed change ticket for `payment_decisions` while omitting source and output records.
Explanation
Correct Answer
C:Correlate pagination tokens, 429 responses across affected and unaffected `R034-CASE-027` runs.. By joining pagination tokens, 429 responses, source total, and destination row counts by page across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: a one-page REST response does not represent the complete source data, and throttling requires controlled retry. It also sets a measurable baseline for simulate a 429 midway through a multi-page pull and verify no page is skipped or loaded twice.
Incorrect Answers
A:Examine only a normal successful run of `payment_decisions` and trend pagination tokens without recreating the fault. A healthy-run trend can be useful, but it does not expose a one-page REST response does not represent the complete source data, and throttling requires controlled retry. The failing-path pagination tokens, 429 responses, source total, and destination row counts by page has to be correlated before attributing cause.
B:Review aggregate cluster availability and job completion for `payment_decisions` without correlating the observed error path. A successful aggregate platform state can coexist with a one-page REST response does not represent the complete source data, and throttling requires controlled retry. This check never observes the affected `payment_decisions` records or their causal path.
D:Compare the saved configuration with the signed change ticket for `payment_decisions` while omitting source and output records. A desired configuration and approval ticket are not runtime proof. In this case they omit pagination tokens, 429 responses, source total, and destination row counts by page, the direct means of distinguishing a one-page REST response does not represent the complete source data, and throttling requires controlled retry.
Question 132
At a regional insurer, a REST customer API imposes strict page limits and throttles large pulls, leaving the daily bronze dataset incomplete. The dataset `payment_decisions` is in scope, and an interrupted delivery must be recoverable without data loss. Which option targets the actual technical dependency rather than an incidental symptom?
- Run the exact same first-page request repeatedly without a cursor; use that approach for `payment_decisions`.
- Ignore HTTP 429 responses and mark the job successful; use that approach for `payment_decisions`.
- Page through the API with bounded rate-limited retries and persist the ingestion watermark before scheduled Delta writes
- Increase the API page size above its published maximum; use that approach for `payment_decisions`.
Explanation
Correct Answer
C:Page through the API with bounded rate-limited retries and persist the ingestion watermark before scheduled Delta writes. This directly addresses a one-page REST response does not represent the complete source data, and throttling requires controlled retry. The design should be accepted only after simulate a 429 midway through a multi-page pull and verify no page is skipped or loaded twice; the related operational boundary is to accept longer bounded extraction time to respect the source API contract and preserve completeness.
Incorrect Answers
A:Run the exact same first-page request repeatedly without a cursor; use that approach for `payment_decisions`. Repeated first-page reads duplicate early records while omitting later pages. For `payment_decisions`, this cannot remove the causal limitation: a one-page REST response does not represent the complete source data, and throttling requires controlled retry.
B:Ignore HTTP 429 responses and mark the job successful; use that approach for `payment_decisions`. Throttled pages are missing, causing silent gaps in the destination. For `payment_decisions`, this cannot remove the causal limitation: a one-page REST response does not represent the complete source data, and throttling requires controlled retry.
D:Increase the API page size above its published maximum; use that approach for `payment_decisions`. An unsupported page size will be rejected or truncated, not retrieve a complete source. For `payment_decisions`, this cannot remove the causal limitation: a one-page REST response does not represent the complete source data, and throttling requires controlled retry.
Question 133
At a regional insurer, a REST customer API imposes strict page limits and throttles large pulls, leaving the daily bronze dataset incomplete. The dataset `payment_decisions` is in scope, and an interrupted delivery must be recoverable without data loss. A teammate proposes: "Increase the API page size above its published maximum." Which technical limitation is the decisive reason not to approve that specific proposal?
- An unsupported page size will be rejected or truncated, not retrieve a complete source. The proposal does not repair `payment_decisions`.
- Throttled pages are missing, causing silent gaps in the destination. This would apply to an alternative change for `payment_decisions`.
- Repeated first-page reads duplicate early records while omitting later pages. This would apply to another option for `payment_decisions`.
- Insufficient executor memory is the primary fault; source-file handling and ingestion checkpoints are correct.
Explanation
Correct Answer
A:An unsupported page size will be rejected or truncated, not retrieve a complete source. The proposal does not repair `payment_decisions`. This identifies the known limitation of the exact proposed action. An unsupported page size will be rejected or truncated, not retrieve a complete source. The underlying problem remains a one-page REST response does not represent the complete source data, and throttling requires controlled retry; Page through the API with bounded rate-limited retries and persist the ingestion watermark before scheduled Delta writes instead targets that failure.
Incorrect Answers
B:Throttled pages are missing, causing silent gaps in the destination. This would apply to an alternative change for `payment_decisions`. This failure applies to the separate proposal "Ignore HTTP 429 responses and mark the job successful".
C:Repeated first-page reads duplicate early records while omitting later pages. This would apply to another option for `payment_decisions`. This limitation belongs to the different alternative "Run the exact same first-page request repeatedly without a cursor". The stem calls for the specific failure of "Increase the API page size above its published maximum".
D: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 a one-page REST response does not represent the complete source data, and throttling requires controlled retry.
Question 134
At a regional insurer, a REST customer API imposes strict page limits and throttles large pulls, leaving the daily bronze dataset incomplete. The dataset `payment_decisions` is in scope, and an interrupted delivery must be recoverable without data loss. What operational boundary should be documented for approval?
- Ignore HTTP 429 responses and mark the job successful; monitor results only after launch of `payment_decisions`.
- Accept longer bounded extraction time to respect the source API contract and preserve completeness
- Run the exact same first-page request repeatedly without a cursor; monitor results only after launch of `payment_decisions`.
- Increase the API page size above its published maximum; monitor results only after launch of `payment_decisions`.
Explanation
Correct Answer
B:Accept longer bounded extraction time to respect the source API contract and preserve completeness. This explicitly bounds the compromise while still addressing a one-page REST response does not represent the complete source data, and throttling requires controlled retry. Acceptance relies on simulate a 429 midway through a multi-page pull and verify no page is skipped or loaded twice rather than simply declaring the change complete.
Incorrect Answers
A:Ignore HTTP 429 responses and mark the job successful; monitor results only after launch of `payment_decisions`. Throttled pages are missing, causing silent gaps in the destination. Monitoring after deployment does not make this approach a safe bounded tradeoff for `payment_decisions`.
C:Run the exact same first-page request repeatedly without a cursor; monitor results only after launch of `payment_decisions`. Repeated first-page reads duplicate early records while omitting later pages. Monitoring after deployment does not make this approach a safe bounded tradeoff for `payment_decisions`.
D:Increase the API page size above its published maximum; monitor results only after launch of `payment_decisions`. An unsupported page size will be rejected or truncated, not retrieve a complete source. Monitoring after deployment does not make this approach a safe bounded tradeoff for `payment_decisions`.
Question 135
At a regional insurer, a REST customer API imposes strict page limits and throttles large pulls, leaving the daily bronze dataset incomplete. The dataset `payment_decisions` is in scope, and an interrupted delivery must be recoverable without data loss. Which validation should be required in the release record?
- Run only a normal, unchanged `payment_decisions` sample and review pagination tokens.
- Simulate a 429 midway through a multi-page pull and verify no page is skipped or loaded twice
- Review a platform-level availability report for `payment_decisions` without testing whether a one-page REST response does not represent the complete source data, and throttling requires controlled retry.
- Check that the intended configuration exists for `payment_decisions` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
B:Simulate a 429 midway through a multi-page pull and verify no page is skipped or loaded twice. This reproduces the scenario-dependent condition, verifies pagination tokens, 429 responses, source total, and destination row counts by page, and directly tests whether a one-page REST response does not represent the complete source data, and throttling requires controlled retry is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Run only a normal, unchanged `payment_decisions` sample and review pagination tokens. A normal sample does not challenge a one-page REST response does not represent the complete source data, and throttling requires controlled retry.
C:Review a platform-level availability report for `payment_decisions` without testing whether a one-page REST response does not represent the complete source data, and throttling requires controlled retry. Aggregate availability does not establish the behavior of affected `payment_decisions` records. It cannot replace the direct exercise: simulate a 429 midway through a multi-page pull and verify no page is skipped or loaded twice.
D: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 one-page REST response does not represent the complete source data, and throttling requires controlled retry.
Question 136
At a freight port operator, a finance notebook connects to an external JDBC source with credentials embedded directly in shared code. The dataset `course_enrollments` is in scope, and the target must retain every valid late-arriving event. Before choosing a remedy, which investigation actually distinguishes the failure mechanism from a green dashboard?
- Inspect normal-period success metrics for the stated dataset without reproducing the source error
- Correlate secret access audit, JDBC effective role across affected and unaffected `R034-CASE-028` runs.
- 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.
Explanation
Correct Answer
B:Correlate secret access audit, JDBC effective role across affected and unaffected `R034-CASE-028` runs.. By joining secret access audit, JDBC effective role, notebook revisions, and scheduled job result across the affected and unaffected conditions, the investigation directly tests the recorded mechanism: hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations. It also sets a measurable baseline for rotate the database credential and verify the job still retrieves it securely without exposing it in source code.
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 hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations. The failing-path secret access audit, JDBC effective role, notebook revisions, and scheduled job result 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 hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations. This check never observes the affected `course_enrollments` records or their causal path.
D: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 secret access audit, JDBC effective role, notebook revisions, and scheduled job result, the direct means of distinguishing hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations.
Question 137
At a freight port operator, a finance notebook connects to an external JDBC source with credentials embedded directly in shared code. The dataset `course_enrollments` is in scope, and the target must retain every valid late-arriving event. Which implementation best resolves the stated defect without breaking the business constraint?
- Publish the notebook to all analysts with its password redacted only in comments; use that approach for `course_enrollments`.
- Copy the JDBC password into a shared Delta configuration table; use that approach for `course_enrollments`.
- Use a least-privilege credential retrieved through an approved secret facility and schedule the read through Lakeflow Jobs
- Use the same privileged database account for every analyst and job; use that approach for `course_enrollments`.
Explanation
Correct Answer
C:Use a least-privilege credential retrieved through an approved secret facility and schedule the read through Lakeflow Jobs. This directly addresses hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations. The design should be accepted only after rotate the database credential and verify the job still retrieves it securely without exposing it in source code; the related operational boundary is to retain automated access with a dedicated read-only service identity and auditable rotation.
Incorrect Answers
A:Publish the notebook to all analysts with its password redacted only in comments; use that approach for `course_enrollments`. Comments do not remove secrets from the executable connection string or revision history. For `course_enrollments`, this cannot remove the causal limitation: hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations.
B:Copy the JDBC password into a shared Delta configuration table; use that approach for `course_enrollments`. A readable data table is not a controlled secret store. For `course_enrollments`, this cannot remove the causal limitation: hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations.
D:Use the same privileged database account for every analyst and job; use that approach for `course_enrollments`. A shared admin principal broadens privilege and prevents meaningful attribution. For `course_enrollments`, this cannot remove the causal limitation: hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations.
Question 138
At a freight port operator, a finance notebook connects to an external JDBC source with credentials embedded directly in shared code. The dataset `course_enrollments` is in scope, and the target must retain every valid late-arriving event. A teammate proposes: "Copy the JDBC password into a shared Delta configuration table." 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 readable data table is not a controlled secret store. The proposal does not repair `course_enrollments`.
- Comments do not remove secrets from the executable connection string or revision history. This would apply to an alternative change for `course_enrollments`.
- A shared admin principal broadens privilege and prevents meaningful attribution. This would apply to another option for `course_enrollments`.
Explanation
Correct Answer
B:A readable data table is not a controlled secret store. The proposal does not repair `course_enrollments`. This identifies the known limitation of the exact proposed action. A readable data table is not a controlled secret store. The underlying problem remains hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations; Use a least-privilege credential retrieved through an approved secret facility and schedule the read through Lakeflow Jobs 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 hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations.
C:Comments do not remove secrets from the executable connection string or revision history. This would apply to an alternative change for `course_enrollments`. This failure applies to the separate proposal "Publish the notebook to all analysts with its password redacted only in comments".
D:A shared admin principal broadens privilege and prevents meaningful attribution. This would apply to another option for `course_enrollments`. This limitation belongs to the different alternative "Use the same privileged database account for every analyst and job". The stem calls for the specific failure of "Copy the JDBC password into a shared Delta configuration table".
Question 139
At a freight port operator, a finance notebook connects to an external JDBC source with credentials embedded directly in shared code. The dataset `course_enrollments` is in scope, and the target must retain every valid late-arriving event. Which bounded tradeoff would preserve the core outcome and control operational risk?
- Retain automated access with a dedicated read-only service identity and auditable rotation
- Publish the notebook to all analysts with its password redacted only in comments
- Copy the JDBC password into a shared Delta configuration table
- Use the same privileged database account for every analyst and job; monitor results only after launch of `course_enrollments`.
Explanation
Correct Answer
A:Retain automated access with a dedicated read-only service identity and auditable rotation. This explicitly bounds the compromise while still addressing hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations. Acceptance relies on rotate the database credential and verify the job still retrieves it securely without exposing it in source code rather than simply declaring the change complete.
Incorrect Answers
B:Publish the notebook to all analysts with its password redacted only in comments. Comments do not remove secrets from the executable connection string or revision history. Monitoring after deployment does not make this approach a safe bounded tradeoff for `course_enrollments`.
C:Copy the JDBC password into a shared Delta configuration table. A readable data table is not a controlled secret store. Monitoring after deployment does not make this approach a safe bounded tradeoff for `course_enrollments`.
D:Use the same privileged database account for every analyst and job; monitor results only after launch of `course_enrollments`. A shared admin principal broadens privilege and prevents meaningful attribution. Monitoring after deployment does not make this approach a safe bounded tradeoff for `course_enrollments`.
Question 140
At a freight port operator, a finance notebook connects to an external JDBC source with credentials embedded directly in shared code. The dataset `course_enrollments` 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 `course_enrollments` without testing whether hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations.
- Run only a normal, unchanged `course_enrollments` sample and review secret access audit.
- Rotate the database credential and verify the job still retrieves it securely without exposing it in source code
- Check that the intended configuration exists for `course_enrollments` and that a healthy run succeeded, without inducing the earlier failure.
Explanation
Correct Answer
C:Rotate the database credential and verify the job still retrieves it securely without exposing it in source code. This reproduces the scenario-dependent condition, verifies secret access audit, JDBC effective role, notebook revisions, and scheduled job result, and directly tests whether hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations is resolved. Observed results, not intent, determine approval.
Incorrect Answers
A:Review a platform-level availability report for `course_enrollments` without testing whether hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations. Aggregate availability does not establish the behavior of affected `course_enrollments` records. It cannot replace the direct exercise: rotate the database credential and verify the job still retrieves it securely without exposing it in source code.
B:Run only a normal, unchanged `course_enrollments` sample and review secret access audit. A normal sample does not challenge hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations.
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 hard-coded JDBC credentials leak in notebook revisions and can outlive approved rotations.