A pilot includes a rewrite of a shared utility program with no clear caller or business owner identified. What is the risk in transforming it now?
Select an answer to reveal the explanation.
Short Explanation
If you transform a utility without a known caller or owner, you can't tell whether you preserved the right behavior or whether it was worth doing. You need a real use case to judge value and correctness.
Full Explanation
The correct answer is the option saying that without a known use case or dependency context, there is no basis for judging whether the transformation delivers value or whether its behaviour has been correctly preserved for its actual callers. Value and correctness both depend on knowing how a module is actually used; without an identified use case there is nothing to validate the transformation against. The option saying utility programs cannot be transformed by the tooling under any circumstances is incorrect because utilities can be transformed once their context is understood. The option saying shared utilities always run faster once transformed is incorrect because performance depends on code and workload, not category. The option saying transformation automatically identifies and documents every caller is incorrect because tooling does not discover business context automatically; that must happen beforehand. For the exam, flag missing use-case context as a reason to hold a module out of scope.