I used N-tier architecture most of my projects.There are three layer in N-tier architecture:1) UI Layer 2) Business Logic Layer 3) Data Access LayerBeside this i use two "Helper" class : 1) Data provider 2) DB connectionThis architecture is enough to fulfil my current project demand

My current architecture is a simple 3 tier architecture with UI in ASP.NET, middle layer are simple .NET classes and DAL is using enterprise application blocks. The UI(view) is responsible to take user inputs , all my business validations are centrally located in middle layer and the data access layer is responsible to execute stored procedure and SQL queries to SQL Server. Strongly typed business objects are used to pass data from one layer to other layer. The database of the project is in a 3rd normal form." So first start Explanation with the overall architecture, talk about each layer, how data is passed between each layer and the database design structure.

The answer of this question is not common to all just describe the architecture of the latest project that you have done.

1-UI- UI Is made in asp.net 2-Data Access- is made Application enterprise block -3-Business Logica layer-Used for creating class of business entity

I have Used N-tier layer in our project 1. UI layer which is nothing but our MVC project 2. We have Business logic layer which consist of ll business related logic 3. Data Access Layer which is related to database operation and 4. Web API layer which consist of services related logic..Hope this will help... Good Luck ...

I think this is the first question which anybody will ask as an interviewer. So they can get an idea of your domain knowledge and your technical skills. Just detail out all the layers available in your project and responsibility of each layer.

I used 3-tier architecture most of my projects. 1. Presentation Layer 2. Business Logic Layer 3. Data Access Layer