Spring Core · interview question
How would you explain a potential risk of using field injection instead of constructor injection in a Spring-managed transactional service in an interview?
Multiple choiceHardchapter-9-curatedpremiumspring-coretransactions-and-proxies
Answer and explanation
Correct answer
B. Uninitialized fields at runtime
Why
Field injection can lead to issues where dependencies are not properly initialized before use, especially in transactional contexts. Constructor injection enforces initialization order, reducing this risk.
Test yourself on Spring Core
A free test with instant, explained results. No account needed.
More Spring Core questions
- In a Spring Boot application, what happens if a method annotated with @Transactional calls a private method also…
- Which layer should coordinate inventory checks, payment, and order persistence for a checkout request?
- What role do Entities typically play in a Spring Boot application?
- How can you externalize configuration in a Spring Boot application?
- Which issue might arise from using field injection in Spring Boot, particularly when managing dependencies?
- In a Spring Boot application, what is the main purpose of the @ComponentScan annotation?