Get App

Java: Which practice avoids a common mistake with Encapsulation?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Encapsulation?

  1. Ignore the Encapsulation issue and rely on team discipline instead of APIs or contracts.
  2. Avoid generating public setters for every field when some state changes require validation or coordinated updates.
  3. Silence the Encapsulation problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Encapsulation that makes behavior less predictable as long as the code compiles.

Hint

Look for the option that protects correctness instead of hiding the problem.

Answer and rationale

Correct answer: B. Avoid generating public setters for every field when some state changes require validation or coordinated updates.

Avoid generating public setters for every field when some state changes require validation or coordinated updates. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java