Get App

Java: Which practice avoids a common mistake with Optional?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Optional?

  1. Ignore the Optional issue and rely on team discipline instead of APIs or contracts.
  2. Do not fill entities, DTOs, or every parameter with Optional just to avoid thinking about API boundaries carefully.
  3. Silence the Optional problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Optional 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. Do not fill entities, DTOs, or every parameter with Optional just to avoid thinking about API boundaries carefully.

Do not fill entities, DTOs, or every parameter with Optional just to avoid thinking about API boundaries carefully. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java