100% Latest & Updated Databricks Certified Data Engineer Associate Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 350
A dashboard refresh task should not run if an upstream pipeline task failed its quality check. Which action should the engineer perform to establish the intended control?
- Set the extraction task max retries and suitable backoff while keeping its writes idempotent.
- Set the dependency and valid run-if behavior on the dashboard task.
- Monitor the correct source table update event and retain downstream task dependencies.
- Configure the job DAG and task run-if condition so publication does not run on upstream failure.
Explanation
Correct Answer
B:Set the dependency and valid run-if behavior on the dashboard task. A failed quality pipeline leaves the dashboard refresh skipped and logs the upstream cause.
Incorrect Answers
A:If an upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run, “Set the extraction task max retries and suitable backoff while keeping its writes idempotent” may be the appropriate response. Set the dependency and valid run-if behavior on the dashboard task.
C:When a CDC connector updates a Unity Catalog table multiple times a day and downstream billing should respond to committed changes, “Monitor the correct source table update event and retain downstream task dependencies” could be relevant. Set the dependency and valid run-if behavior on the dashboard task.
D:If 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” may be the appropriate response. Set the dependency and valid run-if behavior on the dashboard task.
Question 351
A dashboard refresh task should not run if an upstream pipeline task failed its quality check. Which observation best proves the workload meets its requirement?
- On validation failure, cleanup and alert occur without running the publish task.
- A failed quality pipeline leaves the dashboard refresh skipped and logs the upstream cause.
- A test multi-file upload is processed only after the configured readiness window.
- The job executes after the source table update rather than before the variable upstream finish.
Explanation
Correct Answer
B:A failed quality pipeline leaves the dashboard refresh skipped and logs the upstream cause.
Incorrect Answers
A: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 failed quality pipeline leaves the dashboard refresh skipped and logs the upstream cause.
C:If a file-arrival job fires too frequently while one large upstream export is still uploading many parts, “A test multi-file upload is processed only after the configured readiness window” may be the appropriate response. A failed quality pipeline leaves the dashboard refresh skipped and logs the upstream cause.
D:A pipeline should start only when a nightly upstream table update is complete, but the update time varies. In those circumstances, “The job executes after the source table update rather than before the variable upstream finish” fits. A failed quality pipeline leaves the dashboard refresh skipped and logs the upstream cause.
Question 352
A dashboard refresh task should not run if an upstream pipeline task failed its quality check. The team observes: The dashboard task refreshes after a failed pipeline and displays stale misleading data. Which underlying cause most directly explains this failure?
- The task did not enforce upstream successful completion.
- A table-update trigger was used despite an unconditional time-bound reporting obligation.
- Unbounded concurrency allowed overlapping executions of the same stateful workload.
- The orchestration uses unconditional frequent cron polling rather than arrival events.
Explanation
Correct Answer
A:The task did not enforce upstream successful completion. Set the dependency and valid run-if behavior on the dashboard task.
Incorrect Answers
B:If an analytics report must be published every morning regardless of whether source tables changed overnight, “A table-update trigger was used despite an unconditional time-bound reporting obligation” may be the appropriate response. The task did not enforce upstream successful completion.
C:An expensive batch that runs for hours must avoid overlapping with its next schedule occurrence. In those circumstances, “Unbounded concurrency allowed overlapping executions of the same stateful workload” fits. The task did not enforce upstream successful completion.
D:When a source archive arrives in a UC volume only at irregular intervals, and polling every minute wastes runs, “The orchestration uses unconditional frequent cron polling rather than arrival events” could be relevant. The task did not enforce upstream successful completion.
Question 353
A regulated daily ledger load must run at 02:00 in the business time zone even with no new files. Which design choice best addresses the stated business and technical requirement?
- Use a pipeline task with a dependency on the validation notebook task.
- Use an explicit Lakeflow Jobs conditional branch based on the quality outcome.
- Use a scheduled Lakeflow Jobs trigger in the intended time zone.
- Use appropriately typed Lakeflow Jobs tasks connected in a DAG.
Explanation
Correct Answer
C:Use a scheduled Lakeflow Jobs trigger in the intended time zone. A dry-run calendar check shows executions at the required local times including daylight changes where relevant.
Incorrect Answers
A:If a Lakeflow Spark Declarative Pipeline must be refreshed only after a file validation notebook succeeds, “Use a pipeline task with a dependency on the validation notebook task” may be the appropriate response. Use a scheduled Lakeflow Jobs trigger in the intended time zone.
B:A data quality score determines whether an export is published or a defect notification is sent. In those circumstances, “Use an explicit Lakeflow Jobs conditional branch based on the quality outcome” fits. Use a scheduled Lakeflow Jobs trigger in the intended time zone.
D:If a weekly pipeline needs a Python notebook for extraction, SQL for transformation and a dashboard refresh after both, “Use appropriately typed Lakeflow Jobs tasks connected in a DAG” may be the appropriate response. Use a scheduled Lakeflow Jobs trigger in the intended time zone.
Question 354
A regulated daily ledger load must run at 02:00 in the business time zone even with no new files. Which setup step most directly realizes the proposed design?
- Write a bounded task value in the notebook and reference that output from the downstream task.
- Set the job's time-based schedule and documented timezone.
- Set the extraction task max retries and suitable backoff while keeping its writes idempotent.
- Configure the relevant Lakeflow Jobs run-if conditions for cleanup and notification branches.
Explanation
Correct Answer
B:Set the job's time-based schedule and documented timezone. A dry-run calendar check shows executions at the required local times including daylight changes where relevant.
Incorrect Answers
A: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. Set the job's time-based schedule and documented timezone.
C:If an upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run, “Set the extraction task max retries and suitable backoff while keeping its writes idempotent” may be the appropriate response. Set the job's time-based schedule and documented timezone.
D:An ETL validation failure should open an alert but still allow a safe cleanup task to release temporary files. In those circumstances, “Configure the relevant Lakeflow Jobs run-if conditions for cleanup and notification branches” fits. Set the job's time-based schedule and documented timezone.
Question 355
A regulated daily ledger load must run at 02:00 in the business time zone even with no new files. What is the most relevant verification evidence for this case?
- On validation failure, cleanup and alert occur without running the publish task.
- The pipeline refresh starts after the validation task succeeded on the expected source files.
- A failed ingestion run leaves the existing published table unchanged and marks downstream skipped.
- A dry-run calendar check shows executions at the required local times including daylight changes where relevant.
Explanation
Correct Answer
D:A dry-run calendar check shows executions at the required local times including daylight changes where relevant.
Incorrect Answers
A:When an ETL validation failure should open an alert but still allow a safe cleanup task to release temporary files, “On validation failure, cleanup and alert occur without running the publish task” could be relevant. A dry-run calendar check shows executions at the required local times including daylight changes where relevant.
B:If a Lakeflow Spark Declarative Pipeline must be refreshed only after a file validation notebook succeeds, “The pipeline refresh starts after the validation task succeeded on the expected source files” may be the appropriate response. A dry-run calendar check shows executions at the required local times including daylight changes where relevant.
C: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 dry-run calendar check shows executions at the required local times including daylight changes where relevant.
Question 356
A regulated daily ledger load must run at 02:00 in the business time zone even with no new files. The team observes: Runs start at unintended UTC offsets during a seasonal time change. What is the most likely mechanism behind the observed defect?
- The job definition referenced a renamed task key that no longer exists.
- The schedule was configured without the business time zone.
- The extraction task had no appropriate retry configuration.
- The job flow lacked a condition gate on the publication task.
Explanation
Correct Answer
B:The schedule was configured without the business time zone. Set the job's time-based schedule and documented timezone.
Incorrect Answers
A:If an operational DAG has a source-to-silver path but the downstream gold task was wired to a different obsolete task key, “The job definition referenced a renamed task key that no longer exists” may be the appropriate response. The schedule was configured without the business time zone.
C: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 schedule was configured without the business time zone.
D:If a data quality score determines whether an export is published or a defect notification is sent, “The job flow lacked a condition gate on the publication task” may be the appropriate response. The schedule was configured without the business time zone.
Question 357
A landing volume receives source files at unpredictable hours and processing should start on arrival. Which approach most directly satisfies the requirement?
- Use Lakeflow Jobs task retry policies instead of manually restarting the whole workflow.
- Use a pipeline task with a dependency on the validation notebook task.
- Represent independent source tasks as parallel branches and gold aggregation as a downstream join node.
- Use a file-arrival trigger monitoring an eligible Unity Catalog storage location.
Explanation
Correct Answer
D:Use a file-arrival trigger monitoring an eligible Unity Catalog storage location. A newly arrived controlled test file launches the job without waiting for a fixed nightly cron.
Incorrect Answers
A:An upstream extraction occasionally fails with a transient network error and finance needs an automatic bounded retry before downstream reports run. In those circumstances, “Use Lakeflow Jobs task retry policies instead of manually restarting the whole workflow” fits. Use a file-arrival trigger monitoring an eligible Unity Catalog storage location.
B:When a Lakeflow Spark Declarative Pipeline must be refreshed only after a file validation notebook succeeds, “Use a pipeline task with a dependency on the validation notebook task” could be relevant. Use a file-arrival trigger monitoring an eligible Unity Catalog storage location.
C:If 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” may be the appropriate response. Use a file-arrival trigger monitoring an eligible Unity Catalog storage location.
Question 358
A landing volume receives source files at unpredictable hours and processing should start on arrival. Which configuration or engineering action would most directly implement the requirement?
- Publish the quality metric to a supported condition task and connect pass/fail task branches.
- Make reconciliation depend on both completed source tasks in the task graph.
- Configure the monitored volume or external location and validate file-arrival trigger access.
- Configure the job DAG and task run-if condition so publication does not run on upstream failure.
Explanation
Correct Answer
C:Configure the monitored volume or external location and validate file-arrival trigger access. A newly arrived controlled test file launches the job without waiting for a fixed nightly cron.
Incorrect Answers
A:When a data quality score determines whether an export is published or a defect notification is sent, “Publish the quality metric to a supported condition task and connect pass/fail task branches” could be relevant. Configure the monitored volume or external location and validate file-arrival trigger access.
B: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. Configure the monitored volume or external location and validate file-arrival trigger access.
D: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. Configure the monitored volume or external location and validate file-arrival trigger access.
Question 359
A landing volume receives source files at unpredictable hours and processing should start on arrival. Which test would establish that the change worked as intended?
- The pipeline refresh starts after the validation task succeeded on the expected source files.
- A newly arrived controlled test file launches the job without waiting for a fixed nightly cron.
- Good data executes the publish branch while bad data executes only the exception branch.
- The reconciler starts only after both prerequisite task runs succeed.
Explanation
Correct Answer
B:A newly arrived controlled test file launches the job without waiting for a fixed nightly cron.
Incorrect Answers
A:If a Lakeflow Spark Declarative Pipeline must be refreshed only after a file validation notebook succeeds, “The pipeline refresh starts after the validation task succeeded on the expected source files” may be the appropriate response. A newly arrived controlled test file launches the job without waiting for a fixed nightly cron.
C:When a data quality score determines whether an export is published or a defect notification is sent, “Good data executes the publish branch while bad data executes only the exception branch” could be relevant. A newly arrived controlled test file launches the job without waiting for a fixed nightly cron.
D:If an enrichment pipeline should run a reconciliation task only after two independent input tasks have both succeeded, “The reconciler starts only after both prerequisite task runs succeed” may be the appropriate response. A newly arrived controlled test file launches the job without waiting for a fixed nightly cron.
Question 360
A landing volume receives source files at unpredictable hours and processing should start on arrival. The team observes: A noon file waits until midnight before ingestion begins. Which configuration or design gap best explains the symptom?
- The job flow lacked a condition gate on the publication task.
- The job was configured only with a nightly schedule rather than a file-arrival trigger.
- Different hard-coded task parameters were used instead of one common run value.
- The pipeline task was configured without an upstream validation dependency.
Explanation
Correct Answer
B:The job was configured only with a nightly schedule rather than a file-arrival trigger. Configure the monitored volume or external location and validate file-arrival trigger access.
Incorrect Answers
A:A data quality score determines whether an export is published or a defect notification is sent. In those circumstances, “The job flow lacked a condition gate on the publication task” fits. The job was configured only with a nightly schedule rather than a file-arrival trigger.
C:If a reporting job uses a dynamic processing date and must pass the identical value to all tasks in one run, “Different hard-coded task parameters were used instead of one common run value” may be the appropriate response. The job was configured only with a nightly schedule rather than a file-arrival trigger.
D: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 job was configured only with a nightly schedule rather than a file-arrival trigger.
Certified Data Engineer Associate Practice Tests