Question 560In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 140, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU. What is the direct residual network risk if the fault remains unresolved? Traffic follows an obsolete service path or reaches the wrong customer site. Large customer frames fail selectively and create difficult-to-reproduce application problems. Unnecessary route changes mask a switching defect and prolong the outage. IBGP clients lack complete reachability and use inconsistent exits. ExplanationCorrect Answer B:Large customer frames fail selectively and create difficult-to-reproduce application problems. Reconcile path MTU with the encapsulation overhead and test representative maximum frames. Encapsulation adds frame overhead that must fit along the Layer 2 service path. Incorrect Answers A:Traffic follows an obsolete service path or reaches the wrong customer site. That could help when a MAC is learned on an unexpected aggregation interface following a customer circuit move; here, a service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU. C:Unnecessary route changes mask a switching defect and prolong the outage. It is relevant if an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown, but the reported issue is that a service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU. D:IBGP clients lack complete reachability and use inconsistent exits. This could help if an internal client learns routes from another client only intermittently after the route-reflector peering address changes, but not when a service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU.
Question 561At fictional Lakewood Carrier 141, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Which targeted remediation best fits the reported behavior? Correct the QinQ service tag mapping and verify the inner customer tag remains intact. Correct permitted VLAN membership on both logical ports and validate MAC learning in the same broadcast domain. Constrain permitted VLAN membership and confirm unauthorized tag handling. Check transit MPLS forwarding state and repair the missing label operation. ExplanationCorrect Answer C:Constrain permitted VLAN membership and confirm unauthorized tag handling. Trunk membership should reflect explicit service authorization, not an unrestricted default. Only the two contracted VLANs are forwarded and other tags are isolated. Incorrect Answers A:Correct the QinQ service tag mapping and verify the inner customer tag remains intact. This could matter when provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag. In this case, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. 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, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. D:Check transit MPLS forwarding state and repair the missing label operation. It is relevant if an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing, but the reported issue is that an interface permits every customer VLAN tag despite a contract listing only two approved VLANs.
Question 562At fictional Lakewood Carrier 141, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Why is this particular correction the best fit for the stated defect? Trunk membership should reflect explicit service authorization, not an unrestricted default. Layer 2 switching forwards traffic within the configured VLAN bridge domain. Customer VLAN IDs are not globally unique and require deliberate provider separation. Penultimate-hop popping can remove the outer transport label before the final LSR. ExplanationCorrect Answer A:Trunk membership should reflect explicit service authorization, not an unrestricted default. Constrain permitted VLAN membership and confirm unauthorized tag handling. Only the two contracted VLANs are forwarded and other tags are isolated. Incorrect Answers B:Layer 2 switching forwards traffic within the configured VLAN bridge domain. This could matter when hosts connected through a service-provider switch cannot exchange traffic because each port references a different VLAN identifier. In this case, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. C:Customer VLAN IDs are not globally unique and require deliberate provider separation. 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 interface permits every customer VLAN tag despite a contract listing only two approved VLANs. D:Penultimate-hop popping can remove the outer transport label before the final LSR. This is applicable when an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP; the present condition is that an interface permits every customer VLAN tag despite a contract listing only two approved VLANs.
Question 563At fictional Lakewood Carrier 141, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. What direct observation would prove the corrective action worked? Only the two contracted VLANs are forwarded and other tags are isolated. MAC entries stabilize on the intended interface after repairing the bridge path. MAC learning and broadcast tests show separation of the two customers. Both endpoints reach the expected adjacency state and share matching area membership. ExplanationCorrect Answer A:Only the two contracted VLANs are forwarded and other tags are isolated. Trunk membership should reflect explicit service authorization, not an unrestricted default. Constrain permitted VLAN membership and confirm unauthorized tag handling. Incorrect Answers B:MAC entries stabilize on the intended interface after repairing the bridge path. 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, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. C:MAC learning and broadcast tests show separation of the two customers. This could matter when two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. In this case, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. D:Both endpoints reach the expected adjacency state and share matching area membership. That could help when two provider routers on a point-to-point circuit cannot form an OSPF adjacency because their interfaces use different area IDs; here, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs.
Question 564At fictional Lakewood Carrier 141, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Which failure consequence follows most closely from ignoring this issue? Repeated flooding and customer frame loss continue despite healthy routes. Customers can inject unapproved Layer 2 traffic into the provider bridge. Excessive flooding consumes bandwidth and exposes traffic across unintended ports. Traffic engineering intent fails despite the community being visible. ExplanationCorrect Answer B:Customers can inject unapproved Layer 2 traffic into the provider bridge. Trunk membership should reflect explicit service authorization, not an unrestricted default. Constrain permitted VLAN membership and confirm unauthorized tag handling. Incorrect Answers A:Repeated flooding and customer frame loss continue despite healthy routes. The choice would be appropriate if a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. Here, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. C:Excessive flooding consumes bandwidth and exposes traffic across unintended ports. It addresses a different problem: An edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. Here, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. D:Traffic engineering intent fails despite the community being visible. This could matter when an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. In this case, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs.
Question 565In a separate fictional JNCIS-SP lab review for Summitfield Carrier 142, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. What intervention most directly restores the intended routing or switching behavior? Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. Match the interface VLAN tagging mode to the customer handoff contract and test ingress frames. Recalculate the supported reservation and link bandwidth design before retrying. Constrain permitted VLAN membership and confirm unauthorized tag handling. ExplanationCorrect Answer D:Constrain permitted VLAN membership and confirm unauthorized tag handling. Only the two contracted VLANs are forwarded and other tags are isolated. Trunk membership should reflect explicit service authorization, not an unrestricted default. Incorrect Answers A:Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. This addresses a situation in which two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services; however, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. B:Match the interface VLAN tagging mode to the customer handoff contract and test ingress frames. The choice would be appropriate if a provider access port drops customer tagged frames because it was configured for untagged access mode. Here, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. C:Recalculate the supported reservation and link bandwidth design before retrying. 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 interface permits every customer VLAN tag despite a contract listing only two approved VLANs.
Question 566In a separate fictional JNCIS-SP lab review for Summitfield Carrier 142, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Which networking principle explains why the proposed correction is appropriate? Virtual switching can provide separate Layer 2 forwarding contexts for tenants. Provider bridging can add an outer service VLAN tag while retaining customer VLAN identity. BGP depends on working IP transport to establish its TCP session. Trunk membership should reflect explicit service authorization, not an unrestricted default. ExplanationCorrect Answer D:Trunk membership should reflect explicit service authorization, not an unrestricted default. Only the two contracted VLANs are forwarded and other tags are isolated. Constrain permitted VLAN membership and confirm unauthorized tag handling. Incorrect Answers A:Virtual switching can provide separate Layer 2 forwarding contexts for tenants. 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 an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. 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, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. C:BGP depends on working IP transport to establish its TCP session. The choice would be appropriate if a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable. Here, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs.
Question 567In a separate fictional JNCIS-SP lab review for Summitfield Carrier 142, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. Which validation result would confirm the design is now functioning? Only the two contracted VLANs are forwarded and other tags are isolated. Local hosts reach the IRB gateway and authorized routed subnets beyond it. MAC entries stabilize on the intended interface after repairing the bridge path. Each tenant's route lookup uses its own instance table and reaches only authorized customer next hops. ExplanationCorrect Answer A:Only the two contracted VLANs are forwarded and other tags are isolated. Constrain permitted VLAN membership and confirm unauthorized tag handling. Trunk membership should reflect explicit service authorization, not an unrestricted default. Incorrect Answers B:Local hosts reach the IRB gateway and authorized routed subnets beyond it. That relates to circumstances in which customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent. Here the problem is that an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. C:MAC entries stabilize on the intended interface after repairing the bridge path. This addresses a situation in which a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables; however, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. D:Each tenant's route lookup uses its own instance table and reaches only authorized customer next hops. The choice would be appropriate if customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table. Here, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs.
Question 568In a separate fictional JNCIS-SP lab review for Summitfield Carrier 142, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An interface permits every customer VLAN tag despite a contract listing only two approved VLANs. What likely service impact does this condition create? Traffic leaks or becomes blackholed at the L2/L3 boundary. Customers can inject unapproved Layer 2 traffic into the provider bridge. Excessive flooding consumes bandwidth and exposes traffic across unintended ports. Unrelated subscribers change transit paths after a narrowly intended policy update. ExplanationCorrect Answer B:Customers can inject unapproved Layer 2 traffic into the provider bridge. Constrain permitted VLAN membership and confirm unauthorized tag handling. Trunk membership should reflect explicit service authorization, not an unrestricted default. Incorrect Answers A:Traffic leaks or becomes blackholed at the L2/L3 boundary. This relates to a case where an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch; the current situation is that an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. C:Excessive flooding consumes bandwidth and exposes traffic across unintended ports. 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 an interface permits every customer VLAN tag despite a contract listing only two approved VLANs. D:Unrelated subscribers change transit paths after a narrowly intended policy update. This addresses a situation in which a broad routing policy term changes preference for all imported prefixes instead of only the intended test network; however, an interface permits every customer VLAN tag despite a contract listing only two approved VLANs.
Question 569At fictional Brightstone Backbone 143, a regional service-provider network, during a two-site transit migration, operations observes: An operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. Which configuration or operational correction most directly addresses this failure? Associate the gateway with the intended routing and bridging contexts and inspect both tables. Investigate Ethernet MAC learning and bridge-table forwarding before changing IP routing. Trace member interface and bridge-domain association, then correct the service attachment. Configure the supported IPv6 IS-IS family and confirm prefix reachability at intended levels. ExplanationCorrect Answer B:Investigate Ethernet MAC learning and bridge-table forwarding before changing IP routing. Layer 2 bridges select egress ports using MAC/VLAN information before any routed-hop lookup. The bridge table resolves the destination MAC to the correct egress port. 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 an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. C:Trace member interface and bridge-domain association, then correct the service attachment. It is useful for situations where a MAC is learned on an unexpected aggregation interface following a customer circuit move; the reported fault, though, is that an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. D:Configure the supported IPv6 IS-IS family and confirm prefix reachability at intended levels. That relates to circumstances in which an IPv6 service prefix is missing from an IS-IS network because the necessary topology and family capability were not enabled. Here the problem is that an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown.
Question 570At fictional Brightstone Backbone 143, a regional service-provider network, during a two-site transit migration, operations observes: An operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. Which Junos forwarding or control-plane rule applies to this case? IRB traffic must bridge and route within an intentionally consistent service context. Unexpected MAC movement often points to changing Layer 2 forwarding topology. Layer 2 bridges select egress ports using MAC/VLAN information before any routed-hop lookup. A route's presence is insufficient if its selected MPLS transport next hop is unusable. ExplanationCorrect Answer C:Layer 2 bridges select egress ports using MAC/VLAN information before any routed-hop lookup. Investigate Ethernet MAC learning and bridge-table forwarding before changing IP routing. The bridge table resolves the destination MAC to the correct egress port. Incorrect Answers A:IRB traffic must bridge and route within an intentionally consistent service context. It is relevant if an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch, but the reported issue is that an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. B:Unexpected MAC movement often points to changing Layer 2 forwarding topology. This could help if a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables, but not when an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. D:A route's presence is insufficient if its selected MPLS transport next hop is unusable. It is useful for situations where a service path references an LSP that is down, but its IP route remains visible in the route table; the reported fault, though, is that an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown.