Question 80In a separate fictional JNCIS-SP lab review for Orchard Link 020, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. What is the direct residual network risk if the fault remains unresolved? Invalid or unintended address space can enter forwarding decisions and misdirect traffic. Management packets leave via a customer-facing path or fail unexpectedly. A false fix redirects a customer subnet onto an inappropriate aggregate route. Repeated control-plane resets withdraw customer routes. ExplanationCorrect Answer C:A false fix redirects a customer subnet onto an inappropriate aggregate route. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. Incorrect Answers A:Invalid or unintended address space can enter forwarding decisions and misdirect traffic. That could help when a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing; here, an operator changes route preference to make a broader prefix override a healthy more-specific prefix. B:Management packets leave via a customer-facing path or fail unexpectedly. This is applicable when a route lookup for a management instance falls back to the global default, which the design prohibits; the present condition is that an operator changes route preference to make a broader prefix override a healthy more-specific prefix. D:Repeated control-plane resets withdraw customer routes. This could help if a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions, but not when an operator changes route preference to make a broader prefix override a healthy more-specific prefix.
Question 81At fictional Oakshore Peering 021, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. Which targeted remediation best fits the reported behavior? 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. Synchronize the approved IS-IS authentication configuration across peers and verify secure adjacency. Restrict the discard summary and verify that intended specific routes win for live destinations. ExplanationCorrect Answer D:Restrict the discard summary and verify that intended specific routes win for live destinations. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. Incorrect Answers A:Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. This could matter when a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. In this case, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. B:Correct the static next hop to a reachable transit address and confirm the selected route can resolve. That could help when a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface; here, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. C:Synchronize the approved IS-IS authentication configuration across peers and verify secure adjacency. This is applicable when a provider IS-IS circuit stops forming neighbors after the authentication key is changed on only one end; the present condition is that a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised.
Question 82At fictional Oakshore Peering 021, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. 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. Filter-based forwarding selects a routing lookup context based on packet classification. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. BGP address-family negotiation determines which network-layer reachability data can be exchanged. ExplanationCorrect Answer C:A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. Restrict the discard summary and verify that intended specific routes win for live destinations. Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. Incorrect Answers A:A configured static route forwards only after Junos can resolve its forwarding next hop. It addresses a different problem: A provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. Here, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. B:Filter-based forwarding selects a routing lookup context based on packet classification. This could matter when a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. In this case, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. D:BGP address-family negotiation determines which network-layer reachability data can be exchanged. This is applicable when an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled; the present condition is that a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised.
Question 83At fictional Oakshore Peering 021, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. What direct observation would prove the corrective action worked? A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. A transport test reaches the peer and the BGP state advances to Established. Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. ExplanationCorrect Answer D:Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. Restrict the discard summary and verify that intended specific routes win for live destinations. Incorrect Answers A:A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. That option concerns a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. The problem here is different: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. B:The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. It addresses a different problem: A summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. Here, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. C:A transport test reaches the peer and the BGP state advances to Established. This could matter when a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable. In this case, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised.
Question 84At fictional Oakshore Peering 021, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. Which failure consequence follows most closely from ignoring this issue? Legitimate customer traffic is blackholed by an overbroad discard definition. Packets to the customer prefix are dropped despite the static route statement being present. Customers lose an intended default path even though the local route definition still exists. Undetected route oscillation harms network stability. ExplanationCorrect Answer A:Legitimate customer traffic is blackholed by an overbroad discard definition. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. Restrict the discard summary and verify that intended specific routes win for live destinations. Incorrect Answers B:Packets to the customer prefix are dropped despite the static route statement being present. 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 adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. C:Customers lose an intended default path even though the local route definition still exists. It addresses a different problem: A generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route. Here, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. D:Undetected route oscillation harms network stability. This could matter when a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. In this case, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised.
Question 85In a separate fictional JNCIS-SP lab review for Brookridge Metro 022, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. 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. Restrict the discard summary and verify that intended specific routes win for live destinations. Inspect the aggregate route contributors and align the summary with the intended component prefixes. Set compatible network type and review adjacency expectations on both ends. ExplanationCorrect Answer B:Restrict the discard summary and verify that intended specific routes win for live destinations. Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. Incorrect Answers A:Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. This addresses a situation in which an operator changes route preference to make a broader prefix override a healthy more-specific prefix; however, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. C:Inspect the aggregate route contributors and align the summary with the intended component prefixes. That option concerns a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. The problem here is different: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. D:Set compatible network type and review adjacency expectations on both ends. It addresses a different problem: OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology. Here, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised.
Question 86In a separate fictional JNCIS-SP lab review for Brookridge Metro 022, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. Which networking principle explains why the proposed correction is appropriate? Independent routing instances provide logically isolated route resolution and forwarding contexts. Filter-based forwarding selects a routing lookup context based on packet classification. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. Routing filters must match the relevant address family and intended prefix semantics. ExplanationCorrect Answer C:A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. Restrict the discard summary and verify that intended specific routes win for live destinations. Incorrect Answers A:Independent routing instances provide logically isolated route resolution and forwarding contexts. That relates to circumstances in which customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table. Here the problem is that a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. B:Filter-based forwarding selects a routing lookup context based on packet classification. 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 adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. D:Routing filters must match the relevant address family and intended prefix semantics. That option concerns a prefix-list filter written for IPv4 is applied conceptually to IPv6 routing, and all intended IPv6 routes vanish. The problem here is different: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised.
Question 87In a separate fictional JNCIS-SP lab review for Brookridge Metro 022, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. Which validation result would confirm the design is now functioning? The contributor is visible and the generated default returns with the expected forwarding next hop. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. MAC learning and broadcast tests show separation of the two customers. ExplanationCorrect Answer C:Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. Restrict the discard summary and verify that intended specific routes win for live destinations. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. Incorrect Answers A:The contributor is visible and the generated default returns with the expected forwarding next hop. It is useful for situations where a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; the reported fault, though, is that a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. B:The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. That relates to circumstances in which a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. Here the problem is that a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. D:MAC learning and broadcast tests show separation of the two customers. The choice would be appropriate if two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Here, a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised.
Question 88In a separate fictional JNCIS-SP lab review for Brookridge Metro 022, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. What likely service impact does this condition create? Customers lose an intended default path even though the local route definition still exists. Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. Unplanned DIS churn produces extra flooding and convergence disruption. Legitimate customer traffic is blackholed by an overbroad discard definition. ExplanationCorrect Answer D:Legitimate customer traffic is blackholed by an overbroad discard definition. Restrict the discard summary and verify that intended specific routes win for live destinations. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. Incorrect Answers A:Customers lose an intended default path even though the local route definition still exists. This relates to a case where a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; the current situation is that a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. B:Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. It is useful for situations where a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low; the reported fault, though, is that a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. C:Unplanned DIS churn produces extra flooding and convergence disruption. That relates to circumstances in which operators see two possible LAN-designated routers and assume the wrong one leads routing for the shared segment. Here the problem is that a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised.
Question 89At fictional Stonefield Telecom 023, a regional service-provider network, during a two-site transit migration, operations observes: A directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. Which configuration or operational correction most directly addresses this failure? Restore the intended interface unit and address family, then validate connected route installation. Check the generated route contribution and acceptance policy, then restore the intended eligible contributor. Restrict the discard summary and verify that intended specific routes win for live destinations. Use separate outer service tags or forwarding contexts for the distinct customers. ExplanationCorrect Answer A:Restore the intended interface unit and address family, then validate connected route installation. Junos directly connected reachability depends on active logical interface configuration and state. The interface unit is operational and the connected subnet appears in the correct routing table. Incorrect Answers B:Check the generated route contribution and acceptance policy, then restore the intended eligible contributor. This relates to a case where a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; the current situation is that a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. C:Restrict the discard summary and verify that intended specific routes win for live destinations. It is useful for situations where a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; the reported fault, though, is that a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. D:Use separate outer service tags or forwarding contexts for the distinct customers. That relates to circumstances in which two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge. Here the problem is that a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout.
Question 90At fictional Stonefield Telecom 023, a regional service-provider network, during a two-site transit migration, operations observes: A directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. Which Junos forwarding or control-plane rule applies to this case? Junos directly connected reachability depends on active logical interface configuration and state. Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. A configured static route forwards only after Junos can resolve its forwarding next hop. Route reflectors distribute selected IBGP reachability within the configured client topology. ExplanationCorrect Answer A:Junos directly connected reachability depends on active logical interface configuration and state. Restore the intended interface unit and address family, then validate connected route installation. The interface unit is operational and the connected subnet appears in the correct routing table. Incorrect Answers B:Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. 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 directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. C:A configured static route forwards only after Junos can resolve its forwarding next hop. This relates to a case where a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface; the current situation is that a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. D:Route reflectors distribute selected IBGP reachability within the configured client topology. It is useful for situations where an internal client learns routes from another client only intermittently after the route-reflector peering address changes; the reported fault, though, is that a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout.