Reflection API · interview question
Why cache reflective metadata into route registries or handler objects after startup?
Multiple choiceHardchapter-16-curatedpremiumreflection-apimethod-invoke
Answer and explanation
Correct answer
A. It avoids repeated lookups and keeps the request path simpler and more stable
Why
Scanning and resolving reflective metadata repeatedly adds overhead and complexity. Caching the result in stable handler objects keeps runtime dispatch faster and easier to reason about.
Test yourself on Reflection API
A free test with instant, explained results. No account needed.
More Reflection API questions
- Given using Class.forName("com.example.MyClass") in Java, what outcome should you expect?
- Which method would you use to check if a class is an interface using Reflection?
- In what scenario would you prefer reflection for method invocation over direct method calls?
- Which of the following is NOT a drawback of using Java Reflection?
- If you use Method.invoke() to call a private method, what must you do first?
- How does Java's reflection API impact type safety?