Object-oriented programming · interview question
What can be a consequence of poor field design in a Java class?
Multiple choiceHardchapter-2-curatedpremiumoopfields-and-state
Answer and explanation
Correct answer
B. Increased risk of bugs and maintenance difficulties
Why
Poor field design, such as using public fields or not encapsulating properly, can lead to bugs and maintenance difficulties. It makes it harder to enforce invariants, validate changes, and can lead to unexpected side effects in methods.
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?