Bird
0
0

Why is it recommended to use @ConditionalOnMissingBean in custom auto-configuration classes?

hard📝 Conceptual Q10 of 15
Spring Boot - Advanced Patterns
Why is it recommended to use @ConditionalOnMissingBean in custom auto-configuration classes?
ATo allow user-defined beans to override auto-configured beans
BTo speed up application startup time
CTo disable auto-configuration completely
DTo force creation of multiple beans of the same type
Step-by-Step Solution
Solution:

  1. Step 1: Understand purpose of @ConditionalOnMissingBean

    This annotation prevents auto-configuration from creating a bean if the user already defined one, allowing customization.

  2. Step 2: Check other options

    It does not speed startup, disable auto-config, or force multiple beans.

  3. Final Answer:

    To allow user-defined beans to override auto-configured beans -> Option A

  4. Quick Check:

    @ConditionalOnMissingBean enables user override [OK]
Quick Trick: Use @ConditionalOnMissingBean to let users override beans [OK]
Common Mistakes:
  • Thinking it disables auto-configuration
  • Assuming it creates multiple beans
  • Believing it improves startup speed

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Spring Boot Quizzes
API Documentation - @Parameter and @Schema annotations - Quiz 5medium Advanced Patterns - Feature flags concept - Quiz 4medium Aspect-Oriented Programming - @Aspect annotation - Quiz 11easy Async Processing - @EnableAsync annotation - Quiz 7medium Async Processing - @EnableAsync annotation - Quiz 13medium Caching - Why caching matters for performance - Quiz 15hard Docker and Deployment - Environment-based profiles - Quiz 10hard Docker and Deployment - Multi-stage Docker builds - Quiz 11easy Docker and Deployment - Environment-based profiles - Quiz 8hard Messaging - Message serialization - Quiz 7medium