What is encapsulation primarily protecting?

What is encapsulation primarily protecting?

• A. Invariants and internal state; it also defines a clear interface
• B. It exposes internal state publicly
• C. It eliminates the need for interfaces
• D. It makes all fields public

Answer: (A)

Encapsulation is about hiding the object's internal state and details, and exposing a controlled, well-defined interface to interact with it. By keeping data private and offering public methods to modify or read that data, the object can maintain its invariants—rules that must always hold true for the object to be valid. This protective boundary lets the object validate inputs, enforce constraints, and ensure state changes happen in a consistent, predictable way. It also lets you change how the internal state is stored or implemented without forcing every user of the class to change their code, as long as the public interface remains the same. For example, think of a bank account with a balance. If the balance is private and you provide deposit and withdraw methods, these methods can check for overdraws or invalid amounts, keeping the account in a valid state. Exposing the balance directly would let anyone set it to an invalid value, breaking invariants. So, the best choice highlights protecting invariants and internal state while defining a clear interface for interaction. The other ideas—exposing internal state publicly, eliminating the need for interfaces, or making all fields public—do not align with encapsulation’s purpose of hiding implementation details and safeguarding the object's valid states.

Encapsulation is about hiding the object's internal state and details, and exposing a controlled, well-defined interface to interact with it. By keeping data private and offering public methods to modify or read that data, the object can maintain its invariants—rules that must always hold true for the object to be valid. This protective boundary lets the object validate inputs, enforce constraints, and ensure state changes happen in a consistent, predictable way. It also lets you change how the internal state is stored or implemented without forcing every user of the class to change their code, as long as the public interface remains the same.

For example, think of a bank account with a balance. If the balance is private and you provide deposit and withdraw methods, these methods can check for overdraws or invalid amounts, keeping the account in a valid state. Exposing the balance directly would let anyone set it to an invalid value, breaking invariants.

So, the best choice highlights protecting invariants and internal state while defining a clear interface for interaction. The other ideas—exposing internal state publicly, eliminating the need for interfaces, or making all fields public—do not align with encapsulation’s purpose of hiding implementation details and safeguarding the object's valid states.