DRAG DROP
You plan a new ASP. NET MVC application.
The application uses the Model-View Controller (MVC) pattern to separate the modeling of the domain, the
presentation, and the actions. This separation is based on user input into three separate classes.
You need to diagram the structural relationship between the three classes.What should you do? To answer, drag the appropriate class to the correct location or locations. Each class
name may be used once, more than once, or not at all. You may need to drag the split bar between panes or
scroll to view content.
Select and Place:
Answer: 
Explanation:
Graphically, MVC can be shown like on image bellow:
http://www.beansoftware.com/ASP.NET-Tutorials/Intro-ASP.NET-MVC.aspx
Incorrect ?
From the “Developing ASP.NET MVC 4 Web Application” Book*, Chapitre 1, page 7 : http://www.daoudisamir.com/references/vs_ebooks/asp_mvc4.pdf
Dunno which one is correct, depending of the point of view, but I prefer to trust the official Microsoft book than a random web site…
Hi, I found the diagram on the msdn site and this is different from the book. But I find important that MSDN version provides comment which I find correct. So I believe the MSDN version. https://msdn.microsoft.com/en-us/library/ff649643.aspx It is important to note that both the view and the controller depend on the model. However, the model depends on neither the view nor the controller. This is one the key benefits of the separation. This separation allows the model to be built and tested independent of the visual presentation. The separation between view and controller is secondary in many rich-client applications, and, in fact, many user interface frameworks implement the roles as one object. In Web applications, on the other hand, the separation between view (the browser) and controller (the server-side components handling the HTTP request) is very well defined.
correct