Java: Which practice avoids a common mistake with Prefix Sums on Arrays?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Prefix Sums on Arrays?

  1. Ignore the Prefix Sums on Arrays issue and rely on team discipline instead of APIs or contracts.
  2. Silence the Prefix Sums on Arrays problem by using raw types, broad catches, or shared mutable state.
  3. Do not lose track of the zero-boundary case when turning an inclusive range into prefix subtraction.
  4. Prefer the version of Prefix Sums on Arrays 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: C. Do not lose track of the zero-boundary case when turning an inclusive range into prefix subtraction.

Do not lose track of the zero-boundary case when turning an inclusive range into prefix subtraction. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java