Question
When should a Java developer choose Reflection deliberately?
- Choose Reflection mainly when you want to postpone validation and fix problems manually later.
- Choose Reflection whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Reflection only to avoid modeling domain rules explicitly in Java code.
- Use reflection for framework infrastructure, metadata-driven tools, serialization, or dependency injection internals.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: D. Use reflection for framework infrastructure, metadata-driven tools, serialization, or dependency injection internals.
Use reflection for framework infrastructure, metadata-driven tools, serialization, or dependency injection internals. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java