Question 470In a separate fictional JNCIS-SP lab review for Brightstone Backbone 118, a carrier-edge and core routing team, following a monitored network change window, engineers find: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Which networking principle explains why the proposed correction is appropriate? BGP depends on working IP transport to establish its TCP session. IBGP connects peers within an AS while EBGP represents inter-AS exchange with different policy expectations. BGP route stability depends on both peer health and consistent route advertisements. For otherwise comparable routes, Junos route preference influences which eligible route becomes active. ExplanationCorrect Answer C:BGP route stability depends on both peer health and consistent route advertisements. The source of withdrawals is identified and the prefix stays available during observation. Inspect BGP update history, peer flaps and policy events before changing transit selection. Incorrect Answers A:BGP depends on working IP transport to establish its TCP session. That relates to circumstances in which a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable. Here the problem is that an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. B:IBGP connects peers within an AS while EBGP represents inter-AS exchange with different policy expectations. This addresses a situation in which an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary; however, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. D:For otherwise comparable routes, Junos route preference influences which eligible route becomes active. 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: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route.
Question 471In a separate fictional JNCIS-SP lab review for Brightstone Backbone 118, a carrier-edge and core routing team, following a monitored network change window, engineers find: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Which validation result would confirm the design is now functioning? The intended EBGP neighbor becomes Established and exchanges authorized prefixes. The source of withdrawals is identified and the prefix stays available during observation. Both client sessions stabilize and expected reflected routes reach peers. MAC entries stabilize on the intended interface after repairing the bridge path. ExplanationCorrect Answer B:The source of withdrawals is identified and the prefix stays available during observation. Inspect BGP update history, peer flaps and policy events before changing transit selection. BGP route stability depends on both peer health and consistent route advertisements. Incorrect Answers A:The intended EBGP neighbor becomes Established and exchanges authorized prefixes. It is useful for situations where an external BGP session never reaches Established because the local peer definition uses the wrong remote AS; the reported fault, though, is that an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. C:Both client sessions stabilize and expected reflected routes reach peers. This addresses a situation in which an internal client learns routes from another client only intermittently after the route-reflector peering address changes; however, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. D:MAC entries stabilize on the intended interface after repairing the bridge path. The choice would be appropriate if a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables. Here, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route.
Question 472In a separate fictional JNCIS-SP lab review for Brightstone Backbone 118, a carrier-edge and core routing team, following a monitored network change window, engineers find: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. What likely service impact does this condition create? A route leak consumes routing resources and destabilizes production services. Traffic engineering decisions depend on a route attribute outside its applicable selection scope. Customers experience a blackhole hidden by otherwise present route advertisements. Intermittent route loss causes repeated customer outages. ExplanationCorrect Answer D:Intermittent route loss causes repeated customer outages. Inspect BGP update history, peer flaps and policy events before changing transit selection. BGP route stability depends on both peer health and consistent route advertisements. Incorrect Answers A:A route leak consumes routing resources and destabilizes production services. This relates to a case where a misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale; the current situation is that an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. B:Traffic engineering decisions depend on a route attribute outside its applicable selection scope. It is useful for situations where a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems; the reported fault, though, is that an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. C:Customers experience a blackhole hidden by otherwise present route advertisements. That relates to circumstances in which a service path references an LSP that is down, but its IP route remains visible in the route table. Here the problem is that an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route.
Question 473At fictional Eastbridge Networks 119, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. Which configuration or operational correction most directly addresses this failure? Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy. Restore deliberate local-preference assignment and check selected egress paths. Add an explicit approved community match and verify the intended import or export action. Inspect label stack, bottom-of-stack indicator, and the expected transport operation. ExplanationCorrect Answer C:Add an explicit approved community match and verify the intended import or export action. BGP communities label routes for policy decisions only when a policy uses those labels. Tagged prefixes receive the documented policy action and untagged routes are unaffected. Incorrect Answers A:Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy. This could help if an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability, but not when an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. B:Restore deliberate local-preference assignment and check selected egress paths. This relates to a case where a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset; the current situation is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. D:Inspect label stack, bottom-of-stack indicator, and the expected transport operation. That relates to circumstances in which operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. Here the problem is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning.
Question 474At fictional Eastbridge Networks 119, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. Which Junos forwarding or control-plane rule applies to this case? BGP communities label routes for policy decisions only when a policy uses those labels. BGP route stability depends on both peer health and consistent route advertisements. BGP address-family negotiation determines which network-layer reachability data can be exchanged. Penultimate-hop popping can remove the outer transport label before the final LSR. ExplanationCorrect Answer A:BGP communities label routes for policy decisions only when a policy uses those labels. Add an explicit approved community match and verify the intended import or export action. Tagged prefixes receive the documented policy action and untagged routes are unaffected. Incorrect Answers B:BGP route stability depends on both peer health and consistent route advertisements. This could help if an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route, but not when an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. C:BGP address-family negotiation determines which network-layer reachability data can be exchanged. This relates to a case where an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled; the current situation is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. D:Penultimate-hop popping can remove the outer transport label before the final LSR. It is useful for situations where an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP; the reported fault, though, is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning.
Question 475At fictional Eastbridge Networks 119, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. What operational evidence best establishes successful remediation? The BGP session stays Established across a stability window with predictable negotiated timers. Tagged prefixes receive the documented policy action and untagged routes are unaffected. The BGP route becomes active and the next hop resolves to a reachable core interface. BGP and IGP neighbors remain stable through a controlled Routing Engine switchover. ExplanationCorrect Answer B:Tagged prefixes receive the documented policy action and untagged routes are unaffected. BGP communities label routes for policy decisions only when a policy uses those labels. Add an explicit approved community match and verify the intended import or export action. Incorrect Answers A:The BGP session stays Established across a stability window with predictable negotiated timers. This is applicable when a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions; the present condition is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. C:The BGP route becomes active and the next hop resolves to a reachable core interface. This could help if an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability, but not when an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. D:BGP and IGP neighbors remain stable through a controlled Routing Engine switchover. This relates to a case where traffic briefly vanishes after a Routing Engine failure because the backup does not maintain protocol state; the current situation is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning.
Question 476At fictional Eastbridge Networks 119, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. Which operational harm would persist without the intended correction? Traffic engineering intent fails despite the community being visible. Outbound traffic takes an expensive or congested transit link. Repeated control-plane resets withdraw customer routes. A provider domain becomes partitioned and service prefixes disappear. ExplanationCorrect Answer A:Traffic engineering intent fails despite the community being visible. BGP communities label routes for policy decisions only when a policy uses those labels. Add an explicit approved community match and verify the intended import or export action. Incorrect Answers B:Outbound traffic takes an expensive or congested transit link. This is applicable when a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset; the present condition is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. C:Repeated control-plane resets withdraw customer routes. It is relevant if a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions, but the reported issue is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. D:A provider domain becomes partitioned and service prefixes disappear. This could help if two adjacent core routers cannot establish IS-IS because one is configured only for Level 1 and the other only for Level 2, but not when an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning.
Question 477In a separate fictional JNCIS-SP lab review for Orchard Link 120, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. What should the Junos specialist change first to resolve this specific fault? Inspect AS path and applicable policy before changing unrelated preference settings. Inspect full route attributes and the BGP decision outcome for all candidate paths. Add an explicit approved community match and verify the intended import or export action. Validate the advertised label behavior and egress processing expectations. ExplanationCorrect Answer C:Add an explicit approved community match and verify the intended import or export action. Tagged prefixes receive the documented policy action and untagged routes are unaffected. BGP communities label routes for policy decisions only when a policy uses those labels. Incorrect Answers A:Inspect AS path and applicable policy before changing unrelated preference settings. This could matter when an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. In this case, an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. B:Inspect full route attributes and the BGP decision outcome for all candidate paths. That could help when a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored; here, an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. D:Validate the advertised label behavior and egress processing expectations. It is relevant if an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP, but the reported issue is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning.
Question 478In a separate fictional JNCIS-SP lab review for Orchard Link 120, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. What technical principle underlies the right remedy? BGP communities label routes for policy decisions only when a policy uses those labels. Junos routing policy is evaluated by terms whose order and matching conditions affect the outcome. Route reflectors distribute selected IBGP reachability within the configured client topology. A healthy IS-IS adjacency does not prove the intended shortest path is active in the forwarding plane. ExplanationCorrect Answer A:BGP communities label routes for policy decisions only when a policy uses those labels. Tagged prefixes receive the documented policy action and untagged routes are unaffected. Add an explicit approved community match and verify the intended import or export action. Incorrect Answers B:Junos routing policy is evaluated by terms whose order and matching conditions affect the outcome. This could matter when a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through. In this case, an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. C:Route reflectors distribute selected IBGP reachability within the configured client topology. That could help when an internal client learns routes from another client only intermittently after the route-reflector peering address changes; here, an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. D:A healthy IS-IS adjacency does not prove the intended shortest path is active in the forwarding plane. This is applicable when the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change; the present condition is that an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning.
Question 479In a separate fictional JNCIS-SP lab review for Orchard Link 120, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. Which acceptance finding demonstrates the affected service has recovered? The forbidden test prefix is rejected while approved prefixes are accepted. Both client sessions stabilize and expected reflected routes reach peers. The interface unit is operational and the connected subnet appears in the correct routing table. Tagged prefixes receive the documented policy action and untagged routes are unaffected. ExplanationCorrect Answer D:Tagged prefixes receive the documented policy action and untagged routes are unaffected. Add an explicit approved community match and verify the intended import or export action. BGP communities label routes for policy decisions only when a policy uses those labels. Incorrect Answers A:The forbidden test prefix is rejected while approved prefixes are accepted. That option concerns a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through. The problem here is different: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. B:Both client sessions stabilize and expected reflected routes reach peers. It addresses a different problem: An internal client learns routes from another client only intermittently after the route-reflector peering address changes. Here, an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. C:The interface unit is operational and the connected subnet appears in the correct routing table. This could matter when a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. In this case, an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning.
Question 480In a separate fictional JNCIS-SP lab review for Orchard Link 120, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. What is the direct residual network risk if the fault remains unresolved? Intermittent route loss causes repeated customer outages. Attempts to fix policy distract from a network reachability failure. Dual-stack service is only partially operational. Traffic engineering intent fails despite the community being visible. ExplanationCorrect Answer D:Traffic engineering intent fails despite the community being visible. Add an explicit approved community match and verify the intended import or export action. BGP communities label routes for policy decisions only when a policy uses those labels. Incorrect Answers A:Intermittent route loss causes repeated customer outages. The choice would be appropriate if an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Here, an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. B:Attempts to fix policy distract from a network reachability failure. That option concerns a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable. The problem here is different: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. C:Dual-stack service is only partially operational. It addresses a different problem: A core network runs IS-IS for IPv4 but has no IPv6 service reachability after dual-stack activation. Here, an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning.