Question 900At fictional Glenwood Connectivity 225, a regional service-provider network, during a preproduction design validation, operations observes: A GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. Which failure consequence follows most closely from ignoring this issue? GRE packets are discarded by a transit filter despite valid inner routes. A hidden encapsulation or decapsulation fault persists behind a green interface alarm. Overlay routes remain configured but customer packets never reach the remote site. Policy and reachability behavior is distorted by a false external session. ExplanationCorrect Answer A:GRE packets are discarded by a transit filter despite valid inner routes. Tunnel endpoints must use source and destination addresses that the underlay can route and permit. Use the approved source address and confirm matching outer-packet forwarding and policy. Incorrect Answers B:A hidden encapsulation or decapsulation fault persists behind a green interface alarm. That option concerns monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. The problem here is different: A GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. C:Overlay routes remain configured but customer packets never reach the remote site. It addresses a different problem: A configured GRE tunnel stays unusable after the remote outer IP endpoint changes. Here, a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. D:Policy and reachability behavior is distorted by a false external session. This could matter when an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary. In this case, a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL.
Question 901In a separate fictional JNCIS-SP lab review for Hillside Transit 226, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. What intervention most directly restores the intended routing or switching behavior? Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. Update the tunnel endpoint and restore underlying IP reachability before testing overlay traffic. Use the approved source address and confirm matching outer-packet forwarding and policy. Apply the supported LDP and IGP synchronization design and verify staged activation. ExplanationCorrect Answer C:Use the approved source address and confirm matching outer-packet forwarding and policy. A capture shows outer packets with the approved source and destination and working return traffic. Tunnel endpoints must use source and destination addresses that the underlay can route and permit. Incorrect Answers A:Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. This addresses a situation in which large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU; however, a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. B:Update the tunnel endpoint and restore underlying IP reachability before testing overlay traffic. The choice would be appropriate if a configured GRE tunnel stays unusable after the remote outer IP endpoint changes. Here, a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. D:Apply the supported LDP and IGP synchronization design and verify staged activation. It addresses a different problem: A new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. Here, a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL.
Question 902In a separate fictional JNCIS-SP lab review for Hillside Transit 226, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. Which networking principle explains why the proposed correction is appropriate? Tunnel endpoints must use source and destination addresses that the underlay can route and permit. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. Adding a GRE outer header reduces the effective payload MTU available to the inner packet. Encapsulation adds frame overhead that must fit along the Layer 2 service path. ExplanationCorrect Answer A:Tunnel endpoints must use source and destination addresses that the underlay can route and permit. A capture shows outer packets with the approved source and destination and working return traffic. Use the approved source address and confirm matching outer-packet forwarding and policy. Incorrect Answers B:Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. This addresses a situation in which monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered; however, a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. C:Adding a GRE outer header reduces the effective payload MTU available to the inner packet. The choice would be appropriate if large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. Here, a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. D:Encapsulation adds frame overhead that must fit along the Layer 2 service path. That option concerns a service-provider QinQ link carries small frames but drops customer frames when the extra VLAN header exceeds the link MTU. The problem here is different: A GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL.
Question 903In a separate fictional JNCIS-SP lab review for Hillside Transit 226, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. Which validation result would confirm the design is now functioning? Outer reachability and an encapsulated test both succeed over the tunnel. Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service. The target loopback FEC has a valid binding and corresponding programmed label action. A capture shows outer packets with the approved source and destination and working return traffic. ExplanationCorrect Answer D:A capture shows outer packets with the approved source and destination and working return traffic. Use the approved source address and confirm matching outer-packet forwarding and policy. Tunnel endpoints must use source and destination addresses that the underlay can route and permit. Incorrect Answers A:Outer reachability and an encapsulated test both succeed over the tunnel. It is useful for situations where a configured GRE tunnel stays unusable after the remote outer IP endpoint changes; the reported fault, though, is that a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. B:Counters advance at both tunnel endpoints and a sample inner packet reaches the remote service. That relates to circumstances in which monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. Here the problem is that a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. C:The target loopback FEC has a valid binding and corresponding programmed label action. This addresses a situation in which monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback; however, a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL.
Question 904In a separate fictional JNCIS-SP lab review for Hillside Transit 226, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. What likely service impact does this condition create? Overlay routes remain configured but customer packets never reach the remote site. GRE packets are discarded by a transit filter despite valid inner routes. A hidden encapsulation or decapsulation fault persists behind a green interface alarm. A nominally redundant network fails its practical customer continuity requirement. ExplanationCorrect Answer B:GRE packets are discarded by a transit filter despite valid inner routes. Use the approved source address and confirm matching outer-packet forwarding and policy. Tunnel endpoints must use source and destination addresses that the underlay can route and permit. Incorrect Answers A:Overlay routes remain configured but customer packets never reach the remote site. This relates to a case where a configured GRE tunnel stays unusable after the remote outer IP endpoint changes; the current situation is that a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. C:A hidden encapsulation or decapsulation fault persists behind a green interface alarm. That relates to circumstances in which monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. Here the problem is that a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL. D:A nominally redundant network fails its practical customer continuity requirement. This addresses a situation in which an availability test is signed off because BFD and VRRP report healthy, but customer packets still drop during failover; however, a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL.
Question 905At fictional Westbridge Exchange 227, a regional service-provider network, during a core-routing acceptance test, operations observes: Large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. Which configuration or operational correction most directly addresses this failure? Update the tunnel endpoint and restore underlying IP reachability before testing overlay traffic. Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. Use the approved source address and confirm matching outer-packet forwarding and policy. Adopt the supported rapid spanning-tree configuration consistently and validate role transitions. ExplanationCorrect Answer B:Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. Adding a GRE outer header reduces the effective payload MTU available to the inner packet. Representative large overlay packets cross the complete GRE path without loss. Incorrect Answers A:Update the tunnel endpoint and restore underlying IP reachability before testing overlay traffic. This could help if a configured GRE tunnel stays unusable after the remote outer IP endpoint changes, but not when large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. C:Use the approved source address and confirm matching outer-packet forwarding and policy. It is useful for situations where a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL; the reported fault, though, is that large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. D:Adopt the supported rapid spanning-tree configuration consistently and validate role transitions. That relates to circumstances in which a redundant access network takes far too long to recover from a link failure because it uses inappropriate legacy STP behavior. Here the problem is that large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU.
Question 906At fictional Westbridge Exchange 227, a regional service-provider network, during a core-routing acceptance test, operations observes: Large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. Which Junos forwarding or control-plane rule applies to this case? GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. Tunnel endpoints must use source and destination addresses that the underlay can route and permit. Adding a GRE outer header reduces the effective payload MTU available to the inner packet. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. ExplanationCorrect Answer C:Adding a GRE outer header reduces the effective payload MTU available to the inner packet. Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. Representative large overlay packets cross the complete GRE path without loss. Incorrect Answers A:GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. It is relevant if a configured GRE tunnel stays unusable after the remote outer IP endpoint changes, but the reported issue is that large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. B:Tunnel endpoints must use source and destination addresses that the underlay can route and permit. This could help if a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL, but not when large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. D:MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. It is useful for situations where operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header; the reported fault, though, is that large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU.
Question 907At fictional Westbridge Exchange 227, a regional service-provider network, during a core-routing acceptance test, operations observes: Large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. What operational evidence best establishes successful remediation? The outer endpoint routes through the physical transit and tunnel probes succeed without recursion. A capture shows outer packets with the approved source and destination and working return traffic. Representative large overlay packets cross the complete GRE path without loss. The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. ExplanationCorrect Answer C:Representative large overlay packets cross the complete GRE path without loss. Adding a GRE outer header reduces the effective payload MTU available to the inner packet. Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. Incorrect Answers A:The outer endpoint routes through the physical transit and tunnel probes succeed without recursion. This is applicable when a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution; the present condition is that large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. B:A capture shows outer packets with the approved source and destination and working return traffic. It is relevant if a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL, but the reported issue is that large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. D:The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. 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 large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU.
Question 908At fictional Westbridge Exchange 227, a regional service-provider network, during a core-routing acceptance test, operations observes: Large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. Which operational harm would persist without the intended correction? GRE packets are discarded by a transit filter despite valid inner routes. Overlay routes remain configured but customer packets never reach the remote site. Packets to the customer prefix are dropped despite the static route statement being present. Applications suffer selective stalls and retransmissions. ExplanationCorrect Answer D:Applications suffer selective stalls and retransmissions. Adding a GRE outer header reduces the effective payload MTU available to the inner packet. Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. Incorrect Answers A:GRE packets are discarded by a transit filter despite valid inner routes. That could help when a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL; here, large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. B:Overlay routes remain configured but customer packets never reach the remote site. This is applicable when a configured GRE tunnel stays unusable after the remote outer IP endpoint changes; the present condition is that large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. C:Packets to the customer prefix are dropped despite the static route statement being present. It is relevant if a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface, but the reported issue is that large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU.
Question 909In a separate fictional JNCIS-SP lab review for Crestland Networks 228, a carrier-edge and core routing team, following a monitored network change window, engineers find: Large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. What should the Junos specialist change first to resolve this specific fault? Update the tunnel endpoint and restore underlying IP reachability before testing overlay traffic. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. Check label advertisements for the FEC and restore a valid LDP downstream binding. Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. ExplanationCorrect Answer D:Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. Representative large overlay packets cross the complete GRE path without loss. Adding a GRE outer header reduces the effective payload MTU available to the inner packet. Incorrect Answers A:Update the tunnel endpoint and restore underlying IP reachability before testing overlay traffic. This could matter when a configured GRE tunnel stays unusable after the remote outer IP endpoint changes. In this case, large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. B:Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. That could help when monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered; here, large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. C:Check label advertisements for the FEC and restore a valid LDP downstream binding. This is applicable when an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop; the present condition is that large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU.
Question 910In a separate fictional JNCIS-SP lab review for Crestland Networks 228, a carrier-edge and core routing team, following a monitored network change window, engineers find: Large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. What technical principle underlies the right remedy? GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Adding a GRE outer header reduces the effective payload MTU available to the inner packet. ExplanationCorrect Answer D:Adding a GRE outer header reduces the effective payload MTU available to the inner packet. Representative large overlay packets cross the complete GRE path without loss. Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. Incorrect Answers A:GRE encapsulates inner packets in outer IP packets that must reach the remote tunnel endpoint. It addresses a different problem: A configured GRE tunnel stays unusable after the remote outer IP endpoint changes. Here, large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. B:Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. This could matter when monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. In this case, large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU. C:For otherwise comparable routes, Junos route preference influences which eligible route becomes active. That could help when a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low; here, large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU.