A.@ActiveProfiles is a class-level annotation that is used to instruct the Spring TestContext Framework to record all application events that are published in the ApplicationContext during the execution of a single test.

B.@ActiveProfiles is a class-level annotation that you can use to configure the locations of properties files and inlined properties to be added to the set of PropertySources in the Environment for an ApplicationContext loaded for an integration test.

C.@ActiveProfiles is a class-level annotation that is used to declare which bean definition profiles should be active when loaded an ApplicationContext for an integration test.

D.@ActiveProfiles is a class-level annotation that you can use to configure how the Spring TestContext Framework is bootstrapped.

A.REST is Relative.

B.REST is a Protocol.

C.REST is Reliable.

D.REST is Interoperable.

E.REST is Stateful.

A.BeanPostProcessors cannot be ordered in a Spring Boot application.

B.Custom BeanPostProcessors can be implemented for Spring applications.

C.BeanPostProcessors are called before the BeanFactoryPostProcessors.

D.BeanPostProcessors are called during the initialization phase of a bean life cycle.

E.BeanPostProcessors are called before the dependencies have been injected.

A.A setting for specifying which code you want Spring Boot to generate for you.

B.An easy way to include multiple, coordinated dependencies related to a specific technology, like web or JDBC.

C.A specific POM which you must build to control Spring Boot's opinionated runtime.

D.A pre-existing model project you can download and use as the basis of your project.

A.Add @EnableTransactionManagement to a Java configuration class.

B.A class requiring a transaction must implement the TransactionInterceptor interface.

C.Annotate a class, an interface, or individual methods requiring a transaction with the @Transactional annotation.

D.A class must be annotated with @Service and @Transaction.

E.Write a Spring AOP advice to implement transactional behavior.