Get App

Java: Which practice avoids a common mistake with Thread Lifecycle and Creation?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Thread Lifecycle and Creation?

  1. Ignore the Thread Lifecycle and Creation issue and rely on team discipline instead of APIs or contracts.
  2. Do not create an unbounded new thread per request or per small background action.
  3. Silence the Thread Lifecycle and Creation problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Thread Lifecycle and Creation 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 create an unbounded new thread per request or per small background action.

Do not create an unbounded new thread per request or per small background action. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java