On what basis should cohesive modules or services be identified in a discovered mainframe application?
Select an answer to reveal the explanation.
Short Explanation
You should group code by the business capability it supports and the real dependencies it shares. File size, incidental file access, and developer preference don't make a module cohesive.
Full Explanation
Cohesive modules or services should be identified by business capability and dependency analysis, grouping the code that implements a related function and shares real relationships. This approach makes boundaries meaningful and maintainable because they reflect what the application does and how components actually depend on one another. Splitting programs into equally sized chunks based on line count is incorrect because equal-sized chunks ignore whether the code inside a chunk belongs together at all. Grouping transactions only because they share file access is incorrect because sharing a file is often incidental and does not imply the transactions are functionally related. Letting individual developer preference choose boundaries is incorrect because personal preference produces inconsistent, unjustifiable boundaries across the codebase. For the exam, tie module boundaries to business capability plus dependency evidence.