Why AOP matters in Spring Boot - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an aspect in Spring Boot.

Spring Boot

@Aspect
@Component
public class LoggingAspect {
    @Before("[1]")
    public void logBefore() {
        System.out.println("Method is about to execute");
    }
}

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

A"execution(* com.example.service.*.*(..))"

B"@Aspect"

C"@Component"

D"@Before"

Attempts:

3 left

💡 Hint

Common Mistakes

Putting annotation names instead of pointcut expressions.

Leaving the blank empty.

Using incorrect pointcut syntax.

The @Before annotation needs a pointcut expression like execution(* com.example.service.*.*(..)) to specify where to apply the advice.

2fill in blank

medium

Complete the code to apply advice after a method returns successfully.

Spring Boot

@AfterReturning(pointcut = "execution(* com.example.repo.*.*(..))", returning = "result")
public void logAfterReturning([1] result) {
    System.out.println("Method returned: " + result);
}

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

AObject

Bvoid

CString

Dint

Attempts:

3 left

💡 Hint

Common Mistakes

Using void as parameter type.

Using a specific type that may not match the returned value.

The advice method parameter must match the type of the returned object or use Object to accept any type.

3fill in blank

hard

Fix the error in the advice method signature to correctly capture exceptions.

Spring Boot

@AfterThrowing(pointcut = "execution(* com.example.service.*.*(..))", throwing = "ex")
public void logAfterThrowing([1] ex) {
    System.out.println("Exception thrown: " + ex.getMessage());
}

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

AString

Bvoid

CException

Dint

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-exception types as parameter.

Omitting the parameter.

The advice method must accept an Exception or subclass to capture thrown exceptions.

4fill in blank

hard

Fill both blanks to create a pointcut that matches all methods in service package and apply advice before execution.

Spring Boot

@Aspect
@Component
public class AuditAspect {
    @[1]("[2]")
    public void audit() {
        System.out.println("Audit: method called");
    }
}

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

ABefore

BAfter

Cexecution(* com.example.service.*.*(..))

Dexecution(* com.example.repo.*.*(..))

Attempts:

3 left

💡 Hint

Common Mistakes

Using @After instead of @Before.

Using pointcut for repo package instead of service.

The @Before annotation applies advice before method execution, and the pointcut expression matches all methods in the service package.

5fill in blank

hard

Fill all three blanks to create an around advice that logs method start, proceeds with method execution, and logs method end.

Spring Boot

@Around("[1]")
public Object logAround(ProceedingJoinPoint joinPoint) throws Throwable {
    System.out.println("Start: " + joinPoint.getSignature().getName());
    Object result = joinPoint.[2]();
    System.out.println("End: " + joinPoint.getSignature().getName());
    return [3];
}

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

Aexecution(* com.example.controller.*.*(..))

Bproceed

Cresult

Dexecution(* com.example.service.*.*(..))

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong pointcut expression.

Calling a wrong method instead of proceed().

Returning something other than the result.

The @Around advice uses a pointcut expression to match service methods, calls proceed() to continue execution, and returns the result.

Practice

1. What is the main purpose of Aspect-Oriented Programming (AOP) in Spring Boot?

easy

A. To separate common tasks like logging and security from business logic

B. To replace the need for writing any business logic

C. To make the application run faster by skipping method calls

D. To store data in the database automatically

Solution

1. Step 1: Understand AOP's role

   AOP helps keep common tasks like logging or security separate from the main business code.

2. Step 2: Identify the main benefit

   This separation makes the code easier to read and maintain without changing the business logic itself.

3. Final Answer:

   To separate common tasks like logging and security from business logic -> Option A

4. Quick Check:

   AOP separates concerns = D [OK]

Hint: AOP separates cross-cutting tasks from main code [OK]

Common Mistakes:

• Thinking AOP replaces business logic
• Believing AOP speeds up method execution
• Confusing AOP with database operations

2. Which of the following is the correct way to define an aspect in Spring Boot using AOP?

easy

A. @Component
public class MyAspect { }

B. @Aspect
public class MyAspect { }

C. @Service
public class MyAspect { }

D. @Repository
public class MyAspect { }

Solution

1. Step 1: Recognize the annotation for aspects

   In Spring AOP, the @Aspect annotation marks a class as an aspect.

2. Step 2: Confirm the correct syntax

   Only @Aspect correctly defines an aspect; @Component alone does not define aspect behavior.

3. Final Answer:

   @Aspect public class MyAspect { } -> Option B

4. Quick Check:

   @Aspect marks aspect classes = B [OK]

Hint: Use @Aspect to define aspects in Spring Boot [OK]

Common Mistakes:

• Using @Component alone without @Aspect
• Confusing @Service or @Repository with aspects
• Missing the @Aspect annotation

3. Given this Spring Boot aspect code snippet, what will be printed when myService.doWork() is called?

@Aspect
@Component
public class LoggingAspect {
  @Before("execution(* com.example.MyService.doWork(..))")
  public void logBefore() {
    System.out.println("Starting work");
  }
}

@Service
public class MyService {
  public void doWork() {
    System.out.println("Doing work");
  }
}

medium

A. Starting work
Doing work

B. Doing work
Starting work

C. Doing work

D. Starting work

Solution

1. Step 1: Understand @Before advice

   The @Before advice runs before the target method, so "Starting work" prints first.

2. Step 2: Trace method call output

   Then the actual method prints "Doing work" after the advice.

3. Final Answer:

   Starting work Doing work -> Option A

4. Quick Check:

   @Before runs before method = A [OK]

Hint: @Before advice runs before method call output [OK]

Common Mistakes:

• Assuming advice runs after method
• Mixing order of printed lines
• Ignoring advice output

4. Identify the error in this Spring Boot aspect code that prevents the advice from running:

@Aspect
@Component
public class SecurityAspect {
  @Before("execution(* com.example.MyService.secureMethod())")
  public void checkSecurity() {
    System.out.println("Checking security");
  }
}

@Service
public class MyService {
  public void secureMethod(String user) {
    System.out.println("Secure method for " + user);
  }
}

medium

A. secureMethod should be private

B. Missing @Component annotation on MyService

C. Advice method must return a value

D. The pointcut expression does not match the method signature

Solution

1. Step 1: Compare pointcut and method signature

   The pointcut expects a method with no parameters, but secureMethod takes a String parameter.

2. Step 2: Understand pointcut matching rules

   Because the signature does not match, the advice never runs.

3. Final Answer:

   The pointcut expression does not match the method signature -> Option D

4. Quick Check:

   Pointcut must match method signature = A [OK]

Hint: Match pointcut exactly to method signature [OK]

Common Mistakes:

• Ignoring method parameters in pointcut
• Thinking @Component missing on service blocks advice
• Believing advice must return a value

5. You want to add logging before and after all methods in your service without changing each method. Which AOP approach best achieves this in Spring Boot?

hard

A. Create a new service class that duplicates all methods with logging

B. Manually add logging code inside every service method

C. Use @Before and @After advices with a pointcut matching all service methods

D. Use @Transactional annotation on service methods

Solution

1. Step 1: Identify the goal

   You want to add logging around all service methods without modifying them individually.

2. Step 2: Choose the correct AOP approach

   @Before and @After advices with a pointcut covering all service methods allow running code before and after each method automatically.

3. Final Answer:

   Use @Before and @After advices with a pointcut matching all service methods -> Option C

4. Quick Check:

   AOP advices automate cross-cutting tasks = C [OK]

Hint: Use @Before and @After with pointcut for all methods [OK]

Common Mistakes:

• Adding logging manually in every method
• Duplicating service classes unnecessarily
• Confusing logging with transaction management