Question 60At fictional Bluehaven Backbone 015, a regional service-provider network, during a preproduction design validation, operations observes: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. Which operational harm would persist without the intended correction? A false fix redirects a customer subnet onto an inappropriate aggregate route. Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. IBGP clients lack complete reachability and use inconsistent exits. A single uplink becomes overloaded while redundant capacity remains idle. ExplanationCorrect Answer D:A single uplink becomes overloaded while redundant capacity remains idle. Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. Incorrect Answers A:A false fix redirects a customer subnet onto an inappropriate aggregate route. The choice would be appropriate if an operator changes route preference to make a broader prefix override a healthy more-specific prefix. Here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. B:Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. That option concerns a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. The problem here is different: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. C:IBGP clients lack complete reachability and use inconsistent exits. It addresses a different problem: An internal client learns routes from another client only intermittently after the route-reflector peering address changes. Here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.
Question 61In a separate fictional JNCIS-SP lab review for Lakewood Carrier 016, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. What should the Junos specialist change first to resolve this specific fault? Check the generated route contribution and acceptance policy, then restore the intended eligible contributor. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. Correct the static next hop to a reachable transit address and confirm the selected route can resolve. Inspect BGP update history, peer flaps and policy events before changing transit selection. ExplanationCorrect Answer B:Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. Incorrect Answers A:Check the generated route contribution and acceptance policy, then restore the intended eligible contributor. This addresses a situation in which a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; however, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. C:Correct the static next hop to a reachable transit address and confirm the selected route can resolve. That option concerns a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. The problem here is different: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. D:Inspect BGP update history, peer flaps and policy events before changing transit selection. It addresses a different problem: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.
Question 62In a separate fictional JNCIS-SP lab review for Lakewood Carrier 016, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. What technical principle underlies the right remedy? Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. Route lookup and default selection occur within the configured routing-instance context. Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. An Ethernet port's VLAN tagging behavior must match the frames it receives. ExplanationCorrect Answer A:Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. Incorrect Answers B:Route lookup and default selection occur within the configured routing-instance context. This addresses a situation in which a route lookup for a management instance falls back to the global default, which the design prohibits; however, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. C:Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. The choice would be appropriate if an operator changes route preference to make a broader prefix override a healthy more-specific prefix. Here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. D:An Ethernet port's VLAN tagging behavior must match the frames it receives. That option concerns a provider access port drops customer tagged frames because it was configured for untagged access mode. The problem here is different: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.
Question 63In a separate fictional JNCIS-SP lab review for Lakewood Carrier 016, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. Which acceptance finding demonstrates the affected service has recovered? The interface unit is operational and the connected subnet appears in the correct routing table. The primary path stays selected normally and the backup is activated only when the primary is unavailable. A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. ExplanationCorrect Answer C:A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. Incorrect Answers A:The interface unit is operational and the connected subnet appears in the correct routing table. It is useful for situations where a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout; the reported fault, though, is that a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. B:The primary path stays selected normally and the backup is activated only when the primary is unavailable. That relates to circumstances in which a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. Here the problem is that a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. D:The tenant VLAN reaches only its intended IRB gateway and routing-instance routes. The choice would be appropriate if an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch. Here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.
Question 64In a separate fictional JNCIS-SP lab review for Lakewood Carrier 016, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. What is the direct residual network risk if the fault remains unresolved? Legitimate customer traffic is blackholed by an overbroad discard definition. Management packets leave via a customer-facing path or fail unexpectedly. Subscriber VLANs collide or customer traffic arrives in the wrong service. A single uplink becomes overloaded while redundant capacity remains idle. ExplanationCorrect Answer D:A single uplink becomes overloaded while redundant capacity remains idle. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. Incorrect Answers A:Legitimate customer traffic is blackholed by an overbroad discard definition. 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 a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. B:Management packets leave via a customer-facing path or fail unexpectedly. It is useful for situations where a route lookup for a management instance falls back to the global default, which the design prohibits; the reported fault, though, is that a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. 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 a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.
Question 65At fictional Summitfield Carrier 017, a regional service-provider network, during a core-routing acceptance test, operations observes: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Which targeted remediation best fits the reported behavior? Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. Compare protocol route state with the active route and forwarding-table next-hop installation. Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. ExplanationCorrect Answer D:Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Filter-based forwarding selects a routing lookup context based on packet classification. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. Incorrect Answers A:Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. 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 traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. B:Compare protocol route state with the active route and forwarding-table next-hop installation. This relates to a case where an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop; the current situation is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. C:Account for GRE and outer-IP overhead and implement a supported MTU or fragmentation strategy. It is useful for situations where large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU; the reported fault, though, is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup.
Question 66At fictional Summitfield Carrier 017, a regional service-provider network, during a core-routing acceptance test, operations observes: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Why is this particular correction the best fit for the stated defect? A RIB group permits specifically configured routes to be installed into additional routing tables. Martian route handling protects the routing table from addresses that should not be treated as normally reachable. Filter-based forwarding selects a routing lookup context based on packet classification. A calculated OSPF path is not a substitute for functional packet forwarding validation. ExplanationCorrect Answer C:Filter-based forwarding selects a routing lookup context based on packet classification. Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. 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 traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. B:Martian route handling protects the routing table from addresses that should not be treated as normally reachable. This could help if a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing, but not when a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. D:A calculated OSPF path is not a substitute for functional packet forwarding validation. It is useful for situations where an engineer sees an OSPF route in the routing table and closes the incident without testing the egress path; the reported fault, though, is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup.
Question 67At fictional Summitfield Carrier 017, a regional service-provider network, during a core-routing acceptance test, operations observes: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. What direct observation would prove the corrective action worked? The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. The circuit forms the expected point-to-point adjacency without an unwanted DR election. ExplanationCorrect Answer C:Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. Filter-based forwarding selects a routing lookup context based on packet classification. Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Incorrect Answers A:The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. This is applicable when a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it; the present condition is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. B:A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. It is relevant 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 the reported issue is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. D:The circuit forms the expected point-to-point adjacency without an unwanted DR election. This relates to a case where OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology; the current situation is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup.
Question 68At fictional Summitfield Carrier 017, a regional service-provider network, during a core-routing acceptance test, operations observes: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Which failure consequence follows most closely from ignoring this issue? Customers lose an intended default path even though the local route definition still exists. Packets to the customer prefix are dropped despite the static route statement being present. Sensitive application traffic bypasses the required upstream inspection or transit path. Packets cannot reach the intended next hop despite a syntactically valid address. ExplanationCorrect Answer C:Sensitive application traffic bypasses the required upstream inspection or transit path. Filter-based forwarding selects a routing lookup context based on packet classification. Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Incorrect Answers A:Customers lose an intended default path even though the local route definition still exists. That could help when a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; here, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. B:Packets to the customer prefix are dropped despite the static route statement being present. This is applicable when a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface; the present condition is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. D:Packets cannot reach the intended next hop despite a syntactically valid address. This could help if an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design, but not when a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup.
Question 69In a separate fictional JNCIS-SP lab review for Brightstone Backbone 018, a carrier-edge and core routing team, following a monitored network change window, engineers find: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. What intervention most directly restores the intended routing or switching behavior? Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Correct the RIB-group import/export table membership and verify only the intended route exchange. Set compatible network type and review adjacency expectations on both ends. Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. ExplanationCorrect Answer D:Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. Filter-based forwarding selects a routing lookup context based on packet classification. Incorrect Answers A:Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. This could matter when an operator changes route preference to make a broader prefix override a healthy more-specific prefix. In this case, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. B:Correct the RIB-group import/export table membership and verify only the intended route exchange. 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 traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. C:Set compatible network type and review adjacency expectations on both ends. This is applicable when OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology; the present condition is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup.
Question 70In a separate fictional JNCIS-SP lab review for Brightstone Backbone 018, a carrier-edge and core routing team, following a monitored network change window, engineers find: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Which networking principle explains why the proposed correction is appropriate? Filter-based forwarding selects a routing lookup context based on packet classification. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. Routing policy terms should match only their explicitly intended routes before altering route attributes. Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. ExplanationCorrect Answer A:Filter-based forwarding selects a routing lookup context based on packet classification. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. Correct the filter-based forwarding action and confirm the classification matches only the approved traffic. Incorrect Answers B:For otherwise comparable routes, Junos route preference influences which eligible route becomes active. This could matter when a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. In this case, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. C:Routing policy terms should match only their explicitly intended routes before altering route attributes. That could help when a broad routing policy term changes preference for all imported prefixes instead of only the intended test network; here, a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. D:Graceful Routing Engine switchover seeks to preserve forwarding state across a Routing Engine change. This is applicable when a planned Routing Engine switchover resets forwarding unexpectedly because chassis graceful switchover was not prepared; the present condition is that a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup.