Get App

Java: Which practice avoids a common mistake with Deadlocks and Race Conditions?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Deadlocks and Race Conditions?

  1. Do not debug concurrency only by rerunning until the issue disappears or becomes harder to reproduce.
  2. Ignore the Deadlocks and Race Conditions issue and rely on team discipline instead of APIs or contracts.
  3. Silence the Deadlocks and Race Conditions problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Deadlocks and Race Conditions 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: A. Do not debug concurrency only by rerunning until the issue disappears or becomes harder to reproduce.

Do not debug concurrency only by rerunning until the issue disappears or becomes harder to reproduce. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java