220-301 220-302 N10-003 SY0-101 640-801 640-821 640-811 Subnetting 70-210 70-216 70-218 70-270
| Domain 4.0 | Network Support | 35% |
|---|
4.1 Given a troubleshooting scenario, select the appropriate network utility from the following:
| arp | ping | nbtstat | ipconfig |
|---|---|---|---|
| netstat | winipcfg | Tracert | ifconfig |
| trace route | nslookup/dig |
4.2 Given output from a network diagnostic utility (For example: those utilities listed in objective 4.1), identify the utility and interpret the output.
4.3 Given a network scenario, interpret visual indicators (For example: link LEDs (Light Emitting Diode) and collision LEDs (Light Emitting Diode)) to determine the nature of a stated problem.
4.4 Given a troubleshooting scenario involving a client accessing remote network services, identify the cause of the problem For example:
| file services | print services |
|---|---|
| protocol configuration | SOHO router |
| authentication failure | physical connectivity |
4.5 Given a troubleshooting scenario between a client and the following server environments, identify the cause of a stated problem:
| UNIX | Linux |
|---|---|
| Mac OS X Server | Netware |
| Windows | Appleshare IP |
4.6 Given a scenario, determine the impact of modifying, adding or removing network services For example:
| DHCP | DNS | WINS |
|---|
4.7 Given a troubleshooting scenario involving a network with a particular physical topology (For exam-ple: bus, star, mesh or ring) and including a network diagram, identify the network area affected and the cause of the stated failure.
4.8 Given a network troubleshooting scenario involving an infrastructure (For example: wired or wireless) problem, identify the cause of a stated problem (For example: bad media, interference, network hardware or environment).
4.9 Given a network problem scenario, select an appropriate course of action based on a logical trouble-shooting strategy. This strategy can include the following steps: