Quick study sessions to strengthen memory and retain key concepts.
Why should fields typically be private in Java classes?
To protect the object's internal state from external changes. Private fields restrict direct access from outside the class,…
View Card →Why does immutable objects in Java help in practice?
They are inherently thread-safe. Frame the concept in practical terms so you can explain it during interview discussion.…
View Card →How can you make a class with collections immutable?
Use unmodifiable wrappers or defensive copying. To ensure a class with collections is immutable, use Collections.unmodifiableList() or create…
View Card →When should you avoid using setter methods?
In immutable classes, to prevent state changes. In Java, setter methods allow modification of an object's state. In…
View Card →What's the difference between immutability and encapsulation?
Immutability prevents change; encapsulation controls access. Immutability ensures an object's state cannot change after creation, while encapsulation restricts…
View Card →How does immutability help in handling customer profiles?
It ensures data integrity by preventing accidental changes. An immutable customer profile guarantees that once a profile is…
View Card →Why does encapsulation matter when enforcing domain rules?
It lets an object guard its own invariants instead of trusting every caller to update state correctly. Chapter…
View Card →What does declaring a field as 'final' mean in Java?
A final field cannot be reassigned after it's initialized. In Java, a final field is a constant for…
View Card →When is immutability a strong design choice?
When the object represents data that should not change after creation. IDs, profiles, and snapshots are often easier…
View Card →What are the tradeoffs in exposing a large API surface?
A large API surface increases complexity and potential for error. Exposing a large API surface in a class…
View Card →