Object-oriented programming · interview question
When is immutability often a strong choice?
Multiple choiceMediumchapter-3-curatedpremiumoopimmutability-basics
Answer and explanation
Correct answer
A. When a value-like object should not change after creation
Why
Immutability is useful for value-like data such as customer profiles, IDs, or snapshots that are safer when they never change. It removes whole categories of mutation-related bugs.
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?