Cross-cutting concerns concept in Spring Boot - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Cross-cutting Concerns in Spring Boot

Which of the following best describes a cross-cutting concern in a Spring Boot application?

A A UI component that handles user input.

B A feature that affects multiple parts of the application, like logging or security, implemented separately from business logic.

C A database entity that stores user information.

D A specific business rule applied only in one service class.

💡 Hint

Think about features that are needed across many parts of the app, not just one place.

Cross-cutting concerns are aspects like logging, security, or transaction management that affect many parts of an application. Spring Boot uses AOP to separate these from core business logic.

❓ component_behavior

intermediate

Behavior of Aspect in Spring Boot

Given a Spring Boot aspect that logs method execution time, what will happen when a method annotated with @LogExecutionTime is called?

Spring Boot

@Aspect
@Component
public class LoggingAspect {
    @Around("@annotation(com.example.LogExecutionTime)")
    public Object logTime(ProceedingJoinPoint joinPoint) throws Throwable {
        long start = System.currentTimeMillis();
        Object proceed = joinPoint.proceed();
        long executionTime = System.currentTimeMillis() - start;
        System.out.println(joinPoint.getSignature() + " executed in " + executionTime + "ms");
        return proceed;
    }
}

A The method runs twice because of the aspect.

B The method is skipped and only the execution time is printed.

C The method throws a runtime exception due to missing annotation.

D The method runs normally and its execution time is printed to the console.

💡 Hint

The aspect wraps the method to measure time but does not prevent execution.

The @Around advice runs code before and after the method. It calls proceed() to run the method and then logs the time.

📝 Syntax

advanced

Correct Syntax for Defining a Pointcut

Which option correctly defines a pointcut that matches all methods in the package com.example.service and its subpackages?

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

B @Pointcut("execution(* com.example.service.*(..))")

C @Pointcut("execution(* com.example..service.*(..))")

D @Pointcut("execution(* com.example.service.*.*(..))")

💡 Hint

Use '..' to include subpackages in pointcut expressions.

The '..' in the expression means any subpackage depth. Option A matches all methods in com.example.service and its subpackages.

🔧 Debug

advanced

Identifying the Cause of Aspect Not Triggering

A developer created an aspect to log method calls but notices it never runs. Which of the following is the most likely cause?

A The aspect class is not annotated with @Component or not scanned by Spring.

B The application is missing a database connection.

C The method being called is private.

D The method has no parameters.

💡 Hint

Spring needs to know about the aspect bean to apply it.

For Spring AOP to work, the aspect must be a Spring bean, typically annotated with @Component and scanned by Spring. Otherwise, it won't be applied.

❓ state_output

expert

Output of Logging Aspect with Multiple Method Calls

Given the following Spring Boot aspect and service, what will be printed to the console when main() calls service.process() twice?

Spring Boot

public class Service {
    @LogExecutionTime
    public void process() throws InterruptedException {
        Thread.sleep(100);
    }
}

public class Main {
    public static void main(String[] args) throws InterruptedException {
        Service service = new Service();
        service.process();
        service.process();
    }
}

@Aspect
@Component
public class LoggingAspect {
    @Around("@annotation(com.example.LogExecutionTime)")
    public Object logTime(ProceedingJoinPoint joinPoint) throws Throwable {
        long start = System.currentTimeMillis();
        Object proceed = joinPoint.proceed();
        long time = System.currentTimeMillis() - start;
        System.out.println(joinPoint.getSignature() + " executed in " + time + "ms");
        return proceed;
    }
}

A Compilation error due to missing annotations on Service class.

B Two lines printed showing execution time for each process() call.

C No output because the aspect is not applied to the service instance created with new.

D One line printed showing execution time for the first call only.

💡 Hint

Spring AOP works only on Spring-managed beans, not on objects created with new.

The service instance is created manually with new, so Spring does not manage it and the aspect is not applied. No logging output appears.

Practice

1. What is the main purpose of cross-cutting concerns in a Spring Boot application?

easy

A. To manage database connections and queries

B. To define the main business logic of the application

C. To create user interface components

D. To handle common tasks like logging and security across multiple parts of the app

Solution

1. Step 1: Understand the role of cross-cutting concerns

   Cross-cutting concerns are tasks that affect many parts of an application, such as logging, security, or transaction management.

2. Step 2: Identify their purpose in Spring Boot

   Spring Boot uses cross-cutting concerns to keep these common tasks separate from business logic, improving code clarity and reuse.

