100% Latest & Updated Databricks Certified Data Engineer Associate Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 380
A CDC connector updates a Unity Catalog table multiple times a day and downstream billing should respond to committed changes. The team observes: Billing reports do not respond to a mid-day source update. Which root cause should be addressed first given this evidence?
- The notebook never published the named task value required by the downstream condition.
- The pipeline task was configured without an upstream validation dependency.
- The cleanup action was gated on upstream success instead of an appropriate completion condition.
- The workflow relies solely on a fixed nightly schedule.
Explanation
Correct Answer
D:The workflow relies solely on a fixed nightly schedule. Monitor the correct source table update event and retain downstream task dependencies.
Incorrect Answers
A:If a source notebook should output a small validated row-count value used by a later condition task, “The notebook never published the named task value required by the downstream condition” may be the appropriate response. The workflow relies solely on a fixed nightly schedule.
B:A Lakeflow Spark Declarative Pipeline must be refreshed only after a file validation notebook succeeds. In those circumstances, “The pipeline task was configured without an upstream validation dependency” fits. The workflow relies solely on a fixed nightly schedule.
C:When an ETL validation failure should open an alert but still allow a safe cleanup task to release temporary files, “The cleanup action was gated on upstream success instead of an appropriate completion condition” could be relevant. The workflow relies solely on a fixed nightly schedule.
Question 381
A source archive arrives in a UC volume only at irregular intervals, and polling every minute wastes runs. Which technical design is most appropriate for the stated constraint?
- Keep the publication task dependent on successful upstream completion.
- Repair task-key references and dependencies before changing transformation code.
- Choose a file-arrival trigger for the governed landing path.
- Express the required wait-for-both dependency in the Lakeflow Jobs task DAG.
Explanation
Correct Answer
C:Choose a file-arrival trigger for the governed landing path. A new archive launches the processing job, and no run occurs during idle periods.
Incorrect Answers
A:A nightly fraud model table must never publish when its upstream ETL task reports a hard failure. In those circumstances, “Keep the publication task dependent on successful upstream completion” fits. Choose a file-arrival trigger for the governed landing path.
B:When an operational DAG has a source-to-silver path but the downstream gold task was wired to a different obsolete task key, “Repair task-key references and dependencies before changing transformation code” could be relevant. Choose a file-arrival trigger for the governed landing path.
D:An enrichment pipeline should run a reconciliation task only after two independent input tasks have both succeeded. In those circumstances, “Express the required wait-for-both dependency in the Lakeflow Jobs task DAG” fits. Choose a file-arrival trigger for the governed landing path.
Question 382
A source archive arrives in a UC volume only at irregular intervals, and polling every minute wastes runs. Which action should the engineer perform to establish the intended control?
- Configure the job DAG and task run-if condition so publication does not run on upstream failure.
- Monitor the allowed UC volume path and test trigger permission and timing.
- Write a bounded task value in the notebook and reference that output from the downstream task.
- Configure the relevant Lakeflow Jobs run-if conditions for cleanup and notification branches.
Explanation
Correct Answer
B:Monitor the allowed UC volume path and test trigger permission and timing. A new archive launches the processing job, and no run occurs during idle periods.
Incorrect Answers
A:When a nightly fraud model table must never publish when its upstream ETL task reports a hard failure, “Configure the job DAG and task run-if condition so publication does not run on upstream failure” could be relevant. Monitor the allowed UC volume path and test trigger permission and timing.
C:A source notebook should output a small validated row-count value used by a later condition task. In those circumstances, “Write a bounded task value in the notebook and reference that output from the downstream task” fits. Monitor the allowed UC volume path and test trigger permission and timing.
D:When an ETL validation failure should open an alert but still allow a safe cleanup task to release temporary files, “Configure the relevant Lakeflow Jobs run-if conditions for cleanup and notification branches” could be relevant. Monitor the allowed UC volume path and test trigger permission and timing.
Question 383
A source archive arrives in a UC volume only at irregular intervals, and polling every minute wastes runs. Which observation best proves the workload meets its requirement?
- A failed ingestion run leaves the existing published table unchanged and marks downstream skipped.
- On validation failure, cleanup and alert occur without running the publish task.
- A new archive launches the processing job, and no run occurs during idle periods.
- All tasks' output partition dates agree for the same triggered run.
Explanation
Correct Answer
C:A new archive launches the processing job, and no run occurs during idle periods.
Incorrect Answers
A:If a nightly fraud model table must never publish when its upstream ETL task reports a hard failure, “A failed ingestion run leaves the existing published table unchanged and marks downstream skipped” may be the appropriate response. A new archive launches the processing job, and no run occurs during idle periods.
B:An ETL validation failure should open an alert but still allow a safe cleanup task to release temporary files. In those circumstances, “On validation failure, cleanup and alert occur without running the publish task” fits. A new archive launches the processing job, and no run occurs during idle periods.
D:If a reporting job uses a dynamic processing date and must pass the identical value to all tasks in one run, “All tasks' output partition dates agree for the same triggered run” may be the appropriate response. A new archive launches the processing job, and no run occurs during idle periods.
Question 384
A source archive arrives in a UC volume only at irregular intervals, and polling every minute wastes runs. The team observes: Jobs continue launching when the landing path has not changed. Which underlying cause most directly explains this failure?
- The task did not enforce upstream successful completion.
- The extraction task had no appropriate retry configuration.
- The notebook never published the named task value required by the downstream condition.
- The orchestration uses unconditional frequent cron polling rather than arrival events.
Explanation
Correct Answer
D:The orchestration uses unconditional frequent cron polling rather than arrival events. Monitor the allowed UC volume path and test trigger permission and timing.
Incorrect Answers
A:A dashboard refresh task should not run if an upstream pipeline task failed its quality check. In those circumstances, “The task did not enforce upstream successful completion” fits. The orchestration uses unconditional frequent cron polling rather than arrival events.
B:When an upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run, “The extraction task had no appropriate retry configuration” could be relevant. The orchestration uses unconditional frequent cron polling rather than arrival events.
C:If a source notebook should output a small validated row-count value used by a later condition task, “The notebook never published the named task value required by the downstream condition” may be the appropriate response. The orchestration uses unconditional frequent cron polling rather than arrival events.
Question 385
An analytics report must be published every morning regardless of whether source tables changed overnight. Which design choice best addresses the stated business and technical requirement?
- Use a job-level parameter propagated into task parameters.
- Choose a time-based trigger that expresses the publication SLA.
- Keep the publication task dependent on successful upstream completion.
- Use supported task-value exchange for small control metadata, not a giant driver payload.
Explanation
Correct Answer
B:Choose a time-based trigger that expresses the publication SLA. A morning report run exists even on days with no upstream table modifications.
Incorrect Answers
A:When a reporting job uses a dynamic processing date and must pass the identical value to all tasks in one run, “Use a job-level parameter propagated into task parameters” could be relevant. Choose a time-based trigger that expresses the publication SLA.
C:A nightly fraud model table must never publish when its upstream ETL task reports a hard failure. In those circumstances, “Keep the publication task dependent on successful upstream completion” fits. Choose a time-based trigger that expresses the publication SLA.
D:When a source notebook should output a small validated row-count value used by a later condition task, “Use supported task-value exchange for small control metadata, not a giant driver payload” could be relevant. Choose a time-based trigger that expresses the publication SLA.
Question 386
An analytics report must be published every morning regardless of whether source tables changed overnight. Which setup step most directly realizes the proposed design?
- Define the run parameter once and reference it consistently in each task configuration.
- Schedule the report task for its required time and preserve data-availability checks.
- Pass the region list into a supported loop and parameterize the validation task.
- Make reconciliation depend on both completed source tasks in the task graph.
Explanation
Correct Answer
B:Schedule the report task for its required time and preserve data-availability checks. A morning report run exists even on days with no upstream table modifications.
Incorrect Answers
A:If a reporting job uses a dynamic processing date and must pass the identical value to all tasks in one run, “Define the run parameter once and reference it consistently in each task configuration” may be the appropriate response. Schedule the report task for its required time and preserve data-availability checks.
C:When a pipeline must apply identical validation to each element of a bounded list of ten regional entities, “Pass the region list into a supported loop and parameterize the validation task” could be relevant. Schedule the report task for its required time and preserve data-availability checks.
D:If an enrichment pipeline should run a reconciliation task only after two independent input tasks have both succeeded, “Make reconciliation depend on both completed source tasks in the task graph” may be the appropriate response. Schedule the report task for its required time and preserve data-availability checks.
Question 387
An analytics report must be published every morning regardless of whether source tables changed overnight. What is the most relevant verification evidence for this case?
- A failed ingestion run leaves the existing published table unchanged and marks downstream skipped.
- The task graph correctly shows gold after silver and executes in that order.
- A morning report run exists even on days with no upstream table modifications.
- A simulated transient error retries within policy and downstream tasks begin only after success.
Explanation
Correct Answer
C:A morning report run exists even on days with no upstream table modifications.
Incorrect Answers
A:A nightly fraud model table must never publish when its upstream ETL task reports a hard failure. In those circumstances, “A failed ingestion run leaves the existing published table unchanged and marks downstream skipped” fits. A morning report run exists even on days with no upstream table modifications.
B:When an operational DAG has a source-to-silver path but the downstream gold task was wired to a different obsolete task key, “The task graph correctly shows gold after silver and executes in that order” could be relevant. A morning report run exists even on days with no upstream table modifications.
D:An upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run. In those circumstances, “A simulated transient error retries within policy and downstream tasks begin only after success” fits. A morning report run exists even on days with no upstream table modifications.
Question 388
An analytics report must be published every morning regardless of whether source tables changed overnight. The team observes: No report is produced on a quiet data day. What is the most likely mechanism behind the observed defect?
- A table-update trigger was used despite an unconditional time-bound reporting obligation.
- The dashboard task had no dependency on the transformation task.
- The SQL task's supported warehouse and query configuration were missing.
- The extraction task had no appropriate retry configuration.
Explanation
Correct Answer
A:A table-update trigger was used despite an unconditional time-bound reporting obligation. Schedule the report task for its required time and preserve data-availability checks.
Incorrect Answers
B:If a weekly pipeline needs a Python notebook for extraction, SQL for transformation and a dashboard refresh after both, “The dashboard task had no dependency on the transformation task” may be the appropriate response. A table-update trigger was used despite an unconditional time-bound reporting obligation.
C:A SQL-only analytics team needs to run a saved query as part of a governed batch job. In those circumstances, “The SQL task's supported warehouse and query configuration were missing” fits. A table-update trigger was used despite an unconditional time-bound reporting obligation.
D:When an upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run, “The extraction task had no appropriate retry configuration” could be relevant. A table-update trigger was used despite an unconditional time-bound reporting obligation.
Question 389
A pipeline should start only when a nightly upstream table update is complete, but the update time varies. Which approach most directly satisfies the requirement?
- Use a job-level parameter propagated into task parameters.
- Prefer a data-driven table trigger to guessing the completion time with cron.
- Represent independent source tasks as parallel branches and gold aggregation as a downstream join node.
- Use supported task-value exchange for small control metadata, not a giant driver payload.
Explanation
Correct Answer
B:Prefer a data-driven table trigger to guessing the completion time with cron. The job executes after the source table update rather than before the variable upstream finish.
Incorrect Answers
A:If a reporting job uses a dynamic processing date and must pass the identical value to all tasks in one run, “Use a job-level parameter propagated into task parameters” may be the appropriate response. Prefer a data-driven table trigger to guessing the completion time with cron.
C:When a data platform has three independent bronze sources and a gold aggregator that needs all three complete, “Represent independent source tasks as parallel branches and gold aggregation as a downstream join node” could be relevant. Prefer a data-driven table trigger to guessing the completion time with cron.
D:If a source notebook should output a small validated row-count value used by a later condition task, “Use supported task-value exchange for small control metadata, not a giant driver payload” may be the appropriate response. Prefer a data-driven table trigger to guessing the completion time with cron.
Question 390
A pipeline should start only when a nightly upstream table update is complete, but the update time varies. Which configuration or engineering action would most directly implement the requirement?
- Pass the region list into a supported loop and parameterize the validation task.
- Write a bounded task value in the notebook and reference that output from the downstream task.
- Configure a supported table-update trigger and dependent pipeline tasks.
- Configure the job DAG and task run-if condition so publication does not run on upstream failure.
Explanation
Correct Answer
C:Configure a supported table-update trigger and dependent pipeline tasks. The job executes after the source table update rather than before the variable upstream finish.
Incorrect Answers
A:A pipeline must apply identical validation to each element of a bounded list of ten regional entities. In those circumstances, “Pass the region list into a supported loop and parameterize the validation task” fits. Configure a supported table-update trigger and dependent pipeline tasks.
B:When a source notebook should output a small validated row-count value used by a later condition task, “Write a bounded task value in the notebook and reference that output from the downstream task” could be relevant. Configure a supported table-update trigger and dependent pipeline tasks.
D:A nightly fraud model table must never publish when its upstream ETL task reports a hard failure. In those circumstances, “Configure the job DAG and task run-if condition so publication does not run on upstream failure” fits. Configure a supported table-update trigger and dependent pipeline tasks.
Certified Data Engineer Associate Practice Tests