Get App

Java: What deeper point about Inheritance vs Composition should a senior Java developer mention?

Difficulty:

Hard

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

What deeper point about Inheritance vs Composition should a senior Java developer mention?

  1. Inheritance increases fragile-base-class risk because parent changes can quietly alter subclass behavior in production.
  2. At senior level, the right answer is that Inheritance vs Composition exists mostly for historical syntax reasons.
  3. At senior level, the JVM removes the tradeoffs around Inheritance vs Composition, so design choices barely matter.
  4. At senior level, any approach to Inheritance vs Composition is equally correct if it compiles and passes a small test.

Hint

Look beyond syntax and explain the runtime, API, or design consequence.

Answer and rationale

Correct answer: A. Inheritance increases fragile-base-class risk because parent changes can quietly alter subclass behavior in production.

Inheritance increases fragile-base-class risk because parent changes can quietly alter subclass behavior in production. This is the kind of tradeoff-aware answer senior interviews usually expect.

Track: Java