Reflection API · interview question
When using MethodHandle.invokeExact, why is it necessary to match the method signature exactly?
Multiple choiceHardchapter-16-curatedpremiumreflection-apimethodhandles
Answer and explanation
Correct answer
D. Because it bypasses type checks at runtime.
Why
MethodHandle.invokeExact enforces strict type matching, meaning the caller must provide arguments and a return type that match the MethodType exactly, as it bypasses the type checks typically performed at runtime for performance reasons.
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?