Question 350In a separate fictional JNCIS-SP lab review for Windmere Fiber 088, a carrier-edge and core routing team, following a monitored network change window, engineers find: The IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. What technical principle underlies the right remedy? IS-IS elects a designated intermediate system on broadcast networks to manage pseudonode representation. IS-IS routers need consistent flooded LSP information for reliable SPF results. BGP import policy governs which learned prefixes enter local route selection. A healthy IS-IS adjacency does not prove the intended shortest path is active in the forwarding plane. ExplanationCorrect Answer D:A healthy IS-IS adjacency does not prove the intended shortest path is active in the forwarding plane. The route table and forwarding lookup show the expected metric-driven next hop. Inspect LSDB entries, SPF route selection, and forwarding next hops instead of relying on neighbor state alone. Incorrect Answers A:IS-IS elects a designated intermediate system on broadcast networks to manage pseudonode representation. 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 the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. B:IS-IS routers need consistent flooded LSP information for reliable SPF results. This addresses a situation in which a remote PE misses a new loopback route because IS-IS link-state flooding is incomplete after an adjacency reset; however, the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. C:BGP import policy governs which learned prefixes enter local route selection. The choice would be appropriate if a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. Here, the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change.
Question 351In a separate fictional JNCIS-SP lab review for Windmere Fiber 088, a carrier-edge and core routing team, following a monitored network change window, engineers find: The IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. Which acceptance finding demonstrates the affected service has recovered? The LSDB lists separate stable system IDs for the two routers. The planned L1 adjacency forms and the corresponding area information is consistent. The route table and forwarding lookup show the expected metric-driven next hop. Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. ExplanationCorrect Answer C:The route table and forwarding lookup show the expected metric-driven next hop. Inspect LSDB entries, SPF route selection, and forwarding next hops instead of relying on neighbor state alone. A healthy IS-IS adjacency does not prove the intended shortest path is active in the forwarding plane. Incorrect Answers A:The LSDB lists separate stable system IDs for the two routers. It is useful for situations where a device cloned from a lab template has the same IS-IS system ID as a production router; the reported fault, though, is that the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. B:The planned L1 adjacency forms and the corresponding area information is consistent. That relates to circumstances in which a Level 1 IS-IS adjacency fails between routers with different area addresses even though the physical link is up. Here the problem is that the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. D:Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. The choice would be appropriate if a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. Here, the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change.
Question 352In a separate fictional JNCIS-SP lab review for Windmere Fiber 088, a carrier-edge and core routing team, following a monitored network change window, engineers find: The IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. What is the direct residual network risk if the fault remains unresolved? Operations declares recovery while customer packets use a degraded detour. Intra-area routes never propagate between connected devices. Duplicate identity creates conflicting LSPs and unstable route computation. IPv6 service fails across a still-configured but unusable tunnel. ExplanationCorrect Answer A:Operations declares recovery while customer packets use a degraded detour. Inspect LSDB entries, SPF route selection, and forwarding next hops instead of relying on neighbor state alone. A healthy IS-IS adjacency does not prove the intended shortest path is active in the forwarding plane. Incorrect Answers B:Intra-area routes never propagate between connected devices. It is useful for situations where a Level 1 IS-IS adjacency fails between routers with different area addresses even though the physical link is up; the reported fault, though, is that the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. C:Duplicate identity creates conflicting LSPs and unstable route computation. That relates to circumstances in which a device cloned from a lab template has the same IS-IS system ID as a production router. Here the problem is that the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change. D:IPv6 service fails across a still-configured but unusable tunnel. This addresses a situation in which an IPv6 service is carried through an IPv4 underlay, but the tunnel endpoint's IPv4 route has disappeared; however, the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change.
Question 353At fictional Meadowcrest Telecom 089, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. Which targeted remediation best fits the reported behavior? Inspect full route attributes and the BGP decision outcome for all candidate paths. Inspect AS path and applicable policy before changing unrelated preference settings. Correct the peer autonomous-system setting and validate session negotiation. Align the intended OSPF area on both endpoints and inspect neighbor state. ExplanationCorrect Answer C:Correct the peer autonomous-system setting and validate session negotiation. BGP peers need mutually consistent AS and transport/session parameters. The intended EBGP neighbor becomes Established and exchanges authorized prefixes. Incorrect Answers A:Inspect full route attributes and the BGP decision outcome for all candidate paths. This could help if a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored, but not when an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. B:Inspect AS path and applicable policy before changing unrelated preference settings. This relates to a case where an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path; the current situation is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. D:Align the intended OSPF area on both endpoints and inspect neighbor state. That relates to circumstances in which two provider routers on a point-to-point circuit cannot form an OSPF adjacency because their interfaces use different area IDs. Here the problem is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS.
Question 354At fictional Meadowcrest Telecom 089, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. Why is this particular correction the best fit for the stated defect? BGP route stability depends on both peer health and consistent route advertisements. BGP peers need mutually consistent AS and transport/session parameters. A BGP path cannot be installed for forwarding when its next hop cannot be resolved. A configured static route forwards only after Junos can resolve its forwarding next hop. ExplanationCorrect Answer B:BGP peers need mutually consistent AS and transport/session parameters. Correct the peer autonomous-system setting and validate session negotiation. The intended EBGP neighbor becomes Established and exchanges authorized prefixes. Incorrect Answers A:BGP route stability depends on both peer health and consistent route advertisements. It is relevant if an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route, but the reported issue is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. C:A BGP path cannot be installed for forwarding when its next hop cannot be resolved. This relates to a case where an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability; the current situation is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. D:A configured static route forwards only after Junos can resolve its forwarding next hop. It is useful for situations where a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface; the reported fault, though, is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS.
Question 355At fictional Meadowcrest Telecom 089, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. What direct observation would prove the corrective action worked? Peer details show the intended internal AS relationship and routes propagate by design. The intended EBGP neighbor becomes Established and exchanges authorized prefixes. A transport test reaches the peer and the BGP state advances to Established. Remote routers receive the intended interarea route and retain correct area separation. ExplanationCorrect Answer B:The intended EBGP neighbor becomes Established and exchanges authorized prefixes. BGP peers need mutually consistent AS and transport/session parameters. Correct the peer autonomous-system setting and validate session negotiation. Incorrect Answers A:Peer details show the intended internal AS relationship and routes propagate by design. This is applicable when an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary; the present condition is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. C:A transport test reaches the peer and the BGP state advances to Established. This could help if a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable, but not when an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. D:Remote routers receive the intended interarea route and retain correct area separation. This relates to a case where a site advertises internal prefixes inside one area, but a remote OSPF area cannot learn them because the area border configuration is incomplete; the current situation is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS.
Question 356At fictional Meadowcrest Telecom 089, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. Which failure consequence follows most closely from ignoring this issue? A route loop or false path preference persists due to misdiagnosis. A route leak consumes routing resources and destabilizes production services. The interprovider route exchange remains unavailable. IPv6 customers lose service even when IPv4 routing remains healthy. ExplanationCorrect Answer C:The interprovider route exchange remains unavailable. BGP peers need mutually consistent AS and transport/session parameters. Correct the peer autonomous-system setting and validate session negotiation. Incorrect Answers A:A route loop or false path preference persists due to misdiagnosis. That could help when an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path; here, an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. B:A route leak consumes routing resources and destabilizes production services. This is applicable when a misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale; the present condition is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. D:IPv6 customers lose service even when IPv4 routing remains healthy. This could help if an IPv6 service prefix is configured with a next-hop address that does not resolve on the intended transit interface, but not when an external BGP session never reaches Established because the local peer definition uses the wrong remote AS.
Question 357In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 090, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. What intervention most directly restores the intended routing or switching behavior? Inspect full route attributes and the BGP decision outcome for all candidate paths. Correct the peer autonomous-system setting and validate session negotiation. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. Synchronize the approved IS-IS authentication configuration across peers and verify secure adjacency. ExplanationCorrect Answer B:Correct the peer autonomous-system setting and validate session negotiation. The intended EBGP neighbor becomes Established and exchanges authorized prefixes. BGP peers need mutually consistent AS and transport/session parameters. Incorrect Answers A:Inspect full route attributes and the BGP decision outcome for all candidate paths. 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, an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. C:Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. 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 an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. D:Synchronize the approved IS-IS authentication configuration across peers and verify secure adjacency. It is relevant if a provider IS-IS circuit stops forming neighbors after the authentication key is changed on only one end, but the reported issue is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS.
Question 358In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 090, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. Which networking principle explains why the proposed correction is appropriate? BGP communities label routes for policy decisions only when a policy uses those labels. BGP address-family negotiation determines which network-layer reachability data can be exchanged. BGP peers need mutually consistent AS and transport/session parameters. Bridge-table observations must be interpreted alongside actual physical and logical port membership. ExplanationCorrect Answer C:BGP peers need mutually consistent AS and transport/session parameters. The intended EBGP neighbor becomes Established and exchanges authorized prefixes. Correct the peer autonomous-system setting and validate session negotiation. Incorrect Answers A:BGP communities label routes for policy decisions only when a policy uses those labels. It addresses a different problem: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. Here, an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. B:BGP address-family negotiation determines which network-layer reachability data can be exchanged. This could matter when an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. In this case, an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. D:Bridge-table observations must be interpreted alongside actual physical and logical port membership. This is applicable when a MAC is learned on an unexpected aggregation interface following a customer circuit move; the present condition is that an external BGP session never reaches Established because the local peer definition uses the wrong remote AS.
Question 359In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 090, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. Which validation result would confirm the design is now functioning? A controlled excess-route test triggers the intended protective response and logging. The intended EBGP neighbor becomes Established and exchanges authorized prefixes. Tagged prefixes receive the documented policy action and untagged routes are unaffected. Authenticated neighbors become Full and reject intentionally incorrect credentials. ExplanationCorrect Answer B:The intended EBGP neighbor becomes Established and exchanges authorized prefixes. Correct the peer autonomous-system setting and validate session negotiation. BGP peers need mutually consistent AS and transport/session parameters. Incorrect Answers A:A controlled excess-route test triggers the intended protective response and logging. That option concerns a misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale. The problem here is different: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. C:Tagged prefixes receive the documented policy action and untagged routes are unaffected. This could matter when an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. In this case, an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. D:Authenticated neighbors become Full and reject intentionally incorrect credentials. That could help when a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree; here, an external BGP session never reaches Established because the local peer definition uses the wrong remote AS.
Question 360In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 090, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. What likely service impact does this condition create? A route loop or false path preference persists due to misdiagnosis. IPv6 customers lose external paths despite healthy IPv4 peering. A false fix redirects a customer subnet onto an inappropriate aggregate route. The interprovider route exchange remains unavailable. ExplanationCorrect Answer D:The interprovider route exchange remains unavailable. Correct the peer autonomous-system setting and validate session negotiation. BGP peers need mutually consistent AS and transport/session parameters. Incorrect Answers A:A route loop or false path preference persists due to misdiagnosis. The choice would be appropriate if an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. Here, an external BGP session never reaches Established because the local peer definition uses the wrong remote AS. B:IPv6 customers lose external paths despite healthy IPv4 peering. 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: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. C:A false fix redirects a customer subnet onto an inappropriate aggregate route. It addresses a different problem: An operator changes route preference to make a broader prefix override a healthy more-specific prefix. Here, an external BGP session never reaches Established because the local peer definition uses the wrong remote AS.