Quick study sessions to strengthen memory and retain key concepts.
What happens if `CartItem` directly modifies `Product`?
It breaks encapsulation and can lead to inconsistency. Directly modifying a `Product` from a `CartItem` violates encapsulation and…
View Card →Why should a `CartItem` use `Product` methods?
Using `Product` methods maintains encapsulation. Encapsulation ensures that an object's internal state is protected and can only be…
View Card →How do objects share data in Java?
Objects share data by calling methods on each other. In Java, objects share data by invoking methods on…
View Card →How would you explain a common mistake when designing object interactions in an interview?
Directly accessing and modifying another object's fields. A common mistake is allowing one object to directly modify another's…
View Card →How does information flow between `CartItem` and `Product`?
Through method calls and references. Frame the concept in practical terms so you can explain it during interview…
View Card →Why is method encapsulation important in object interaction?
It protects object data and simplifies interaction. Encapsulation ensures that objects control their data through methods, preventing unwanted…
View Card →How are objects created in Java?
Using the `new` keyword. Frame the concept in practical terms so you can explain it during interview discussion.…
View Card →Why might a `Product` class use a getter method?
To provide controlled access to its fields. Getter methods allow controlled access to private fields, maintaining encapsulation. For…
View Card →What design flaw exists if a `User` class directly accesses `ShoppingCart`'s item list?
It breaks encapsulation, leading to tight coupling. Directly accessing another object's internals, like a list of items in…
View Card →How do you identify awkward interaction patterns in object designs?
Look for excessive direct access to another object's fields. Awkward interaction patterns often occur when objects access each…
View Card →