Object-oriented programming · interview question
How would you explain a consequence of not using encapsulation in Java classes in an interview?
Multiple choiceMediumchapter-3-curatedpremiumoopcontrolled-mutation
Answer and explanation
Correct answer
D. Increased likelihood of bugs due to uncontrolled access
Why
Without encapsulation, fields can be modified from outside the class, leading to bugs and inconsistencies, as the internal state can be altered without any control or validation.
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?