Core Java · interview question
Consider a class Customer with a method addToOrderHistory(Product product). Which aspect of this design could indicate a need for refactoring?
Multiple choiceMediumchapter-2-curatedpremiumcore-javacode-reading-and-refactoring-to-objects
Answer and explanation
Correct answer
B. The method modifies the customer's private order history list directly.
Why
Accessing and modifying private fields directly within a method can lead to fragile code. Encapsulation should be used to manage access, which may involve using getters and setters or other methods.
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?