Which design pattern separates concerns into a model, a view, and a controller?

Which design pattern separates concerns into a model, a view, and a controller?

• A. MVVM
• B. MVP
• C. Client-Server
• D. MVC (Model-View-Controller)

Answer: (D)

The main idea here is separating responsibilities into three distinct parts: data and business rules, how that data is presented, and how user input is handled. In this pattern, the Model manages the data and core logic, the View renders the user interface and displays data to the user, and the Controller handles user actions, translating them into updates to the Model (and sometimes updates to the View). The flow typically goes like this: a user interacts with the interface (the View), the View delegates the action to the Controller, the Controller updates the Model, and the Model notifies the View to refresh the display. This separation makes it easier to modify the UI without touching the underlying data, to test components in isolation, and to reuse components across different parts of the application. Other patterns you might see adjust the roles slightly—MVVM uses a ViewModel with data binding to the View, and MVP uses a Presenter with a more passive View—while ensuring a triad around UI concerns. Client-Server is a different architectural approach focused on distributed components rather than UI structure. The trio of Model, View, and Controller directly matches the description of separating concerns into those three areas.

The main idea here is separating responsibilities into three distinct parts: data and business rules, how that data is presented, and how user input is handled. In this pattern, the Model manages the data and core logic, the View renders the user interface and displays data to the user, and the Controller handles user actions, translating them into updates to the Model (and sometimes updates to the View). The flow typically goes like this: a user interacts with the interface (the View), the View delegates the action to the Controller, the Controller updates the Model, and the Model notifies the View to refresh the display. This separation makes it easier to modify the UI without touching the underlying data, to test components in isolation, and to reuse components across different parts of the application.

Other patterns you might see adjust the roles slightly—MVVM uses a ViewModel with data binding to the View, and MVP uses a Presenter with a more passive View—while ensuring a triad around UI concerns. Client-Server is a different architectural approach focused on distributed components rather than UI structure. The trio of Model, View, and Controller directly matches the description of separating concerns into those three areas.