MVVM quiz

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

How does MVVM's separation of concerns differ from a design where a View directly manipulates Model objects with no intermediary layer?

1. How does MVVM's separation of concerns differ from a design where a View directly manipulates Model objects with no intermediary layer?
2. What potential downside can arise if a ViewModel accumulates too much unrelated logic and state over time (a "massive ViewModel")?
3. What is a common criticism of adopting MVVM for a very simple screen with minimal state or logic?
4. What is a reasonable way to decide the appropriate granularity for a ViewModel (one ViewModel per screen, vs. one per smaller reusable component)?
5. Why is dependency injection commonly used alongside MVVM (injecting services/repositories into a ViewModel rather than the ViewModel creating them directly)?
6. How does a ViewModel typically expose asynchronous operations (like a network request) to the View in MVVM?
7. Why does keeping the ViewModel free of direct UI framework references (like a specific button class) matter for testability?
8. What is a "command" in the context of MVVM (as used in frameworks like WPF)?
9. How does the View typically communicate user actions (like a button tap) back to the ViewModel in MVVM?
10. What does MVVM stand for?
11. What is the key mechanism that typically connects a View to its ViewModel in MVVM (in frameworks that support it natively)?
12. What is a practical benefit of a ViewModel exposing already-formatted, presentation-ready values (like a formatted date string) rather than raw Model data?

More quizzes