Identify a concept which is NOT related to MVC pattern among the below:
-
The MVC pattern introduces extra classes due to the separation of the model,view and the controller components
-
The view component accesses the enterprise data through the model component
-
The model-view separation principle states that the application logic should not be put in the UI object method
-
The Model-View separation principle helps minimize the impact of requirement change in the interface on the controller layer
This question tests understanding of MVC relationships. Options A, B, and C all describe genuine MVC concepts: A acknowledges the pattern introduces more classes due to separation, B correctly states views access data through models, and C accurately states application logic should not reside in UI methods. Option D claims Model-View separation minimizes interface changes' impact on the controller layer, which is misleading. Model-View separation primarily isolates business logic from presentation. The controller layer sits between them and handles input, but the principle specifically addresses decoupling Model from View, not interface-to-controller relationships.