@EnableAsync annotation in Spring Boot - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when @EnableAsync is added to a Spring Boot configuration?

Consider a Spring Boot application where the @EnableAsync annotation is added to a configuration class. What is the effect of this annotation on the application's behavior?

A It disables all asynchronous processing in the application.

B It enables the processing of methods annotated with @Async to run asynchronously in a separate thread.

C It automatically schedules all methods to run at fixed intervals.

D It converts all synchronous methods into reactive streams.

💡 Hint

Think about what @Async methods need to work properly in Spring.

The @EnableAsync annotation tells Spring to look for methods annotated with @Async and run them in a separate thread, enabling asynchronous execution.

📝 Syntax

intermediate

Identify the correct way to enable async processing in Spring Boot

Which of the following code snippets correctly enables asynchronous method execution in a Spring Boot application?

Spring Boot

public class AppConfig {
    // ...
}

A

@Configuration
@EnableAsync(true)
public class AppConfig {}

B

@EnableAsync
public class AppConfig {}

C

@Configuration
@EnableAsync()
public class AppConfig {}

D

@Configuration
@EnableAsync
public class AppConfig {}

💡 Hint

Remember that @EnableAsync is a meta-annotation and usually combined with @Configuration.

The correct way is to annotate a @Configuration class with @EnableAsync without parameters. Option D shows this correctly.

🔧 Debug

advanced

Why does @Async not work despite @EnableAsync being present?

A developer added @EnableAsync to their Spring Boot configuration but notices that methods annotated with @Async still run synchronously. What is the most likely cause?

A The @Async method is called from within the same class, bypassing Spring's proxy mechanism.

B The @EnableAsync annotation must be placed on the main application class only.

C The @Async annotation requires a special bean name to work.

D Spring Boot disables @Async by default even with @EnableAsync.

💡 Hint

Think about how Spring proxies work with self-invocation.

Spring uses proxies to intercept calls to @Async methods. Calling an @Async method from the same class bypasses the proxy, so it runs synchronously.

❓ state_output

advanced

What thread name prefix is used by default for @Async methods?

When a method annotated with @Async runs, what is the default prefix of the thread name executing it?

A SimpleAsyncTaskExecutor-

B ThreadPoolTaskExecutor-

C AsyncExecutor-

D DefaultAsyncThread-

💡 Hint

Look at the default executor Spring uses if none is configured.

By default, Spring uses SimpleAsyncTaskExecutor which names threads with the prefix 'SimpleAsyncTaskExecutor-'.

🧠 Conceptual

expert

How does @EnableAsync affect Spring's proxy creation and bean lifecycle?

Which statement best describes the impact of @EnableAsync on Spring's proxy creation and bean lifecycle?

A @EnableAsync replaces all beans with asynchronous versions at runtime without using proxies.

B @EnableAsync delays bean initialization until the first @Async method is called.

C @EnableAsync triggers Spring to create proxies for beans with @Async methods, enabling asynchronous execution by intercepting method calls.

D @EnableAsync disables Spring's default proxy mechanism to allow direct thread spawning.

💡 Hint

Consider how Spring intercepts method calls to add behavior.

@EnableAsync causes Spring to create proxies around beans that have @Async methods. These proxies intercept calls and run them asynchronously.