Why does attempting transformation before components are configured fail unhelpfully?
Select an answer to reveal the explanation.
Short Explanation
You get an infrastructure error dressed up as a transformation failure, and the team starts inspecting COBOL. Check the component configuration first, because the workflow can't run when components are missing or unreachable.
Full Explanation
The workflow cannot run at all, and the resulting errors describe missing or unreachable components rather than anything about the code, so the team debugs the wrong problem. Running it against an unconfigured platform produces environment errors, and teams unfamiliar with the architecture often read them as source problems. The idea that it completes but produces uncompilable Java is wrong because no output is produced. The idea that COBOL source is modified in place is wrong because the source is not altered. The idea that it consumes the project's transformation quota is wrong because quota consumption is not the issue. For the exam, verify component status before diagnosing a workflow failure as a code problem.