Fault Detection

Correct Answer: Network logs

In case of intermittent connectivity issues, the first point of investigation should be 'Network Logs'. Network logs provide detailed information about what is happening in the network - they record data about network traffic, allowing the technician to trace back and identify issues such as connectivity interruptions. Checking the network logs will help identify if there are specific times or events correlating with the reported issue. The other responses, while potentially valid in other scenarios, aren't typically the first steps in diagnosing intermittent connectivity problems. 'Switch configurations' would usually be checked if there were persistent connectivity issues with specific devices or locations. 'Implementing load balancing' and 'Increasing failover tolerance' are measures generally taken to prevent potential connectivity issues, not to diagnose existing ones.

Correct Answer: A. Check the server's power supply

The best troubleshooting step for a server that is powered off is to check the server's power supply (Answer A). This is the most logical first step because if the server is not receiving power, it will not function. Checking the power supply will determine if the server is plugged in, if the power cords are working, or if there are any issues with the power source or connection. The other options are not the best first steps. Replacing the server motherboard (Answer B) is a very drastic step, and should be a last resort, not the first troubleshooting step. Reinstalling the server's operating system (Answer C) or performing a factory reset on the server (Answer D) would not resolve the issue if the server isn't receiving power.

Correct Answer: A. Check the VLAN configuration on switches

The VLAN experiencing high packet loss may be due to a misconfiguration. The initial troubleshooting step a network administrator should take is to 'A. Check the VLAN configuration on switches' to ensure that all configurations are correct. Checking the affected VLAN's configuration will potentially reveal any errors or anomalies that might cause packet loss. The other options, although possibly relevant in different contexts, are generally not the first steps in a structured approach to network troubleshooting. 'B. Reboot all switches in the network' can be disruptive and may not necessarily resolve the issue if it's caused by misconfiguration. 'C. Disable and then re-enable the affected VLAN' might be useful later in the troubleshooting process if configuration checks don't reveal any problems. Lastly, 'D. Replace the switches connected to the VLAN' is an extreme measure that should be considered only when serious hardware faults have been identified after other troubleshooting steps were unsuccessful.