Modules 5 6 Redundant Networks Exam: Exact Answer & Steps

Do you ever stare at a practice test and wonder why the “redundant networks” questions feel like a whole other language?
Still, you’re not alone. And most of us have hit that wall when the exam throws module 5 or module 6 at us, and suddenly every diagram looks like a maze. The short version is: if you can untangle the concepts behind redundancy, those questions stop being a mystery and start feeling like a puzzle you actually enjoy solving.

What Is Redundant Networks (Modules 5 & 6)

When you hear “redundant network” you might picture a backup server farm or a spare router tucked away in a closet. In reality, redundancy is the design philosophy that keeps traffic flowing even when something fails But it adds up..

In the context of the Cisco, CompTIA, or vendor‑specific certification exams, modules 5 and 6 usually cover:

• Module 5 – Design Principles – How to architect a network so there’s more than one path for data. Think of it as building a bridge with multiple lanes; if one lane gets blocked, traffic can still cross.
• Module 6 – Implementation & Troubleshooting – The nuts‑and‑bolts: configuring protocols, verifying failover, and diagnosing why a supposedly “redundant” link isn’t actually doing its job.

So, redundant networks aren’t just about having extra gear; they’re about intelligent, coordinated failover that the network itself can manage without human intervention Simple as that..

Core Concepts

• Layer 2 Redundancy – Spanning Tree Protocol (STP), Rapid‑STP (RSTP), Multiple STP (MSTP).
• Layer 3 Redundancy – HSRP, VRRP, GLBP, and static routing tricks.
• Link Aggregation – LACP/EtherChannel to bundle several physical links into one logical pipe.
• Physical Path Diversity – Cabling routes, separate power supplies, and diverse ISP connections.

If you can keep those four pillars straight, you’ll breeze through the exam scenarios.

Why It Matters / Why People Care

Real‑world networks don’t get a “please hold” button when a switch blows up. Companies lose money, reputation, and sometimes even lives when a single point of failure brings everything down But it adds up..

On the exam, the stakes are similar: you’ll be asked to design a network that won’t go dark if a link or device fails. If you can explain why redundancy is needed, you’ll also be able to pick the right protocol for the job.

Business Impact

• Uptime Guarantees – Service Level Agreements (SLAs) often demand 99.9 % or higher availability. Redundancy is the only realistic way to hit those numbers.
• Scalability – A well‑designed redundant fabric can grow without a complete redesign.
• Cost Efficiency – Ironically, adding the right redundancy saves money by avoiding emergency repairs and downtime penalties.

Exam Impact

• Scenario Questions – You’ll see a diagram with a broken link and be asked what protocol will keep traffic moving.
• Configuration Tasks – Write the exact CLI commands for HSRP or LACP.
• Troubleshooting – Identify why a “redundant” link is still a single point of failure (mis‑configured STP priority, wrong VLAN, etc.).

Understanding the “why” turns those multiple‑choice questions from guesswork into logical deductions Not complicated — just consistent..

How It Works (or How to Do It)

Below is the meat of the matter. Grab a notebook, because these steps are the ones you’ll actually type into a lab or write on a test.

### Layer 2 Redundancy: Spanning Tree Protocol

1. What STP Does – It blocks just enough ports to prevent loops while keeping at least one active path.
2. Key Parameters
   • Bridge ID (BID) – Combination of priority + MAC. Lower wins.
   • Port ID – Determines which port stays forwarding when BIDs tie.
3. Rapid‑STP (RSTP) – Faster convergence (sub‑second). Use when you need quick failover.
4. Multiple STP (MSTP) – Lets you map several VLANs to a single instance, saving CPU.
5. Practical CLI (Cisco example)

Switch(config)# spanning‑tree mode rapid-pvst  
Switch(config)# spanning‑tree vlan 10 priority 24576  
Switch(config)# interface Gig0/1  
Switch(config-if)# spanning‑tree portfast  

Tip: Always set the root bridge on the device with the most CPU headroom, not the edge switch Nothing fancy..

### Layer 3 Redundancy: HSRP, VRRP, GLBP

How to configure HSRP (Cisco)

interface Gig0/0  
 ip address 10.1.1.2 255.255.255.0  
 standby 1 ip 10.1.1.1  
 standby 1 priority 110  
 standby 1 preempt  

What most people miss: The preempt command. Without it, a higher‑priority router won’t take over after a reboot, leaving the network stuck on the old standby.

### Link Aggregation: EtherChannel & LACP

1. Why bundle? – Increases bandwidth and provides redundancy; if one physical link dies, the logical link stays up.
2. LACP vs. PAgP – LACP is IEEE standard; PAgP is Cisco‑only. Stick with LACP for exam‑friendly, multi‑vendor scenarios.
3. CLI Example

interface range Gig0/1‑2  
 channel-group 1 mode active   // LACP active  

4. Verification – show etherchannel summary should list “Port-channel1” as “U” (up) and “P” (bundled).

### Physical Path Diversity

• Separate Trunk Cables – Run fiber on a different route than copper.
• Dual Power Supplies – Connect each to a different UPS or PDU.
• Multiple ISPs – BGP with local‑preference tuning ensures traffic shifts when one provider fails.

