Get App

Java: In Java, which comparison about ConcurrentHashMap and Concurrent Collections is accurate?

Difficulty:

Easy

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

In Java, which comparison about ConcurrentHashMap and Concurrent Collections is accurate?

  1. There is no practical difference in behavior, performance, or API design when ConcurrentHashMap and Concurrent Collections is involved.
  2. It usually scales better than wrapping a plain HashMap with one synchronized lock around every access.
  3. The oldest option related to ConcurrentHashMap and Concurrent Collections is always the right production choice regardless of context.
  4. Differences around ConcurrentHashMap and Concurrent Collections are mostly cosmetic, so correctness and maintainability do not change.

Hint

Focus on the behavior or tradeoff, not just the keyword.

Answer and rationale

Correct answer: B. It usually scales better than wrapping a plain HashMap with one synchronized lock around every access.

It usually scales better than wrapping a plain HashMap with one synchronized lock around every access. This is the comparison that usually separates memorization from understanding.

Track: Java