How encapsulation differs from abstraction

Transcript

This daily challenge question caught people out: why do classes keep fields private?

Encapsulation bundles data with methods. Inside BankAccount, your balance is private, so a negative deposit gets refused before touching the internal state.

Without encapsulation, outside code can change data directly and bypass validation. But with private fields, every deposit must strictly follow your class rules.

Here is the key idea: abstraction shows what an object does and hides how, while encapsulation binds data with methods to block changes directly.

So, a List interface hides whether nodes or arrays run underneath, while a BankAccount hides its balance to refuse any illegal updates safely.

Now, keeping fields private and exposing behaviour only through methods is an example of what? Pause the video right now and pick your option.

The correct option is D, encapsulation. Option A is wrong because inheritance focuses on sharing code through a class hierarchy, not data protection.

Encapsulation protects data, while abstraction hides implementation. Save this to revise before your semester exams, and practice core concepts daily on InternDoor.