3. Final Answer:

   To handle common tasks like logging and security across multiple parts of the app -> Option D

4. Quick Check:

   Cross-cutting concerns = common tasks across app [OK]

Hint: Cross-cutting concerns handle shared tasks across many parts [OK]

Common Mistakes:

• Confusing cross-cutting concerns with main business logic
• Thinking they manage database or UI directly
• Assuming they are only for security

2. Which annotation is used in Spring Boot to define an aspect for cross-cutting concerns?

easy

A. @Aspect

B. @Controller

C. @Service

D. @Repository

Solution

1. Step 1: Recall Spring AOP annotations

   Spring Boot uses Aspect-Oriented Programming (AOP) to implement cross-cutting concerns, and the key annotation to define an aspect is @Aspect.

2. Step 2: Differentiate from other annotations

   @Controller is for web controllers, @Service for service layer, and @Repository for data access. None of these define aspects.

3. Final Answer:

   @Aspect -> Option A

4. Quick Check:

   Aspect annotation = @Aspect [OK]

Hint: Use @Aspect to mark cross-cutting concern classes [OK]

Common Mistakes:

• Choosing @Controller or @Service by mistake
• Confusing @Aspect with @Component
• Not knowing which annotation defines an aspect

3. Given this Spring Boot aspect code snippet:

@Aspect
public class LoggingAspect {
  @Before("execution(* com.example.service.*.*(..))")
  public void logBefore() {
    System.out.println("Method called");
  }
}

What will happen when a method in com.example.service package is called?

medium

A. The message "Method called" will print after the method executes

B. The message "Method called" will print before the method executes

C. No message will print because the pointcut is incorrect

D. The method call will be blocked and not executed

Solution

1. Step 1: Understand the @Before advice

   The @Before annotation means the method logBefore() runs before the matched method executes.

2. Step 2: Analyze the pointcut expression

   The pointcut execution(* com.example.service.*.*(..)) matches any method in any class inside com.example.service package.

3. Final Answer:

   The message "Method called" will print before the method executes -> Option B

4. Quick Check:

   @Before advice prints message before method [OK]

Hint: @Before runs code before matched methods [OK]

Common Mistakes:

• Confusing @Before with @After advice
• Thinking pointcut matches other packages
• Assuming method is blocked

4. Identify the error in this Spring Boot aspect code:

@Aspect
public class SecurityAspect {
  @Before("execution(* com.example..*(..))")
  public void checkSecurity() {
    // security check code
  }
}

medium

A. The pointcut expression syntax is invalid

B. The method name must start with 'validate'

C. The advice method must return a value

D. The class is missing @Component or @Configuration annotation

Solution

1. Step 1: Examine the pointcut expression

   The pointcut execution(* com.example..*(..)) has invalid syntax because it is missing the method name pattern .*. Correct syntax is execution(* com.example..*.*(..)) to match any method in com.example package and subpackages.

2. Step 2: Rule out other options

   Advice methods can be void and have any name; missing bean annotation is secondary.

3. Final Answer:

   The pointcut expression syntax is invalid -> Option A

4. Quick Check:

   Pointcut requires .* for method pattern [OK]

Hint: Pointcut syntax: execution(* pkg..*.*(..)) [OK]

Common Mistakes:

• Thinking it's missing @Component annotation
• Believing method name must start with 'validate'
• Assuming advice must return a value

5. You want to apply a logging aspect only to methods annotated with @Transactional in your Spring Boot app. Which pointcut expression correctly targets these methods?

hard

A. execution(@Transactional * *(..))

B. within(@Transactional *)

C. @annotation(org.springframework.transaction.annotation.Transactional)

D. args(@Transactional)

Solution

1. Step 1: Understand pointcut for annotations

   To target methods with a specific annotation, Spring AOP uses the @annotation pointcut designator with the full annotation class name.

2. Step 2: Evaluate options

   @annotation(org.springframework.transaction.annotation.Transactional) uses @annotation(org.springframework.transaction.annotation.Transactional), which correctly matches methods annotated with @Transactional. Other options are invalid or incorrect syntax.

3. Final Answer:

   @annotation(org.springframework.transaction.annotation.Transactional) -> Option C

4. Quick Check:

   Use @annotation for method-level annotation matching [OK]

Hint: Use @annotation with full annotation class for method targeting [OK]

Common Mistakes:

• Using execution with annotation incorrectly
• Confusing within and args pointcuts
• Not specifying full annotation package