Why is grouping mainframe code by business capability preferred over grouping by raw code volume?
Select an answer to reveal the explanation.
Short Explanation
Group mainframe code by business capability because that reflects what the code actually does for the business. You get services that match how the organisation operates and evolves, not just bundles of lines.
Full Explanation
Business capability reflects what the code is for, producing services aligned with how the organisation operates and evolves. Capability-aligned services are easier to reason about, own, and evolve because they map to how the business is organised, unlike a bundle chosen purely by size. The volume-based grouping option claiming it compiles faster is incorrect because compile speed has no bearing on how service boundaries should be chosen. The option saying volume-based grouping is required by IBM watsonx Code Assistant for Z tooling is incorrect because the tooling does not impose a volume-based grouping requirement. The option saying business-capability grouping always produces fewer services overall is incorrect because capability grouping can produce more, fewer, or the same number of services depending on the application; count is not the point. For the exam, justify boundaries by capability, not by convenient size.