1. What are all filters and why we use them?

[Link] MVC Filters are used to injects extra logic at the different
levels of MVC Framework request processing.
There are five type of filters in MVC.
 Authentication filter: Authentication filter runs before any
other filter or action method. Authentication confirm that you are
a valid or invalid user. Action filter implements
IAuthenticationFilter Interface.
 Authorization Filter: Authorization Filter are responsible for
checking user Access: these implement the IAuthorizationFilter
Interface.
 Action Filter: Action Filter is an attribute that you can apply to a
controller section or entire controller. These filter contains logic
that is executed before or after a controller action executes.
 Result Filter: These filter contains logic that is executed before
and after a view result is executed.
 Exception Filter: These filter can be used as an exception filter
to handle errors raised by either Controller Actions or Controller
action results.

2. Indexers in SQL.
SQL Indexes are special lookup tables that are used to speed up
the process of data retrieval. They hold pointers that refer to the
data stored in a database, which makes it easier to locate the
required data records in a database table.
While an index speeds up the performance of data retrieval queries
(SELECT statement), it slows down the performance of data input
queries (UPDATE and INSERT statements). However, these indexes
do not have any effect on the data.
SQL Indexes need their own storage space within the database.
Despite that, the users cannot view them physically as they are just
performance tools.
Syntax:
The basic syntax of a CREATE INDEX is as follows −
CREATE INDEX index_name ON table_name;

3. Foreign key in SQL.

In SQL, a Foreign Key is a column in one table that matches a
Primary Key in another table, allowing the two tables to be
connected together.
 A foreign key also maintains referential integrity between two
tables, making it impossible to drop the table containing the primary
key (preserving the connection between the tables).

4. View and partial view in MVC.

Partial View
Partial view does not contain
View contains the layout page
the layout page
Partial view does not check for a
_viewstart.cshtml. We cannot
_viewstart page is rendered
place any common code for a
before any view is rendered
partial view within the
_viewStart.cshtml page.
The Partial view is specially
View may have markup tags like
designed to render within the
html, body, head, title, meta
view and as a result it does not
etc.
contain any mark up.
Partial view is more lightweight
than the view. We can also pass
a regular view to the Render
Partial method.

5. MVC Life cycle.

6. First and FirstOrDefault Difference.

The major difference between First and FirstOrDefault is that First()
will throw an exception if there is no result data for the supplied
criteria whereas FirstOrDefault() will return the default value ( null )
if there is no result data.
7. Read-only and Const.
 const fields has to be initialized while declaration only, while
read-only fields can be initialized at declaration or in the
constructor.
 const variables can declared in methods ,while read-only fields
cannot be declared in methods.
 const fields cannot be used with static modifier, while read-only
fields can be used with static modifier.
 A const field is a compile-time constant, the read-only field can
be used for run time constants.

8. Routing in MVC.
Routing is a mechanism to process the incoming to URL to their
specific path . This comes under [Link] interface.
 Convention based routing
 Attribute based routing

9. Dependency Injection.
Dependency Injection (DI) is a software design pattern that helps
developers build better software. It allows us to develop loosely-
coupled code that is easy to maintain. Dependency Injection
reduces the hard-coded dependencies among your classes by
injecting those dependencies at run time instead of design time
technically.

10. State Management in MVC.

[Link] MVC also provides state management techniques that can
help us to maintain the data when redirecting from one page to
other page or in the same page after reloading. There are several
ways to do this in [Link] MVC –
 Hidden Field
 Cookies
 Query String
 ViewData
 ViewBag
 TempData
The above objects help us to persist our data on the same page or
when moving from “Controller” to “View” or “Controller” to
Controller”. Let us start practical implementation of these so that we
can understand in a better way.
Hidden Field
It is not new, we all know it from HTML programming. Hidden field is
used to hide your data on client side. It is not directly visible to the
user on UI but we can see the value in the page source. So, this is
not recommended if you want to store a sensitive data. It’s only
used to store a small amount of data which is frequently changed.
Cookies
Cookies are used for storing the data but that data should be small.
It is like a small text file where we can store our data. The good
thing is that a cookie is created on client side memory in the
browser. Most of the times, we use a cookie for storing the user
information after login with some expiry time. Basically, a cookie is
created by the server and sent to the browser in response. The
browser saves it in client-side memory.
We can also use cookies in [Link] MVC for maintaining the data on
request and respond.

