Question
Which statement about Interface vs Abstract Class is the strongest interview answer?
- Interface vs Abstract Class is mostly a naming style choice and has little effect on runtime or design.
- Interfaces define capabilities, while abstract classes combine a contract with partial shared implementation.
- Interface vs Abstract Class exists mainly to reduce the number of Java files in a project.
- Interface vs Abstract Class matters only for frontend frameworks, not for core Java applications.
Hint
Start with the core rule behind Interface vs Abstract Class.
Answer and rationale
Correct answer: B. Interfaces define capabilities, while abstract classes combine a contract with partial shared implementation.
Interfaces define capabilities, while abstract classes combine a contract with partial shared implementation. This is the base concept interviewers commonly test first.
Track: Java