Get App

Java: Which practice avoids a common mistake with StringBuilder vs StringBuffer?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with StringBuilder vs StringBuffer?

  1. Ignore the StringBuilder vs StringBuffer issue and rely on team discipline instead of APIs or contracts.
  2. Avoid repeated string concatenation in tight loops when a mutable builder better expresses the workload.
  3. Silence the StringBuilder vs StringBuffer problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of StringBuilder vs StringBuffer 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. Avoid repeated string concatenation in tight loops when a mutable builder better expresses the workload.

Avoid repeated string concatenation in tight loops when a mutable builder better expresses the workload. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java