Object-oriented programming · interview question
Why can setting all fields in a Java class to public become a problem in practice?
Multiple choiceHardchapter-2-curatedpremiumoopfields-and-state
Answer and explanation
Correct answer
A. It breaks encapsulation and can lead to unintended modifications
Why
Public fields allow any class to modify the object's state directly, which breaks encapsulation principles and can lead to unintended changes, making the system harder to maintain and debug.
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?