Play Framework quiz

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

What is Play's built-in JSON support commonly used for in building REST APIs?

1. What is Play's built-in JSON support commonly used for in building REST APIs?
2. What is a general architectural tradeoff a team should weigh when choosing between Play Framework and a more traditional Java EE / Spring MVC-style servlet-based framework?
3. What does Play's dependency injection support (commonly via Guice) provide for a Play application?
4. What is Play's built-in templating engine (Twirl) used for?
5. How does Play Framework typically define URL routing?
6. Why might Play Framework applications commonly return a `Future[Result]` from a controller action rather than a plain `Result`?
7. What does it mean that Play Framework is built around a "non-blocking, asynchronous I/O" model, as opposed to a traditional thread-per-request servlet model?
8. What is a Play "controller" and "action," in the framework's MVC-style architecture?
9. What is a "reverse route" in Play Framework, generated from the `conf/routes` file?
10. What is a Play "Filter," and what is a common use case for one?
11. How did Play Framework historically relate to Akka?
12. Why might a company evaluating Play Framework for a new service consider its relative position in the current JVM web framework landscape (compared to, say, Spring Boot)?

More quizzes