Get App

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

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Streams Basics?

  1. Ignore the Streams Basics issue and rely on team discipline instead of APIs or contracts.
  2. Silence the Streams Basics problem by using raw types, broad catches, or shared mutable state.
  3. Prefer the version of Streams Basics that makes behavior less predictable as long as the code compiles.
  4. Do not force streams into workflows that need complex branching, stepwise mutation, or heavy side effects.

Hint

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

Answer and rationale

Correct answer: D. Do not force streams into workflows that need complex branching, stepwise mutation, or heavy side effects.

Do not force streams into workflows that need complex branching, stepwise mutation, or heavy side effects. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java