Test your Akka knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
What does it mean that message delivery in classic Akka actors is generally "at-most-once" by default, and why does that matter for application design?
In this round
What does it mean that message delivery in classic Akka actors is generally "at-most-once" by default, and why does that matter for application design?
Why does the actor model's "no shared mutable state between actors" property help avoid classic concurrency bugs like race conditions?
What is Akka HTTP, and how does it relate to the rest of the Akka ecosystem?
How does Akka's "let it crash" supervision strategy typically decide what to do when a child actor throws an unhandled exception?
What is the relationship between Akka and the Play Framework in the Scala/JVM ecosystem?
What is Akka Typed, and what problem does it solve compared to the original "classic" untyped Akka actors API?
What does it mean that Akka provides tools for building "reactive" systems, per the Reactive Manifesto (responsive, resilient, elastic, message-driven)?
What does Akka's hierarchical actor supervision model provide, similar in spirit to Erlang/Elixir's supervision trees?
What does "location transparency" mean in the context of Akka actors, particularly relevant to Akka Cluster?
Why might a JVM application choose Akka's actor model over traditional Java concurrency primitives (threads, locks, `synchronized` blocks) for a complex concurrent system?