Object-oriented programming · interview question
Why can providing public setter methods for all fields in a class become a problem in production code?
Multiple choiceMediumchapter-3-curatedpremiumoopencapsulation
Answer and explanation
Correct answer
D. It can lead to an invalid object state
Why
Public setters allow external code to modify fields without any validation, which can result in an object being put into an invalid state, violating encapsulation principles.
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?