Why async processing matters in Spring Boot - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable asynchronous processing in a Spring Boot method.

Spring Boot

@[1]
public void processTask() {
    // task logic here
}

Drag options to blanks, or click blank then click option'

AEnableAsync

BAsync

CAsyncMethod

DAsyncProcessing

Attempts:

3 left

💡 Hint

Common Mistakes

Using @EnableAsync on a method instead of a configuration class

Misspelling the annotation name

Forgetting the '@' symbol

The @Async annotation tells Spring Boot to run this method asynchronously.

2fill in blank

medium

Complete the code to enable async support in a Spring Boot application.

Spring Boot

@Configuration
@[1]
public class AsyncConfig {
}

Drag options to blanks, or click blank then click option'

AAsyncEnabled

BAsyncSupport

CAsyncConfiguration

DEnableAsync

Attempts:

3 left

💡 Hint

Common Mistakes

Placing @EnableAsync on a method instead of a configuration class

Using @Async instead of @EnableAsync here

Misspelling the annotation

The @EnableAsync annotation enables Spring's asynchronous method execution capability.

3fill in blank

hard

Fix the error in the method signature to return a future result asynchronously.

Spring Boot

@Async
public [1]<String> fetchData() {
    // fetch data logic
}

Drag options to blanks, or click blank then click option'

ACompletableFuture

BFuture

CListenableFuture

DOptional

Attempts:

3 left

💡 Hint

Common Mistakes

Using Future which is less flexible

Using Optional which is not for async

Using ListenableFuture without proper dependencies

CompletableFuture is commonly used in Spring Boot for async methods returning results.

4fill in blank

hard

Fill both blanks to create a method that runs asynchronously and returns a completed future.

Spring Boot

@Async
public CompletableFuture<String> [1]() {
    return CompletableFuture.[2]("Done");
}

Drag options to blanks, or click blank then click option'

ArunTask

BcompletedFuture

CsupplyAsync

DexecuteTask

Attempts:

3 left

💡 Hint

Common Mistakes

Using supplyAsync inside the method without executor

Choosing method names that don't describe an action

Returning incomplete futures

The method name can be runTask, and completedFuture returns a completed CompletableFuture.

5fill in blank

hard

Fill all three blanks to configure a custom executor bean for async processing.

Spring Boot

@Bean
public Executor [1]() {
    ThreadPoolTaskExecutor executor = new ThreadPoolTaskExecutor();
    executor.setCorePoolSize([2]);
    executor.setMaxPoolSize([3]);
    executor.initialize();
    return executor;
}

Drag options to blanks, or click blank then click option'

AtaskExecutor

B5

C10

DasyncExecutor

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong bean name that conflicts with defaults

Setting core pool size larger than max pool size

Forgetting to initialize the executor

The bean name asyncExecutor is common, with core pool size 5 and max pool size 10 for thread management.

Practice

1. Why is async processing important in Spring Boot applications?

easy

A. It makes the application use more memory by duplicating tasks.

B. It forces all tasks to run one after another in sequence.

C. It allows tasks to run in the background without blocking the main thread.

D. It disables error handling for faster execution.

Solution

1. Step 1: Understand async processing purpose

   Async processing lets tasks run separately from the main thread, so the app stays responsive.

2. Step 2: Identify correct behavior in Spring Boot

   Spring Boot uses @Async to run methods in the background, improving speed and user experience.

3. Final Answer:

   It allows tasks to run in the background without blocking the main thread. -> Option C

4. Quick Check:

   Async means background tasks = B [OK]

Hint: Async means background work without blocking main thread [OK]

Common Mistakes:

• Thinking async duplicates tasks unnecessarily
• Believing async forces sequential execution
• Assuming async disables error handling

2. Which annotation is used in Spring Boot to enable async processing on a method?

easy

A. @BackgroundTask

B. @EnableAsync

C. @AsyncMethod

D. @Async

Solution

1. Step 1: Recall Spring Boot async annotations

   @Async is the annotation placed on methods to run them asynchronously.

