Get App

Java: Which practice avoids a common mistake with Primitive Types and Wrappers?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Primitive Types and Wrappers?

  1. Ignore the Primitive Types and Wrappers issue and rely on team discipline instead of APIs or contracts.
  2. Silence the Primitive Types and Wrappers problem by using raw types, broad catches, or shared mutable state.
  3. Prefer the version of Primitive Types and Wrappers that makes behavior less predictable as long as the code compiles.
  4. Avoid comparing wrapper objects with == when you actually mean value equality.

Hint

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

Answer and rationale

Correct answer: D. Avoid comparing wrapper objects with == when you actually mean value equality.

Avoid comparing wrapper objects with == when you actually mean value equality. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java