Get App

Java: Which practice avoids a common mistake with Annotations?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Annotations?

  1. Ignore the Annotations issue and rely on team discipline instead of APIs or contracts.
  2. Silence the Annotations problem by using raw types, broad catches, or shared mutable state.
  3. Prefer the version of Annotations that makes behavior less predictable as long as the code compiles.
  4. Do not hide critical business behavior behind annotation magic that the team cannot trace or reason about.

Hint

Look for the option that protects correctness instead of hiding the problem.

Answer and rationale

Correct answer: D. Do not hide critical business behavior behind annotation magic that the team cannot trace or reason about.

Do not hide critical business behavior behind annotation magic that the team cannot trace or reason about. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java