Core Java · interview question
How would you explain a potential issue with a class design where most fields are set to public in an e-commerce application in an interview?
Multiple choiceHardchapter-2-curatedpremiumcore-javacode-reading-and-refactoring-to-objects
Answer and explanation
Correct answer
C. It breaks encapsulation and makes the class harder to maintain.
Why
Setting most fields to public breaks encapsulation, exposing the internal state of the class and making it harder to maintain. This design can lead to unintended interactions and makes future changes to the class more difficult.
Test yourself on Core Java
A free test with instant, explained results. No account needed.
More Core Java questions
- What does executing a throw statement inside a catch block evaluate to?
- In Java, what happens if an exception is thrown in a method and not caught within that method?
- Which method would you use to add an element to a List at a specific position?
- Consider the following code snippet. What is the issue with the 'applyDiscount' method?
- How do you correctly initialize a BigDecimal to represent the monetary value 50.75?
- Why might using == with Integer objects sometimes return false even if they have the same value?