Turning a proof of concept into a governed refactoring effort, the plan calls for moving straight to producing deployment artifacts. What step is being skipped?
Select an answer to reveal the explanation.
Short Explanation
Jumping straight to deployment artifacts skips the analysis and review that tell you whether the components are even right. You need to analyze the application, select candidate modules, and review them before you generate anything for deployment.
Full Explanation
The correct choice is analyzing the application and selecting and reviewing candidate modular components before any deployment artifact is generated. The proof of concept demonstrates feasibility on a narrow slice; it does not substitute for analyzing the full application, selecting appropriate component boundaries, and reviewing them before anything is generated for deployment. The option saying nothing is skipped, because deployment artifacts can be produced directly once a proof of concept exists, is wrong because it bypasses validation of component boundaries. The option saying only the final review is skipped and can be done after deployment is wrong because review belongs before generation, not after deployment when mistakes are costlier. The option saying only analysis is skipped because a proof of concept is sufficient analysis is wrong because the narrow scope of a proof of concept does not cover analysis across the full application. For the exam, deployment artifacts should follow analysis, selection and review, never precede them.