Get App

Java: Which practice avoids a common mistake with Reflection?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Reflection?

  1. Do not use reflection in hot paths or as a replacement for sensible API and domain design.
  2. Ignore the Reflection issue and rely on team discipline instead of APIs or contracts.
  3. Silence the Reflection problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Reflection 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 use reflection in hot paths or as a replacement for sensible API and domain design.

Do not use reflection in hot paths or as a replacement for sensible API and domain design. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java