Moderate Orchestration Question 125 of 221

How should a training DAG handle a mid-job failure?

MLOps track · Speak this in 60–90 seconds · Faridabad & Delhi NCR

PICTURE THIS: DATA SPLIT

Train 70%Val 15%Test 15%

Fit on train, tune on val, report on test once.

Simple meaning

Make steps idempotent, checkpoint weights, and retry from the last successful stage rather than restarting a six-hour fit.

WHY — Orchestration instead of guessing?

Why interviewers care about Orchestration:

Orchestration questions separate people

who only read docs from people who shipped.

Keep it short, concrete,

and tied to MLOps work.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

STEPS — What happens step by step?

Before you speak the answer, walk the interviewer through these steps:

1
Make steps idempotent, checkpoint
weights, and retry from the last successful stage rather than restarting a six-hour fit.
2
Persist intermediate artifacts in
object storage.
3
Alert on repeated failure
so you do not silently skip the daily champion refresh.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

EXAMPLE — See it in action

Here's a short line you can speak, broken into clear beats:

Say this line

“Persist intermediate artifacts in object storage.”

Break into beats

Persistintermediateartifactsinobjectstorage

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Key takeaway

Make steps idempotent, checkpoint weights, and retry from the last successful stage rather than restarting a six-hour fit. Persist intermediate artifacts in object storage.