Query String
In [Link], we generally use a query string to pass the value from
one page to the next page. Same we can do in [Link] MVC as well.
[Link]
I am making one request with the above URL. You can see that in
this, I am passing name’s value as a query string and that will be
accessible on “EditEmployee” action method in “Home” controller as
the following image shows.

ViewData
It helps us to maintain your data when sending the data from
Controller to View. It is a dictionary object and derived from
ViewDataDictionary. As it is a dictionary object, it takes the data in a
key-value pair.
Once you create ViewData object, pass the value, and make
redirection; the value will become null. The data of ViewData is not
valid for next subsequent request. Take care of two things when
using ViewData, first, check for null and second, check
for typecasting for complex data types.
ViewBag
The ViewBag’s task is same as that of ViewData. It is also used to
transfer the data from Controller to View. However, the only
difference is that ViewBag is an object of Dynamic property
introduced in C# 4.a. It is a wrapper around ViewData. If you use
ViewBag rather than ViewData, you will not have to do typecasting
with the complex objects and do not need to check for null.
Note
1. If you are using ViewData that is not defined on Controller, then it
will throw an error; but with ViewBag, it will not.
2. Do not use ViewBag and ViewData with the same name, otherwise,
only one message will display. See the following code in the
controller is using both ViewData and ViewBag with same name
“Message”.
TempData
TempData is also a dictionary object as ViewData and stores value in
key/value pair. It is derived from TempDataDictionary. It is mainly
used to transfer the data from one request to another request or we
can say subsequent request. If the data for TempData has been
read, then it will get cleaned. To persist the data, there are different
ways. It all depends on how you read the data.

