Free Practice Questions for VMware 2V0-72.22 Exam

Add @EnableTransactionManagement to a Java configuration class.

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

annotation.

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

A class requiring a transaction must implement the TransactionInterceptor interface.

Write a Spring AOP advice to implement transactional behavior.

Use the @AutoConfigureAfter or @AutoConfigureBefore annotations to apply configuration in a specific order.

Disable specific auto-configuration classes by using the exclude attribute on the

@EnableAutoConfiguation annotation.

Provide customized auto-configuration by subclassing the provided Spring Boot auto-configuration classes.

Enable component scanning within auto-configuration classes to find necessary components.

Control the order of auto-configuration classes applied with @AutoConfigureOrder.

There are 2 transactions because REQUIRES_NEW always runs in a new transaction.

An exception is thrown as another transaction cannot be started within an existing transaction.

There is only one transaction because REQUIRES_NEW will use an active transaction if one already exists.

There is only one transaction initiated by update1() because the call to update2() does not go through the proxy.

Auto-configuration uses @Conditional annotations to constrain when it should apply.

Auto-configuration could apply when a bean is missing but not when a bean is present.

Auto-configuration is applied by processing candidates listed in META-INF/spring.factories.

Auto-configuration could apply when a bean is present but not when a bean is missing.

Auto-configuration is applied before user-defined beans have been registered.

If there is only one constructor the @Autowired annotation is not required.

Constructor injection only allows one value to be injected.

Constructor injection is preferred over field injection to support unit testing.

Construction injection can be used with multiple constructors without @Autowired annotation.

Field injection is preferred over constructor injection from a unit testing standpoint.

It provides configuration options through which only an authenticated user can display application information.

It is not enabled by default.

It can be used to display arbitrary application information.

It can be used to change a property value on a running application.

Typically it is used to display build or source control information.

Java system properties have higher precedence than the properties loaded from

@TestPropertySource.

Properties defined @PropertySource are not loaded if @TestPropertySource is used.

@TestPropertySource annotation loads a properties file relative to the root of the project by default.

Inlined properties defined in @TestPropertySource can be used to override properties defined in property files.

@TestApplicationContext is used to define additional beans or customizations for a test.

Test methods in a @SpringBootTest class are transactional by default.

@SpringBootTest is typically used for integration testing.

Test methods annotated with @SpringBootTest will recreate the ApplicationContext.

@SpringBootTest without any configuration classes expects there is only one class annotated with @SpringBootConfiguration in the application.

A DataSource bean will not be auto-configured.

A JdbcTemplate bean will not be auto-configured.

A JdbcTemplate bean will be auto-configured.

A DataSource bean will be auto-configured only if a JdbcTemplate bean is explicitly defined.

A DataSource bean will be auto-configured.

The last status in a sorted list of HealthIndicators is used to derive the final system health.

The status with the least severity is used as the top-level status.

Custom status values can be created.

The built-in status values are DOWN, OUT_OF_SERVICE, UNKNOWN, and UP in decreasing order of severity.

The severity order cannot be changed due to security reasons.