Question 370At fictional Brightstone Backbone 093, a regional service-provider network, during a two-site transit migration, operations observes: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. Why is this particular correction the best fit for the stated defect? BGP peers use negotiated timers to detect failed sessions and maintain liveness. BGP MED expresses a neighboring AS's ingress preference and its comparison scope is policy-dependent. A tunnel must not rely on its own encapsulated path to reach the outer endpoint. BGP import policy governs which learned prefixes enter local route selection. ExplanationCorrect Answer D:BGP import policy governs which learned prefixes enter local route selection. Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. The unauthorized prefix is absent and approved transit routes remain usable. Incorrect Answers A:BGP peers use negotiated timers to detect failed sessions and maintain liveness. It addresses a different problem: A neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions. Here, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. B:BGP MED expresses a neighboring AS's ingress preference and its comparison scope is policy-dependent. This could matter when a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems. In this case, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. C:A tunnel must not rely on its own encapsulated path to reach the outer endpoint. That could help when a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution; here, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy.
Question 371At fictional Brightstone Backbone 093, a regional service-provider network, during a two-site transit migration, operations observes: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. What direct observation would prove the corrective action worked? The path comparison identifies the deciding attributes and final active candidate. The unauthorized prefix is absent and approved transit routes remain usable. The forbidden test prefix is rejected while approved prefixes are accepted. The route table and forwarding lookup show the expected metric-driven next hop. ExplanationCorrect Answer B:The unauthorized prefix is absent and approved transit routes remain usable. BGP import policy governs which learned prefixes enter local route selection. Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. Incorrect Answers A:The path comparison identifies the deciding attributes and final active candidate. That option concerns a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. The problem here is different: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. C:The forbidden test prefix is rejected while approved prefixes are accepted. 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, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. D:The route table and forwarding lookup show the expected metric-driven next hop. That could help when the IS-IS session reports established but a core prefix still follows an unexpected path after a circuit metric change; here, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy.
Question 372At fictional Brightstone Backbone 093, a regional service-provider network, during a two-site transit migration, operations observes: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. Which failure consequence follows most closely from ignoring this issue? Unwanted routes may alter forwarding or create customer traffic leakage. Attempts to fix policy distract from a network reachability failure. The interprovider route exchange remains unavailable. The monitoring function loses required reachability or isolation is weakened by broad route copying. ExplanationCorrect Answer A:Unwanted routes may alter forwarding or create customer traffic leakage. BGP import policy governs which learned prefixes enter local route selection. Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. Incorrect Answers 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: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. C:The interprovider route exchange remains unavailable. It addresses a different problem: An external BGP session never reaches Established because the local peer definition uses the wrong remote AS. Here, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. D:The monitoring function loses required reachability or isolation is weakened by broad route copying. This could matter when a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. In this case, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy.
Question 373In a separate fictional JNCIS-SP lab review for Eastbridge Networks 094, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. What intervention most directly restores the intended routing or switching behavior? Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. Place precise deny/accept logic in the intended evaluation order and validate policy results. Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy. Align the supported metric style and review full link metrics across the participating routing level. ExplanationCorrect Answer A:Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. The unauthorized prefix is absent and approved transit routes remain usable. BGP import policy governs which learned prefixes enter local route selection. Incorrect Answers B:Place precise deny/accept logic in the intended evaluation order and validate policy results. The choice would be appropriate if a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through. Here, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. C:Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy. 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: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. D:Align the supported metric style and review full link metrics across the participating routing level. It addresses a different problem: An intended core link metric is truncated by a mismatched metric-style design and fails to shift paths as expected. Here, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy.
Question 374In a separate fictional JNCIS-SP lab review for Eastbridge Networks 094, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. Which networking principle explains why the proposed correction is appropriate? An established BGP session does not by itself establish which received path will be preferred. BGP peers use negotiated timers to detect failed sessions and maintain liveness. BGP multiprotocol families and matching policy control IPv6 route exchange. BGP import policy governs which learned prefixes enter local route selection. ExplanationCorrect Answer D:BGP import policy governs which learned prefixes enter local route selection. The unauthorized prefix is absent and approved transit routes remain usable. Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. Incorrect Answers A:An established BGP session does not by itself establish which received path will be preferred. That relates to circumstances in which a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. Here the problem is that a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. B:BGP peers use negotiated timers to detect failed sessions and maintain liveness. This addresses a situation in which a neighboring BGP session resets frequently because the timer design is incompatible with observed transport conditions; however, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. C:BGP multiprotocol families and matching policy control IPv6 route exchange. The choice would be appropriate if an established BGP peer exchanges IPv4 but rejects all authorized IPv6 prefixes due to a misplaced family-specific filter. Here, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy.
Question 375In a separate fictional JNCIS-SP lab review for Eastbridge Networks 094, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. Which validation result would confirm the design is now functioning? The chosen path follows documented selection policy with MED considered only where applicable. The unauthorized prefix is absent and approved transit routes remain usable. The forbidden test prefix is rejected while approved prefixes are accepted. Authenticated neighbors become Full and reject intentionally incorrect credentials. ExplanationCorrect Answer B:The unauthorized prefix is absent and approved transit routes remain usable. Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. BGP import policy governs which learned prefixes enter local route selection. Incorrect Answers A:The chosen path follows documented selection policy with MED considered only where applicable. 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 a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. C:The forbidden test prefix is rejected while approved prefixes are accepted. This addresses a situation in which a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through; however, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. D:Authenticated neighbors become Full and reject intentionally incorrect credentials. The choice would be appropriate if a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree. Here, a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy.
Question 376In a separate fictional JNCIS-SP lab review for Eastbridge Networks 094, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. What likely service impact does this condition create? Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. Undetected route oscillation harms network stability. Customer equipment captures the root role and disrupts forwarding. Unwanted routes may alter forwarding or create customer traffic leakage. ExplanationCorrect Answer D:Unwanted routes may alter forwarding or create customer traffic leakage. Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. BGP import policy governs which learned prefixes enter local route selection. 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 a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. B:Undetected route oscillation harms network stability. It is useful for situations where a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored; the reported fault, though, is that a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. C:Customer equipment captures the root role and disrupts forwarding. That relates to circumstances in which a customer-facing bridge advertises a superior root and takes over the provider STP topology. Here the problem is that a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy.
Question 377At fictional Orchard Link 095, a regional service-provider network, during a preproduction design validation, operations observes: A customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. Which configuration or operational correction most directly addresses this failure? Inspect full route attributes and the BGP decision outcome for all candidate paths. Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy. Fix the peer export policy match for the authorized prefix and verify the announced routes. Remove inappropriate edge-port assumptions and verify RSTP role transitions. ExplanationCorrect Answer C:Fix the peer export policy match for the authorized prefix and verify the announced routes. Junos BGP exports only routes accepted by the applicable export policy. The expected customer prefix appears in the advertised-route output and unintended prefixes do not. 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 a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. B:Make the BGP next hop reachable through the designed IGP or appropriate next-hop policy. 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 a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. D:Remove inappropriate edge-port assumptions and verify RSTP role transitions. That relates to circumstances in which a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. Here the problem is that a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it.
Question 378At fictional Orchard Link 095, a regional service-provider network, during a preproduction design validation, operations observes: A customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. Which Junos forwarding or control-plane rule applies to this case? BGP address-family negotiation determines which network-layer reachability data can be exchanged. BGP peers use negotiated timers to detect failed sessions and maintain liveness. MPLS label forwarding must follow the current resolved transport topology. Junos BGP exports only routes accepted by the applicable export policy. ExplanationCorrect Answer D:Junos BGP exports only routes accepted by the applicable export policy. Fix the peer export policy match for the authorized prefix and verify the announced routes. The expected customer prefix appears in the advertised-route output and unintended prefixes do not. Incorrect Answers A:BGP address-family negotiation determines which network-layer reachability data can be exchanged. It is relevant if an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled, but the reported issue is that a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. 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 a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. C:MPLS label forwarding must follow the current resolved transport topology. This relates to a case where after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; the current situation is that a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it.
Question 379At fictional Orchard Link 095, a regional service-provider network, during a preproduction design validation, operations observes: A customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. What operational evidence best establishes successful remediation? The intended EBGP neighbor becomes Established and exchanges authorized prefixes. Tagged prefixes receive the documented policy action and untagged routes are unaffected. The expected customer prefix appears in the advertised-route output and unintended prefixes do not. MAC tables and customer bridge forwarding remain stable during controlled switchover. ExplanationCorrect Answer C:The expected customer prefix appears in the advertised-route output and unintended prefixes do not. Junos BGP exports only routes accepted by the applicable export policy. Fix the peer export policy match for the authorized prefix and verify the announced routes. Incorrect Answers A:The intended EBGP neighbor becomes Established and exchanges authorized prefixes. This is applicable when an external BGP session never reaches Established because the local peer definition uses the wrong remote AS; the present condition is that a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. B:Tagged prefixes receive the documented policy action and untagged routes are unaffected. It is relevant if an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning, but the reported issue is that a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. D:MAC tables and customer bridge forwarding remain stable during controlled switchover. This relates to a case where a switch with redundant Routing Engines loses Layer 2 MAC learning state during switchover despite planned availability targets; the current situation is that a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it.
Question 380At fictional Orchard Link 095, a regional service-provider network, during a preproduction design validation, operations observes: A customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. Which operational harm would persist without the intended correction? Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. Policy and reachability behavior is distorted by a false external session. A route leak consumes routing resources and destabilizes production services. An unnoticed bridging loop can trigger widespread broadcast storms. ExplanationCorrect Answer A:Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. Junos BGP exports only routes accepted by the applicable export policy. Fix the peer export policy match for the authorized prefix and verify the announced routes. Incorrect Answers B:Policy and reachability behavior is distorted by a false external session. 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 a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. C:A route leak consumes routing resources and destabilizes production services. It is relevant if a misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale, but the reported issue is that a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. D:An unnoticed bridging loop can trigger widespread broadcast storms. This could help if a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior, but not when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it.