Object-oriented programming · interview question
Why is it generally a bad idea to expose a class's internal fields as public?
Multiple choiceMediumchapter-3-curatedpremiumoopencapsulation
Answer and explanation
Correct answer
A. It breaks encapsulation by allowing uncontrolled access
Why
Having public fields allows external code to change an object's state without validation, breaking the encapsulation principle and potentially leading to inconsistent or invalid states.
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?