Java: What deeper point about Abstraction should a senior Java developer mention?

Difficulty:

Hard

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

What deeper point about Abstraction should a senior Java developer mention?

  1. At senior level, the right answer is that Abstraction exists mostly for historical syntax reasons.
  2. At senior level, the JVM removes the tradeoffs around Abstraction, so design choices barely matter.
  3. At senior level, any approach to Abstraction is equally correct if it compiles and passes a small test.
  4. Useful abstractions reduce coupling only when the contract matches stable business behavior rather than speculative flexibility.

Hint

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

Answer and rationale

Correct answer: D. Useful abstractions reduce coupling only when the contract matches stable business behavior rather than speculative flexibility.

Useful abstractions reduce coupling only when the contract matches stable business behavior rather than speculative flexibility. This is the kind of tradeoff-aware answer senior interviews usually expect.

Track: Java