Get App

Java: Which practice avoids a common mistake with Design Patterns and SOLID?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Design Patterns and SOLID?

  1. Do not force a pattern onto simple code when composition and plain objects already communicate the solution clearly.
  2. Ignore the Design Patterns and SOLID issue and rely on team discipline instead of APIs or contracts.
  3. Silence the Design Patterns and SOLID problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Design Patterns and SOLID 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 force a pattern onto simple code when composition and plain objects already communicate the solution clearly.

Do not force a pattern onto simple code when composition and plain objects already communicate the solution clearly. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java