Question 270 A job currently refreshes a daily report using a notebook task, but the logic is a saved Databricks SQL query. Which task type better expresses the operation? A For each task with an empty array Only a cluster startup script A SQL query task targeting the approved SQL resource A file arrival task on a random volume Explanation Correct Answer C:A SQL task directly invokes the saved query without needing an unrelated notebook wrapper. Incorrect Answers A:An empty iteration would not execute the intended report query. B:Startup scripts configure compute and are not the saved SQL query workload. D:A file event is not the actual SQL query execution step.
Question 271 A recurring workload runs a Databricks notebook that transforms landing records into silver data. Which common Lakeflow Jobs task type fits? Notebook task with the appropriate notebook path and compute Only a dashboard task for the transform Use a SQL query task that references the notebook Git branch but not the notebook path Only a storage credential object Explanation Correct Answer A:A notebook task runs authored notebook logic under orchestration. Incorrect Answers B:A dashboard task is for reporting refresh, not arbitrary PySpark transformation logic. C:A SQL query task is designed to run SQL query definitions, not execute the PySpark notebook transformation as required. D:A storage credential governs access and is not an executable job task.
Question 272 A data engineering team has a Lakeflow Spark Declarative Pipelines definition that should execute as part of a larger job after ingestion. Which task type should it use? A pipeline task with an upstream ingestion dependency Use a notebook task that only calls a SQL SELECT against a pipeline output Use only a SQL query task to invoke the pipeline without declaring the actual pipeline task A file arrival trigger used as a replacement for the pipeline Explanation Correct Answer A:The pipeline task invokes the managed pipeline and can be ordered after its prerequisite ingestion. Incorrect Answers B:A notebook query can read data but does not execute the separately defined Lakeflow pipeline as part of the job. C:A SQL statement is not the explicit Lakeflow pipeline task type needed to orchestrate a managed pipeline as part of the job DAG. D:A trigger initiates a job but is not itself the pipeline execution task.
Question 273 A business analyst dashboard must refresh after gold tables finish updating. Which task sequence is appropriate? Dashboard refresh before gold build Gold and dashboard independently scheduled at the same time Only a table grant with no refresh task Gold pipeline success followed by a dashboard task Explanation Correct Answer D:A dashboard task can refresh reporting only after the relevant data products are ready. Incorrect Answers A:This risks displaying the prior gold state. B:Independent starts permit a dashboard-data race. C:Authorization does not execute the dashboard refresh.
Question 274 A Lakeflow Jobs task runs every night but repeatedly overlaps with the next execution if an incident makes it slow. What configuration should be evaluated? A permanent unrestricted table grant Removing every task dependency Job maximum concurrent runs and the intended queuing policy Increase the cron schedule frequency while retaining unlimited simultaneous runs Explanation Correct Answer C:Concurrency limits and queuing help avoid overlapping runs that contend for resources or mutate the same target. Incorrect Answers A:Permissions are separate from job-instance concurrency. B:Fewer dependencies could worsen data races and do not limit concurrent job runs. D:More frequent starts aggravate overlapping runs and fail to enforce the intended concurrency limit.
Question 275 Two scheduled runs can update the same business table. The pipeline must avoid a second run writing before the first has committed. What control is relevant? Disable task errors on both runs Bound concurrency or implement explicit safe transactional/idempotent coordination Drop the destination table after every run Schedule the second run a few minutes later without checking prior-run completion Explanation Correct Answer B:Serializing conflicting runs or making the updates concurrency-safe prevents stale or duplicate writes. Incorrect Answers A:Suppressing failures hides potential update conflicts. C:Table deletion is unsafe and does not establish ordered writes. D:A fixed delay cannot guarantee safe serialization when the earlier run takes longer than expected.
Question 276 An operations engineer sees a failure in task C of a six-task DAG. What UI information is most useful for identifying which prerequisite failed? Inspect only task C’s error text without opening upstream task states The run task graph with statuses and upstream dependencies Inspect only the final task output without expanding its upstream dependencies Inspect task definitions in source control without reviewing this execution’s task-status graph Explanation Correct Answer B:The DAG view shows the path through the workflow and which task outcomes blocked C. Incorrect Answers A:A downstream failure message may be the symptom of a blocked predecessor; the run DAG shows which dependency actually failed. C:Final output can reflect an upstream failure, but without DAG statuses it cannot locate the failed prerequisite reliably. D:Definitions show configured prerequisites, not which prerequisite failed or was skipped during the specific run.
Question 277 A job runs four tasks and one failed upstream dependency causes downstream tasks to be skipped. Which job status interpretation is accurate? The entire job always succeeds when any task is skipped Every skipped task necessarily failed while executing its notebook code Skipped tasks automatically repair their upstream inputs Skipped downstream tasks may be blocked by a failed prerequisite even if their code never started Explanation Correct Answer D:Dependency semantics can prevent execution when an upstream success condition was not met. Incorrect Answers A:A failed required upstream task can make the overall job fail. B:A task can be skipped before execution due to dependency results. C:A skipped task performs no corrective processing by itself.
Question 278 A job must send an alert only if its upstream quality validation failed. Which downstream setting best expresses the condition? Run if: All succeeded Run if: At least one failed on the validation dependency Schedule the alert at the same time as validation Use Run if: All done and assume it fires only on validation failure Explanation Correct Answer B:This condition initiates the alert path for a failed prerequisite, not for successful validation. Incorrect Answers A:This would send alerts when the quality task passed. C:An independent schedule cannot know the validation outcome. D:All done runs after successful or failed upstream completion, so it cannot express a failure-only alert.
Question 279 A team wants to inspect failed job runs over 30 days and compare durations against healthy baselines. Which Lakeflow Jobs surface is relevant? Job run history with per-run status and execution time Inspect only the present job configuration without historical per-run execution records Only UC table ownership details A new source file extension Explanation Correct Answer A:Run history tracks outcomes and durations so failure patterns and regressions can be compared. Incorrect Answers B:Current task definitions do not show which historical runs failed or how long each run lasted. C:Ownership does not summarize individual job execution times. D:Source naming does not expose past job run statuses.
Question 280 An upstream data table is updated unpredictably throughout the day, and a downstream transformation should react to those updates rather than a fixed clock. Which trigger fits? Table update trigger for the supported source object Use a five-minute schedule to poll the table instead of a supported table-update trigger A nightly schedule only Schedule the downstream task once per hour but assume it exactly matches every upstream table update Explanation Correct Answer A:A table-change trigger aligns downstream job runs with actual updates. Incorrect Answers B:Periodic polling adds latency and redundant runs and does not directly respond to the unpredictable table update event. C:A fixed daily schedule can miss the desired event-driven freshness window. D:A fixed clock can lag and create needless runs because source table changes occur at unpredictable times.