Question
When should a Java developer choose static, final, and Initialization deliberately?
- Choose static, final, and Initialization mainly when you want to postpone validation and fix problems manually later.
- Use static methods for stateless utilities or factories that do not depend on object-specific data.
- Choose static, final, and Initialization whenever you want the code to look more advanced, even if the design gets less clear.
- Choose static, final, and Initialization only to avoid modeling domain rules explicitly in Java code.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: B. Use static methods for stateless utilities or factories that do not depend on object-specific data.
Use static methods for stateless utilities or factories that do not depend on object-specific data. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java