Get App

Java: Which practice avoids a common mistake with Parallel Streams?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Parallel Streams?

  1. Ignore the Parallel Streams issue and rely on team discipline instead of APIs or contracts.
  2. Do not combine parallel streams with shared mutable state and still expect deterministic, safe behavior.
  3. Silence the Parallel Streams problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Parallel Streams 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 combine parallel streams with shared mutable state and still expect deterministic, safe behavior.

Do not combine parallel streams with shared mutable state and still expect deterministic, safe behavior. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java