Java Interview Questions · interview question

Which practice avoids a common mistake with Interface vs Abstract Class?

Multiple choiceMediumjava-interview-2026interviewjavapitfall

Prefer the version of Interface vs Abstract Class that makes behavior less predictable as long as the code compiles.Do not push mutable shared state into an abstract base type unless every subclass genuinely owns that state.Silence the Interface vs Abstract Class problem by using raw types, broad catches, or shared mutable state.Ignore the Interface vs Abstract Class issue and rely on team discipline instead of APIs or contracts.

Answer and explanation

Correct answer

B. Do not push mutable shared state into an abstract base type unless every subclass genuinely owns that state.

Why

Do not push mutable shared state into an abstract base type unless every subclass genuinely owns that state. This is a common failure mode in real Java code and a frequent interview follow-up.

Test yourself on Java Interview Questions

A free test with instant, explained results. No account needed.

Start free test

All Java Interview Questions questions →

Which practice avoids a common mistake with Interface vs Abstract Class?

Correct answer

Why

More Java Interview Questions questions