Object-oriented programming · interview question
Why are public mutable fields risky in a store model?
Multiple choiceEasychapter-3-curatedpremiumoopencapsulation
Answer and explanation
Correct answer
A. Any caller can push the object into invalid business state
Why
If outside code can assign any value directly, the object cannot defend its own rules. Encapsulation matters because it protects the truth of the model, not just because private fields look cleaner.
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 can generating getters and setters for every field in a class become a problem in production code?