Home / Data Engineer Associate / Objective 4.1

Domain 4: Working with Lakeflow Jobs · 16% of the exam · Full exam outline

4.1 Implement control flows (retries and conditional tasks such as branching and looping) using Lakeflow Jobs for pipeline orchestration

Practice questions

Question 1easy

A data engineer must run one ingestion notebook 30 times inside a single Lakeflow Jobs job, once per source system, with each run receiving a different source system name. Which task setup fits this requirement?

Included in Sample: sample every domain.See plans

Choose an answer to check it. Afterward, select any option to review its explanation.

Schedules decide when a job starts, not how a task iterates over values inside one run. The requirement is a loop within a single job run.

Retries rerun a task only after it fails and reuse the same parameters, so they cannot hand each attempt a different source system name.

The For each task loops over an input array and runs its nested task once per element, passing that element as the iteration's parameters, which is exactly one notebook run per source system.

If/else is tempting because it reads a parameter, but it evaluates one boolean expression and picks a branch. It does not repeat a task for a list of values.

Question 2easy

An engineer adds a new task below an If/else condition task named check_rows and leaves the new task's Depends on field at its default value. Under which outcome of check_rows does the new task run?

Included in Master: master every domain.See plans