Which statement best captures how cohesive modules should be identified when discovering an existing mainframe application?

The correct statement is the one that analyses business capability and dependencies together, so services group logic that belongs together and reflects how it depends on other logic. Combining what the code does with what it depends on is what identifies genuinely cohesive groupings, rather than groupings that are merely convenient or incidental. Splitting the codebase into equal-sized files for convenience is incorrect because equal size has no relationship to functional cohesion. Grouping any code that references the same copybook, regardless of purpose, is incorrect because shared copybook use does not imply shared purpose. Letting each engineer draw boundaries according to personal style is incorrect because personal style produces inconsistent, unjustifiable results. For the exam, name both capability and dependency analysis together as the basis for module identification.