Question 580At fictional Orchard Link 145, a regional service-provider network, during a preproduction design validation, operations observes: A MAC is learned on an unexpected aggregation interface following a customer circuit move. Which failure consequence follows most closely from ignoring this issue? Unnecessary filtering interrupts normal bridged service. Large customer frames fail selectively and create difficult-to-reproduce application problems. A partial label-distribution failure persists without an alert. Traffic follows an obsolete service path or reaches the wrong customer site. ExplanationCorrect Answer D:Traffic follows an obsolete service path or reaches the wrong customer site. Bridge-table observations must be interpreted alongside actual physical and logical port membership. Trace member interface and bridge-domain association, then correct the service attachment. Incorrect Answers A:Unnecessary filtering interrupts normal bridged service. This relates to a case where a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop; the current situation is that a MAC is learned on an unexpected aggregation interface following a customer circuit move. B:Large customer frames fail selectively and create difficult-to-reproduce application problems. 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 MAC is learned on an unexpected aggregation interface following a customer circuit move. C:A partial label-distribution failure persists without an alert. That relates to circumstances in which monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. Here the problem is that a MAC is learned on an unexpected aggregation interface following a customer circuit move.
Question 581In a separate fictional JNCIS-SP lab review for Oakshore Peering 146, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A MAC is learned on an unexpected aggregation interface following a customer circuit move. What intervention most directly restores the intended routing or switching behavior? Associate the gateway with the intended routing and bridging contexts and inspect both tables. Trace member interface and bridge-domain association, then correct the service attachment. Correct the QinQ service tag mapping and verify the inner customer tag remains intact. Add an explicit approved community match and verify the intended import or export action. ExplanationCorrect Answer B:Trace member interface and bridge-domain association, then correct the service attachment. The customer MAC is relearned on the authorized new handoff interface. Bridge-table observations must be interpreted alongside actual physical and logical port membership. Incorrect Answers A:Associate the gateway with the intended routing and bridging contexts and inspect both tables. This could help if an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch, but not when a MAC is learned on an unexpected aggregation interface following a customer circuit move. C:Correct the QinQ service tag mapping and verify the inner customer tag remains intact. It is useful for situations where provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag; the reported fault, though, is that a MAC is learned on an unexpected aggregation interface following a customer circuit move. D:Add an explicit approved community match and verify the intended import or export action. That relates to circumstances in which an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. Here the problem is that a MAC is learned on an unexpected aggregation interface following a customer circuit move.
Question 582In a separate fictional JNCIS-SP lab review for Oakshore Peering 146, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A MAC is learned on an unexpected aggregation interface following a customer circuit move. Which networking principle explains why the proposed correction is appropriate? Customer VLAN IDs are not globally unique and require deliberate provider separation. Trunk membership should reflect explicit service authorization, not an unrestricted default. Bridge-table observations must be interpreted alongside actual physical and logical port membership. BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers. ExplanationCorrect Answer C:Bridge-table observations must be interpreted alongside actual physical and logical port membership. The customer MAC is relearned on the authorized new handoff interface. Trace member interface and bridge-domain association, then correct the service attachment. Incorrect Answers A:Customer VLAN IDs are not globally unique and require deliberate provider separation. It is relevant if two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge, but the reported issue is that a MAC is learned on an unexpected aggregation interface following a customer circuit move. B:Trunk membership should reflect explicit service authorization, not an unrestricted default. This could help if an interface permits every customer VLAN tag despite a contract listing only two approved VLANs, but not when a MAC is learned on an unexpected aggregation interface following a customer circuit move. D:BFD can detect forwarding-path failure more promptly than many ordinary routing protocol timers. It is useful for situations where a core route remains active long after a forwarding path fails because the routing protocol's regular timeout is too slow; the reported fault, though, is that a MAC is learned on an unexpected aggregation interface following a customer circuit move.
Question 583In a separate fictional JNCIS-SP lab review for Oakshore Peering 146, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A MAC is learned on an unexpected aggregation interface following a customer circuit move. Which validation result would confirm the design is now functioning? MAC learning and broadcast tests show separation of the two customers. The customer MAC is relearned on the authorized new handoff interface. Local hosts reach the IRB gateway and authorized routed subnets beyond it. Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service. ExplanationCorrect Answer B:The customer MAC is relearned on the authorized new handoff interface. Trace member interface and bridge-domain association, then correct the service attachment. Bridge-table observations must be interpreted alongside actual physical and logical port membership. Incorrect Answers A:MAC learning and broadcast tests show separation of the two customers. This is applicable when two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services; the present condition is that a MAC is learned on an unexpected aggregation interface following a customer circuit move. C:Local hosts reach the IRB gateway and authorized routed subnets beyond it. This could help if customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent, but not when a MAC is learned on an unexpected aggregation interface following a customer circuit move. D:Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service. This relates to a case where monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered; the current situation is that a MAC is learned on an unexpected aggregation interface following a customer circuit move.
Question 584In a separate fictional JNCIS-SP lab review for Oakshore Peering 146, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A MAC is learned on an unexpected aggregation interface following a customer circuit move. What likely service impact does this condition create? Subscriber VLANs collide or customer traffic arrives in the wrong service. Repeated flooding and customer frame loss continue despite healthy routes. Unwanted routes may alter forwarding or create customer traffic leakage. Traffic follows an obsolete service path or reaches the wrong customer site. ExplanationCorrect Answer D:Traffic follows an obsolete service path or reaches the wrong customer site. Trace member interface and bridge-domain association, then correct the service attachment. Bridge-table observations must be interpreted alongside actual physical and logical port membership. Incorrect Answers A:Subscriber VLANs collide or customer traffic arrives in the wrong service. That could help when provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag; here, a MAC is learned on an unexpected aggregation interface following a customer circuit move. B:Repeated flooding and customer frame loss continue despite healthy routes. This is applicable when a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables; the present condition is that a MAC is learned on an unexpected aggregation interface following a customer circuit move. C:Unwanted routes may alter forwarding or create customer traffic leakage. It is relevant if a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy, but the reported issue is that a MAC is learned on an unexpected aggregation interface following a customer circuit move.
Question 585At fictional Brookridge Metro 147, a regional service-provider network, during a core-routing acceptance test, operations observes: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. Which configuration or operational correction most directly addresses this failure? Trace member interface and bridge-domain association, then correct the service attachment. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Use separate outer service tags or forwarding contexts for the distinct customers. Apply the approved BPDU protection policy to the access edge and test the violation response. ExplanationCorrect Answer C:Use separate outer service tags or forwarding contexts for the distinct customers. Customer VLAN IDs are not globally unique and require deliberate provider separation. Two identical inner customer tags remain isolated by separate outer tags or service instances. Incorrect Answers A:Trace member interface and bridge-domain association, then correct the service attachment. This could matter when a MAC is learned on an unexpected aggregation interface following a customer circuit move. In this case, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. B:Check MAC aging and traffic timing before adding disruptive forwarding restrictions. That could help when a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop; here, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. D:Apply the approved BPDU protection policy to the access edge and test the violation response. It is relevant if a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only, but the reported issue is that two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.
Question 586At fictional Brookridge Metro 147, a regional service-provider network, during a core-routing acceptance test, operations observes: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. Which Junos forwarding or control-plane rule applies to this case? Trunk membership should reflect explicit service authorization, not an unrestricted default. Virtual switching can provide separate Layer 2 forwarding contexts for tenants. Junos directly connected reachability depends on active logical interface configuration and state. Customer VLAN IDs are not globally unique and require deliberate provider separation. ExplanationCorrect Answer D:Customer VLAN IDs are not globally unique and require deliberate provider separation. Use separate outer service tags or forwarding contexts for the distinct customers. Two identical inner customer tags remain isolated by separate outer tags or service instances. Incorrect Answers A:Trunk membership should reflect explicit service authorization, not an unrestricted default. It addresses a different problem: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Here, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. B:Virtual switching can provide separate Layer 2 forwarding contexts for tenants. This could matter when two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. In this case, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. C:Junos directly connected reachability depends on active logical interface configuration and state. That could help when a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout; here, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.
Question 587At fictional Brookridge Metro 147, a regional service-provider network, during a core-routing acceptance test, operations observes: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. What operational evidence best establishes successful remediation? Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch. The bridge table resolves the destination MAC to the correct egress port. MAC tables and customer bridge forwarding remain stable during controlled switchover. Two identical inner customer tags remain isolated by separate outer tags or service instances. ExplanationCorrect Answer D:Two identical inner customer tags remain isolated by separate outer tags or service instances. Customer VLAN IDs are not globally unique and require deliberate provider separation. Use separate outer service tags or forwarding contexts for the distinct customers. Incorrect Answers A:Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch. That option concerns hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier. The problem here is different: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. B:The bridge table resolves the destination MAC to the correct egress port. It addresses a different problem: An operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. Here, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. C:MAC tables and customer bridge forwarding remain stable during controlled switchover. This could matter when a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets. In this case, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.
Question 588At fictional Brookridge Metro 147, a regional service-provider network, during a core-routing acceptance test, operations observes: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. Which operational harm would persist without the intended correction? Subscriber VLANs collide or customer traffic arrives in the wrong service. Traffic leaks or becomes blackholed at the L2/L3 boundary. Traffic bypasses an approved low-latency or protected path. A repeated VLAN number causes cross-customer broadcast leakage. ExplanationCorrect Answer D:A repeated VLAN number causes cross-customer broadcast leakage. Customer VLAN IDs are not globally unique and require deliberate provider separation. Use separate outer service tags or forwarding contexts for the distinct customers. Incorrect Answers A:Subscriber VLANs collide or customer traffic arrives in the wrong service. The choice would be appropriate if provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. Here, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. B:Traffic leaks or becomes blackholed at the L2/L3 boundary. 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: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. C:Traffic bypasses an approved low-latency or protected path. It addresses a different problem: A tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change. Here, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.
Question 589In a separate fictional JNCIS-SP lab review for Stonefield Telecom 148, a carrier-edge and core routing team, following a monitored network change window, engineers find: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. What should the Junos specialist change first to resolve this specific fault? Constrain permitted VLAN membership and confirm unauthorized tag handling. Use separate outer service tags or forwarding contexts for the distinct customers. Trace member interface and bridge-domain association, then correct the service attachment. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. ExplanationCorrect Answer B:Use separate outer service tags or forwarding contexts for the distinct customers. Two identical inner customer tags remain isolated by separate outer tags or service instances. Customer VLAN IDs are not globally unique and require deliberate provider separation. 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, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. C:Trace member interface and bridge-domain association, then correct the service attachment. That option concerns a MAC is learned on an unexpected aggregation interface following a customer circuit move. The problem here is different: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. D:Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. It addresses a different problem: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. Here, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.
Question 590In a separate fictional JNCIS-SP lab review for Stonefield Telecom 148, a carrier-edge and core routing team, following a monitored network change window, engineers find: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. What technical principle underlies the right remedy? Layer 2 switching forwards traffic within the configured VLAN bridge domain. Bridge-table observations must be interpreted alongside actual physical and logical port membership. Customer VLAN IDs are not globally unique and require deliberate provider separation. Route policy controls which eligible nonnative prefixes are intentionally originated into IS-IS. ExplanationCorrect Answer C:Customer VLAN IDs are not globally unique and require deliberate provider separation. Two identical inner customer tags remain isolated by separate outer tags or service instances. Use separate outer service tags or forwarding contexts for the distinct customers. Incorrect Answers A:Layer 2 switching forwards traffic within the configured VLAN bridge domain. That relates to circumstances in which hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier. Here the problem is that two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. B:Bridge-table observations must be interpreted alongside actual physical and logical port membership. This addresses a situation in which a MAC is learned on an unexpected aggregation interface following a customer circuit move; however, two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. D:Route policy controls which eligible nonnative prefixes are intentionally originated into IS-IS. That option concerns a customer service route never reaches another IS-IS area because the required export policy omits it. The problem here is different: Two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge.