Question 460At fictional Bluehaven Backbone 115, a regional service-provider network, during a preproduction design validation, operations observes: An internal client learns routes from another client only intermittently after the route-reflector peering address changes. Which operational harm would persist without the intended correction? Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. A route loop or false path preference persists due to misdiagnosis. Excessive flooding consumes bandwidth and exposes traffic across unintended ports. IBGP clients lack complete reachability and use inconsistent exits. ExplanationCorrect Answer D:IBGP clients lack complete reachability and use inconsistent exits. Route reflectors distribute selected IBGP reachability within the configured client topology. Restore consistent client-to-reflector peering and reachable loopback endpoints. Incorrect Answers A:Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. This relates to a case where a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it; the current situation is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes. B:A route loop or false path preference persists due to misdiagnosis. It is useful for situations where an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path; the reported fault, though, is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes. C:Excessive flooding consumes bandwidth and exposes traffic across unintended ports. That relates to circumstances in which an edge switch floods ordinary known unicast frames because it never learns the destination MAC on the expected port. Here the problem is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes.
Question 461In a separate fictional JNCIS-SP lab review for Lakewood Carrier 116, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: An internal client learns routes from another client only intermittently after the route-reflector peering address changes. What should the Junos specialist change first to resolve this specific fault? Restore consistent client-to-reflector peering and reachable loopback endpoints. Fix the peer export policy match for the authorized prefix and verify the announced routes. Review negotiated hold time and keepalive settings alongside transport health, then correct the design. Apply the approved BPDU protection policy to the access edge and test the violation response. ExplanationCorrect Answer A:Restore consistent client-to-reflector peering and reachable loopback endpoints. Both client sessions stabilize and expected reflected routes reach peers. Route reflectors distribute selected IBGP reachability within the configured client topology. Incorrect Answers B:Fix the peer export policy match for the authorized prefix and verify the announced routes. This relates to a case where a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it; the current situation is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes. C:Review negotiated hold time and keepalive settings alongside transport health, then correct the design. It is useful for situations where a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions; the reported fault, though, is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes. D:Apply the approved BPDU protection policy to the access edge and test the violation response. That relates to circumstances in which a subscriber accidentally connects a switch that sends BPDUs into a provider edge expected to accept endpoints only. Here the problem is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes.
Question 462In a separate fictional JNCIS-SP lab review for Lakewood Carrier 116, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: An internal client learns routes from another client only intermittently after the route-reflector peering address changes. What technical principle underlies the right remedy? Route reflectors distribute selected IBGP reachability within the configured client topology. BGP peers use negotiated timers to detect failed sessions and maintain liveness. Junos routing policy is evaluated by terms whose order and matching conditions affect the outcome. Tunnel endpoints must use source and destination addresses that the underlay can route and permit. ExplanationCorrect Answer A:Route reflectors distribute selected IBGP reachability within the configured client topology. Both client sessions stabilize and expected reflected routes reach peers. Restore consistent client-to-reflector peering and reachable loopback endpoints. Incorrect Answers B:BGP peers use negotiated timers to detect failed sessions and maintain liveness. This could help if a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions, but not when an internal client learns routes from another client only intermittently after the route-reflector peering address changes. C:Junos routing policy is evaluated by terms whose order and matching conditions affect the outcome. This relates to a case where a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through; the current situation is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes. D:Tunnel endpoints must use source and destination addresses that the underlay can route and permit. It is useful for situations where a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL; the reported fault, though, is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes.
Question 463In a separate fictional JNCIS-SP lab review for Lakewood Carrier 116, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: An internal client learns routes from another client only intermittently after the route-reflector peering address changes. Which acceptance finding demonstrates the affected service has recovered? The unauthorized prefix is absent and approved transit routes remain usable. The BGP route becomes active and the next hop resolves to a reachable core interface. Both client sessions stabilize and expected reflected routes reach peers. Two identical inner customer tags remain isolated by separate outer tags or service instances. ExplanationCorrect Answer C:Both client sessions stabilize and expected reflected routes reach peers. Restore consistent client-to-reflector peering and reachable loopback endpoints. Route reflectors distribute selected IBGP reachability within the configured client topology. Incorrect Answers A:The unauthorized prefix is absent and approved transit routes remain usable. This is applicable when a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy; the present condition is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes. B:The BGP route becomes active and the next hop resolves to a reachable core interface. It is relevant if an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability, but the reported issue is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes. D:Two identical inner customer tags remain isolated by separate outer tags or service instances. This relates to a case where two unrelated customers use the same inner VLAN ID, and a template accidentally merges them into one provider bridge; the current situation is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes.
Question 464In a separate fictional JNCIS-SP lab review for Lakewood Carrier 116, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: An internal client learns routes from another client only intermittently after the route-reflector peering address changes. What is the direct residual network risk if the fault remains unresolved? IBGP clients lack complete reachability and use inconsistent exits. A route leak consumes routing resources and destabilizes production services. A route loop or false path preference persists due to misdiagnosis. Customer equipment captures the root role and disrupts forwarding. ExplanationCorrect Answer A:IBGP clients lack complete reachability and use inconsistent exits. Restore consistent client-to-reflector peering and reachable loopback endpoints. Route reflectors distribute selected IBGP reachability within the configured client topology. Incorrect Answers 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 internal client learns routes from another client only intermittently after the route-reflector peering address changes. C:A route loop or false path preference persists due to misdiagnosis. It is relevant if an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path, but the reported issue is that an internal client learns routes from another client only intermittently after the route-reflector peering address changes. D:Customer equipment captures the root role and disrupts forwarding. This could help if a customer-facing bridge advertises a superior root and takes over the provider STP topology, but not when an internal client learns routes from another client only intermittently after the route-reflector peering address changes.
Question 465At fictional Summitfield Carrier 117, a regional service-provider network, during a core-routing acceptance test, operations observes: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Which targeted remediation best fits the reported behavior? Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. Recalculate the supported reservation and link bandwidth design before retrying. Inspect BGP update history, peer flaps and policy events before changing transit selection. ExplanationCorrect Answer D: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. The source of withdrawals is identified and the prefix stays available during observation. Incorrect Answers A:Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. This could matter when a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. In this case, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. B:Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. That could help when an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled; here, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. C:Recalculate the supported reservation and link bandwidth design before retrying. This is applicable when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; the present condition is that an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route.
Question 466At fictional Summitfield Carrier 117, a regional service-provider network, during a core-routing acceptance test, operations observes: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Why is this particular correction the best fit for the stated defect? A BGP path cannot be installed for forwarding when its next hop cannot be resolved. BGP route stability depends on both peer health and consistent route advertisements. Junos BGP exports only routes accepted by the applicable export policy. VRRP provides a shared virtual gateway address with an active router and standby candidates. ExplanationCorrect Answer B:BGP route stability depends on both peer health and consistent route advertisements. Inspect BGP update history, peer flaps and policy events before changing transit selection. The source of withdrawals is identified and the prefix stays available during observation. Incorrect Answers A:A BGP path cannot be installed for forwarding when its next hop cannot be resolved. It addresses a different problem: An IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. Here, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. C:Junos BGP exports only routes accepted by the applicable export policy. That could help when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it; here, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. D:VRRP provides a shared virtual gateway address with an active router and standby candidates. This is applicable when an access VLAN loses default-gateway access after the primary router fails because the backup's VRRP state is incorrect; the present condition is that an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route.
Question 467At fictional Summitfield Carrier 117, a regional service-provider network, during a core-routing acceptance test, operations observes: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. What direct observation would prove the corrective action worked? Tagged prefixes receive the documented policy action and untagged routes are unaffected. Peer details show the intended internal AS relationship and routes propagate by design. Neighbor state stabilizes and hello and dead intervals match on both endpoints. The source of withdrawals is identified and the prefix stays available during observation. ExplanationCorrect Answer D:The source of withdrawals is identified and the prefix stays available during observation. BGP route stability depends on both peer health and consistent route advertisements. Inspect BGP update history, peer flaps and policy events before changing transit selection. Incorrect Answers A:Tagged prefixes receive the documented policy action and untagged routes are unaffected. That option concerns an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. The problem here is different: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. B:Peer details show the intended internal AS relationship and routes propagate by design. It addresses a different problem: An operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary. Here, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. C:Neighbor state stabilizes and hello and dead intervals match on both endpoints. This could matter when OSPF neighbors remain down after one endpoint inherits a different hello and dead timer template. In this case, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route.
Question 468At fictional Summitfield Carrier 117, a regional service-provider network, during a core-routing acceptance test, operations observes: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Which failure consequence follows most closely from ignoring this issue? Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. Services remain blackholed despite a received BGP update. Intermittent route loss causes repeated customer outages. Customers experience a blackhole hidden by otherwise present route advertisements. ExplanationCorrect Answer C:Intermittent route loss causes repeated customer outages. BGP route stability depends on both peer health and consistent route advertisements. Inspect BGP update history, peer flaps and policy events before changing transit selection. Incorrect Answers A:Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. The choice would be appropriate if a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. Here, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. B:Services remain blackholed despite a received BGP update. That option concerns an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. The problem here is different: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. D:Customers experience a blackhole hidden by otherwise present route advertisements. This could matter when a service path references an LSP that is down, but its IP route remains visible in the route table. In this case, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route.
Question 469In 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 intervention most directly restores the intended routing or switching behavior? Confirm MED comparison applicability and use a suitable local outbound policy if needed. Repair transport routing and source-address selection before modifying BGP policy. Check label advertisements for the FEC and restore a valid LDP downstream binding. Inspect BGP update history, peer flaps and policy events before changing transit selection. ExplanationCorrect Answer D:Inspect BGP update history, peer flaps and policy events before changing transit selection. The source of withdrawals is identified and the prefix stays available during observation. BGP route stability depends on both peer health and consistent route advertisements. Incorrect Answers A:Confirm MED comparison applicability and use a suitable local outbound policy if needed. This addresses a situation in which a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems; however, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. B:Repair transport routing and source-address selection before modifying BGP policy. The choice would be appropriate if a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable. Here, an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. C:Check label advertisements for the FEC and restore a valid LDP downstream binding. That option concerns an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop. The problem here is different: An upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route.
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.