In a pilot deployment, a modernised component keeps failing because a dependency it relies on was never migrated. What was skipped?
Select an answer to reveal the explanation.
Short Explanation
You skipped the discovery work that maps dependencies before drawing a modernisation boundary. Without that map, you can miss a dependency until the component fails in a pilot.
Full Explanation
The correct answer is the discovery work to map dependencies before committing to a modernisation boundary around the component. A dependency surfacing only after deployment indicates it was not identified during discovery, which means the modernisation boundary was drawn on incomplete information.
The option saying nothing was skipped and that missing dependencies are unavoidable is incorrect because this class of failure is largely avoidable with thorough upfront dependency analysis.
The option pointing to the component's user interface testing is incorrect because interface testing would not have caught a missing backend dependency.
The option pointing to performance testing under peak transaction load is incorrect because a missing dependency is a functional gap, not a load-related performance issue.
For the exam, missing dependencies discovered post-deployment point back to inadequate discovery, not bad luck.