Refer to the exhibit. Based on the default Spring behavior, choose the correct answer. (Choose the best answer.)

Question

Exhibit

Options

• AOne AccountRepository bean will be instantiated since the default scope is singleton.
• BThree AccountRepository beans will be instantiated as the accountRepository() method will be
• CMany AccountRepository beans will be instantiated, depending how often accountRepository(),
• DTwo AccountRepository beans will be instantiated as the accountRepository() method will be

• A
  89% (47)
• B
  4% (2)
• C
  2% (1)
• D
  6% (3)

Explanation

In Spring, the default bean scope is singleton, meaning the container creates exactly one instance of a bean per ApplicationContext and returns that same cached instance every time it is requested - regardless of how many other beans depend on it or how many times the factory method is called. This works because Spring wraps @Configuration classes with a CGLIB proxy that intercepts @Bean method calls and returns the existing instance instead of invoking the method again.

Options B, C, and D all describe prototype scope behavior, where a new instance is created on each request or injection - that is not the default. The distractors are designed to trick you into thinking Spring calls the method literally (like a plain Java method), which would create multiple objects, but the CGLIB proxy prevents that in a proper @Configuration class.

Memory tip: Think "Spring is stingy by default" - it creates beans once and reuses them everywhere, so singleton is the default until you explicitly annotate otherwise with @Scope("prototype") or another scope.

No community discussion yet for this question.