Question 510In a separate fictional JNCIS-SP lab review for Crestland Networks 128, a carrier-edge and core routing team, following a monitored network change window, engineers find: An edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. What technical principle underlies the right remedy? Ethernet bridges learn source MAC locations to forward known unicast traffic efficiently. An Ethernet port's VLAN tagging behavior must match the frames it receives. Customer VLAN IDs are not globally unique and require deliberate provider separation. IPv6-over-IPv4 tunnels depend on the transport underlay used to carry encapsulated traffic. ExplanationCorrect Answer A:Ethernet bridges learn source MAC locations to forward known unicast traffic efficiently. The MAC table shows each endpoint on the proper interface and known unicast flooding stops. Review bridge-domain membership, MAC learning and aging behavior and correct the affected interface configuration. Incorrect Answers B:An Ethernet port's VLAN tagging behavior must match the frames it receives. This could help if a provider access port drops customer tagged frames because it was configured for untagged access mode, but not when an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. C:Customer VLAN IDs are not globally unique and require deliberate provider separation. This relates to a case where two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge; the current situation is that an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. D:IPv6-over-IPv4 tunnels depend on the transport underlay used to carry encapsulated traffic. It is useful for situations where an IPv6 service is carried through an IPv4 underlay, but the tunnel endpoint's IPv4 route has disappeared; the reported fault, though, is that an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port.
Question 511In a separate fictional JNCIS-SP lab review for Crestland Networks 128, a carrier-edge and core routing team, following a monitored network change window, engineers find: An edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. Which acceptance finding demonstrates the affected service has recovered? Tagged customer frames enter the intended VLAN while disallowed tags are rejected. The MAC table shows each endpoint on the proper interface and known unicast flooding stops. A test frame relearns the source MAC and later packets forward as known unicast. The interswitch link uses normal RSTP role and state handling during topology tests. ExplanationCorrect Answer B:The MAC table shows each endpoint on the proper interface and known unicast flooding stops. Review bridge-domain membership, MAC learning and aging behavior and correct the affected interface configuration. Ethernet bridges learn source MAC locations to forward known unicast traffic efficiently. Incorrect Answers A:Tagged customer frames enter the intended VLAN while disallowed tags are rejected. This is applicable when a provider access port drops customer tagged frames because it was configured for untagged access mode; the present condition is that an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. C:A test frame relearns the source MAC and later packets forward as known unicast. This could help if a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop, but not when an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. D:The interswitch link uses normal RSTP role and state handling during topology tests. This relates to a case where a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior; the current situation is that an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port.
Question 512In a separate fictional JNCIS-SP lab review for Crestland Networks 128, a carrier-edge and core routing team, following a monitored network change window, engineers find: An edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. What is the direct residual network risk if the fault remains unresolved? A repeated VLAN number causes cross-customer broadcast leakage. Subscriber VLANs collide or customer traffic arrives in the wrong service. A redundant Layer 2 link becomes a forwarding loop and floods the provider network. Excessive flooding consumes bandwidth and exposes traffic across unintended ports. ExplanationCorrect Answer D:Excessive flooding consumes bandwidth and exposes traffic across unintended ports. Review bridge-domain membership, MAC learning and aging behavior and correct the affected interface configuration. Ethernet bridges learn source MAC locations to forward known unicast traffic efficiently. Incorrect Answers A:A repeated VLAN number causes cross-customer broadcast leakage. That could help when two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge; here, an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. B:Subscriber VLANs collide or customer traffic arrives in the wrong service. This is applicable when provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag; the present condition is that an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. C:A redundant Layer 2 link becomes a forwarding loop and floods the provider network. It is relevant if a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge, but the reported issue is that an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port.
Question 513At fictional Silverlake Routing 129, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. Which targeted remediation best fits the reported behavior? Constrain permitted VLAN membership and confirm unauthorized tag handling. Correct permitted VLAN membership on both logical ports and validate MAC learning in the same broadcast domain. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Set deliberate interface priorities and confirm the DR and BDR roles after a controlled election. ExplanationCorrect Answer C:Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Dynamic MAC entries may age out and be relearned on subsequent traffic. A test frame relearns the source MAC and later packets forward as known unicast. Incorrect Answers A:Constrain permitted VLAN membership and confirm unauthorized tag handling. This could matter when an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. In this case, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. B:Correct permitted VLAN membership on both logical ports and validate MAC learning in the same broadcast domain. That could help when hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier; here, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. D:Set deliberate interface priorities and confirm the DR and BDR roles after a controlled election. It is relevant if an unplanned access router becomes designated router after its interface receives an unexpectedly high priority, but the reported issue is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.
Question 514At fictional Silverlake Routing 129, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. Why is this particular correction the best fit for the stated defect? Customer VLAN IDs are not globally unique and require deliberate provider separation. Unexpected MAC movement often points to changing Layer 2 forwarding topology. Dynamic MAC entries may age out and be relearned on subsequent traffic. Martian route handling protects the routing table from addresses that should not be treated as normally reachable. ExplanationCorrect Answer C:Dynamic MAC entries may age out and be relearned on subsequent traffic. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. A test frame relearns the source MAC and later packets forward as known unicast. Incorrect Answers A:Customer VLAN IDs are not globally unique and require deliberate provider separation. It addresses a different problem: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. Here, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. B:Unexpected MAC movement often points to changing Layer 2 forwarding topology. This could matter when a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. In this case, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. D:Martian route handling protects the routing table from addresses that should not be treated as normally reachable. This is applicable when a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing; the present condition is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.
Question 515At fictional Silverlake Routing 129, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. What direct observation would prove the corrective action worked? The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. MAC learning and broadcast tests show separation of the two customers. A test frame relearns the source MAC and later packets forward as known unicast. Packet capture and forwarding state show the intended outgoing transport label. ExplanationCorrect Answer C:A test frame relearns the source MAC and later packets forward as known unicast. Dynamic MAC entries may age out and be relearned on subsequent traffic. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Incorrect Answers A:The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. That option concerns an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. The problem here is different: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. B:MAC learning and broadcast tests show separation of the two customers. It addresses a different problem: Two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Here, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. D:Packet capture and forwarding state show the intended outgoing transport label. That could help when operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header; here, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.
Question 516At fictional Silverlake Routing 129, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. Which failure consequence follows most closely from ignoring this issue? Unnecessary route changes mask a switching defect and prolong the outage. Unnecessary filtering interrupts normal bridged service. Hosts remain confined to a local broadcast domain. IPv6 traffic is entirely lost due to an unsuitable policy match. ExplanationCorrect Answer B:Unnecessary filtering interrupts normal bridged service. Dynamic MAC entries may age out and be relearned on subsequent traffic. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Incorrect Answers A:Unnecessary route changes mask a switching defect and prolong the outage. The choice would be appropriate if an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. Here, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. C:Hosts remain confined to a local broadcast domain. It addresses a different problem: Customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. Here, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. D:IPv6 traffic is entirely lost due to an unsuitable policy match. This could matter when a prefix-list filter written for IPv4 is applied conceptually to IPv6 routing, and all intended IPv6 routes vanish. In this case, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.
Question 517In a separate fictional JNCIS-SP lab review for Seabrook Metro 130, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. What intervention most directly restores the intended routing or switching behavior? Constrain permitted VLAN membership and confirm unauthorized tag handling. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Associate the gateway with the intended routing and bridging contexts and inspect both tables. Restore deliberate local-preference assignment and check selected egress paths. ExplanationCorrect Answer B:Check MAC aging and traffic timing before adding disruptive forwarding restrictions. A test frame relearns the source MAC and later packets forward as known unicast. Dynamic MAC entries may age out and be relearned on subsequent traffic. Incorrect Answers A:Constrain permitted VLAN membership and confirm unauthorized tag handling. This addresses a situation in which an interface permits every customer VLAN tag despite a contract listing only two approved VLANs; however, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. C:Associate the gateway with the intended routing and bridging contexts and inspect both tables. That option concerns an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. The problem here is different: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. D:Restore deliberate local-preference assignment and check selected egress paths. It addresses a different problem: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. Here, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.
Question 518In a separate fictional JNCIS-SP lab review for Seabrook Metro 130, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. Which networking principle explains why the proposed correction is appropriate? Ethernet bridges learn source MAC locations to forward known unicast traffic efficiently. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. Dynamic MAC entries may age out and be relearned on subsequent traffic. On multiaccess links, not all OSPF neighbors must become fully adjacent to each other. ExplanationCorrect Answer C:Dynamic MAC entries may age out and be relearned on subsequent traffic. A test frame relearns the source MAC and later packets forward as known unicast. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Incorrect Answers A:Ethernet bridges learn source MAC locations to forward known unicast traffic efficiently. That relates to circumstances in which an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. Here the problem is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. B:Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. This addresses a situation in which provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag; however, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. D:On multiaccess links, not all OSPF neighbors must become fully adjacent to each other. That option concerns on a broadcast segment, one non-designated router shows a peer at 2-Way and an operator incorrectly treats it as a failure. The problem here is different: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.
Question 519In a separate fictional JNCIS-SP lab review for Seabrook Metro 130, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. Which validation result would confirm the design is now functioning? A correctly sized customer frame traverses the entire provider handoff without drops. MAC learning and broadcast tests show separation of the two customers. A test frame relearns the source MAC and later packets forward as known unicast. The approved prefix is present as an external OSPF route and unauthorized prefixes remain absent. ExplanationCorrect Answer C:A test frame relearns the source MAC and later packets forward as known unicast. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Dynamic MAC entries may age out and be relearned on subsequent traffic. Incorrect Answers A:A correctly sized customer frame traverses the entire provider handoff without drops. It is useful for situations where a service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU; the reported fault, though, is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. B:MAC learning and broadcast tests show separation of the two customers. That relates to circumstances in which two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Here the problem is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. D:The approved prefix is present as an external OSPF route and unauthorized prefixes remain absent. The choice would be appropriate if a static service prefix is missing from OSPF because the export policy was attached but does not match it. Here, a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.
Question 520In a separate fictional JNCIS-SP lab review for Seabrook Metro 130, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. What likely service impact does this condition create? Unnecessary route changes mask a switching defect and prolong the outage. Customers can inject unapproved Layer 2 traffic into the provider bridge. IPv6 traffic is entirely lost due to an unsuitable policy match. Unnecessary filtering interrupts normal bridged service. ExplanationCorrect Answer D:Unnecessary filtering interrupts normal bridged service. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Dynamic MAC entries may age out and be relearned on subsequent traffic. Incorrect Answers A:Unnecessary route changes mask a switching defect and prolong the outage. This relates to a case where an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown; the current situation is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. B:Customers can inject unapproved Layer 2 traffic into the provider bridge. It is useful for situations where an interface permits every customer VLAN tag despite a contract listing only two approved VLANs; the reported fault, though, is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. C:IPv6 traffic is entirely lost due to an unsuitable policy match. That relates to circumstances in which a prefix-list filter written for IPv4 is applied conceptually to IPv6 routing, and all intended IPv6 routes vanish. Here the problem is that a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop.