In the following display, can status handling be enabled for both the Extract transformation and the Sort transformation?

Question

Exhibit

Options

• AYes. The Return Code Check transformation can be added to the job flow immediately
• BNo. Both the Extract and the Sort transformations do not have a Status Handling tab in their
• CYes. The Return Code Check transformation can be added to the job flow twice, once
• DYes. The status handling tab in the job properties window will allow you to select which

• A
  4% (2)
• B
  2% (1)
• C
  80% (37)
• D
  13% (6)

Explanation

Option C is correct because in this ETL job flow tool (likely IBM DataStage), the Return Code Check transformation is reusable - it can be inserted into the job flow multiple times, once immediately after the Extract transformation and once after the Sort transformation, independently capturing and evaluating the return/status code of each.

Why the distractors are wrong:

• A is wrong because adding the Return Code Check once (immediately, without specifying placement) would only capture status for one transformation, not both - it doesn't automatically cover the entire flow.
• B is wrong in its premise: the transformations can support status handling; the absence of a dedicated "Status Handling tab" doesn't mean status handling is impossible - it's handled externally via the Return Code Check transformation.
• D is wrong because there is no single job-level status handling tab that lets you select which transformation to monitor from one central location; handling must be wired individually in the flow.

Memory tip: Think of the Return Code Check as a reusable "checkpoint" block you snap into a pipeline - just like you can add multiple checkpoints on a highway, you can add multiple Return Code Check transformations, one per stage you want to monitor. One block = one monitored stage.

No community discussion yet for this question.