Object-oriented programming · interview question
In designing a 'Customer' class, which field should ideally be immutable?
Multiple choiceHardchapter-2-curatedpremiumoopfields-and-state
Answer and explanation
Correct answer
A. Customer ID
Why
The 'Customer ID' is typically immutable as it uniquely identifies the customer and should not change once assigned. Keeping it immutable ensures consistency in identifying the customer across different systems and processes.
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?