A project lead turning a proof of concept into a governed process finds that a previous optimization pass hid several business rules inside generated wrapper classes to make the top-level code look tidier. What is wrong with this?
Select an answer to reveal the explanation.
Short Explanation
You don't win by making the top level look tidy while burying the business rules where nobody wants to dig. That hides the logic maintainers need to find and understand, so it hurts maintainability instead of helping.
Full Explanation
The right answer is that obscuring logic maintainers need to find and understand trades apparent tidiness for reduced maintainability—the opposite of optimization. Optimization should make important logic easier to locate and reason about; burying business rules in a wrapper to tidy the surface makes code harder to maintain.
Wrapper classes are not prohibited in Java; they are a normal, legitimate pattern.
Business rules do not execute more slowly merely because they are inside a wrapper class.
Build tooling can compile logic in wrapper classes just like any other class.
For the exam, judge optimization by whether logic is easier to find, not by how tidy the surface looks.