Ah, the age-old debate: class or interface? It's like asking whether to use a hammer or a screwdriver to build a house. The answer is, of course, both have their place in the world of software engineering.
Hold on, did anyone else notice the hilarious typo in the question? It says 'CustomerRepository should be a class, not an interface.' That's like saying 'a square should be a circle, not a square.' Comedy gold!
Hmm, I'm not sure about this one. Option B looks promising, but I'm not convinced that JPA annotations are required for Spring Data JDBC. I'll have to think about this some more.
I'm leaning towards option C. Spring Data JPA can automatically generate repository implementations, so that seems like the best fit for this scenario.
I think option D is the correct answer. The question states that an implementation of the CustomerRepository must be implemented and declared as a Spring Bean, which aligns with that choice.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Xochitl
10 days agoSheridan
11 days agoElly
12 days agoSheridan
13 days agoCaprice
14 days agoSharika
14 days agoRyann
15 days agoJolene
16 days agoSharika
17 days agoTeresita
19 days agoChristiane
2 days agoLisbeth
8 days agoLoren
22 days ago