What Does Loop Guard Mean?
On This Page
Quick Definition
Loop Guard is a safety feature for network switches. It prevents network loops when a switch port stops receiving important control messages. If those messages stop, instead of risking a loop, the port is put into a special blocking state until the messages return.
Commonly Confused With
BPDU Guard is an STP protection mechanism that shuts down a port (puts it in errdisable state) if that port receives a BPDU. It is used on access ports connected to end devices that should never send BPDUs. Loop Guard, in contrast, operates on blocking ports and reacts when expected BPDUs stop arriving by placing the port in a loop-inconsistent state, not by shutting it down.
On a port connected to a user's PC, you enable BPDU Guard so if someone mistakenly plugs in a switch, the port shuts down. On a trunk port between two switches that is in a blocking state, you enable Loop Guard to prevent a loop if a cable fails.
Root Guard is an STP feature that prevents an external switch from becoming the root bridge. If a port with Root Guard enabled receives a superior BPDU (one that would make the local switch become non-root), the port is put into a root-inconsistent state and blocks traffic. Loop Guard does not care about which switch is the root; it only monitors the presence or absence of BPDUs. Root Guard protects the root bridge election, while Loop Guard protects against loops from unidirectional failures.
On a port connecting to a customer switch, you enable Root Guard to ensure that customer switch cannot become the root. On the same link, you might also enable Loop Guard to protect against cable failures, but they serve different purposes.
UDLD is a Layer 2 protocol that actively monitors the physical link in both directions by exchanging 'hello' frames. If a unidirectional link is detected, UDLD can either send an alert or shut down the port (depending on configuration). Loop Guard is a passive feature that relies on STP BPDUs. UDLD works independently of STP and can detect unidirectional failures even on forwarding ports, while Loop Guard only works on blocking ports and when BPDUs are expected. They are complementary; many networks use both.
UDLD is like a 'hello, are you there?' watchdog on every link. Loop Guard is like a 'if this guard stops hearing the other guard, lock the door' mechanism. For a forwarding port, UDLD would detect the failure; Loop Guard would not.
Must Know for Exams
Loop Guard is a staple topic in networking certification exams, including the Cisco Certified Network Associate (CCNA), Cisco Certified Network Professional (CCNP) Enterprise, and the CompTIA Network+ certifications. In these exams, it falls under the broader domain of Layer 2 network stability and STP optimization. For CCNA (200-301), the exam blueprint explicitly includes STP variants and enhancements like Loop Guard, Root Guard, and BPDU Guard. Learners must understand the problem each protection solves and when to apply them. For CCNP Enterprise (350-401 ENCOR), Loop Guard is part of the advanced STP troubleshooting section, where candidates must interpret complex network scenarios and choose the correct protection mechanism.
Exam questions typically test three aspects: operational understanding (what does Loop Guard do?), configuration knowledge (syntax and where to apply it), and troubleshooting scenarios (why is a port in loop-inconsistent state?). A common objective is to distinguish Loop Guard from BPDU Guard and Root Guard. For example, a question might describe a switch port that is up but receiving no BPDUs, and ask which feature would prevent a loop. Another question might present a show spanning-tree output showing a port in a loop-inconsistent state and ask for the cause (unidirectional link failure) and solution (check cable or optics).
For CompTIA Network+, the coverage is less deep but still important. The exam expects candidates to know that Loop Guard is a feature that prevents loops during unidirectional link failures, and to identify it among other STP features. It may appear in a multiple-choice question about STP optimization or as a correct answer in a scenario question.
The key exam takeaway is that Loop Guard solves a specific problem: unidirectional link failures. Many learners confuse it with BPDU Guard, which shuts down a port if it receives an unexpected BPDU. Loop Guard does not shut the port down; it places it in a blocking state until BPDUs return. This distinction is a frequent exam trap. Candidates should memorize that Loop Guard is enabled on blocking/alternate ports and that it reacts to the absence of BPDUs, not their presence.
Simple Meaning
Imagine you are in a large office building with many doors, and each door has a guard who decides who can go through. These guards talk to each other using walkie-talkies to make sure only one person enters a hallway at a time, preventing a traffic jam. Now, suppose one guard’s walkie-talkie breaks, and he can no longer hear the other guards.
Without hearing instructions, he might start letting people through, which could cause a massive, chaotic jam. Loop Guard is like a fail-safe for that guard: if his radio goes silent, he automatically locks his door and refuses to let anyone through until the radio works again. In networking terms, switches use a protocol called Spanning Tree Protocol (STP) to prevent data loops, where data goes around in circles and crashes the network.
They send out special messages called Bridge Protocol Data Units (BPDUs) to coordinate which ports should forward traffic and which should block it. A cable problem or a switch failure can cause a port to stop receiving BPDUs. Without Loop Guard, that port might wrongly assume it is safe to start forwarding data, which could create a loop and bring down the network.
With Loop Guard enabled, when BPDUs stop arriving, the port is put into a Loop Inconsistent state, which blocks all traffic until BPDUs are heard again. This simple but powerful mechanism is one of the key ways network engineers keep local area networks stable and loop-free.
Full Technical Definition
Loop Guard is an enhancement to the Spanning Tree Protocol (STP) family, which includes classic STP (IEEE 802.1D), Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w), and Multiple Spanning Tree Protocol (MSTP, IEEE 802.1s). Its primary purpose is to detect and prevent unidirectional link failures that could cause bridging loops. A unidirectional link failure occurs when a switch can send data to a neighbor but cannot receive data (or vice versa), often due to a faulty cable, transceiver, or interface.
In normal STP operation, designated and root ports continuously receive BPDUs from the root bridge. If a port stops receiving BPDUs, the STP algorithm may assume the upstream switch is gone and eventually transition the port to the forwarding state, potentially creating a loop. Loop Guard prevents this by monitoring ports that are in a blocking or alternate state. When the port stops receiving BPDUs, Loop Guard places it into a Loop-Inconsistent state (sometimes called a loop-guard blocked state). In this state, the port does not forward any traffic and does not participate in normal STP transitions. It periodically checks for BPDUs; once they resume, the port returns to its previous STP role (e.g., alternate or backup) and eventually transitions to the appropriate state.
Loop Guard is configured on a per-port basis (interface configuration mode) using the command spanning-tree guard loop (on Cisco IOS). It works in conjunction with other STP protection mechanisms like Root Guard and BPDU Guard, but each addresses different failure scenarios. Loop Guard is particularly effective against unidirectional link failures, which are notoriously difficult to troubleshoot because the link appears up at the physical layer (light is present), but only one direction of traffic flows.
In real IT implementations, engineers enable Loop Guard on all non-designated ports-that is, ports that are not actively forwarding traffic. This is because these ports are the ones at risk of incorrectly transitioning to forwarding. Best practices recommend enabling Loop Guard globally on the switch or on all access and trunk ports except those where BPDU filtering is intentionally used. Loop Guard adds minimal CPU overhead and is considered a must-have for any production network that relies on STP.
The protocol does not require any changes to the BPDU format or to neighbor switches; it is purely a local switch decision. However, it must be used with care on ports that connect to devices that do not send BPDUs (like end hosts), because Loop Guard would cause those ports to go into a loop-inconsistent state permanently. For such ports, BPDU Guard or PortFast are more appropriate.
Real-Life Example
Think about a busy two-lane bridge connecting two parts of a city. Traffic lights at both ends coordinate with each other to ensure that cars flow smoothly and that no two cars enter the bridge from opposite ends at the same time, which would cause a gridlock. Each traffic light sends a signal to the other light every few seconds to confirm it is working.
Now imagine that the signal wire on one side gets cut. The working traffic light stops hearing from the broken one. If it assumes the other side is empty and starts letting cars through, both ends could send cars onto the bridge simultaneously, creating a devastating jam that halts all movement.
To prevent this disaster, the city installs a fail-safe: if any traffic light stops receiving confirmation signals from the other side, it immediately turns red in both directions and blocks all entry until the connection is restored. This fail-safe is exactly what Loop Guard does in a computer network. In our city analogy, the bridge is the network link, the traffic lights are the switch ports, and the confirmation signals are BPDUs.
A cut signal wire is like a unidirectional link fault-data can still travel from the broken light to the working one, but not the other way. The fail-safe that turns both lights red is Loop Guard putting the port into a loop-inconsistent state. Without this fail-safe, the network would suffer a loop, causing data packets to travel in circles, exponentially multiplying until the network becomes completely unusable.
Just as the city’s fail-safe saves commuters hours of frustration, Loop Guard saves network administrators from catastrophic outages.
Why This Term Matters
In modern enterprise networks, downtime can cost thousands of dollars per minute, and network loops are among the most disruptive failures. A single loop can bring down an entire broadcast domain, consuming all available bandwidth and CPU resources, effectively halting all communication. Loop Guard is a critical defense against such outages because it addresses a specific and common failure mode: the unidirectional link failure. These failures are particularly insidious because they often go unnoticed by other monitoring tools-the link appears up, interface counters show no errors, yet data flows only one way.
Without Loop Guard, an STP port that stops receiving BPDUs because of a unidirectional failure will eventually time out (Max Age timer, default 20 seconds) and transition through the listening and learning states (about 30 seconds total for classic STP) before becoming forwarding. During this transition, the switch has no knowledge of the network topology from that direction, so it may create a loop. With Loop Guard, the port moves directly to a loop-inconsistent state and blocks all traffic, preventing the loop entirely. Once the BPDUs resume (e.g., the faulty cable is replaced), the port automatically returns to its proper STP role without manual intervention.
For network engineers, enabling Loop Guard is a low-effort, high-impact configuration. It is supported on virtually all managed switches from major vendors (Cisco, Juniper, HP Aruba, etc.) and is a best practice in STP design. It complements other protections like Root Guard (which prevents a rogue switch from becoming root) and BPDU Guard (which shuts down ports that receive unexpected BPDUs). Together, these features form a robust STP security and stability toolkit. Loop Guard is particularly important in networks with redundant links, such as data centers, campus networks, or any environment using link aggregation or stackwise virtual links. It is also valuable in networks with long fiber runs where unidirectional failures are more common due to fiber cuts or dirty connectors.
How It Appears in Exam Questions
In certification exams, Loop Guard questions usually fall into three patterns: scenario-based, configuration-based, and troubleshooting-based.
Scenario-based questions present a network topology with redundant links and a failure event. For example: A network has two switches connected by two redundant links. One of the links develops a unidirectional failure where Switch A can send data to Switch B but cannot receive from Switch B. The question will ask which STP feature prevents a loop. The correct answer is Loop Guard. Sometimes the question will present a false lead by mentioning a broadcast storm or high CPU utilization, but the root cause is the absence of BPDUs on a blocked port.
Configuration-based questions test the command syntax and placement. A typical question: Which command enables Loop Guard on an interface? Correct: spanning-tree guard loop. Another question may ask which ports should have Loop Guard enabled: answer is non-designated ports (alternate and backup ports). A variation might ask which ports should NOT have Loop Guard enabled, such as ports with BPDU filtering or PortFast enabled, because those ports do not expect BPDUs.
Troubleshooting-based questions require analyzing command outputs. For instance, the output of show spanning-tree interface gigabitethernet 0/1 might show Port State: Loop Inconsistent. The question asks what this indicates. The answer is that the interface stopped receiving BPDUs due to a unidirectional link failure. The follow-up question could ask what action to take: check the physical layer (cable, optics) on that link. Another common output is show spanning-tree summary, which might show total number of ports in loop-inconsistent state.
Multiple-choice questions may list several STP features and ask which one addresses unidirectional link failures. Distractors often include BPDU Guard, Root Guard, UDLD (Unidirectional Link Detection), and PortFast. While UDLD also detects unidirectional links, it operates differently (Layer 1/2) and can shut down a port, whereas Loop Guard is purely STP-based. Exam writers love to test these nuances.
Practise Loop Guard Questions
Test your understanding with exam-style practice questions.
Example Scenario
Consider a small office network with two switches, Switch-1 and Switch-2, connected by two fiber optic cables to provide redundancy. The Spanning Tree Protocol is running, and one of the ports on Switch-2 is in a blocking state (alternate port) to prevent a loop. Suddenly, a technician accidentally bends one of the fiber cables too sharply, causing only one direction of light to pass through. Data can still travel from Switch-1 to Switch-2 over that cable, but no data can go from Switch-2 back to Switch-1 over that same cable. This is a unidirectional link failure.
On Switch-2, the blocked port stops receiving BPDUs from Switch-1 because the receive path is broken. Without Loop Guard, after the Max Age timer expires (20 seconds by default), Switch-2 would assume that the path via Switch-1 is no longer valid and would transition this port through listening and learning states to forwarding. Meanwhile, Switch-1 still thinks its path to Switch-2 is fine because it can still send traffic. Now, both switches believe they have a valid forwarding path to each other, creating a loop. Broadcast frames will circulate endlessly, consuming bandwidth and CPU, and the network will crash.
With Loop Guard enabled on that blocked port, the moment BPDUs stop arriving, the port is immediately placed into a Loop Inconsistent state. No traffic is forwarded, even after the Max Age timer expires. The rest of the network continues operating normally, using the other redundant link. The network administrator receives an alert (often via SNMP or syslog) that a port is in a loop-inconsistent state. They inspect the fiber cable, find the bad bend, replace it, and within seconds BPDUs start flowing again. The port automatically transitions back to its proper blocking state, and full redundancy is restored without any outage. This scenario shows how Loop Guard acts as a silent, automatic guardian against a failure mode that could otherwise bring down the entire office.
Common Mistakes
Thinking Loop Guard shuts down the port completely.
Loop Guard does not administratively disable (shut down) the interface. It places the port into a Loop Inconsistent state where the port is still logically up but blocks all traffic. The port remains active and can be seen in the running configuration. Shutting down a port would require manual intervention, while Loop Guard automatically recovers when BPDUs resume.
Understand that Loop Guard uses a special STP state, not an administrative shutdown. The port stays up at Layer 1 but blocks at Layer 2.
Confusing Loop Guard with BPDU Guard.
BPDU Guard reacts to the presence of unexpected BPDUs (e.g., on an access port) and disables the port (errdisable state). Loop Guard reacts to the absence of expected BPDUs and blocks traffic without disabling the port. They solve opposite problems.
Remember: BPDU Guard shuts the port if it receives a BPDU; Loop Guard blocks the port if it stops receiving BPDUs.
Enabling Loop Guard on a port with PortFast enabled.
PortFast is used on ports connected to end hosts that do not send BPDUs. If Loop Guard is also enabled, the port will never receive BPDUs, so it will immediately go into a loop-inconsistent state and block traffic. This combination breaks connectivity for end users.
Do not enable Loop Guard on PortFast-enabled ports. PortFast ports should use BPDU Guard instead, if needed.
Believing Loop Guard can detect all types of unidirectional failures.
Loop Guard only detects unidirectional failures where BPDUs stop arriving on a port that was previously receiving them. It will not detect failures on a designated forwarding port because those ports do not rely on receiving BPDUs. Also, it does not detect failures at the physical layer; a link can be up, but if BPDUs still flow, Loop Guard will not trigger.
Use Loop Guard together with UDLD or other physical-layer monitoring tools for complete protection against unidirectional failures.
Assuming Loop Guard works on all switch ports by default.
Loop Guard is not enabled by default on most switches. It must be explicitly configured either globally (spanning-tree loopguard default) or per-interface (spanning-tree guard loop). Many administrators forget to enable it and assume they are protected.
Always verify Loop Guard configuration in the switch. Use show spanning-tree summary to see if loopguard is enabled globally or per interface.
Exam Trap — Don't Get Fooled
{"trap":"In an exam question, the scenario describes a switch port that stops receiving BPDUs, and the candidate is asked which feature will prevent a loop. One of the answer choices is BPDU Guard. Many learners choose BPDU Guard because they remember it is related to BPDUs and security."
,"why_learners_choose_it":"Learners often lump all STP protections together. They recall that BPDU Guard is a feature triggered by BPDUs, so they assume it applies whenever BPDUs are absent. They may also think 'guard' means it guards against BPDU problems, making BPDU Guard the 'obvious' answer."
,"how_to_avoid_it":"Remember the trigger for each feature: BPDU Guard triggers when a BPDU is received unexpectedly. Loop Guard triggers when a BPDU is NOT received. If the question says 'stops receiving BPDUs,' the answer is Loop Guard.
Practice memorizing the phrase: 'No BPDU? Loop Guard! Unexpected BPDU? BPDU Guard!'
Step-by-Step Breakdown
STP Convergence and Port Roles
When Spanning Tree Protocol runs on a network with redundant links, the switches elect a root bridge and each switch determines which of its ports will be the root port (closest to the root), designated ports (forwarding traffic on a segment), and alternate/backup ports (blocking to prevent loops). Alternate and backup ports continuously listen for BPDUs from the designated switch on their segment to maintain a loop-free topology.
Loop Guard Configuration
A network administrator enables Loop Guard on specific interfaces using a command like spanning-tree guard loop (Cisco) or a global command spanning-tree loopguard default. This instructs the switch to monitor BPDU reception on any port that is in a blocking (alternate or backup) state. Loop Guard is not active on designated or root ports because those ports are expected to forward traffic and do not depend on receiving BPDUs to stay loop-free.
Unidirectional Link Failure Occurs
A physical issue such as a damaged fiber, dirty connector, or faulty transceiver causes data transmission to become unidirectional. The switch with the blocking port can still send BPDUs to its neighbor (if the transmit path works), but it stops receiving BPDUs from the neighbor because the receive path is broken. From the switch's perspective, the neighbor is silent.
BPDU Absence Detection
The switch's STP process notices that BPDUs have not been received on that blocking port for a period equal to the hello time (default 2 seconds) multiplied by a configurable multiplier (often 3 or 4). When this threshold is exceeded, Loop Guard activates and prevents the normal STP aging process from transitioning the port to forwarding. Instead, the port is moved to the Loop Inconsistent state.
Port in Loop Inconsistent State
In the Loop Inconsistent state, the port does not forward any data traffic and does not participate in the normal STP state machine (blocking, listening, learning, forwarding). It effectively stays disabled for data, but the physical link remains up. The switch logs a message (e.g., %SPANTREE-2-LOOPGUARD_BLOCK) indicating the event. The rest of the network continues using the redundant path that is still working, so no loop occurs.
Recovery After BPDUs Resume
Once the physical issue is resolved and BPDUs begin arriving again on the port, the switch detects the first valid BPDU. Loop Guard automatically transitions the port out of the Loop Inconsistent state and back to its original STP role (alternate or backup). The port then follows normal STP convergence steps (listening, learning) before returning to the appropriate state (usually blocking). No manual intervention is needed.
Practical Mini-Lesson
Loop Guard is a feature that every network professional should understand and consider for deployment in any switched network that relies on STP. In practice, enabling Loop Guard is straightforward: the command spanning-tree guard loop on an interface, or the global command spanning-tree loopguard default (Cisco IOS) which applies it to all interfaces except those that are PortFast-enabled. The global option is often simpler and reduces configuration overhead. However, careful planning is needed: do not enable it on interfaces that intentionally do not receive BPDUs, such as access ports with PortFast or ports connected to non-STP devices.
One of the most common real-world mistakes is enabling Loop Guard on a port that also has BPDU filtering configured. BPDU filtering suppresses the transmission and reception of BPDUs on a port, so with Loop Guard active, the port will never receive BPDUs and will always go into a loop-inconsistent state, effectively breaking that link. Always check for BPDU filtering before applying Loop Guard.
Another practical consideration is recovery behavior. The default recovery is automatic: as soon as BPDUs are received again, the port returns to normal. This is generally good, but in some environments administrators prefer manual recovery to ensure they are aware of the issue and can inspect the faulty hardware. Some switch platforms allow configuring the recovery to be manual by setting an errdisable recovery policy, but since Loop Guard does not actually put the port in errdisable, that approach does not apply. Instead, some switches offer a delay timer or persistent blocking until cleared. Check vendor documentation for granular control.
Professionals should also know that Loop Guard works best when combined with UDLD. While Loop Guard protects against unidirectional failures on blocking ports, UDLD can detect and shut down a faulty link even if it is a designated or root port. Together, they provide comprehensive coverage. In data center environments with many redundant links, a default configuration of spanning-tree loopguard default and udld enable aggressive is a common best practice.
What can go wrong? The most common problem is a port stuck in loop-inconsistent state due to a intermittent hardware fault. The switch may keep cycling between normal and loop-inconsistent as the cable makes and breaks contact. This can cause flapping and network instability. In such cases, the administrator should immediately replace the faulty physical component rather than rely on the automatic recovery. Another issue is human error: applying Loop Guard on a PortFast port accidentally, causing all end users on that switch to lose connectivity until the misconfiguration is fixed.
Finally, remember that Loop Guard does not protect against all types of loops. It only prevents loops caused by unidirectional failures on blocking ports. Other loop sources (e.g., misconfigured STP priorities, rogue switches, or software bugs) require different mitigation strategies. Always use a comprehensive STP design with multiple protections.
Memory Tip
Loop Guard: No BPDU? Block the port. BPDU Guard: Got a BPDU? Shut the port. The ‘L’ in Loop stands for ‘Lack of BPDU.’
Covered in These Exams
Current Exam Context
Current exam versions that test this topic — use these objectives when studying.
200-301Cisco CCNA →N10-009CompTIA Network+ →Related Glossary Terms
802.1Q is the networking standard that allows multiple virtual LANs (VLANs) to share a single physical network link by tagging Ethernet frames with VLAN identification information.
802.1X is a network access control standard that authenticates devices before they are allowed to connect to a wired or wireless network.
An A record is a type of DNS resource record that maps a domain name to an IPv4 address.
AAA (Authentication, Authorization, and Accounting) is a security framework that controls who can access a network, what they are allowed to do, and tracks what they did.
An AAAA record is a DNS record that maps a domain name to an IPv6 address, allowing devices to find each other over the internet using the newer IP addressing system.
Frequently Asked Questions
Why does Loop Guard only work on blocking ports?
Loop Guard is designed to prevent a blocking port from incorrectly transitioning to a forwarding state when BPDUs are lost. Designated ports and root ports already forward traffic and do not depend on receiving BPDUs to prevent loops, so Loop Guard is not needed on them.
Can Loop Guard be used on a port that connects to a single end device like a PC?
No. End devices do not send BPDUs, so the port would never receive any. Loop Guard would immediately put the port into a loop-inconsistent state, blocking all traffic. For host-facing ports, use PortFast and optionally BPDU Guard.
Does Loop Guard work with Rapid Spanning Tree Protocol (RSTP) and Multiple Spanning Tree Protocol (MSTP)?
Yes, Loop Guard is compatible with RSTP (802.1w) and MSTP (802.1s). The behavior is the same: if a port in an alternate or backup role stops receiving BPDUs, it is placed in a loop-inconsistent state. The protocol enhances all STP variants.
How do I verify if Loop Guard is enabled on my switch?
Use the command 'show spanning-tree summary' (Cisco) or the equivalent for your vendor. Look for 'LoopGuard' in the output. You can also check individual interfaces with 'show spanning-tree interface [interface-id]' to see the port state and any protections.
What is the difference between Loop Guard and UDLD?
Loop Guard is an STP-based feature that only works on blocking ports and relies on the presence of BPDUs. UDLD is a Layer 2 protocol that actively tests link health on all ports and can detect unidirectional failures even on forwarding ports. They complement each other; many networks use both.
What should I do if a port is stuck in loop-inconsistent state?
First, check the physical layer: examine cables, connectors, and transceivers. Replace any faulty components. Once the link is fully bidirectional, BPDUs will resume and the port will automatically recover. If the port does not recover, verify that BPDU filtering is not enabled on that port.
Summary
Loop Guard is a vital Spanning Tree Protocol enhancement that protects networks from loops caused by unidirectional link failures. When a blocking port stops receiving BPDUs-an indication that the receive path is broken-Loop Guard immediately prevents that port from transitioning to forwarding, which would create a loop. Instead, it places the port in a Loop Inconsistent state, blocking all traffic until BPDUs resume. This automatic, self-healing mechanism is one of the most important tools a network engineer has for maintaining Layer 2 stability.
Why does Loop Guard matter? In modern networks, redundancy is essential, but redundancy introduces the risk of loops. Loop Guard addresses a specific and common failure scenario that other protections like BPDU Guard or Root Guard do not cover. It is lightweight, easy to configure, and widely supported across vendor platforms. For any network with redundant switches, enabling Loop Guard on all non-designated ports is a best practice that can prevent hours of downtime.
For certification exams, Loop Guard is a recurring topic, especially in CCNA and CCNP. Candidates must understand the exact problem it solves (unidirectional failure on a blocking port) and how it differs from BPDU Guard and Root Guard. The single most important exam takeaway is: Loop Guard blocks port traffic when BPDUs stop arriving; BPDU Guard disables a port when BPDUs are received. Memorize this distinction, and you will ace any STP protection question. In practice and on the exam, Loop Guard is a simple but powerful feature that every networking professional should master.