Question
Which practice avoids a common mistake with Lambdas and Functional Interfaces?
- Ignore the Lambdas and Functional Interfaces issue and rely on team discipline instead of APIs or contracts.
- Silence the Lambdas and Functional Interfaces problem by using raw types, broad catches, or shared mutable state.
- Do not hide complex business rules inside large lambda bodies where debugging and naming become harder.
- Prefer the version of Lambdas and Functional Interfaces that makes behavior less predictable as long as the code compiles.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: C. Do not hide complex business rules inside large lambda bodies where debugging and naming become harder.
Do not hide complex business rules inside large lambda bodies where debugging and naming become harder. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java