In practice, you’ll combine all these layers. A typical data‑center design might have LACP for uplinks, RSTP for the access layer, and HSRP for default‑gateway redundancy The details matter here. But it adds up..

Common Mistakes / What Most People Get Wrong

1. Forgetting the Root Bridge – Leaving the default priority (32768) on every switch means the switch closest to the core becomes root by luck, not design. Exams love to trip you up with a “which switch should be root?” question.
2. Mixing STP Modes – You can’t have RSTP on one switch and classic STP on another in the same VLAN; they’ll fall back to the slowest mode.
3. Skipping preempt in HSRP/VRRP – The standby never hands back control, so after a power loss the network stays on the lower‑priority router.
4. Mis‑aligned VLANs on EtherChannel – All member ports must be in the same VLAN; otherwise the bundle won’t form and you’ll see “Port‑channel down”.
5. Assuming Redundancy = No Configuration – A spare router sitting idle does nothing until you configure a failover protocol.

If you catch these early, you’ll avoid the “I thought I was redundant, but the lab still failed” trap.

Practical Tips / What Actually Works

• Label your diagrams – Write the protocol name next to each link. When you see “HSRP Group 1” you instantly know which IP is virtual.
• Use the “lowest‑priority‑wins” rule – Set the core switch to a lower priority (e.g., 24576) and edge switches higher (e.g., 28672). It’s a quick way to force the right root.
• Test failover in a lab – Pull the cable on the active link, watch STP reconverge, then re‑plug. Timing matters; RSTP should recover in <1 second.
• Document LACP mode – Always use active on both ends; passive on one side and active on the other works, but active‑active is clearer.
• Check the MAC address table – After HSRP, both routers should be learning the virtual MAC on the same VLAN. If not, you have a VLAN mismatch.

And remember: the exam doesn’t care how fancy your network looks; it cares that you can prove redundancy works under failure conditions Easy to understand, harder to ignore. And it works..

FAQ

Q: When should I use RSTP instead of MSTP?
A: RSTP is fine for a single VLAN or a small number of VLANs. MSTP shines when you have many VLANs and want to group them into a few STP instances to reduce CPU load.

Q: Can HSRP and VRRP run on the same subnet?
A: Technically yes, but it’s a recipe for confusion. Stick to one protocol per VLAN unless you have a very specific requirement.

Q: How do I verify that an EtherChannel is truly redundant?
A: Use show etherchannel detail. Look for “Ports in channel: 2” and “Port‑channel is up”. Then physically disconnect one member cable; the Port‑channel should stay up Most people skip this — try not to..

Q: What’s the difference between “active” and “standby” in HSRP?
A: The active router forwards traffic for the virtual IP. The standby monitors the active and takes over if it disappears. Both share the same MAC address.

Q: Do I need to enable BFD for HSRP failover?
A: Not required for basic HSRP, but BFD can speed up detection of a failed router, especially across a WAN link.

Redundancy isn’t a buzzword; it’s the safety net that keeps modern networks humming.
If you walk away from this article with a clear picture of how STP, HSRP/VRRP, LACP, and physical diversity fit together, you’ll not only ace the modules 5 and 6 exam—you’ll have a solid foundation for real‑world network design The details matter here..

Now go fire up that lab, break a link, and watch the magic happen. Good luck!

Putting It All Together – A Mini‑Design Walkthrough

Imagine you’ve just been handed a 20‑port campus core that must stay up 99.99 % of the time. Here’s a quick‑fire blueprint that stitches the concepts above into a single, cohesive design.

Why this works

1. Two‑node core with RSTP/MSTP – Even if one chassis loses power, the other instantly becomes the sole STP root. Because MST groups all VLANs into a single instance, the CPU overhead stays low while still providing per‑VLAN control if you later need it.
2. LACP Port‑Channels – Every leaf sees both cores as a single logical link. If a fiber cut removes one member, traffic simply re‑balances across the remaining member; the port‑channel never flaps.
3. HSRP/VRRP on the same VLANs – The leaf switches share a virtual IP (10.0.10.1 and 10.0.20.1). The router with the higher priority becomes active; the other sits standby, ready to take over instantly. Because the virtual MAC is learned on every downstream port, hosts never need to change ARP entries during a failover.
4. BFD on the WAN – While HSRP will eventually notice a router outage, BFD shrinks the detection window to a few hundred milliseconds, which is essential for a service‑provider link where latency matters.

Checklist Before You Walk Away

If each line checks out, you’ve built a network that not only passes the exam but also survives the real world.

Conclusion

Redundancy isn’t a checklist; it’s a mindset. By understanding the why behind STP’s root election, seeing the traffic flow when HSRP hands off a virtual IP, and watching the link‑aggregation counters as a single cable disappears, you transform abstract protocol names into tangible, test‑able mechanisms.

When you approach a Cisco exam question—or a production rollout—ask yourself:

1. What single point of failure am I protecting?
2. Which protocol gives me the fastest, most deterministic recovery for that point?
3. How will I prove it works?

Answer those three, and you’ll not only collect the right configuration commands, you’ll also be able to demonstrate that the network stays up when the unexpected happens.

So fire up the simulator, break a link, watch the LEDs, and let the protocols do their dance. Consider this: mastering redundancy is the final piece that turns a good network engineer into a trusted one. Good luck, and may your links always stay up It's one of those things that adds up..