Object-oriented programming · interview question
How would you explain a potential risk of exposing internal mutable collections directly in an interview?
Multiple choiceMediumchapter-3-curatedpremiumoopdefensive-copying
Answer and explanation
Correct answer
C. They might be modified outside the class, breaking encapsulation
Why
Exposing internal mutable collections directly allows external code to modify them, which can break encapsulation and potentially lead 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?