An administrator troubleshooting a pilot finds that a transformed utility program calls three other programs whose behaviour was never discovered or documented. What does this indicate about the selection that put it in scope?
Select an answer to reveal the explanation.
Short Explanation
Undiscovered callers surfacing mid-pilot tells you the module wasn't really ready for transformation. You need to know its dependencies before selecting it, or the pilot exposes gaps instead of proving readiness.
Full Explanation
Readiness for transformation depends on dependencies being known ahead of time; three undocumented calls surfacing during the pilot shows the selection went ahead before that understanding existed. The option saying the module's dependencies were not adequately understood before selection, so it was not actually ready despite being chosen, is correct. The option about transformation tooling failing to generate correct Java is incorrect because the finding is about missing discovery, not a tooling generation error. The option about the pilot environment lacking sufficient compute capacity is incorrect because capacity is unrelated to whether dependencies were documented. The option about the COBOL compiler being misconfigured is incorrect because a compiler configuration issue would not explain undocumented calling programs. For the exam, treat undiscovered dependencies surfacing mid-pilot as a selection-readiness gap.