CompTIA Network+ Domain 5: Network Troubleshooting and Tools

The CompTIA Network+ certification can help bring your career to the next level and is a strong professional asset to have on your side. To earn this certification, you have to pass the Network+ certification exam. This exam is comprised of five different Domains of knowledge that certification candidates will need to master.

This article will detail Domain 5.0 — Network Troubleshooting and Tools, complete with its different objectives and what material you will need to cover. This article should not serve as your sole means of preparing for the Network+ certification exam, but rather as a general review or an outline foundation.

Network Troubleshooting and Tools Outline

The following subtopics can be expected to be tested in the Network Troubleshooting and Tools domain:

5.1 Network Troubleshooting Methodology

5.2 Appropriate Tools for Different Scenarios

5.3 Troubleshooting Common Wired Connectivity/Performance Issues

5.4 Troubleshooting Common Wireless Connectivity/Performance Issues

5.5 Troubleshooting Common Network Service Issues

Network Troubleshooting Methodology

Many do not notice that the scientific method is reflected in network troubleshooting. For a refresher, the scientific method is:

  1. Identifying the problem
  2. Researching said problem
  3. Hypothesis creation
  4. Testing a solution
  5. Analysis of said solution
  6. Conclusion

These steps match up to certain network troubleshooting steps. Network troubleshooting steps are listed below:

  1. Identify the problem
    1. Gather information
    2. Duplicate the problem if possible
    3. Identify symptoms
    4. Questions users
    5. Determine if there have been any changes
    6. Approach multiple problems individually
  2. Establish a theory of probable cause
    1. Consider the obvious
    2. Consider multiple approaches/keep an open mind
  3. Test the theory to determine the cause
    1. After confirming theory, determine next steps in resolution
    2. If theory is not confirmed, either establish a new theory or escalate
  4. Establish a plan of action to resolve problem and identify potential effects
  5. Implement the solution or escalate as needed
  6. Verify full (Read more...)

*** This is a Security Bloggers Network syndicated blog from InfoSec Resources authored by Greg Belding. Read the original post at: http://feedproxy.google.com/~r/infosecResources/~3/Cf3Yz21mgyg/