Java: Which practice avoids a common mistake with List, Set, and Map?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with List, Set, and Map?

  1. Ignore the List, Set, and Map issue and rely on team discipline instead of APIs or contracts.
  2. Silence the List, Set, and Map problem by using raw types, broad catches, or shared mutable state.
  3. Prefer the version of List, Set, and Map that makes behavior less predictable as long as the code compiles.
  4. Do not default to ArrayList when the real requirement is uniqueness or key-based retrieval.

Hint

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

Answer and rationale

Correct answer: D. Do not default to ArrayList when the real requirement is uniqueness or key-based retrieval.

Do not default to ArrayList when the real requirement is uniqueness or key-based retrieval. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java