IIS Server Configuration and Performance Quiz

Answer is 50

Remote virtual directories introduce network latency and I/O overhead because content must be accessed across the network instead of locally. This significantly degrades performance compared to local storage. The other options (keeping web and FTP on separate machines, using ISAPI extensions over filters, minimizing FTP isolation) are generally valid performance optimization strategies for IIS.

IIS 6.0 defaults to allowing 4 concurrent CGI applications to execute simultaneously. This limit exists because CGI creates a new process for each request, which is resource-intensive. Administrators can adjust this setting based on server capacity and requirements, but 4 is the out-of-the-box default.

To answer this question, the user needs to be familiar with IIS and its features. The feature for monitoring the health of multiple worker processes servicing an application pool is called Rapid-fail protection.

A. HTTP keep-alive: This is a feature that allows multiple requests to be sent over the same TCP connection, which can improve performance by reducing the overhead of setting up and tearing down connections. However, it is not related to monitoring the health of worker processes.

B. IS monitoring services: This is not a feature in IIS. Therefore, it is incorrect.

C. Application failsafe: This is not a feature in IIS. Therefore, it is incorrect.

D. Rapid-fail protection: This feature monitors the status of worker processes and disables any that are not responding or are experiencing errors. This helps to ensure that users are not routed to a failing worker process, which can improve the reliability and availability of the application. Therefore, the correct answer is D.

The Answer is: D

The Memory:Pages/sec counter measures hard page faults - when Windows must read from the disk rather than RAM. A value under 20 (roughly) is considered acceptable and indicates sufficient RAM. Values consistently above 20 suggest memory pressure. The option about 'coffee and relax' is the intended answer despite its informal tone, as it correctly indicates the system is healthy.

The Web Application Stress Tool (WAST) is Microsoft's tool for simulating multiple concurrent users connecting to a web server. It tests how IIS handles load by mimicking real-world traffic patterns. Microsoft Operations Manager (MOM) is for monitoring, and the other 'Traffic' options are fictional or misnamed distractors.

To solve this question, the user needs to know about HTTP compression and its history.

HTTP compression is a technique that reduces the amount of data transmitted between a server and a client by compressing the data before it is sent over the network. This can improve the performance of web pages and reduce the amount of bandwidth required to load them.

Now, let's go through each option:

A. 1996: This option is incorrect. HTTP compression was not introduced until later, so web browsers developed before 1996 would not support it.

B. 1997: This option is also incorrect. While some early implementations of HTTP compression were developed around this time, it was not widely adopted until later.

C. 1998: This option is correct. The first version of the HTTP compression protocol, called "mod_gzip," was introduced in 1998. Web browsers developed after this time should support HTTP compression.

D. 1999: This option is incorrect. While HTTP compression was becoming more widely used around this time, it had already been introduced the year before.

E. 2000: This option is incorrect. By 2000, HTTP compression was well established and widely supported by web browsers.

Therefore, the answer is: C. 1998

Application pools in IIS 6 isolate worker processes for stability and security, but they do NOT apply to CGI applications. CGI runs in a separate process space outside the application pool architecture. ISAPI extensions, ASP, and ASP.NET applications all run within application pools and benefit from their isolation and recycling features.

NEVER leaving caching enabled is obviously detrimental to performance - caching is a key optimization. The distractors have typos but identify bad practices: using exceptions for control flow (trap exceptions) is inefficient; disabling unused session state is ACTUALLY good practice; and 'storied procedures' is a garbled 'stored procedures' which ARE better than ad-hoc queries. The claimed answer D is correct as the 'NOT good' option.

Making the paging file large and keeping it on a single drive prevents fragmentation because the file has room to grow contiguously. Static sizing helps but isn't sufficient alone - the file must also be large enough. Dynamic sizing causes fragmentation as the file shrinks and expands. Third-party defragmentation tools aren't the primary solution.