Get App

Java: What deeper point about Encapsulation should a senior Java developer mention?

Difficulty:

Hard

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

What deeper point about Encapsulation should a senior Java developer mention?

  1. At senior level, the right answer is that Encapsulation exists mostly for historical syntax reasons.
  2. At senior level, the JVM removes the tradeoffs around Encapsulation, so design choices barely matter.
  3. Encapsulation shrinks the bug surface because fewer call sites can push an object into an invalid or inconsistent state.
  4. At senior level, any approach to Encapsulation is equally correct if it compiles and passes a small test.

Hint

Look beyond syntax and explain the runtime, API, or design consequence.

Answer and rationale

Correct answer: C. Encapsulation shrinks the bug surface because fewer call sites can push an object into an invalid or inconsistent state.

Encapsulation shrinks the bug surface because fewer call sites can push an object into an invalid or inconsistent state. This is the kind of tradeoff-aware answer senior interviews usually expect.

Track: Java