GSEC · Question #380
When an IIS filename extension is mapped, what does this mean?
The correct answer is B. The file and all the data from the browser's request are handed off to the mapped interpreter. In IIS, mapping a filename extension associates that extension with a specific handler so that matching requests are forwarded to that interpreter for server-side processing.
Question
When an IIS filename extension is mapped, what does this mean?
Options
- AFiles with the mapped extensions cannot be interpreted by the web server.
- BThe file and all the data from the browser's request are handed off to the mapped interpreter.
- CThe files with the mapped extensions are interpreted by CMD.EXE.
- DThe files with the mapped extensions are interpreted by the web browser.
How the community answered
(51 responses)- A2% (1)
- B82% (42)
- C10% (5)
- D6% (3)
Why each option
In IIS, mapping a filename extension associates that extension with a specific handler so that matching requests are forwarded to that interpreter for server-side processing.
Mapping an extension enables interpretation, not prevents it - unmapped extensions are what IIS typically cannot execute.
When IIS maps a filename extension to an interpreter (such as an ISAPI DLL or CGI executable), any HTTP request for a file with that extension causes IIS to pass both the file path and the full request data to the mapped handler. The handler then processes the file server-side and returns the output to the client, enabling dynamic content generation for extensions like .asp, .php, or .pl.
Mapped extensions are handed to the specific interpreter defined in the mapping configuration, not generically to CMD.EXE.
Interpretation of server-side scripts occurs on the web server, not in the client's web browser.
Concept tested: IIS filename extension mapping and request handling
Source: https://learn.microsoft.com/en-us/iis/configuration/system.webserver/handlers/
Topics
Community Discussion
No community discussion yet for this question.