You deploy an ASP.NET MVC Web application to Internet Information Services (IIS). The application has a
secure area that provides access to custom reports.
You must develop custom business logic to support the reports. The custom business logic has the following
requirements:
It must run each time that a report is requested.
It must not run for other IIS requests.
It must be mapped to the request extension of the report.
It must be written by using a managed language that is supported by the .NET framework.
You must be able to quickly modify and deploy updates to the business logic.
You need to develop the custom business logic.
What should you do?
A.
Update the report logic to include the custom business logic. Use WebDAV to publish the reports to the
server.
B.
Develop a new HTTP module that includes the custom business logic. Deploy the HTTP module to IIS.
C.
Develop a new HTTP handler that includes the custom business logic. Deploy the HTTP handler to IIS.
D.
Develop a new ISAPI filter that includes the custom business logic. Deploy the ISAPI filter to IIS.
Explanation:
An ASP.NET HTTP handler is the process that runs in response to a request that is made to an ASP.NET Web
application.
ASP.NET maps HTTP requests to HTTP handlers based on a file name extension.
Incorrect:
Not B: HTTP modules differ from HTTP handlers. An HTTP handler returns a response to a request that is
identified by a file name extension or family of file name extensions. In contrast, an HTTP module is invoked for
all requests and responses. It subscribes to event notifications in the request pipeline and lets you run code in
registered event handlers.
https://msdn.microsoft.com/en-us/library/bb398986.aspx