[Solved] Why might you prefer @After advice over @AfterReturning advice in some cases? — Ans: Because @After runs regardless of method success or failure, useful for cleanup. | Spring Boot

Spring Boot - Aspect-Oriented Programming

Why might you prefer @After advice over @AfterReturning advice in some cases?

ABecause @After runs only before the method starts.

BBecause @After runs regardless of method success or failure, useful for cleanup.

CBecause @AfterReturning runs even if method throws exceptions.

DBecause @AfterReturning advice cannot access return values.

Step-by-Step Solution

Solution:

Step 1: Compare advice execution timing
@After runs always after method finishes, whether it succeeded or failed.
Step 2: Use case for cleanup
This makes @After ideal for cleanup tasks that must run no matter what.
Final Answer:
Because @After runs regardless of method success or failure, useful for cleanup. -> Option B
Quick Check:
@After = always runs after method, good for cleanup [OK]

Quick Trick: Use @After for always-run cleanup after method [OK]

Common Mistakes:

Master "Aspect-Oriented Programming" in Spring Boot

9 interactive learning modes - each teaches the same concept differently

More Spring Boot Quizzes

Why might you prefer @After advice over @AfterReturning advice in some cases?