2. Step 2: Differentiate from other annotations

   @EnableAsync enables async support globally but is not placed on methods; @AsyncMethod and @BackgroundTask do not exist in Spring Boot.

3. Final Answer:

   @Async -> Option D

4. Quick Check:

   Method-level async annotation = A [OK]

Hint: Use @Async on methods to run them asynchronously [OK]

Common Mistakes:

• Confusing @EnableAsync with @Async
• Using non-existent annotations like @AsyncMethod
• Applying @Async on classes instead of methods

3. What will be the output behavior of this Spring Boot method annotated with @Async?

@Async
public CompletableFuture<String> fetchData() {
    // simulate delay
    Thread.sleep(1000);
    return CompletableFuture.completedFuture("Done");
}

medium

A. The method immediately returns a CompletableFuture, running the delay in the background.

B. The method returns null because async methods cannot return values.

C. The method throws a compile-time error due to Thread.sleep in async method.

D. The method blocks the caller for 1 second before returning "Done".

Solution

1. Step 1: Understand @Async with CompletableFuture

   @Async runs the method in a separate thread, so the caller gets a CompletableFuture immediately.

2. Step 2: Analyze Thread.sleep effect

   The delay happens inside the async thread, not blocking the caller thread.

3. Final Answer:

   The method immediately returns a CompletableFuture, running the delay in the background. -> Option A

4. Quick Check:

   @Async returns immediately with CompletableFuture = D [OK]

Hint: Async method returns CompletableFuture immediately, delay runs in background [OK]

Common Mistakes:

• Thinking Thread.sleep blocks the caller thread
• Assuming async methods cannot return values
• Believing async causes compile errors with sleep

4. Identify the error in this Spring Boot async method:

@Async
public void process() {
    CompletableFuture<String> result = CompletableFuture.supplyAsync(() -> {
        throw new RuntimeException("Fail");
    });
    System.out.println(result.get());
}

medium

A. Calling result.get() blocks the async thread, defeating async benefits.

B. Throwing RuntimeException inside supplyAsync is not allowed.

C. The method must return CompletableFuture<String>, not void.

D. Missing @EnableAsync annotation on the class.

Solution

1. Step 1: Analyze use of result.get()

   Calling get() waits for the CompletableFuture to finish, blocking the async thread.

2. Step 2: Understand async best practices

   Blocking defeats async purpose; exceptions inside supplyAsync are allowed and handled asynchronously.

3. Final Answer:

   Calling result.get() blocks the async thread, defeating async benefits. -> Option A

4. Quick Check:

   Blocking call inside async method = C [OK]

Hint: Avoid blocking calls like get() inside async methods [OK]

Common Mistakes:

• Thinking exceptions inside supplyAsync are disallowed
• Believing async methods must always return CompletableFuture
• Forgetting to enable async globally (not always required)

5. You want to improve a Spring Boot app's responsiveness by running multiple independent tasks in parallel. Which approach best uses async processing to achieve this?

hard

A. Run all tasks sequentially in the main thread to avoid thread overhead.

B. Annotate each task method with @Async and return CompletableFuture, then combine results with CompletableFuture.allOf().

C. Use @Async but return void from all methods to simplify code.

D. Create new threads manually inside each method without @Async.

Solution

1. Step 1: Identify best async pattern for parallel tasks

   Using @Async with CompletableFuture allows tasks to run in parallel and return results.

2. Step 2: Combine results properly

   CompletableFuture.allOf() waits for all async tasks to finish, enabling coordinated processing.

3. Final Answer:

   Annotate each task method with @Async and return CompletableFuture, then combine results with CompletableFuture.allOf(). -> Option B

4. Quick Check:

   Parallel async tasks + combine results = A [OK]

Hint: Use @Async + CompletableFuture.allOf() for parallel task coordination [OK]

Common Mistakes:

• Running tasks sequentially loses async benefits
• Returning void loses ability to track task completion
• Manually creating threads ignores Spring Boot async support