DOMAIN 4.0: Network Support

4.1 Given a troubleshooting scenario, select the appropriate TCP/IP utility from among the following:

4.2 Given a troubleshooting scenario involving a small office/home office network failure (e.g., xDSL, cable, home satellite, wireless, POTS), identify the cause of the failure.

4.3 Given a troubleshooting scenario involving a remote connectivity problem (e.g., authentication failure, protocol configuration, physical connectivity) identify the cause of the problem.

4.4 Given specific parameters, configure a client to connect to the following servers:

4.5 Given a wiring task, select the appropriate tool (e.g., wire crimper, media tester/certifier, punch down tool, tone generator, optical tester, etc.).

4.6 Given a network scenario interpret visual indicators (e.g., link lights, collision lights, etc.) to determine the nature of the problem.

4.7 Given output from a diagnostic utility (e.g. tracert, ping, ipconfig, etc.), identify the utility and interpret the output.

4.8 Given a scenario, predict the impact of modifying, adding, or removing network services (e.g., DHCP, DNS, WINS, etc.) on network resources and users.

4.9 Given a network problem scenario, select an appropriate course of action based on a general troubleshooting strategy. This strategy includes the following steps:

4.10 Given a troubleshooting scenario involving a network with a particular physical topology (i.e., bus, star/hierarchical, mesh, ring, and wireless) and including a network diagram, identify the network area effected and the cause of the problem.

4.11 Given a network troubleshooting scenario involving a client connectivity problem (e.g., incorrect protocol/client software/authentication configuration, or insufficient rights/permission), identify the cause of the problem.

4.12 Given a network troubleshooting scenario involving a wiring/infrastructure problem, identify the cause of the problem (e.g., bad media, interference, network hardware).