MobX quiz

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

What is MobX State Tree (MST), and how does it relate to plain MobX?

1. What is MobX State Tree (MST), and how does it relate to plain MobX?
2. In what kind of application might MobX be a particularly good fit compared to a more rigid, immutable-state library?
3. What is a potential pitfall of MobX's deep observability when working with very large arrays or objects?
4. What is the core philosophy that distinguishes MobX from Redux-style state management?
5. How does the `observer` higher-order component from mobx-react (or mobx-react-lite) integrate MobX with React?
6. What does `runInAction` provide that a plain function wrapped in `action` might not cover?
7. Can MobX observable state include nested objects and arrays, and how does MobX handle mutations to them?
8. What is a common criticism or tradeoff of MobX's mutable-state, "magic" reactivity model compared to Redux's explicit, immutable model?
9. What does `makeAutoObservable` (in modern MobX) simplify compared to manually annotating each class field with `@observable`, `@computed`, or `@action`?
10. Why must an `observer`-wrapped React component actually read observable values during its render function for reactivity to work correctly?
11. How does MobX typically handle asynchronous operations like fetching data, given that actions are meant to be synchronous?
12. Does MobX require a specific UI framework like React to function?

More quizzes