Which of the following concerns is BEST addressed by defining job dependencies when creating job schedules?

Question

Options

• AThe jobs rely on manual data preparation
• BJob failure notifications are not sent in a timely manner
• CSubsequent jobs rely on unprocessed information
• DSubsequent jobs require additional approvals

• A
  5% (1)
• C
  89% (17)
• D
  5% (1)

Explanation

Defining job dependencies ensures that a subsequent job only executes after its predecessor has successfully completed, directly solving the problem of downstream jobs consuming data that hasn't been fully processed yet - which is exactly what option C describes.

Why the distractors are wrong:

• A (manual data preparation): Job dependencies govern automated sequencing between jobs, not whether data prep requires human intervention - that's a process design issue.
• B (failure notifications): Alerting and notification timing are handled by monitoring/alerting configurations, not dependency definitions.
• D (additional approvals): Approval workflows are an access control or change management concern, not a scheduling dependency concern.

Memory tip: Think of job dependencies as a "traffic light" system - downstream jobs are held at red until the upstream job turns green (completes successfully). If you see a question about jobs consuming unfinished or stale output, the answer almost always points to missing dependencies.

No community discussion yet for this question.