Question
When should a Java developer choose Polymorphism, Overloading, and Overriding deliberately?
- Use overriding when callers should rely on one contract while different implementations supply the behavior.
- Choose Polymorphism, Overloading, and Overriding mainly when you want to postpone validation and fix problems manually later.
- Choose Polymorphism, Overloading, and Overriding whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Polymorphism, Overloading, and Overriding only to avoid modeling domain rules explicitly in Java code.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: A. Use overriding when callers should rely on one contract while different implementations supply the behavior.
Use overriding when callers should rely on one contract while different implementations supply the behavior. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java