Question
When should a Java developer choose Encapsulation deliberately?
- Use encapsulation when an object's state has rules that must stay valid across its lifetime.
- Choose Encapsulation mainly when you want to postpone validation and fix problems manually later.
- Choose Encapsulation whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Encapsulation 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: A. Use encapsulation when an object's state has rules that must stay valid across its lifetime.
Use encapsulation when an object's state has rules that must stay valid across its lifetime. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java