B. Spring provides a Dependency Injection container. True. One of the core features of Spring is its powerful Dependency Injection (DI) container, which helps manage the lifecycle and dependencies of the application’s components. E. Spring provides abstractions over infrastructure such as persistence and messaging. True. Spring provides a range of abstractions over various infrastructure concerns, such as persistence (with Spring Data and JPA), messaging (with Spring JMS and Spring AMQP), transaction management, and more. These abstractions simplify and unify the way developers interact with these systems.

A. Locale

This is true because the Locale argument can be used to resolve the current locale that the client is using, based on the Accept-Language header or a cookie 1 .

B. Principal

This is true because the Principal argument can be used to access the currently authenticated user, if any 1 .

F. HttpSession

This is true because the HttpSession argument can be used to access the current session, if any 1 . Note that this argument is not required and will be null if a session does not exist.

A. @Configuration This annotation indicates that the class has @Bean definition methods and may be processed by the Spring container to generate bean definitions and service requests for those beans at runtime. B. @ComponentScan This annotation configures component scanning directives for use with @Configuration classes. Provides support parallel with Spring XML ' s context:component-scan element.

A Spring Boot starter dependency is a special type of dependency that provides a convenient way to add multiple, coordinated dependencies related to a specific technology or feature, such as web, JDBC, security, etc. A starter dependency usually has a name that starts with spring-boot-starter- followed by the name of the technology or feature. For example, spring-boot-starter-web is a starter dependency that includes all the dependencies needed for creating web applications with Spring MVC and RESTful services.

Transactions are units of work that ensure data consistency and integrity by enforcing atomicity, consistency, isolation, and durability (ACID) properties. Spring provides an abstraction layer for transaction management that supports various transaction APIs such as JDBC, JPA, Hibernate, etc. To use transactions in Spring, we need to do two things:

Enable transaction management by adding @EnableTransactionManagement annotation to a Java configuration class or  tx:annotation-driven/  element to an XML configuration file.

Declare transactional boundaries by annotating a class, an interface, or individual methods with the @Transactional annotation. This annotation indicates that the execution of the annotated element should be wrapped in a transaction.

This is true because the default scope of a bean in Spring is singleton, which means that only one instance of the bean will be created and shared by the entire application context. The @Bean annotation on the accountRepository() method indicates that this method will return a bean that will be managed by Spring. However, this method will not be called every time the bean is needed, but only once when the bean is first created. Therefore, only one AccountRepository bean will be instantiated and injected into the TransferService and AccountService beans.

This is true because Spring ' s JdbcTemplate class offers a variety of methods to execute SQL queries against a relational database. These include methods for executing SQL queries (query, queryForObject, queryForList, etc.), updates (update), and batch operations (batchUpdate).