Why is it important to place @EnableCaching on a configuration class rather than on a regular service class?

hard📝 Conceptual Q10 of 15

Spring Boot - Caching

Why is it important to place @EnableCaching on a configuration class rather than on a regular service class?

ABecause service classes cannot have annotations

BBecause @EnableCaching triggers global cache setup and should be on a config class

CBecause @EnableCaching only works on classes with main method

DBecause placing it on service classes disables caching

Step-by-Step Solution

Solution:

Step 1: Understand the purpose of @EnableCaching
@EnableCaching activates Spring's caching infrastructure globally.
Step 2: Why on configuration class?
It should be on a configuration or main class to apply caching support application-wide, not on individual beans.
Final Answer:
Because @EnableCaching triggers global cache setup and should be on a config class -> Option B
Quick Check:
@EnableCaching = global cache setup on config [OK]

Quick Trick: Put @EnableCaching on config class for global effect [OK]

Common Mistakes:

Master "Caching" in Spring Boot

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Spring Boot Quizzes