Which architectural pattern uses a View and a ViewModel to enable data binding with the Model?

• A. MVVM
• B. MVC
• C. MVP
• D. Layered Architecture

Answer: (A)

The main idea being tested is a binding-friendly separation between the user interface and the data through a ViewModel. In this pattern, the View binds directly to properties and commands exposed by the ViewModel. The ViewModel sits between the UI and the Model, exposing data from the Model and handling user actions, translating them into changes to the Model and updating its own bound properties so the UI updates automatically. This makes the UI simple and easy to unit test, since the ViewModel can be tested without any UI. The Model stays focused on business data, while the View handles rendering and input through bindings to the ViewModel. Other patterns don’t center on this binding bridge—the Controller in MVC and the Presenter in MVP coordinate UI logic in different ways, and Layered Architecture is a general structural approach rather than a binding pattern.