Object-oriented programming · interview question
Which scenario might justify exposing a public setter for a 'description' field in a Product class?
Multiple choiceHardchapter-3-curatedpremiumoopgetters-and-setters-design
Answer and explanation
Correct answer
C. When frequent updates are required from different modules.
Why
A public setter could be justified if multiple modules need to update the 'description' field frequently and the field does not require complex validation or business logic, allowing for flexibility in data entry.
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?