Absinthe quiz

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

How does Absinthe typically represent a validation or business-logic error returned from a mutation resolver?

1. How does Absinthe typically represent a validation or business-logic error returned from a mutation resolver?
2. What is the purpose of GraphQL "mutations" in an Absinthe schema, as distinct from "queries"?
3. What is a "fragment" in a GraphQL query sent to an Absinthe server?
4. What is a GraphQL "subscription", which Absinthe supports via Phoenix Channels?
5. Why does Absinthe integrate particularly well with the Phoenix web framework?
6. What does defining a custom GraphQL scalar type in Absinthe (e.g. for a Date) allow?
7. What does it mean that GraphQL (and Absinthe) queries are typically served over a single endpoint, unlike REST's many resource-specific endpoints?
8. Why might overly deep or complex GraphQL queries pose a performance/security concern for an Absinthe-backed API, and what is one way to mitigate it?
9. What is Absinthe?
10. What is the relationship between Absinthe's `object`, `field`, and `arg` macros when defining a query?
11. What is a "resolver" in the context of an Absinthe GraphQL field?
12. What is a practical benefit of GraphQL's strongly-typed schema (as enforced by Absinthe) for API consumers?

More quizzes