Question 250 A source dataset has 250 rows, and a transformation filters to 100 active rows before a left join with a unique-key dimension that matches 90 of them. How many left-side rows will remain? 90 250 190 100 Explanation Correct Answer D:A left outer join retains all 100 filtered fact rows, including ten with missing dimension matches. Incorrect Answers A:Ninety is the matched portion, which would be the inner-join count. B:The filter removed 150 inactive rows before the join. C:The join does not add the 90 matches to the 100 original left rows when the dimension key is unique.
Question 251 A data engineer computes `groupBy("region").agg(countDistinct("customer_id"))` and sees fewer results than `count("customer_id")`. Why? Repeated customer IDs within regions contribute once to distinct count Distinct count automatically drops every customer who has one purchase count() always groups on the entire DataFrame regardless of region Delta transaction history is disabled Explanation Correct Answer A:Distinct aggregation counts unique identifiers rather than every non-null row. Incorrect Answers B:One-purchase customers still count once when their ID is non-null. C:Both aggregations can use the same region grouping; the difference is distinctness. D:History configuration is unrelated to the two aggregate definitions.
Question 252 A job has an ingestion task, then cleaning, then a gold aggregation. Gold must not begin before cleaning completes successfully. How should the job be configured? Define three independent scheduled tasks without explicit dependencies Launch gold first to warm the warehouse Use task dependencies ingestion → cleaning → gold Schedule all three tasks independently at the same timestamp Explanation Correct Answer C:A DAG dependency ensures gold runs only after its required upstream processing succeeds under the default success condition. Incorrect Answers A:Separate schedules can run out of order; only a DAG dependency prevents gold from starting before cleaning succeeds. B:An earlier gold execution would process incomplete or stale silver data. D:Independent starts can race before required upstream data is ready.
Question 253 A Lakeflow Job has parallel tasks A and B. Task C must start only after both finish successfully. What dependency should C have? Add A and B as scheduled job triggers instead of task dependencies Run if at least one upstream task fails Run immediately when the job starts Depend on both A and B with all-succeeded semantics Explanation Correct Answer D:C waits for both prerequisites and proceeds when each has succeeded. Incorrect Answers A:Independent triggers can start C without both prerequisite task results; explicit DAG dependencies ensure both upstream tasks finish first. B:Failure-triggered execution is not the requested two-success join. C:No dependency would violate the two-input readiness condition.
Question 254 A job starts task A, then tasks B and C can run independently once A finishes. What graph shape expresses the concurrency? A → B → C in a serial chain Run B before A but C after A preceding B and C, with no dependency between B and C Have B and C independent of A Explanation Correct Answer C:After A succeeds, the two branches may execute in parallel. Incorrect Answers A:Serializing C behind B adds an unnecessary dependency. B:B would start before its required source task. D:Both branches could start without the prerequisite data.
Question 255 A three-task job has ingestion → validate → publish. Validate fails. Under ordinary success dependencies, what should happen to publish? Publish should ignore the validation task result Publish should delete the job definition Publish should run on partial data automatically Publish should not execute because its prerequisite did not succeed Explanation Correct Answer D:The downstream task should be blocked or skipped until the validation dependency succeeds. Incorrect Answers A:Ignoring a required dependency would violate the specified workflow. B:A failed task does not require deleting orchestration assets. C:A default success dependency is intended to prevent publishing after failed validation.
Question 256 A noncritical notification task must execute even when an upstream transformation task fails, so the team receives a completion report. Which Run if mode is suitable? All done for the relevant upstream dependency Never depend on the transformation File arrival trigger on an unrelated folder All succeeded only Explanation Correct Answer A:All done allows the downstream reporting task to run after upstream completion regardless of success or failure. Incorrect Answers B:Without the dependency, notification may run before the transformation finishes. C:A source event does not implement post-task completion reporting. D:All succeeded would skip the notification if the upstream transformation failed.
Question 257 A recovery handler should execute only when at least one upstream branch fails, and ignore the path where both branches succeed. Which Run if choice fits? All succeeded At least one succeeded All done At least one failed Explanation Correct Answer D:The handler starts when any required upstream task fails, matching the failure condition. Incorrect Answers A:That condition runs precisely when there are no failures. B:This may run despite the failure logic not being satisfied. C:All done also runs on success, which would trigger unnecessary recovery.
Question 258 A cleanup task must run when all upstream tasks have reached a terminal state, even if some have failed. Which condition is most direct? None failed All succeeded At least one succeeded All done Explanation Correct Answer D:This mode waits for upstream tasks to finish without requiring success. Incorrect Answers A:This disallows cleanup when failure recovery might need it most. B:This would not run cleanup after a task failure. C:A single success need not imply all upstream tasks are finished.
Question 259 A data pipeline must start whenever new files are placed in a monitored Unity Catalog volume rather than at a fixed hour. Which Lakeflow Jobs trigger applies? Use a frequent scheduled trigger that starts regardless of whether a new source file arrived Table update trigger Scheduled cron trigger File arrival trigger Explanation Correct Answer D:File arrival triggers respond to new files in supported monitored UC storage locations. Incorrect Answers A:A frequent schedule polls on elapsed time and may run empty; the requirement asks for starts based on arrivals at a monitored location. B:A table update responds to table data changes, not necessarily new volume files. C:A scheduled trigger starts on time, regardless of whether files arrived.
Question 260 A downstream task must run whenever a source Unity Catalog table is updated. Which trigger is most relevant? Table update trigger A fixed cron schedule regardless of data changes Use a file-arrival trigger on the table’s underlying Delta data directory instead of a table-update trigger File arrival trigger Explanation Correct Answer A:A table update trigger starts the job in response to supported changes to monitored tables. Incorrect Answers B:A clock trigger cannot guarantee alignment with the actual table update. C:Physical file-arrival events do not establish the logical governed table update semantics requested for an upstream table. D:A file-arrival trigger observes storage objects, not the requested table update event.