Once a pilot deployment issue has been fixed, preventing the same class of problem from recurring in the next phase becomes the priority. Which practice should be adopted?
Select an answer to reveal the explanation.
Short Explanation
The fix for a missed dependency is more discovery, not less. You need to map dependencies, data flows, and transactions across the next candidate programs before drawing modernisation boundaries.
Full Explanation
Complete discovery of dependencies, data flows and transactions across the next candidate programs before drawing modernisation boundaries is correct. The pilot's failure traces back to an incomplete picture of dependencies and data flow; avoid repeating it by doing that analysis thoroughly for the next candidates, not skipping it. Relying on the team's existing familiarity with the codebase instead of running discovery again is incorrect because informal familiarity is exactly what led to the gap the pilot exposed. Assuming that programs with similar names behave similarly and skipping individual analysis is incorrect because similar names do not imply similar behaviour, as the pilot itself demonstrated. Selecting the next phase's programs purely by size, smallest first, is incorrect because size, on its own, was never a reliable prioritisation signal. For the exam, a missed dependency is resolved by strengthening discovery, not bypassing it.