Clean Architecture quiz

Test your Clean Architecture knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.

What is a Data Transfer Object (DTO), and why might Clean Architecture use one when passing data across a layer boundary?

1. What is a Data Transfer Object (DTO), and why might Clean Architecture use one when passing data across a layer boundary?
2. What is a "Gateway" (or "Repository" interface) in Clean Architecture, and why is it defined in an inner layer even though its implementation lives in an outer layer?
3. What is a "Controller" (or "Presenter") responsible for in Clean Architecture, and what layer does it belong to?
4. What does it mean that Clean Architecture aims to make "the database and the web... details" rather than core architectural decisions?
5. What is a realistic risk of over-applying Clean Architecture's abstraction layers even where they aren't needed?
6. What is the role of "Use Cases" (or "Interactors") in Clean Architecture?
7. In Clean Architecture's typical layering, what are "Entities"?
8. What problem does "leaky abstraction" pose to a Clean Architecture-style repository interface, and what's a concrete example?
9. What is the "Dependency Rule" in Clean Architecture?
10. What is a "boundary" in Clean Architecture terminology?
11. What is the central goal of Clean Architecture (as popularized by Robert C. Martin)?
12. What is a reasonable pragmatic guideline for deciding how strictly to apply Clean Architecture's full layering to a given project?

More quizzes