If a request is blocked by Request Filtering in IIS 7.0, what is the likely outcome?

If a request is blocked by Request Filtering in IIS 7.0, what is the likely outcome?

• A. The request is silently dropped and the client never receives a response.
• B. The request is redirected to a different URL.
• C. The request is logged but later processed.
• D. The request is blocked or rejected to protect the server.

Answer: (D)

Request Filtering in IIS 7.0 acts as a security gate that blocks requests which match configured rules, such as disallowed file extensions, suspicious characters, or overly long URLs. When a request triggers these filters, IIS halts processing the request and returns an error to the client, often accompanied by a log entry for auditing. This behavior is specifically intended to protect the server from potentially harmful or unintended access. So the likely outcome is that the request is blocked or rejected to protect the server.

Request Filtering in IIS 7.0 acts as a security gate that blocks requests which match configured rules, such as disallowed file extensions, suspicious characters, or overly long URLs. When a request triggers these filters, IIS halts processing the request and returns an error to the client, often accompanied by a log entry for auditing. This behavior is specifically intended to protect the server from potentially harmful or unintended access. So the likely outcome is that the request is blocked or rejected to protect the server.