Object-oriented programming · interview question
In a Java class representing a product, why might you choose to make the 'price' field private with no public setter?
Multiple choiceEasychapter-3-curatedpremiumoopgetters-and-setters-design
Answer and explanation
Correct answer
D. To prevent unauthorized modifications.
Why
Making the 'price' field private with no public setter ensures that only controlled methods within the class can modify the price, maintaining data integrity and preventing unauthorized changes.
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?