Get App

Java: Which practice avoids a common mistake with Class Loading and Initialization?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Class Loading and Initialization?

  1. Ignore the Class Loading and Initialization issue and rely on team discipline instead of APIs or contracts.
  2. Do not assume a type is fully initialized just because the compiler can see its name in source code.
  3. Silence the Class Loading and Initialization problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Class Loading and Initialization 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 assume a type is fully initialized just because the compiler can see its name in source code.

Do not assume a type is fully initialized just because the compiler can see its name in source code. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java