Question 1At fictional Hillside Transit 001, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. Which targeted remediation best fits the reported behavior? Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Check the generated route contribution and acceptance policy, then restore the intended eligible contributor. Correct the static next hop to a reachable transit address and confirm the selected route can resolve. Review planned OSPF costs in both directions and correct the traffic-engineering values. ExplanationCorrect Answer C:Correct the static next hop to a reachable transit address and confirm the selected route can resolve. A configured static route forwards only after Junos can resolve its forwarding next hop. The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. Incorrect Answers A:Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. This addresses a situation in which a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup; however, a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. B:Check the generated route contribution and acceptance policy, then restore the intended eligible contributor. The choice would be appropriate if a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route. Here, a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. D:Review planned OSPF costs in both directions and correct the traffic-engineering values. It addresses a different problem: Provider traffic takes a long backup path because OSPF interface costs were changed inconsistently. Here, a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface.
Question 2At fictional Hillside Transit 001, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. Why is this particular correction the best fit for the stated defect? A configured static route forwards only after Junos can resolve its forwarding next hop. Martian route handling protects the routing table from addresses that should not be treated as normally reachable. Junos directly connected reachability depends on active logical interface configuration and state. BGP address-family negotiation determines which network-layer reachability data can be exchanged. ExplanationCorrect Answer A:A configured static route forwards only after Junos can resolve its forwarding next hop. Correct the static next hop to a reachable transit address and confirm the selected route can resolve. The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. Incorrect Answers B:Martian route handling protects the routing table from addresses that should not be treated as normally reachable. This addresses a situation in which a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing; however, a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. C:Junos directly connected reachability depends on active logical interface configuration and state. The choice would be appropriate if a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. Here, a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. D:BGP address-family negotiation determines which network-layer reachability data can be exchanged. That option concerns an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. The problem here is different: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface.
Question 3At fictional Hillside Transit 001, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. What direct observation would prove the corrective action worked? The route is active and the forwarding lookup shows an operational egress next hop. The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. The contributor is visible and the generated default returns with the expected forwarding next hop. The expected neighbor appears with stable hold time and correct interface state. ExplanationCorrect Answer B:The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. A configured static route forwards only after Junos can resolve its forwarding next hop. Correct the static next hop to a reachable transit address and confirm the selected route can resolve. Incorrect Answers A:The route is active and the forwarding lookup shows an operational egress next hop. It is useful for situations where an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop; the reported fault, though, is that a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. C:The contributor is visible and the generated default returns with the expected forwarding next hop. This addresses a situation in which a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; however, a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. D:The expected neighbor appears with stable hold time and correct interface state. The choice would be appropriate if an IS-IS neighbor remains down after an interface template disables its hello transmission. Here, a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface.
Question 4At fictional Hillside Transit 001, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. Which failure consequence follows most closely from ignoring this issue? Neighbor sessions cannot establish because the local link subnet is unreachable. Invalid or unintended address space can enter forwarding decisions and misdirect traffic. Packets to the customer prefix are dropped despite the static route statement being present. A route leak consumes routing resources and destabilizes production services. ExplanationCorrect Answer C:Packets to the customer prefix are dropped despite the static route statement being present. A configured static route forwards only after Junos can resolve its forwarding next hop. Correct the static next hop to a reachable transit address and confirm the selected route can resolve. Incorrect Answers A:Neighbor sessions cannot establish because the local link subnet is unreachable. This relates to a case where a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout; the current situation is that a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. B:Invalid or unintended address space can enter forwarding decisions and misdirect traffic. It is useful for situations where a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing; the reported fault, though, is that a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. D:A route leak consumes routing resources and destabilizes production services. This addresses a situation in which a misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale; however, a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface.
Question 5In a separate fictional JNCIS-SP lab review for Westbridge Exchange 002, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. What intervention most directly restores the intended routing or switching behavior? Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Correct the RIB-group import/export table membership and verify only the intended route exchange. Correct the static next hop to a reachable transit address and confirm the selected route can resolve. Inspect database-exchange state and repair the adjacency rather than editing unrelated route preferences. ExplanationCorrect Answer C:Correct the static next hop to a reachable transit address and confirm the selected route can resolve. The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. A configured static route forwards only after Junos can resolve its forwarding next hop. Incorrect Answers A:Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. This could help if a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup, but not when a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. B:Correct the RIB-group import/export table membership and verify only the intended route exchange. This relates to a case where a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table; the current situation is that a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. D:Inspect database-exchange state and repair the adjacency rather than editing unrelated route preferences. That relates to circumstances in which two supposed adjacent routers have different views of a backbone link because database synchronization never completes. Here the problem is that a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface.
Question 6In a separate fictional JNCIS-SP lab review for Westbridge Exchange 002, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. Which networking principle explains why the proposed correction is appropriate? A RIB group permits specifically configured routes to be installed into additional routing tables. Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. Customer VLAN IDs are not globally unique and require deliberate provider separation. A configured static route forwards only after Junos can resolve its forwarding next hop. ExplanationCorrect Answer D:A configured static route forwards only after Junos can resolve its forwarding next hop. The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. Correct the static next hop to a reachable transit address and confirm the selected route can resolve. Incorrect Answers A:A RIB group permits specifically configured routes to be installed into additional routing tables. It is relevant if a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table, but the reported issue is that a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. B:Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. This could help if a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed, but not when a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. 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 a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface.
Question 7In a separate fictional JNCIS-SP lab review for Westbridge Exchange 002, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. Which validation result would confirm the design is now functioning? The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. The target table contains the approved route while unrelated tenant tables remain unchanged. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. An injected test BPDU triggers the documented protection while legitimate access ports behave normally. ExplanationCorrect Answer A:The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. Correct the static next hop to a reachable transit address and confirm the selected route can resolve. A configured static route forwards only after Junos can resolve its forwarding next hop. Incorrect Answers B:The target table contains the approved route while unrelated tenant tables remain unchanged. It is relevant if a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table, but the reported issue is that a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. C:The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. This could help if a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it, but not when a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. D:An injected test BPDU triggers the documented protection while legitimate access ports behave normally. This relates to a case where a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only; the current situation is that a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface.
Question 8In a separate fictional JNCIS-SP lab review for Westbridge Exchange 002, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. What likely service impact does this condition create? The monitoring function loses required reachability or isolation is weakened by broad route copying. A single uplink becomes overloaded while redundant capacity remains idle. Packets to the customer prefix are dropped despite the static route statement being present. Traffic between access area and core is silently blackholed. ExplanationCorrect Answer C:Packets to the customer prefix are dropped despite the static route statement being present. Correct the static next hop to a reachable transit address and confirm the selected route can resolve. A configured static route forwards only after Junos can resolve its forwarding next hop. Incorrect Answers A:The monitoring function loses required reachability or isolation is weakened by broad route copying. That could help when a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table; here, a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. B:A single uplink becomes overloaded while redundant capacity remains idle. This is applicable when a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed; the present condition is that a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. D:Traffic between access area and core is silently blackholed. This could help if an L1-only site lacks an approved route to reach destinations in the backbone after a level-transition change, but not when a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface.
Question 9At fictional Crestland Networks 003, a regional service-provider network, during a two-site transit migration, operations observes: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. Which configuration or operational correction most directly addresses this failure? Inspect the aggregate route contributors and align the summary with the intended component prefixes. Restore the intended interface unit and address family, then validate connected route installation. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. Associate the gateway with the intended routing and bridging contexts and inspect both tables. ExplanationCorrect Answer C:Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. The primary path stays selected normally and the backup is activated only when the primary is unavailable. Incorrect Answers A:Inspect the aggregate route contributors and align the summary with the intended component prefixes. This could matter when a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. In this case, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. B:Restore the intended interface unit and address family, then validate connected route installation. That could help when a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout; here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. D:Associate the gateway with the intended routing and bridging contexts and inspect both tables. 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 a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low.
Question 10At fictional Crestland Networks 003, a regional service-provider network, during a two-site transit migration, operations observes: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. Which Junos forwarding or control-plane rule applies to this case? Filter-based forwarding selects a routing lookup context based on packet classification. Route lookup and default selection occur within the configured routing-instance context. RSVP-TE can establish signaled LSPs subject to configured path constraints. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. ExplanationCorrect Answer D:For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. The primary path stays selected normally and the backup is activated only when the primary is unavailable. Incorrect Answers A:Filter-based forwarding selects a routing lookup context based on packet classification. It addresses a different problem: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. B:Route lookup and default selection occur within the configured routing-instance context. This could matter when a route lookup for a management instance falls back to the global default, which the design prohibits. In this case, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. C:RSVP-TE can establish signaled LSPs subject to configured path constraints. That could help when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route; here, a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low.