MobX quiz

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

What happens if you try to mutate an observable outside of an `action` while MobX is running in "strict mode" (enforceActions)?

1. What happens if you try to mutate an observable outside of an `action` while MobX is running in "strict mode" (enforceActions)?
2. What is a MobX "reaction" (or `autorun`)?
3. How does MobX typically handle asynchronous operations like fetching data, given that actions are meant to be synchronous?
4. What does the `observable` decorator/function do in MobX?
5. What is a MobX "computed" value?
6. What does "fine-grained reactivity" mean in the context of MobX, compared to some other state management approaches?
7. What is the core philosophy that distinguishes MobX from Redux-style state management?
8. What is a potential pitfall of MobX's deep observability when working with very large arrays or objects?
9. Can MobX observable state include nested objects and arrays, and how does MobX handle mutations to them?
10. What is a common criticism or tradeoff of MobX's mutable-state, "magic" reactivity model compared to Redux's explicit, immutable model?
11. Why does MobX recommend wrapping state mutations in `action`?
12. What is MobX State Tree (MST), and how does it relate to plain MobX?

More quizzes