Multiple-choice question
Standard question format with several options, one or more correct.
Getting Started: How the Exam Works
Free knowledge base
Everything from the course in one searchable place: 295 entries. Use it to review before a practice test or look up a word you forgot.
295 results
Standard question format with several options, one or more correct.
Getting Started: How the Exam Works
Interactive, hands-on simulation requiring task completion in a virtual environment.
Getting Started: How the Exam Works
A major topic area covered by the certification exam.
Getting Started: How the Exam Works
The percentage of exam questions allocated to a specific domain.
Getting Started: How the Exam Works
A statistically adjusted score that accounts for question difficulty.
Getting Started: How the Exam Works
The minimum scaled score required to achieve certification (720 for N10-009).
Getting Started: How the Exam Works
Computing Technology Industry Association, creator of Network+.
Getting Started: How the Exam Works
To remember the Network+ domains, think: 'Fun Implementations Operate Securely, Troubleshooting problems.' (Fundamentals, Implementations, Operations, Security, Troubleshooting)
Getting Started: How the Exam Works
The N10-009 exam has a maximum of 90 questions and a 90-minute time limit. The passing score is 720 on a scale of 100-900. Remember these precise numbers for the exam.
Getting Started: How the Exam Works
Not reading multiple-choice questions carefully to see if they require one or multiple answers.
Getting Started: How the Exam Works
Spending too much time on a single PBQ and running out of time for other questions.
Getting Started: How the Exam Works
Ignoring the domain weightings and spending equal time on all topics, rather than prioritizing.
Getting Started: How the Exam Works
Official CompTIA document detailing all topics covered on the exam.
Getting Started: How the Exam Works
Engaging with material through note-taking, teaching, or practice.
Getting Started: How the Exam Works
Software that emulates network devices for practice.
Getting Started: How the Exam Works
Exam questions requiring hands-on configuration or troubleshooting.
Getting Started: How the Exam Works
Learning by explaining a concept in simple terms to others.
Getting Started: How the Exam Works
Personal setup of physical networking hardware for practice.
Getting Started: How the Exam Works
To PASS Network+: P-ractice, A-ctive study, S-imulate, S-ucceed!
Getting Started: How the Exam Works
The exam often tests your ability to apply knowledge, not just recall facts. Look for keywords like 'troubleshoot,' 'configure,' 'implement,' or 'recommend' in questions, indicating you need to think like a network professional.
Getting Started: How the Exam Works
Relying solely on memorization without understanding the underlying concepts.
Getting Started: How the Exam Works
Skipping hands-on labs and practice, leading to difficulty with performance-based questions.
Getting Started: How the Exam Works
Not reviewing incorrect answers on practice tests to understand the 'why' behind the correct answer.
Getting Started: How the Exam Works
A 7-layer conceptual framework for network communication.
Networking Concepts
Adding headers to data as it moves down the OSI layers.
Networking Concepts
Removing headers from data as it moves up the OSI layers.
Networking Concepts
Layer 2 device that forwards frames based on MAC addresses.
Networking Concepts
Layer 3 device that forwards packets based on IP addresses.
Networking Concepts
Network security system controlling traffic based on rules.
Networking Concepts
Distributes network traffic across multiple servers for performance.
Networking Concepts
Systems detecting/preventing malicious network activity.
Networking Concepts
Please Do Not Throw Sausage Pizza Away: Physical, Data Link, Network, Transport, Session, Presentation, Application.
Networking Concepts
Memorize the order of the OSI layers and at least one key function for each. The exam often asks which layer a specific device or protocol operates at. Keywords like 'MAC address' point to Layer 2, 'IP address' to Layer 3, and 'port numbers' to Layer 4.
Networking Concepts
Confusing the OSI model with the TCP/IP model; they are related but distinct conceptual frameworks.
Networking Concepts
Incorrectly assigning a device to an OSI layer (e.g., calling a router a Layer 2 device).
Networking Concepts
Believing the OSI model is a physical implementation rather than a conceptual guide.
Networking Concepts
On-demand delivery of computing services over the Internet.
Networking Concepts
Infrastructure as a Service; virtualized computing resources.
Networking Concepts
Platform as a Service; platform for developing and running applications.
Networking Concepts
Software as a Service; software applications delivered over the Internet.
Networking Concepts
Software-Defined Networking; separates control and data planes.
Networking Concepts
Software-Defined Wide Area Network; applies SDN to WAN.
Networking Concepts
Security model: never trust, always verify.
Networking Concepts
Combines public and private cloud environments.
Networking Concepts
For Cloud Service Models: 'I P S' - Infrastructure, Platform, Software. Remember what you 'own' less and less as you go up!
Networking Concepts
The exam often asks to differentiate between IaaS, PaaS, and SaaS. Memorize what the customer manages versus the provider for each. Also, know the core principles of Zero Trust and the benefits of SDN/SD-WAN.
Networking Concepts
Confusing IaaS, PaaS, and SaaS responsibilities. Remember IaaS gives you the most control, SaaS the least.
Networking Concepts
Thinking Zero Trust means no access at all. It means no *unverified* access.
Networking Concepts
Believing SDN is a physical device. It's an architectural approach to network management.
Networking Concepts
A logical endpoint for network communication on a device, identified by a number.
Networking Concepts
A set of rules governing data formatting, transmission, and reception in a network.
Networking Concepts
Transmission Control Protocol; a reliable, connection-oriented transport layer protocol.
Networking Concepts
User Datagram Protocol; a fast, connectionless transport layer protocol.
Networking Concepts
One-to-one network communication from a single source to a single destination.
Networking Concepts
One-to-many network communication to a specific group of recipients.
Networking Concepts
Transmission medium using light pulses for high-speed, long-distance data.
Networking Concepts
To remember common TCP/UDP ports: 'HTTP Hears 80, HTTPS Hears 443, FTP For 20/21, SSH Secures 22, SMTP Sends 25, DNS Does 53, POP3 Picks 110, IMAP Is 143.'
Networking Concepts
The N10-009 exam expects you to know the default port numbers for common protocols like HTTP (80), HTTPS (443), FTP (20, 21), SSH (22), Telnet (23), SMTP (25), DNS (53), DHCP (67, 68), TFTP (69), POP3 (110), NTP (123), NetBIOS (137-139), IMAP (143), SNMP (161, 162), LDAP (389), RDP (3389), and SMB/CIFS (445). Focus on memorizing these specific values.
Networking Concepts
Confusing TCP and UDP: Remember TCP is like a registered letter (guaranteed delivery), while UDP is like a postcard (faster, but no guarantee).
Networking Concepts
Forgetting that port numbers are associated with specific services and protocols, not just random numbers.
Networking Concepts
Underestimating the impact of transmission media choice on network performance and troubleshooting.
Networking Concepts
Actual layout of network cables and devices.
Networking Concepts
How data flows through the network, independent of physical layout.
Networking Concepts
Dividing a larger network into smaller, more manageable subnetworks.
Networking Concepts
32-bit number distinguishing network and host portions of an IP address.
Networking Concepts
Classless Inter-Domain Routing; notation indicating network bits (e.g., /24).
Networking Concepts
Non-routable IP addresses reserved for internal networks (RFC 1918).
Networking Concepts
Globally unique, internet-routable IP addresses.
Networking Concepts
IP address used to send data to all hosts on a subnet.
Networking Concepts
To remember the private IP ranges: 'Ten Cars Sixteen Miles Per Hour, One-Ninety-Two to One-Sixty-Eight'. (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16)
Networking Concepts
The exam expects you to identify common topologies (Star, Mesh, Bus, Ring) and their characteristics. For IPv4 subnetting, be prepared to calculate network addresses, broadcast addresses, and the number of usable hosts given an IP address and a CIDR prefix or subnet mask. Memorize the private IP address ranges.
Networking Concepts
Confusing physical and logical topologies; they describe different aspects of a network.
Networking Concepts
Forgetting to subtract 2 from 2^h when calculating usable hosts (for network and broadcast addresses).
Networking Concepts
Mixing up public and private IP address ranges and their routability on the internet.
Networking Concepts
Internet Protocol version 6, using 128-bit addresses.
Networking Concepts
Globally unique and routable IPv6 address.
Networking Concepts
IPv6 address for communication on a single network segment.
Networking Concepts
Stateless Address Auto-configuration for IPv6 addresses.
Networking Concepts
Running both IPv4 and IPv6 protocols simultaneously.
Networking Concepts
Encapsulating one protocol's packets within another's.
Networking Concepts
Translates IPv6 packets to IPv4 and vice-versa for communication.
Networking Concepts
Method to derive an IPv6 interface ID from a MAC address.
Networking Concepts
For IPv6 address types, remember 'G.L.U.M.A.': Global, Link-Local, Unique Local, Multicast, Anycast.
Networking Concepts
Memorize the common starting prefixes for IPv6 address types: fe80::/10 for Link-Local, fc00::/7 for Unique Local, and ff00::/8 for Multicast. The exam often tests your ability to identify these.
Networking Concepts
Confusing Link-Local addresses (fe80::) with routable Global Unicast addresses.
Networking Concepts
Believing NAT is still required or desirable in a pure IPv6 environment.
Networking Concepts
Forgetting that the double colon (::) can only be used once in an IPv6 address.
Networking Concepts
Manually configured routes on a router.
Network Implementation
Automatic path discovery using protocols.
Network Implementation
A collection of IP networks under one administration.
Network Implementation
Link-state IGP, uses areas, Dijkstra's algorithm.
Network Implementation
Path-vector EGP, routes between ASes on the internet.
Network Implementation
Cisco hybrid protocol, fast convergence with DUAL.
Network Implementation
Routes within a single Autonomous System.
Network Implementation
Routes between different Autonomous Systems.
Network Implementation
OSPF: 'Open Shortest Path First' – like finding the quickest way on a map. BGP: 'Big Global Paths' – for the internet's huge routes. EIGRP: 'Enhanced Interior Good Reliable Protocol' – for Cisco networks.
Network Implementation
The exam often tests the distinction between IGPs (OSPF, EIGRP) and EGPs (BGP). Remember that OSPF and EIGRP operate *within* an AS, while BGP operates *between* ASes.
Network Implementation
Confusing the scope of IGPs and EGPs (e.g., trying to use OSPF to route between ISPs).
Network Implementation
Underestimating the administrative overhead of static routing in large, dynamic networks.
Network Implementation
Not understanding that BGP is policy-driven, not just metric-driven, for inter-AS routing.
Network Implementation
Logical grouping of network devices, segmenting broadcast domains.
Network Implementation
Configuring a switch port to carry traffic for multiple VLANs.
Network Implementation
IEEE standard for VLAN tagging, adding a VLAN ID to frames.
Network Implementation
Switch port configured for a single VLAN, connects end devices.
Network Implementation
Protocol preventing network loops by blocking redundant paths.
Network Implementation
The central switch elected by STP in a spanning tree topology.
Network Implementation
Network segment where all devices receive each other's broadcasts.
Network Implementation
VLANs 'Vary' your LANs. Trunking 'Transports' all VLANs. STP 'Stops' the 'Spirals' (loops).
Network Implementation
The exam often tests the purpose of VLANs (segmentation, security, broadcast control) and the function of 802.1Q for trunking. For STP, know its primary goal (preventing loops) and the concept of a root bridge. Be able to distinguish between access and trunk ports.
Network Implementation
Forgetting to configure trunk ports on both ends of an inter-switch link, leading to VLAN communication failures.
Network Implementation
Not enabling STP or disabling it on switches, which can lead to catastrophic network loops and outages.
Network Implementation
Confusing the purpose of an access port (single VLAN, end device) with a trunk port (multiple VLANs, inter-switch/router).
Network Implementation
Assuming VLANs provide complete security isolation without additional firewall rules or Layer 3 filtering.
Network Implementation
Combining multiple physical links into one logical link for bandwidth and redundancy.
Network Implementation
Protocol for dynamic negotiation and management of aggregated links.
Network Implementation
Latest Wi-Fi standard, offering higher speeds and efficiency in dense environments.
Network Implementation
Wireless frequency with longer range but more interference and fewer channels.
Network Implementation
Wireless frequency with higher speeds, less interference, but shorter range.
Network Implementation
Multiple-Input, Multiple-Output; uses multiple antennas for improved wireless performance.
Network Implementation
Strategically selecting wireless channels to minimize interference and optimize performance.
Network Implementation
To remember Wi-Fi standards: 'A Big Gorilla Naps ACtually AXing.' (a, b, g, n, ac, ax) – each letter reminds you of a standard in rough chronological order!
Network Implementation
For the Network+ exam, memorize the key characteristics (frequency, max speed) of 802.11a/b/g/n/ac/ax. Pay close attention to which standards operate on 2.4 GHz, 5 GHz, or both, and the benefits of each frequency band. Understand that LACP is the dynamic method for link aggregation.
Network Implementation
Forgetting that both ends of a link aggregation must be configured for it to work.
Network Implementation
Confusing the 2.4 GHz and 5 GHz bands' characteristics, especially regarding range vs. speed and interference.
Network Implementation
Assuming that simply upgrading an AP will fix all wireless issues without proper channel planning or site survey.
Network Implementation
Wired Equivalent Privacy, an outdated and insecure wireless security protocol.
Network Implementation
Wi-Fi Protected Access 2, current industry standard using AES encryption.
Network Implementation
Wi-Fi Protected Access 3, latest standard with enhanced security features like SAE.
Network Implementation
Service Set Identifier, the name of a wireless network.
Network Implementation
An unauthorized access point connected to a network, posing a security risk.
Network Implementation
An IEEE standard for port-based network access control, often used with RADIUS.
Network Implementation
Process of planning and designing a wireless network to provide optimal coverage.
Network Implementation
A web page that requires users to agree to terms or authenticate before network access.
Network Implementation
WPA is 'Way Protected, Always' – remember WPA3 is the best, then WPA2, then WPA. WEP is 'Weak, Easily Penetrated'.
Network Implementation
The exam often tests the progression of wireless security protocols. Remember WEP is bad, WPA is better but still vulnerable, WPA2 is the current strong standard, and WPA3 is the newest and most secure. Keywords like 'AES', 'TKIP', 'SAE', and '802.1X' are critical to associate with the correct protocol.
Network Implementation
Relying on SSID hiding as a primary security measure; it provides minimal actual protection.
Network Implementation
Using outdated security protocols like WEP or WPA (TKIP) for new deployments.
Network Implementation
Ignoring physical security of APs, making them vulnerable to tampering or theft.
Network Implementation
Records of network design, configuration, and operation.
Network Operations
Structured process of managing a network from design to retirement.
Network Operations
Illustrates data flow, IP addressing, and logical network segments.
Network Operations
Shows actual device placement, cabling, and rack layouts.
Network Operations
IP Address Management; tracks assigned IP addresses and subnets.
Network Operations
Record of all modifications made to the network infrastructure.
Network Operations
A snapshot of a network's normal operating state for comparison.
Network Operations
To remember the network lifecycle phases, think: 'P.I.O.O.D.' - Planning, Implementation, Operation, Optimization, Decommissioning. Like a 'P.I.' (Private Investigator) who's 'O.O.D.' (Out Of Duty) after a case!
Network Operations
The exam often tests your understanding of *why* documentation is important and *what types* of documents are used in different scenarios (e.g., troubleshooting vs. planning). Be ready to identify the purpose of logical vs. physical diagrams.
Network Operations
Neglecting to update documentation after network changes.
Network Operations
Relying solely on tribal knowledge instead of formal documentation.
Network Operations
Failing to back up configuration files or IPAM databases.
Network Operations
Protocol for managing and monitoring network devices.
Network Operations
Management Information Base; database of device variables.
Network Operations
Object Identifier; unique address for MIB variables.
Network Operations
Most secure SNMP version with authentication and encryption.
Network Operations
Standard for sending and receiving centralized log messages.
Network Operations
Protocol for collecting and analyzing IP traffic flow data.
Network Operations
Sequence of packets with common characteristics.
Network Operations
Plain-text password for SNMPv1/v2c authentication.
Network Operations
SNMP is like a 'Smart Network Monitor Protocol' for device health. Syslog is 'System Log' for events. NetFlow 'Nets' all the traffic details.
Network Operations
Memorize the default ports: SNMP (UDP 161/162), Syslog (UDP 514, TCP 6514 for secure), NetFlow (UDP 2055/4739/9995). Understand that SNMPv3 is the secure version.
Network Operations
Confusing SNMP traps (alerts from agent to manager) with SNMP queries (manager asking agent for data).
Network Operations
Assuming Syslog provides built-in security; it requires TLS for encryption and authentication.
Network Operations
Thinking NetFlow provides packet-level detail; it's flow-level summaries, not full packet captures.
Network Operations
Maximum acceptable data loss in time.
Network Operations
Maximum acceptable downtime after a disaster.
Network Operations
Fully equipped, operational DR site with real-time replication.
Network Operations
Partially equipped DR site with some data/hardware.
Network Operations
Basic facility, no equipment, requires setup after disaster.
Network Operations
Disaster Recovery as a Service, cloud-based DR solutions.
Network Operations
RPO is 'Point' (data point in time), RTO is 'Time' (time to get back up). Hot is 'Hot and ready,' Warm is 'Warming up,' Cold is 'Cold and empty.'
Network Operations
The Network+ exam often presents scenarios and asks you to identify the best DR site type based on given RPO and RTO values. Memorize the characteristics and trade-offs of hot, warm, and cold sites.
Network Operations
Confusing RPO and RTO: RPO is about data loss, RTO is about downtime.
Network Operations
Underestimating the cost implications of hot sites versus cold sites.
Network Operations
Failing to regularly test disaster recovery plans, leading to unexpected issues during an actual event.
Network Operations
Dynamically assigns IP addresses and network config.
Network Operations
Translates domain names to IP addresses.
Network Operations
Creates secure, encrypted tunnel over public network.
Network Operations
Microsoft protocol for graphical remote desktop control.
Network Operations
Secure protocol for remote command-line access.
Network Operations
VPN protocol providing strong network layer security.
Network Operations
DHCP for IPv6, can be stateful or stateless.
Network Operations
To remember the DHCP DORA process: 'DORA the Explorer DISCOVERS an OFFER, REQUESTS it, and ACKNOWLEDGES it!'
Network Operations
For the exam, remember that DHCP is UDP port 67 (server) and 68 (client), while DNS uses UDP/TCP port 53. RDP uses TCP port 3389, and SSH uses TCP port 22. These port numbers are frequently tested.
Network Operations
Confusing the roles of DHCP and DNS: DHCP assigns IPs, DNS resolves names to IPs.
Network Operations
Underestimating the security risks of remote access; always use strong authentication and encryption.
Network Operations
Forgetting that while SLAAC provides IPv6 addresses, stateless DHCPv6 is often used alongside it for other configuration details like DNS servers.
Network Operations
Confidentiality, Integrity, and Availability; core security principles.
Network Security
Protecting information from unauthorized disclosure.
Network Security
Ensuring data is accurate, complete, and untampered.
Network Security
Ensuring authorized users can access resources when needed.
Network Security
Denial of Service; overwhelms a system, making it unavailable.
Network Security
Distributed DoS; uses multiple sources to overwhelm a system.
Network Security
Intercepts and potentially alters communication between parties.
Network Security
Exploits a vulnerability unknown to the vendor or public.
Network Security
Remember 'CIA' for Confidentiality, Integrity, Availability. Think of a 'C'overt agent (confidentiality), an 'I'nvestigator (integrity), and an 'A'ir Traffic Controller (availability).
Network Security
The CompTIA Network+ exam frequently tests your understanding of the CIA Triad and how different attack types relate to each principle. Be ready to identify which principle (Confidentiality, Integrity, or Availability) is compromised by a given attack scenario.
Network Security
Confusing Integrity with Confidentiality: Integrity is about data being correct and unaltered, while Confidentiality is about who can see it.
Network Security
Underestimating the impact of Availability attacks: Downtime can be extremely costly for businesses, not just data breaches.
Network Security
Forgetting that insider threats can compromise all three CIA principles, even with robust external defenses.
Network Security
Bypassing VLAN segmentation to access unauthorized VLANs.
Network Security
Falsifying ARP messages to associate an attacker's MAC with another IP.
Network Security
Any unauthorized hardware connected to a network.
Network Security
Attacker's device pretends to be a trunk port to gain VLAN access.
Network Security
Embedding a malicious VLAN tag inside a legitimate one for hopping.
Network Security
Security feature validating ARP packets to prevent spoofing.
Network Security
Limits MAC addresses per port, preventing unauthorized device connections.
Network Security
Attacker intercepts and relays communication between two parties.
Network Security
VLANs, ARPs, Rogues: Very Annoying Risks, Protect Securely!
Network Security
The exam expects you to differentiate between VLAN hopping methods (switch spoofing vs. double-tagging) and understand that ARP spoofing is a Layer 2 attack that enables MitM. For rogue devices, focus on the security implications and detection methods like WIPS and NAC.
Network Security
Confusing VLAN hopping with simple misconfiguration; it's an attack.
Network Security
Underestimating the impact of ARP spoofing beyond just eavesdropping (e.g., session hijacking).
Network Security
Forgetting that rogue devices aren't just Wi-Fi APs, but can be any unauthorized hardware.
Network Security
Process of securing a system by reducing its attack surface.
Network Security
Sum of all possible points where an unauthorized user can access a system.
Network Security
Process of identifying and quantifying security weaknesses.
Network Security
Simulated cyberattack to find exploitable vulnerabilities.
Network Security
Rules defining which users or systems can access resources.
Network Security
Pre-set password, often a major security risk if unchanged.
Network Security
Software update to fix security vulnerabilities.
Network Security
Protocols designed with encryption and authentication (e.g., SSH).
Network Security
To remember hardening steps, think 'D.U.P.S.': Default passwords changed, Unused services disabled, Patches applied, Secure protocols used.
Network Security
The exam often tests your knowledge of specific hardening steps. Memorize that changing default passwords, disabling unused services/ports, and applying patches are fundamental and immediate actions.
Network Security
Forgetting to change default credentials on new devices.
Network Security
Leaving unused ports or services enabled, creating unnecessary attack vectors.
Network Security
Neglecting regular security updates and patches, leaving known vulnerabilities unaddressed.
Network Security
Enforces policies on devices connecting to a network.
Network Security
The client device requesting network access.
Network Security
The network device (e.g., switch) controlling port access.
Network Security
Validates user/device credentials (e.g., RADIUS).
Network Security
Dividing a network into smaller, isolated subnets.
Network Security
To remember the 802.1X components, think 'S-A-S': Supplicant Asks Server. The supplicant (client) asks the authenticator (switch/AP), which forwards to the Server (RADIUS).
Network Security
The exam often tests your understanding of the components in an 802.1X setup: the supplicant (client), authenticator (switch/AP), and authentication server (RADIUS). Remember that NAC is a broader concept that uses 802.1X as one of its enforcement mechanisms.
Network Security
Confusing 802.1X as a complete NAC solution; it's a key component, but NAC is broader.
Network Security
Underestimating the importance of network segmentation for containing breaches.
Network Security
Forgetting that NAC can perform both pre-admission (before connecting) and post-admission (continuous monitoring) checks.
Network Security
A systematic, step-by-step process for solving problems.
Network Troubleshooting
First step: gather info, symptoms, and scope of the issue.
Network Troubleshooting
Second step: formulate a probable cause, starting simple.
Network Troubleshooting
Third step: perform actions to confirm or deny the hypothesis.
Network Troubleshooting
Fourth step: develop and implement a solution to the problem.
Network Troubleshooting
Fifth step: ensure the system works fully after the fix.
Network Troubleshooting
Sixth step: actions taken to stop the problem from recurring.
Network Troubleshooting
Seventh step: recording findings, actions, and lessons learned.
Network Troubleshooting
I Eat Tasty Tacos, Please Verify Proper Digestion. (Identify, Establish, Test, Plan, Verify, Prevent, Document)
Network Troubleshooting
The CompTIA Network+ exam specifically tests the seven-step troubleshooting methodology. Memorize the order and a brief description of each step. Keywords like 'escalate' or 'document' are often tied to specific steps.
Network Troubleshooting
Jumping directly to a solution without fully understanding the problem or testing theories.
Network Troubleshooting
Failing to document findings, leading to repeated troubleshooting efforts for similar issues.
Network Troubleshooting
Not verifying full system functionality after a fix, potentially introducing new problems.
Network Troubleshooting
The lowest OSI layer, dealing with physical transmission of raw bit streams over a medium.
Network Troubleshooting
An indicator on network devices showing physical connection status and activity.
Network Troubleshooting
A tool to verify if a cable is intact and correctly wired end-to-end.
Network Troubleshooting
An advanced tool that measures cable performance against industry standards.
Network Troubleshooting
Disruption caused by electromagnetic radiation from external sources.
Network Troubleshooting
Disruption caused by radio waves, often affecting wireless signals.
Network Troubleshooting
The loss of signal strength over distance, common in long cable runs.
Network Troubleshooting
L-V-C-E: Link lights, Visual, Cable test, Environment. Always check these in order for physical layer issues!
Network Troubleshooting
The N10-009 exam expects you to identify common physical layer issues (e.g., bad cables, damaged connectors, incorrect cable types, faulty transceivers, or environmental factors like EMI/RFI) and know how to use tools like cable testers and visual inspection for diagnosis. Look for keywords like 'no link light' or 'intermittent connection' as strong indicators of physical layer problems.
Network Troubleshooting
Jumping to complex software troubleshooting before checking basic physical layer components.
Network Troubleshooting
Assuming a cable is good without testing it, especially if it's an older or frequently moved cable.
Network Troubleshooting
Ignoring environmental factors like nearby electronics or long cable runs as potential causes of intermittent issues.
Network Troubleshooting
Automatic Private IP Addressing; a self-assigned IP when DHCP fails.
Network Troubleshooting
The time delay for data to travel from source to destination.
Network Troubleshooting
The maximum data transfer rate of a network path.
Network Troubleshooting
The slowest component in a network path, limiting overall performance.
Network Troubleshooting
Quality of Service; manages network traffic to ensure performance for critical apps.
Network Troubleshooting
Command-line tool to display network connections and statistics.
Network Troubleshooting
To remember the common troubleshooting steps: 'I Gather Info, Isolate, Test, Implement, Verify, Document' – or I G.I.T. I.V.D. for short!
Network Troubleshooting
On the Network+ exam, expect questions that present a scenario with specific symptoms and ask you to identify the most likely cause or the next troubleshooting step. Keywords like 'APIPA address,' 'slow performance,' 'cannot access website,' or 'authentication failed' are critical clues. Memorize common service ports (e.g., DNS 53, DHCP 67/68, HTTP 80, HTTPS 443) and their functions.
Network Troubleshooting
Jumping to conclusions without gathering enough information or isolating the problem.
Network Troubleshooting
Blaming the network immediately without checking local client or server issues first.
Network Troubleshooting
Failing to document troubleshooting steps and solutions, leading to repeated work.
Network Troubleshooting
Tests host reachability and measures round-trip time using ICMP.
Network Troubleshooting
Maps the path an IP packet takes to a destination, showing each hop.
Network Troubleshooting
Queries the Domain Name System (DNS) for domain name or IP address mapping.
Network Troubleshooting
A more advanced and flexible tool for querying DNS name servers.
Network Troubleshooting
A command-line packet analyzer for capturing and displaying network traffic.
Network Troubleshooting
Internet Control Message Protocol, used by ping and traceroute.
Network Troubleshooting
Time To Live, a value in IP packets that limits their lifespan on a network.
Network Troubleshooting
P-T-N-D-T: **P**lease **T**ry **N**etwork **D**iagnostics **T**horoughly! (Ping, Traceroute, Nslookup, Dig, Tcpdump)
Network Troubleshooting
The exam often asks you to identify the best tool for a specific troubleshooting scenario. Remember that `ping` tests reachability, `traceroute` shows the path, `nslookup`/`dig` resolve DNS, and `tcpdump` captures packets.
Network Troubleshooting
Forgetting to specify the network interface when using `tcpdump`, leading to capturing traffic on the wrong interface.
Network Troubleshooting
Misinterpreting `traceroute` output, especially when firewalls block ICMP, causing asterisks (*) to appear instead of hop details.
Network Troubleshooting
Using `nslookup` for complex DNS issues when `dig` would provide more comprehensive and accurate information.
Network Troubleshooting
Device to check network cable continuity and wiring.
Network Troubleshooting
Diagram showing pin-to-pin connections in a cable.
Network Troubleshooting
Tool to scan and visualize wireless network signals.
Network Troubleshooting
Received Signal Strength Indicator; measures Wi-Fi signal strength.
Network Troubleshooting
Network Mapper; scans networks for hosts, open ports, and OS.
Network Troubleshooting
Process of identifying open ports on a network device.
Network Troubleshooting
To remember the tools, think 'C-W-N': **C**able for wires, **W**i-Fi for air, **N**map for network insights.
Network Troubleshooting
For the Network+ exam, memorize the primary function of each tool: Cable testers for physical cable integrity, Wi-Fi analyzers for wireless signal and channel issues, and nmap for host/service discovery and security auditing. Pay attention to scenario questions that describe symptoms and ask for the best tool.
Network Troubleshooting
Using a simple continuity tester for advanced performance issues (like crosstalk) when a certifier is needed.
Network Troubleshooting
Assuming a Wi-Fi issue is always signal strength when channel congestion or interference is the real culprit.
Network Troubleshooting
Using nmap without proper authorization, which can be perceived as a security threat and lead to disciplinary action.
Network Troubleshooting
Confusing the capabilities of a basic cable tester with an advanced cable certifier.
Network Troubleshooting