Bird
0
0

What problem arises if a Spring Boot repository is implemented as a concrete class instead of extending JpaRepository interface?

medium📝 Debug Q6 of 15
Spring Boot - Advanced Patterns
What problem arises if a Spring Boot repository is implemented as a concrete class instead of extending JpaRepository interface?
AThe repository will automatically support multiple databases
BSpring Data JPA features like CRUD methods won't be auto-implemented
CThe application will fail to start due to missing annotations
DThe repository will be treated as a service bean
Step-by-Step Solution
Solution:
  1. Step 1: Understand JpaRepository role

    JpaRepository provides default implementations for CRUD operations.
  2. Step 2: Consequence of concrete class

    Implementing a concrete class bypasses Spring Data's auto-implementation features.
  3. Final Answer:

    Spring Data JPA features like CRUD methods won't be auto-implemented -> Option B
  4. Quick Check:

    JpaRepository interface enables auto CRUD methods [OK]
Quick Trick: Repositories must extend JpaRepository for auto CRUD [OK]
Common Mistakes:
  • Assuming concrete classes get auto CRUD methods
  • Believing missing annotations cause startup failure here
  • Confusing repository with service bean

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Spring Boot Quizzes