Object-oriented programming · interview question
Why doesn't every field deserve a setter?
Multiple choiceEasychapter-3-curatedpremiumoopgetters-and-setters-design
Answer and explanation
Correct answer
A. Because every setter creates a write path that may bypass better domain methods
Why
A getter often just reveals information, but a setter opens a way to change state. Many fields are safer behind meaningful methods like changeQuantity(...) or reserve(...) instead of a generic write-anything path.
Test yourself on Object-oriented programming
A free test with instant, explained results. No account needed.
More Object-oriented programming questions
- Why does declaring a method as 'final' in a superclass change runtime behavior?
- Why might a developer choose to use a 'restock' method rather than a public setter for inventory?
- How do unmodifiable views differ from defensive copies in protecting internal collections?
- In an e-commerce application, what is the advantage of using a 'processOrder' method in a Product class?
- Which statement is true about interfaces in Java?
- Why are public mutable fields risky in a store model?