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.
Question 281 An ingest job sees files only once a week, yet it polls the source every minute. Which supported trigger could reduce empty executions? A cron schedule every 10 seconds A table update trigger on an unrelated table A file arrival trigger on the supported monitored location A continuous trigger that relaunches the polling task after each run Explanation Correct Answer C:An event-driven trigger avoids starting runs when no file has arrived. Incorrect Answers A:More frequent schedules would increase empty runs. B:Unrelated data changes do not represent source-file arrival. D:Continuous triggering can execute repeatedly without new files and does not directly eliminate empty runs from a sparsely populated file location.
Question 282 A job needs to process region-specific reports for a dynamic list returned by an upstream notebook task. Which feature supports this without fixed task copies? Five hardcoded copies for five expected regions One unfiltered cross join of all region datasets Create one static task per region in the original design A For each task over the upstream-produced array value Explanation Correct Answer D:A For each task can iterate a nested operation over a runtime list supplied by the workflow. Incorrect Answers A:Hardcoding fails when the upstream list changes size. B:A data join is not a workflow loop over run parameters. C:Hard-coded tasks require manual edits when the upstream region list changes; For each consumes the dynamic input.
Question 283 A workflow must skip gold publication when validation finds invalid customer keys, but still complete its error-reporting branch. Which control structure fits? Publish gold before validation to reduce runtime An If/else branch driven by validation output with separate success and failure paths Ignore validation and schedule both branches unconditionally Use a Run if: All done rule so gold publishes even after validation fails Explanation Correct Answer B:Conditional branching can route valid data to publish and invalid data to reporting. Incorrect Answers A:This defeats the quality gate for invalid customer keys. C:Unconditional publication risks releasing known bad data. D:All done can allow a downstream task after failed prerequisites; the requirement demands publication only on a successful validation branch.
Question 284 A retry policy is set on the last job task, but a transient source error occurs in the first task. What must be checked? Assume every task inherits the final task's retry count Configure retries on the task that actually experiences the recoverable error Delete every task dependency Raise the retry count of the downstream dashboard task without changing the upstream ingestion task Explanation Correct Answer B:A downstream retry setting does not rerun the failing upstream extraction task automatically. Incorrect Answers A:Task retry settings are not automatically copied backward through the DAG. C:Removing dependencies would not fix the first task's transient error. D:Retries are task scoped. A transient error in the first source task will not be repaired by retrying only a later dashboard task.
Question 285 A DAG includes an upstream task that can succeed with zero new rows. A downstream publish job should run only when a count is positive. What is needed? An If/else condition based on the upstream task value Run if: All succeeded as the sole check Only a cluster-size upgrade A schedule that always runs publication Explanation Correct Answer A:Task result data can choose whether to publish rather than relying only on task success status. Incorrect Answers B:Success does not imply that the task produced new rows. C:More compute cannot infer whether new rows were produced. D:A fixed schedule ignores the zero-row business condition.
Question 286 A source requires an incremental load followed by two independent quality checks, both of which must pass before publication. What graph fits? Publish immediately after load while quality checks run later Load → quality A and quality B in parallel → publish depending on both Only connect publish to quality A Run all tasks independently with no dependency edges Explanation Correct Answer B:This graph allows independent checks concurrently yet blocks publication until both succeed. Incorrect Answers A:Publication could occur without required quality acceptance. C:Quality B would not be enforced as a prerequisite. D:Unordered tasks can publish before validation completes.
Question 287 A scheduled job has a notebook task followed by a SQL query task. The SQL must see the notebook's committed output. Which task property is essential? The notebook has more than one cell The SQL task must depend on the successful notebook task Assign both tasks the same compute resource but leave their dependency unset The SQL task starts five seconds before the notebook Explanation Correct Answer B:An explicit DAG edge ensures the SQL execution begins after the notebook produces its output. Incorrect Answers A:Notebook size does not define orchestration order. C:Using the same compute does not guarantee the SQL query waits for the upstream notebook write to commit. D:Starting early risks stale or missing data.
Question 288 A job owner wants recurring execution every weekday at a specific local business time. What should it configure and verify? A time-based schedule with appropriate weekday expression and timezone A table update event whenever anyone queries a table A notebook autostart whenever a developer opens the workspace A file arrival event on an unrelated bucket Explanation Correct Answer A:The schedule and timezone express business calendar execution rather than relying on external manual starts. Incorrect Answers B:Reading a table is not a table-update schedule. C:Developer attendance cannot ensure weekday production runs. D:A file event may not occur at the required weekday time.
Question 289 An alerting task is configured as All succeeded but must execute after a source task ends in failure. Which condition is needed instead? All succeeded with increased retries on the alert itself At least one succeeded None failed At least one failed for the relevant upstream dependency Explanation Correct Answer D:This changes the trigger from success to actual failure of the source task. Incorrect Answers A:Alert retries cannot make the success condition true after upstream failure. B:A failed source may not satisfy this condition. C:This explicitly excludes the failure the alert must report.
Question 290 A workflow has three independent source ingestions and a final reconciliation step. All three source ingestions must be complete, even if one fails, before reconciliation produces a failure report. Which Run if mode is suitable? At least one succeeded (success in any branch) At least one failed (failure in any branch) All succeeded (all branches successful) All done (regardless of task outcome) Explanation Correct Answer D:Reconciliation waits for all upstream tasks to finish, including failed ones, so it can report their statuses. Incorrect Answers A:A single successful source may complete while another is still running. B:This would skip the report when all sources succeeded, although reconciliation is still required. C:One failure would prevent the requested reconciliation report.