Keep TempData
If you still want to persist your data with the next request after
reading it on “About” page that you can use “Keep()” method after
reading data on “About” page. The Keep method will persist your
data for next subsequent request.
@{
var data = ([Link])TempData["
Emp"];
[Link]();
}
public ActionResult Contact()
{
//TempData will available here because we have keep on about pa
ge
var tempEmpData = TempData["Emp"];
return View();
}
Peek TempData
Using Peek() method, we can directly access the TempData value
and keep it for next subsequent request.
@{
var data = ([Link])TempData.P
eek("Emp");
}
When we move to “Contact” page, the TempData will be available.
public ActionResult Contact()
{
//TempData will available because we have already keep data usin
g Peek() method.
var tempEmpData = TempData["Emp"];
return View();
}
11. Caching in MVC.
Caching is used to improve the performance in [Link] MVC.
Caching is a technique which stores something in memory that is
being used frequently to provide better performance. In [Link]
MVC, Output Cache attribute is used for applying Caching.
OutputCaching will store the output of a Controller in memory and if
any other request comes for the same, it will return it from cache
result.

Output Cache attribute can have a parameter.

12. Virtual keyword.

In C#, a virtual method is a method that can be overridden in a
derived class. When a method is declared as virtual in a base class,
it allows a derived class to provide its own implementation of the
method.
When an instance of the derived class is created and the overridden
method is called, the implementation in the derived class will be
executed instead of the implementation in the base class.
Using virtual methods can be useful in situations where you want to
provide a base implementation in a base class, but allow derived
classes to modify or extend the behaviour of that method.
Virtual Method in C#
1. By default, methods are non-virtual. We can't override a non-virtual
method.
2. We can't use the virtual modifier with the static, abstract, private,
or override modifiers.

13. Self join.

The SQL Self Join is used to join a table to itself as if the table were
two tables. To carry this out, alias of the tables should be used at
least once.
Self Join is a type of inner join, which is performed in cases where
the comparison between two columns of a same table is required;
probably to establish a relationship between them. In other words, a
table is joined with itself when it contains both Foreign
Key and Primary Key in it.

14. Stored Procedure and Function.

Differences between Stored Procedure and User Defined Function in
SQL Server
User Defined Stored Procedure
Function must return a value. Stored Procedure may or not return value
Will allow only Select statements, it will not Can have select statements as well as DM
allow us to use DML statements. such as insert, update, delete and so on
It will allow only input parameters, doesn't
It can have both input and output parame
support output parameters.
It will not allow us to use try-catch blocks. For exception handling we can use try cat
Transactions are not allowed within
Can use transactions within Stored Proced
functions.
We can use only table variables, it will not Can use both table variables as well as tem
allow using temporary tables. in it.
Stored Procedures can't be called from a
Stored Procedures can call functions.
function.
Procedures can't be called from
Select/Where/Having and
Functions can be called from a select
so on statements.
statement.
Execute/Exec statement can be used to ca
Stored Procedure.
A UDF can be used in join clause as a result
Procedures can't be used in Join clause
set.

15. nth Highest Salary in SQL.

select id,salary from Employee e1
where n-1=(select count(distinct salary)
from Employee e2 where [Link]>[Link]
)
with
cte
as
Select salary ,ROW_NUMBER() over(order by salary asc)
as rank
from Employee

select * from cte where rank = n;

16. Transaction.
A transaction is a unit or sequence of work that is performed on a
database. Transactions are accomplished in a logical order, whether
in a manual fashion by a user or automatically by some sort of a
database program.
 Atomicity − ensures that all operations within the work unit are
completed successfully. Otherwise, the transaction is aborted at the
point of failure and all the previous operations are rolled back to
their former state.
 Consistency − ensures that the database properly changes states
upon a successfully committed transaction.
 Isolation − enables transactions to operate independently of and
transparent to each other.
 Durability − ensures that the result or effect of a committed
transaction persists in case of a system failure.
Transactional Control Commands
Transactional control commands are only used with the DML
Commands such as - INSERT, UPDATE and DELETE. They cannot be
used while creating tables or dropping them because these
operations are automatically committed in the database. Following
commands are used to control transactions.
 COMMIT − to save the changes.
 ROLLBACK − to roll back the changes.
 SAVEPOINT − creates points within the groups of transactions in
which to ROLLBACK.
 SET TRANSACTION − Places a name on a transaction.

17. What is API.

A Web API in [Link] is a framework for building HTTP-based
services and applications, allowing communication between client
devices and a server over the web. It enables developers to create
RESTful (Representational State Transfer) services, typically used for
building lightweight, scalable, and stateless applications. Here’s a
breakdown of what an [Link] Web API does and why it’s used:
Key Components and Concepts of [Link] Web API
1. HTTP Protocol-Based:
o [Link] Web API is built on the HTTP protocol, enabling it to
work with various HTTP verbs (e.g., GET, POST, PUT, DELETE).
o It uses standard HTTP methods to handle CRUD (Create, Read,
Update, Delete) operations.
2. RESTful Services:
o It is designed for building RESTful services, which use
standard HTTP methods and a stateless protocol for
communication.
o Each endpoint in the Web API corresponds to a specific
resource, accessible via unique URLs.
3. JSON or XML Data Format:
o [Link] Web API can automatically serialize and deserialize
data to and from JSON, XML, or other formats, making it
versatile and compatible with many client-side applications.
o JSON is often the default format due to its lightweight and
widely accepted nature for web-based communication.
4. Routing:
 o [Link] Web API uses routing to map incoming requests to
appropriate controllers and actions.
o Routes can be configured using attribute routing (e.g.,
[Route("api/products")]) or conventional routing, defining
patterns to match URLs.
5. Controllers and Actions:
o The core building blocks of a Web API are Controllers and
Actions.
o A controller handles incoming HTTP requests and contains
action methods that define the behaviour for different HTTP
methods.
6. Dependency Injection and Middleware:
o [Link] Web API can be integrated with dependency injection
(DI) for managing services and objects throughout the
application’s lifecycle.
o It also uses middleware to handle cross-cutting concerns like
authentication, logging, and error handling.
Typical Use Cases for [Link] Web API
 Mobile Applications: APIs are commonly used to connect mobile
applications to a backend.
 Single Page Applications (SPA): SPAs use APIs to fetch data
dynamically and update the web page without full reloads.
 IoT and Smart Devices: Devices connected to the internet often
need APIs for data retrieval and control.
 Third-Party Integration: [Link] Web APIs are widely used for
creating public or private APIs that allow third-party integrations.
Benefits of Using [Link] Web API
 Platform Independence: Any client that can make HTTP requests can
interact with the API, making it versatile.
 Scalability and Performance: [Link] Web API is built on [Link]
Core, known for its performance and scalability.
 Ease of Testing: HTTP services in [Link] Web API can be easily
tested using tools like Postman or Swagger.
Example
A typical Web API controller might look like this:
csharp
Copy code
[Route("api/[controller]")]
[ApiController]
public class ProductsController : ControllerBase
{
private readonly IProductService _productService;

public ProductsController(IProductService productService)

{
_productService = productService;
 }

[HttpGet]
public async Task<ActionResult<IEnumerable<Product>>>
GetProducts()
{
var products = await _productService.GetAllProductsAsync();
return Ok(products);
}

[HttpGet("{id}")]
public async Task<ActionResult<Product>> GetProduct(int id)
{
var product = await _productService.GetProductByIdAsync(id);
if (product == null)
{
return NotFound();
}
return Ok(product);
}

[HttpPost]
public async Task<ActionResult<Product>>
CreateProduct(Product product)
{
var createdProduct = await
_productService.CreateProductAsync(product);
return CreatedAtAction(nameof(GetProduct), new { id =
[Link] }, createdProduct);
}
}
In this example:
 [HttpGet], [HttpPost], and other attributes map HTTP requests to
specific action methods.
 Dependency Injection (IProductService) allows for separation of
concerns and easy testing.
Summary
[Link] Web API is a powerful framework for creating RESTful,
HTTP-based services that can serve as the backend for a variety of
applications. Its modularity, performance, and compatibility with
[Link] Core’s ecosystem make it a widely-used choice for API
development.

18. What is Triggers in SQL.

 In SQL, a trigger is a set of instructions or an event-driven set of SQL
statements that automatically executes in response to certain
events on a particular table or view. Triggers are commonly used to
maintain data integrity, enforce business rules, or perform audit
logging in a database.
Types of Triggers
1. DML Triggers (Data Manipulation Language Triggers):
o These are activated by data manipulation events like INSERT,
UPDATE, and DELETE.
o Common types of DML triggers include:
 AFTER Triggers: Execute after the triggering event
completes. For example, an AFTER INSERT trigger fires
after a new row is inserted.
 INSTEAD OF Triggers: Replace the triggering event. For
example, an INSTEAD OF DELETE trigger can be used to
prevent direct deletions and perform an alternative
action.
o These triggers can operate on each row affected or on the
statement as a whole.
2. DDL Triggers (Data Definition Language Triggers):
o These are fired by changes in the database schema, such as
CREATE, ALTER, or DROP commands.
o Useful for auditing changes to the structure of a database.
3. Logon Triggers:
o These triggers are specific to logon events in the database
and can be used to control or monitor user login activity.
Advantages of Triggers
 Automated Enforcements: Automatically enforce business rules or
constraints without requiring additional code in the application layer.
 Data Integrity: Maintain data integrity across tables.
 Auditing: Track changes to tables, logging user actions and history.
 Complex Validations: Perform complex validations that might not be
possible using standard constraints alone.

19. What is Function in SQL.

In SQL, a function is a stored program that performs a specific task
and returns a single result (value). Functions are useful for
encapsulating frequently-used logic in reusable blocks of code,
allowing you to perform calculations, manipulate data, or perform
operations within SQL queries. Functions can accept input
parameters, process data, and return a result, making them
versatile tools for database operations.
Types of Functions in SQL
1. System Functions:
 o SQL provides several built-in functions to perform various
operations. These are categorized into:
 Scalar Functions: Operate on a single value and return a
single result (e.g., LEN(), ROUND(), GETDATE()).
 Aggregate Functions: Perform calculations on a set of
values and return a single result (e.g., SUM(), AVG(),
COUNT()).
2. User-Defined Functions (UDFs):
o These are custom functions created by users to perform
specific operations that are not covered by built-in functions.
o User-defined functions in SQL are further divided into:
 Scalar Functions: Return a single value (e.g., a
calculated result based on input).
 Table-Valued Functions (TVFs): Return a table as a result,
which can be used as a subquery in a FROM clause.

20. How to Get only and delete all duplicate records in SQL.
With CTE
AS(
Select Id, ROW_NUM() over(Partition by id order by id asc)
As Data
From Employee)

Delete CTE Where Data>1

21. What is Validation In MVC and how to implement?

In [Link] MVC, validation is a process to ensure that the data
provided by users meets the required criteria before it is saved in
the database. It helps in maintaining data integrity, preventing
incorrect data entry, and providing feedback to users.
Types of Validation in MVC
1. Client-Side Validation:
o Validates data on the client-side, often using JavaScript.
o Provides immediate feedback to users, improving user
experience.
o Reduces server load by catching errors before data
submission.
o MVC provides built-in support for client-side validation through
unobtrusive JavaScript.
2. Server-Side Validation:
o Validates data on the server-side after submission.
o Essential as a security measure because client-side validation
can be bypassed.
 o Ensures that only validated data is processed and stored in
the database.
Validation Methods in MVC
1. Data Annotations:
o A set of attributes added to model properties to enforce
validation rules.
o Attributes like [Required], [StringLength], [Range], and
[RegularExpression] help define validation rules directly on the
model.
2. Custom Validation:
o Allows the creation of custom validation attributes or
validation logic to implement rules that are not covered by
built-in data annotations.
3. Model Validation:
o Use ModelState in the controller to check if the model passes
validation before further processing.

22. How to enable Sorting through SQL.

SELECT FirstName, LastName, City FROM Customers ORDER BY LastName ASC;
23. What are the Async and Await keyword.

24. What are Left, Right, Full, Union and Union all and
Intersection in SQL.
25. What is Inheritance.
26. What is Interface.
27. What is Abstraction.
28. What is Class type.
Abstract class
Sealed Class
Static Class
Partial Class
29. What is View in MVC.
30. What is Temp table.
31. What is difference between View Data and TempData.
32. How to send Controller to Controller data send.
33. What is Looping in C#.
34. What is Dependency Injection.
35. What is Indexers in SQL.
36. What is User Defined Function in SQL.
37. What is Aggregate Function in SQL.
38. What is Cursors in SQL.
39. What is Function in SQL.
40. What is Magic Table.
41. What is Pivot Table.
42. What is Entity Framework.
43. What is Triggers.
44. What is Constraint.
45. What is For and Foreach loop.
46. What is Extension method.
47. What is Partial Class.
48. What is DbSet?
49. What is Var and Dynamic keyword.
50. What is Methodology in C#.
51. How to call the Action Methods?
52. What is Dictionary.
53. What is Abstraction/ Encapsulation
54. What is HttpResponse.
55. FromBody and FromQuery.
56. How to enable Swagger?
57. How to Enable Dependency Injection?
58. Where clause in Linq?
59. How to enable session?
60. Advantage of Dot Net Core over MVC and Classic
[Link].
61. Middleware in Dot Net Core.
62. Which dot net framework support API?
63. Full Outer Join and Outer Join
64. Enable cache in MVC.
65. Return Type of Action Method in MVC.
66. Return Type of APIs.
67. What is 500 error in API?
68. what is .Net & explain its features?
69. What is a namespace in .NET?
70. What is an assembly in .NET?
71. What is the difference between a managed and an
unmanaged code?
72. What are the componenets of .Net framework?
73. Explain the structure of main method.
74. What is array and explain its type?
75. What is string and why it is immutable?
76. Difference between ToString() and [Link]()?
Both are used to Convert the string, the main difference between them is
that [Link]() method handles null while ToString does not and it
throw null reference error.
77. What is constructor? Explain its type advantage.
Constructor is a special type of method which invokes automatically at the
time of creating instance of a class. It is used to initialize the member of
class. Constructor have same name as class itself. Constructor do not
specify a return type not even void, because it returns the instance of the
class itself.
A constructor is automatically called when an object is created.
There are five types of Constructor:
1. Default
2. Parameterized
3. Copy
4. Static
5. Private

78. What is Polymorphism and type of polymorphism?

Ability a class to perform in different task is known as polymorphism. It
has two types, Static Polymorphism and Dynamic Polymorphism.
79. What is function overloading. Explain with examples.
Creating multiple function with same name and different signature is
known as Function Overloading and it is also knows as Early Binding, Static
Polymorphism and Compile time Polymorphism.
80. What is function overriding. Explain with Example.
Creating multiple function with same name and same signature but
different implementation in Superclass and Subclass is known as Function
Overriding and it is also knows as Late Binding, Dynamic Polymorphism
and Run time Polymorphism.

81. What is virtual keyword?

 Virtual keyword is used to declare the Virtual method and a virtual method
is a method that can be overridden in a derived class.
[Link] is abstraction. Explain with example.
Hiding relevant details and show only functionality is known as
Abstraction.
83. Different between Virtual and Abstract method?
 Virtual Method can be overridden while Abstract method must be
overridden.
 Abstract keyword used in Abstract method and Virtual keyword is used in
Virtual Method.
 Abstract method has only declaration not definition while as Virtual
method can have declaration as well as definition.
 We can declare Abstract method only in Abstract class while Virtual
Method can be declared in Abstract and Non-Abstract class.
84. Different between Overloading and overriding?
 Creating method with same name and but diff signature is Overloading,
While creating method with same name, same signature but diff
implementation.
 Overloading is implemented in Current/same class while Overriding is
implemented in Super and Subclass.
 In Overloading, Return type may or may not be same while in Overriding
return type must be same.

85. Diff between Abstract class and normal class.

Normal Class Abstract class

 It may or may not be  It must be inherited.
inherited.
 It does not contain any  It should have at least one
abstract method. abstract method.
 It can be instantiated.  It can not be instantiated.
 It can be declared with  It can not be declared as
sealed. Sealed.

86. It is possible to create constructor of abstract class and

interface?
87. Diff between static, var and instance keyword.

88. Why we use static constructor ?

89. What is C# reflcetion?
90. Explain concept of Boxing and Unboxing?
91. Type of relationships between class and objects?
92. What is error and its type?
93. What is exception and Exception handling?
94. How to handle exception?
95. use of throw keyword.
96. Explain try,catch, finally .
97. What is user defined exception and how to create?
98. Diff between final, finally, and finallize keyword.
99. What are the different parts of an Assembly?
100. What is .NET Core?
101. What is [Link] Core?
102. What are the advantages of [Link] Core over [Link]?
103. What are the features provided by [Link] Core?
104. How do you handle errors in .NET Core?
105. What are the key features of .Net Framework?
106. What is the difference between .NET Framework
and .NET Core?
107. Explain about major components of the .NET framework.
108. What is the role of the Startup class in .NET Core?
109. What is middleware in .NET Core?
110. Explain the architecture of .NET Core.
111. What are the different types of hosting models
supported in .NET Core?
112. How do you implement middleware in .NET Core?
113. What is the role of the [Link] file in .NET Core?
114. Explain the concept of Razor Pages in .NET Core.
115. How does .NET Core support cross-platform
development?
116. What is the difference between Debug and Release
mode in .NET?
117. How do you configure logging in .NET Core?
118. What is the difference between synchronous and
asynchronous programming in .NET Core? When should you
use each approach?
119. What are the benefits of using Entity Framework Core for
data access in a .NET Core application?
120. What is Dependency Injection, and how is it used in .NET
Core?
121. What are the features provided by [Link] Core?
122. What are Metapackages?
123. What is the startup class in [Link] core?
124. What is the use of the ConfigureServices method of the
startup class?
125. What is the use of the Configure method of the startup
class?
126. What is middleware?
127. What is the difference between [Link]()
and [Link]()?
128. What is the use of the "Map" extension while adding
middleware to the [Link] Core pipeline?
129. What are the various JSON files available in [Link]
Core?
130. How to enable Session in [Link] Core?
131. What is tag helper in [Link] Core?
132. How to disable Tag Helper at the element level?
133. What are Razor Pages in [Link] Core?
134. How can we do the automatic model binding in Razor
pages?
135. How can we inject the service dependency into the
controller?