Question 540At fictional Fairhaven Broadband 135, a regional service-provider network, during a preproduction design validation, operations observes: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. Which operational harm would persist without the intended correction? Customers can inject unapproved Layer 2 traffic into the provider bridge. A repeated VLAN number causes cross-customer broadcast leakage. Routers compute incompatible paths and traffic loops or blackholes can result. Traffic leaks or becomes blackholed at the L2/L3 boundary. ExplanationCorrect Answer D:Traffic leaks or becomes blackholed at the L2/L3 boundary. IRB traffic must bridge and route within an intentionally consistent service context. Associate the gateway with the intended routing and bridging contexts and inspect both tables. Incorrect Answers A:Customers can inject unapproved Layer 2 traffic into the provider bridge. The choice would be appropriate if an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. B:A repeated VLAN number causes cross-customer broadcast leakage. That option concerns two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. The problem here is different: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. C:Routers compute incompatible paths and traffic loops or blackholes can result. It addresses a different problem: Two supposed adjacent routers have different views of a backbone link because database synchronization never completes. Here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch.
Question 541In a separate fictional JNCIS-SP lab review for Cedarwater Transit 136, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. What should the Junos specialist change first to resolve this specific fault? Use separate outer service tags or forwarding contexts for the distinct customers. Associate the gateway with the intended routing and bridging contexts and inspect both tables. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. Inspect spanning-tree port role, state, and received BPDU information before changing hardware. ExplanationCorrect Answer B:Associate the gateway with the intended routing and bridging contexts and inspect both tables. The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. IRB traffic must bridge and route within an intentionally consistent service context. Incorrect Answers A:Use separate outer service tags or forwarding contexts for the distinct customers. This addresses a situation in which two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge; however, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. C:Check MAC aging and traffic timing before adding disruptive forwarding restrictions. That option concerns a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. The problem here is different: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. D:Inspect spanning-tree port role, state, and received BPDU information before changing hardware. It addresses a different problem: A link is physically up but stays blocked by spanning tree, and an operator incorrectly blames interface optics. Here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch.
Question 542In a separate fictional JNCIS-SP lab review for Cedarwater Transit 136, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. What technical principle underlies the right remedy? Dynamic MAC entries may age out and be relearned on subsequent traffic. An Ethernet port's VLAN tagging behavior must match the frames it receives. IRB traffic must bridge and route within an intentionally consistent service context. RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources. ExplanationCorrect Answer C:IRB traffic must bridge and route within an intentionally consistent service context. The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. Associate the gateway with the intended routing and bridging contexts and inspect both tables. Incorrect Answers A:Dynamic MAC entries may age out and be relearned on subsequent traffic. That relates to circumstances in which a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. Here the problem is that an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. B:An Ethernet port's VLAN tagging behavior must match the frames it receives. This addresses a situation in which a provider access port drops customer tagged frames because it was configured for untagged access mode; however, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. D:RSVP-TE bandwidth admission constrains whether an LSP can reserve the requested resources. That option concerns an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. The problem here is different: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch.
Question 543In a separate fictional JNCIS-SP lab review for Cedarwater Transit 136, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. Which acceptance finding demonstrates the affected service has recovered? The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch. Two identical inner customer tags remain isolated by separate outer tags or service instances. BGP and IGP neighbors remain stable through a controlled Routing Engine switchover. ExplanationCorrect Answer A:The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. Associate the gateway with the intended routing and bridging contexts and inspect both tables. IRB traffic must bridge and route within an intentionally consistent service context. Incorrect Answers B:Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch. 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 an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. C:Two identical inner customer tags remain isolated by separate outer tags or service instances. This addresses a situation in which two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge; however, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. D:BGP and IGP neighbors remain stable through a controlled Routing Engine switchover. The choice would be appropriate if traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state. Here, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch.
Question 544In a separate fictional JNCIS-SP lab review for Cedarwater Transit 136, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: An IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. What is the direct residual network risk if the fault remains unresolved? Excessive flooding consumes bandwidth and exposes traffic across unintended ports. Traffic leaks or becomes blackholed at the L2/L3 boundary. Subscriber VLANs collide or customer traffic arrives in the wrong service. Routing connectivity fails or a poorly scoped workaround weakens control-plane trust. ExplanationCorrect Answer B:Traffic leaks or becomes blackholed at the L2/L3 boundary. Associate the gateway with the intended routing and bridging contexts and inspect both tables. IRB traffic must bridge and route within an intentionally consistent service context. Incorrect Answers A:Excessive flooding consumes bandwidth and exposes traffic across unintended ports. This relates to a case where an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port; the current situation is that an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. C:Subscriber VLANs collide or customer traffic arrives in the wrong service. That relates to circumstances in which provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. Here the problem is that an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. D:Routing connectivity fails or a poorly scoped workaround weakens control-plane trust. This addresses a situation in which a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree; however, an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch.
Question 545At fictional Riverstone Networks 137, a regional service-provider network, during a core-routing acceptance test, operations observes: Two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Which targeted remediation best fits the reported behavior? Match the interface VLAN tagging mode to the customer handoff contract and test ingress frames. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. Correct permitted VLAN membership on both logical ports and validate MAC learning in the same broadcast domain. Use the approved source address and confirm matching outer-packet forwarding and policy. ExplanationCorrect Answer B:Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. Virtual switching can provide separate Layer 2 forwarding contexts for tenants. MAC learning and broadcast tests show separation of the two customers. Incorrect Answers A:Match the interface VLAN tagging mode to the customer handoff contract and test ingress frames. This could help if a provider access port drops customer tagged frames because it was configured for untagged access mode, but not when two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. C:Correct permitted VLAN membership on both logical ports and validate MAC learning in the same broadcast domain. It is useful for situations where hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier; the reported fault, though, is that two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. D:Use the approved source address and confirm matching outer-packet forwarding and policy. That relates to circumstances in which a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. Here the problem is that two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services.
Question 546At fictional Riverstone Networks 137, a regional service-provider network, during a core-routing acceptance test, operations observes: Two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Why is this particular correction the best fit for the stated defect? Trunk membership should reflect explicit service authorization, not an unrestricted default. An Ethernet port's VLAN tagging behavior must match the frames it receives. OSPF SPF computes least-cost paths using the advertised topology metrics. Virtual switching can provide separate Layer 2 forwarding contexts for tenants. ExplanationCorrect Answer D:Virtual switching can provide separate Layer 2 forwarding contexts for tenants. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. MAC learning and broadcast tests show separation of the two customers. Incorrect Answers A:Trunk membership should reflect explicit service authorization, not an unrestricted default. It is relevant if an interface permits every customer VLAN tag despite a contract listing only two approved VLANs, but the reported issue is that two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. 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 two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. C:OSPF SPF computes least-cost paths using the advertised topology metrics. This relates to a case where provider traffic takes a long backup path because OSPF interface costs were changed inconsistently; the current situation is that two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services.
Question 547At fictional Riverstone Networks 137, a regional service-provider network, during a core-routing acceptance test, operations observes: Two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. What direct observation would prove the corrective action worked? The MAC table shows each endpoint on the proper interface and known unicast flooding stops. MAC learning and broadcast tests show separation of the two customers. Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch. Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. ExplanationCorrect Answer B:MAC learning and broadcast tests show separation of the two customers. Virtual switching can provide separate Layer 2 forwarding contexts for tenants. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. Incorrect Answers A:The MAC table shows each endpoint on the proper interface and known unicast flooding stops. This is applicable when an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port; the present condition is that two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. C:Both client MACs appear in the intended VLAN and bidirectional frames traverse the switch. This could help if hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier, but not when two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. D:Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. This relates to a case where a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; the current situation is that two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services.
Question 548At fictional Riverstone Networks 137, a regional service-provider network, during a core-routing acceptance test, operations observes: Two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Which failure consequence follows most closely from ignoring this issue? Unnecessary filtering interrupts normal bridged service. Customer broadcasts and potentially sensitive frames cross service boundaries. Customer hosts appear connected yet cannot communicate. A provider domain becomes partitioned and service prefixes disappear. ExplanationCorrect Answer B:Customer broadcasts and potentially sensitive frames cross service boundaries. Virtual switching can provide separate Layer 2 forwarding contexts for tenants. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. Incorrect Answers A:Unnecessary filtering interrupts normal bridged service. That could help when a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop; here, two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. C:Customer hosts appear connected yet cannot communicate. It is relevant if hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier, but the reported issue is that two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. D:A provider domain becomes partitioned and service prefixes disappear. This could help if two adjacent core routers cannot establish IS-IS because one is configured only for Level 1 and the other only for Level 2, but not when two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services.
Question 549In a separate fictional JNCIS-SP lab review for Windmere Fiber 138, a carrier-edge and core routing team, following a monitored network change window, engineers find: Two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. What intervention most directly restores the intended routing or switching behavior? Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. Correct the QinQ service tag mapping and verify the inner customer tag remains intact. Constrain permitted VLAN membership and confirm unauthorized tag handling. Set deliberate interface priorities and confirm the DR and BDR roles after a controlled election. ExplanationCorrect Answer A:Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. MAC learning and broadcast tests show separation of the two customers. Virtual switching can provide separate Layer 2 forwarding contexts for tenants. Incorrect Answers B:Correct the QinQ service tag mapping and verify the inner customer tag remains intact. That could help when provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag; here, two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. C:Constrain permitted VLAN membership and confirm unauthorized tag handling. This is applicable when an interface permits every customer VLAN tag despite a contract listing only two approved VLANs; the present condition is that two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. 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 two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services.
Question 550In a separate fictional JNCIS-SP lab review for Windmere Fiber 138, a carrier-edge and core routing team, following a monitored network change window, engineers find: Two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Which networking principle explains why the proposed correction is appropriate? Unexpected MAC movement often points to changing Layer 2 forwarding topology. Customer VLAN IDs are not globally unique and require deliberate provider separation. Virtual switching can provide separate Layer 2 forwarding contexts for tenants. Generated routes depend on qualifying routes and their configured policy, not merely on a destination name. ExplanationCorrect Answer C:Virtual switching can provide separate Layer 2 forwarding contexts for tenants. MAC learning and broadcast tests show separation of the two customers. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. Incorrect Answers A:Unexpected MAC movement often points to changing Layer 2 forwarding topology. It addresses a different problem: A MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. Here, two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. B:Customer VLAN IDs are not globally unique and require deliberate provider separation. This could matter when two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. In this case, two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. D:Generated routes depend on qualifying routes and their configured policy, not merely on a destination name. This is applicable when a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; the present condition is that two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services.