Object-oriented programming · interview question
In the context of a Customer class, why might exposing an email field with a public setter be problematic?
Multiple choiceHardchapter-3-curatedpremiumoopgetters-and-setters-design
Answer and explanation
Correct answer
B. It allows inconsistent state by enabling uncontrolled changes.
Why
A public setter for an email field allows uncontrolled changes, which can lead to inconsistent state if not validated properly. A method that validates the email before setting it is often a better approach.
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?