A customer proposes creating a separate service for every copybook in their mainframe application. Why should a consultant push back?
Select an answer to reveal the explanation.
Short Explanation
Copybooks describe data, not a business function. One copybook can sit inside several unrelated capabilities, so you can't use it as a reliable service boundary.
Full Explanation
The correct answer is that copybooks are data structure definitions, not business capabilities, so splitting by copybook does not reliably isolate cohesive functionality. Copybooks are shared data definitions and can be used across many different business functions, so a service boundary drawn around one does not correspond to a cohesive capability. The claim that copybooks cannot be referenced by more than one program is incorrect because copybooks are commonly shared across multiple programs, which is part of why splitting by copybook is unreliable. The claim that creating multiple services always violates licensing terms for the source platform is incorrect because service count is a design decision, not a licensing matter. The claim that copybooks are automatically deleted once a service is generated from them is incorrect because generating a service from a copybook does not remove the copybook itself. For the exam, distinguish a data structure from a business capability when choosing boundaries.