Certified Incident Handler (CIH) Practice Ecam

Disable ads (and more) with a membership for a one time $2.99 payment

Prepare for the Certified Incident Handler (CIH) Exam. Enhance your knowledge with interactive quizzes and detailed insights into cyber incident handling. Boost your exam readiness with our expert-designed questions!

Each practice test/flash card set has 50 randomly selected questions from a bank of over 500. You'll get a new set of questions each time!

Practice this question and more.


What is the correct sequence to identify the location of the IIS log files on a Windows Server machine?

  1. 2 → 4 → 1 → 3

  2. 1 → 3 → 5 → 2 → 4

  3. 2 → 4 → 1 → 3 → 5

  4. 3 → 2 → 4 → 1

The correct answer is: 2 → 4 → 1 → 3 → 5

The correct sequence to identify the location of the IIS log files on a Windows Server machine involves several specific steps. These steps typically encompass a thorough understanding of the IIS configuration and the default paths established in Windows Server. Starting with the server's role as a web server, the logs are generally stored in a directory that can be found through the IIS Manager. The process often begins by opening the IIS Manager, where you can locate the site for which you need to find the log files. From there, the logging feature can be accessed, allowing you to view or change settings regarding log file generation. The log files are typically located in a default directory such as C:\inetpub\logs\LogFiles, which is a standard path for IIS logging. Thus, identifying the log path begins with understanding where IIS stores its log files by default, following up with any modifications that may have been applied in the server settings or site-specific settings. The correct sequence, therefore, involves steps that lead you through this process in an organized manner: assessing the site settings in IIS, confirming the directory where logs are stored, and understanding any custom configurations that might affect the location. This sequence facilitates a systematic approach to locating the IIS log files, ensuring that all relevant information is