Model View Controller (MVC) Interview Preparation Guide
Download PDF

MVC frequently Asked Questions in various Model View Controller (MVC) job Interviews by interviewer. Get preparation of MVC job interview

48 MVC Questions and Answers:

1 :: What is Model View Controller (MVC)?

Model–View–Controller (MVC) is a design pattern in which "the user input, the modeling of the external world, and the visual feedback to the user are explicitly separated and handled by three types of object." The model consists of data and business rules, and the controller mediates the communication between the model and the user. A view can be any visual element such as a printout or a web page. Multiple views of the same data are possible, such as a pie chart for management and a spreadsheet for accountants.

2 :: What is best way to get a reference to the viewport from anywhere in the code?

I would use refs config to set a reference on the Application/Controllers

3 :: How to run an app in a page with existing content? (no viewport i am guessing, but what else do i need to know?)

There are no requirements.. if you want to use a Viewport you can! If you want to render components into divs... you can do that aswell.

4 :: How to use model validation rules with a form?

Search on Global Guideline I hope you will get answer

6 :: Tell me in other mvc systems, the rule is fat models, skinny controllers. ie the business logic goes in the models and all controllers do is load/save models and load/kill views. is this the extjs way?

What MVC are you using? Views are for presenting the data from a Model. Model is just a representation of data. Controllers should be what controls you app like telling your view to display this model.

9 :: Is it possible to combine ASP.NET webforms and ASP.MVC and develop a single web application?

Yes, it is possible to combine ASP.NET webforms and ASP.MVC and develop a single web application.

10 :: What does Model, View and Controller represent in an MVC application?

Model: Model represents the application data domain. In short the applications business logic is contained with in the model.

View: Views represent the user interface, with which the end users interact. In short the all the user interface logic is contained with in the UI.

Controller: Controller is the component that responds to user actions. Based on the user actions, the respective controller, work with the model, and selects a view to render that displays the user interface. The user input logic is contained with in the controller.