VMware 2V0-72.22 Professional Develop VMware Spring Exam Practice Test

Mocking a Spring Bean requires annotating it with @MockBean annotation.

If a Spring Bean already exists in the web slice test spring context, it cannot be mocked.

Mocks cannot be used in a Spring Boot web slice test.

Mocking a Spring Bean requires annotating it with @Mock annotation.

It will close the existing cached ApplicationContext and recreate a new one before the test method.

It will close the existing cached ApplicationContext and recreate a new one after the test method.

It will keep the existing cached ApplicationContext, all changes to Spring managed beans will be reverted after the test.

It will recreate only the Spring managed beans that are modified inside the test method.

prototype

singleton

request

session

@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.

The @Controller annotated classes can only render views.

The classes are eligible for handling requests in Spring MVC.

The classes must be annotated together with @EnableMvcMappings to be discovered via component scanning.

@Controller is interchangeable with @RestController with no extra code changes for the methods inside the class.

The @Controller annotation is a stereotype annotation like @Component.

@Configuration

@ComponentScan

@SpringBootConfiguration

@SpringApplication

@AutoConfiguration

CustomerRepository should be a class, not an interface.

JPA annotations are required on the Customer class to successfully use Spring Data JDBC.

An implementation of this repository can be automatically generated by Spring Data JPA.

A class that implements CustomerRepository must be implemented and declared as a Spring Bean.

The "fat" JAR contains both the class files and the source files for your project.

The "fat" JAR requires an external Servlet container.

The "fat" JAR contains compiled classes and dependencies that your code needs to run.

The "fat" JAR can contain multiple embedded application servers.

The "fat" JAR is created by the Spring Boot Maven plugin or Gradle plugin.

To get a logging level of a package called account.web, you can access the /actuator/loggers/account.web endpoint.

An application restart is required to change the logging level of the package.

In order to use the loggers endpoint, a logger implementation dependency needs to be added.

The logging levels of a package that can be accessed via the loggers endpoint include configuredLevel and effectiveLevel.

To provide risk governance.

To drive authentication.

To manage application users.

To provide a logout capability.

To enforce authorization (access control).

To encrypt data.

Repository

Messaging

Web

Container

Client

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.

Spring automates a Java application build.

Spring provides a Dependency Injection container.

Spring automates deployment of Java applications to all of the major cloud providers.

Spring provides comprehensive Java IDE support.

Spring provides abstractions over infrastructure such as persistence and messaging.

All JdbcTemplate methods throw SQLException which you are required to handle.

The JdbcTemplate provides the ability to work with result sets.

The JdbcTemplate can only perform update but not insert to the database.

The JdbcTemplate provides methods for query execution.

The JdbcTemplate generates SQL statements.

@Value must be used for environment variables, as @ConfigurationProperties cannot access the environment.

@Value supports relaxed binding of properties, but not property binding through SpEL.

@ConfigurationProperties is preferable over @Value when type-safety during property binding is a concern.

@ConfigurationProperties only bind properties from .properties files, not from .yml files.

@ConfigurationProperties supports relaxed binding of properties, but not property binding through SpEL.

A point in the execution of a program such as a method call or field assignment.

An expression that selects one or more join points.

A module that encapsulated advices.

Code to be executed at each selected join point.

REST is a Protocol.

REST is Stateful.

REST is Reliable.

REST is Interoperable.

REST is Relative.

Use of @Qualifier annotation on the class and @Autowired annotation either on a field or setter methods.

Use of @Qualifier and @Autowired annotations together with setter methods.

Use of @Qualifier annotation only with setter methods (@Autowired is optional for setters).

Use of @Qualifier and @Autowired annotations together on a field.

Use of @Qualifier annotation only on a field (@Autowired is optional for fields).

The URLs can be specified via configuration (using authorizeRequests () and request matchers), with the most specific rule first and the least specific last.

Spring Security can obtain URLs from Spring MVC controllers, the Spring Security configuration just needs a reference to the controller to be protected.

The URLs are specified in a special properties file, used by Spring Security.

The URLs can be specified via configuration (using authorizeRequests () and request matchers), with the least specific rule first and the most specific last.

A HelloService bean will be created from the helloService() method even if the

HelloService.class is not in the classpath.

A HelloService bean will be created from the helloService() method only when there is no other

HelloService bean in the ApplicationContext.

This auto-configuration class is used only when the HelloService.class is not on the classpath.

This auto-configuration class is used only when the HelloService.class is on the classpath.

A HelloService bean will be created from the helloService() method and will replace existing a

HelloService bean in the ApplicationContext.

Allows for the transformation of Spring bean definitions after the beans have been instantiated.

Allows for the transformation of Spring bean definitions before the beans are instantiated.

Creates proxies for the Spring beans that require an extra behavior like transaction management.

PropertySourcesPlaceholderConfigurer implements BeanFactoryPostProcessor and is used to read property values from the Spring Environment.

Detects annotations such as @PostConstruct and @PreDestroy and then invokes appropriate behavior.

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.

Add @PathVariable(“id”) String accountId argument to the update() handler method.

Add @PathVariable long accountId argument to the update() handler method.

Add @RequestParam long accountId argument to the update() handler method.

Add @RequestParam(“id”) String accountId argument to the update() handler method.