
DatabricksCertified Data Engineer Associate
Domain 4Objective 1
Implement Control Flows (retries and Conditional Tasks Such as Branching and Looping) Using Lakeflow Jobs for Pipeline Orchestration DATA-ENGINEER-ASSOCIATE Practice Questions (Page 2)
Part of the Working with Lakeflow Jobs domain, which accounts for 16% of the DATA-ENGINEER-ASSOCIATE exam. Databricks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~6–10 in this domain), expect 2–3 from this objective — we provide 12 practice questions to prepare you well beyond it. (estimate)
12questions here
3free pages
5concepts
16%of the exam
Questions 6–10
- 6
A data engineering team uses Lakeflow Jobs to orchestrate a nightly pipeline. After the 'ingest' task completes, they need to run a 'validate' task. If validation fails, they want to run a 'notify' task that sends an alert to the data team. If validation succeeds, they want to proceed directly to the 'publish' task. Which Lakeflow Jobs feature should they use to implement this logic?
Select an answer first - 7
In Lakeflow Jobs, what is the purpose of conditional branching?
Select an answer first - 8
A data engineering team has a Lakeflow Jobs pipeline with a 'load' task that can succeed, fail, or be skipped. They want to run a 'reconcile' task only if the 'load' task succeeds, and a 'cleanup' task if the 'load' task fails or is skipped. Which configuration should they use?
Select an answer first - 9
What is the primary benefit of using a looping construct in a Lakeflow Jobs pipeline?
Select an answer first - 10
A Lakeflow Jobs task sometimes fails with a specific exit code that indicates a transient issue, but other exit codes indicate permanent failures. Which feature allows the task to be retried only for that specific exit code?
Select an answer first
Finished these 5 questions?
Review the revealed explanations, or continue through the curriculum.
Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Databricks. “DATA-ENGINEER-ASSOCIATE” is a trademark of its owner, used for identification only.