JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
A control-plane policy blocks OSPF IP protocol 89 on one link even though TCP and ICMP connectivity are healthy. The proposed correction is: Permit the narrowly scoped OSPF control protocol traffic between authorized adjacent routers. Which observation MOST directly confirms this fault is resolved?
Captured OSPF Hellos and database exchange return and the neighbor reaches Full. This is the direct acceptance evidence for the observed failure: A control-plane policy blocks OSPF IP protocol 89 on one link even though TCP and ICMP connectivity are healthy. The mechanism being validated is: OSPF uses its own IP protocol for routing messages rather than TCP port sessions.
Stabilized Hello reception prevents Dead timer expiry and adjacency flaps during peak traffic. That would validate a different condition: An OSPF neighbor repeatedly resets because a saturated control plane delays Hellos beyond the configured Dead timer. The decisive check for the current issue is: Captured OSPF Hellos and database exchange return and the neighbor reaches Full.
Database summaries reconcile and neighbor state reports Full after successful exchange. That would validate a different condition: Two adjacent OSPF ABRs have different LSDB checksums after a link flap, while operational staff look only at interface ping success. The decisive check for the current issue is: Captured OSPF Hellos and database exchange return and the neighbor reaches Full.
The area LSDB includes only approved external advertisements after flooding settles. That would validate a different condition: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. The decisive check for the current issue is: Captured OSPF Hellos and database exchange return and the neighbor reaches Full.
A Junos engineer proposes this response: Permit the narrowly scoped OSPF control protocol traffic between authorized adjacent routers. The situation is: A control-plane policy blocks OSPF IP protocol 89 on one link even though TCP and ICMP connectivity are healthy. Which technical principle BEST justifies the response?
OSPF uses its own IP protocol for routing messages rather than TCP port sessions. This is the controlling mechanism in the specific case: A control-plane policy blocks OSPF IP protocol 89 on one link even though TCP and ICMP connectivity are healthy. It predicts the acceptance result: Captured OSPF Hellos and database exchange return and the neighbor reaches Full.
OSPF Dead intervals detect loss of expected Hellos independently of the physical link state. This principle explains a separate situation: An OSPF neighbor repeatedly resets because a saturated control plane delays Hellos beyond the configured Dead timer. For this issue the relevant mechanism is: OSPF uses its own IP protocol for routing messages rather than TCP port sessions.
An OSPF adjacency needs synchronized link-state databases in addition to basic reachability. This principle explains a separate situation: Two adjacent OSPF ABRs have different LSDB checksums after a link flap, while operational staff look only at interface ping success. For this issue the relevant mechanism is: OSPF uses its own IP protocol for routing messages rather than TCP port sessions.
Type-5 external LSAs distribute AS-external reachability across eligible OSPF areas. This principle explains a separate situation: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. For this issue the relevant mechanism is: OSPF uses its own IP protocol for routing messages rather than TCP port sessions.
A control-plane policy blocks OSPF IP protocol 89 on one link even though TCP and ICMP connectivity are healthy. If the team bypasses or fails to implement the targeted correction (Permit the narrowly scoped OSPF control protocol traffic between authorized adjacent routers.), which direct operational risk or residual exposure is MOST relevant?
A firewall that allows only TCP and ICMP can block OSPF while giving misleading reachability tests. This is the consequence linked to the observed situation: A control-plane policy blocks OSPF IP protocol 89 on one link even though TCP and ICMP connectivity are healthy. It is prevented by: Permit the narrowly scoped OSPF control protocol traffic between authorized adjacent routers. The underlying reason is: OSPF uses its own IP protocol for routing messages rather than TCP port sessions.
Blindly raising timers can mask congestion rather than resolving recurrent neighbor instability. This risk belongs to a different operational problem: An OSPF neighbor repeatedly resets because a saturated control plane delays Hellos beyond the configured Dead timer. The stated condition instead exposes this direct risk: A firewall that allows only TCP and ICMP can block OSPF while giving misleading reachability tests. The appropriate mitigation is: Permit the narrowly scoped OSPF control protocol traffic between authorized adjacent routers.
Assuming ping success proves LSDB correctness can leave SPF decisions inconsistent. This risk belongs to a different operational problem: Two adjacent OSPF ABRs have different LSDB checksums after a link flap, while operational staff look only at interface ping success. The stated condition instead exposes this direct risk: A firewall that allows only TCP and ICMP can block OSPF while giving misleading reachability tests. The appropriate mitigation is: Permit the narrowly scoped OSPF control protocol traffic between authorized adjacent routers.
Failing to filter redistributed routes expands LSDB size and may expose undesired routes. This risk belongs to a different operational problem: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. The stated condition instead exposes this direct risk: A firewall that allows only TCP and ICMP can block OSPF while giving misleading reachability tests. The appropriate mitigation is: Permit the narrowly scoped OSPF control protocol traffic between authorized adjacent routers.
Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. Which targeted engineering change is MOST directly justified by the observed evidence?
Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection. This change specifically addresses the reported evidence: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. The relevant protocol mechanism is: Junos BGP compares higher LOCAL_PREF before shorter AS-path in ordinary best-path selection. A decisive acceptance test would be: The best-path display chooses ISP-A when reachability and earlier selection criteria are satisfied.
Check Junos BGP selection order and the IGP cost to each reachable next hop. This is a valid solution to a different Junos situation: The enterprise wants to steer traffic toward the upstream with lower IGP cost only after local preference and AS-path checks tie. It does not directly correct the specific failure evidence here: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. The required targeted change is: Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection.
Restore a usable unicast route to the BGP next hop before trying to override local preference. This is a valid solution to a different Junos situation: A route from an EBGP peer shows a valid next-hop address that cannot be resolved to any active transport route. It does not directly correct the specific failure evidence here: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. The required targeted change is: Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection.
Assess MED eligibility and comparison rules before choosing a policy that treats MED as universal. This is a valid solution to a different Junos situation: A supplier sends a BGP route with a MED that is intended only for comparison among paths received from the same neighboring AS. It does not directly correct the specific failure evidence here: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. The required targeted change is: Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection.
Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. The proposed correction is: Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection. Which observation MOST directly confirms this fault is resolved?
The best-path display chooses ISP-A when reachability and earlier selection criteria are satisfied. This is the direct acceptance evidence for the observed failure: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. The mechanism being validated is: Junos BGP compares higher LOCAL_PREF before shorter AS-path in ordinary best-path selection.
The path with one AS hop becomes the BGP best path under the controlled comparison. That would validate a different condition: Two BGP routes are equal in local preference, but one includes three AS hops and the other one, and no earlier attribute resolves the comparison. The decisive check for the current issue is: The best-path display chooses ISP-A when reachability and earlier selection criteria are satisfied.
IBGP speakers select the preferred primary egress consistently for the target prefixes. That would validate a different condition: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. The decisive check for the current issue is: The best-path display chooses ISP-A when reachability and earlier selection criteria are satisfied.
The peer establishes its TCP session and enters Established with received NLRI. That would validate a different condition: A new BGP neighbor is stuck in Active despite a valid static route to its IP address, and TCP port 179 is blocked on the transit firewall. The decisive check for the current issue is: The best-path display chooses ISP-A when reachability and earlier selection criteria are satisfied.
A Junos engineer proposes this response: Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection. The situation is: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. Which technical principle BEST justifies the response?
Junos BGP compares higher LOCAL_PREF before shorter AS-path in ordinary best-path selection. This is the controlling mechanism in the specific case: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. It predicts the acceptance result: The best-path display chooses ISP-A when reachability and earlier selection criteria are satisfied.
BGP AS-path length acts as a path-selection discriminator after local preference. This principle explains a separate situation: Two BGP routes are equal in local preference, but one includes three AS hops and the other one, and no earlier attribute resolves the comparison. For this issue the relevant mechanism is: Junos BGP compares higher LOCAL_PREF before shorter AS-path in ordinary best-path selection.
LOCAL_PREF is propagated inside the AS and selects the preferred external exit among reachable paths. This principle explains a separate situation: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. For this issue the relevant mechanism is: Junos BGP compares higher LOCAL_PREF before shorter AS-path in ordinary best-path selection.
BGP establishes a reliable TCP transport session before exchanging routing updates. This principle explains a separate situation: A new BGP neighbor is stuck in Active despite a valid static route to its IP address, and TCP port 179 is blocked on the transit firewall. For this issue the relevant mechanism is: Junos BGP compares higher LOCAL_PREF before shorter AS-path in ordinary best-path selection.
Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. If the team bypasses or fails to implement the targeted correction (Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection.), which direct operational risk or residual exposure is MOST relevant?
Ignoring local preference can produce a wrong expected egress and incorrect policy remediation. This is the consequence linked to the observed situation: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. It is prevented by: Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection. The underlying reason is: Junos BGP compares higher LOCAL_PREF before shorter AS-path in ordinary best-path selection.
Ignoring AS-path differences can produce a different best path than policy designers expect. This risk belongs to a different operational problem: Two BGP routes are equal in local preference, but one includes three AS hops and the other one, and no earlier attribute resolves the comparison. The stated condition instead exposes this direct risk: Ignoring local preference can produce a wrong expected egress and incorrect policy remediation. The appropriate mitigation is: Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection.
Adjusting only MED on external advertisements may not control the enterprise's own outbound choice. This risk belongs to a different operational problem: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. The stated condition instead exposes this direct risk: Ignoring local preference can produce a wrong expected egress and incorrect policy remediation. The appropriate mitigation is: Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection.
Changing route attributes cannot repair a transport ACL blocking BGP's TCP connection. This risk belongs to a different operational problem: A new BGP neighbor is stuck in Active despite a valid static route to its IP address, and TCP port 179 is blocked on the transit firewall. The stated condition instead exposes this direct risk: Ignoring local preference can produce a wrong expected egress and incorrect policy remediation. The appropriate mitigation is: Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection.
An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. Which targeted engineering change is MOST directly justified by the observed evidence?
Assign a higher local preference to the primary ISP routes at ingress and propagate it internally. This change specifically addresses the reported evidence: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. The relevant protocol mechanism is: LOCAL_PREF is propagated inside the AS and selects the preferred external exit among reachable paths. A decisive acceptance test would be: IBGP speakers select the preferred primary egress consistently for the target prefixes.
Prefer the valid path with higher local preference before comparing AS-path length under Junos BGP selection. This is a valid solution to a different Junos situation: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. It does not directly correct the specific failure evidence here: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. The required targeted change is: Assign a higher local preference to the primary ISP routes at ingress and propagate it internally.
Apply controlled AS-path prepending on the applicable outbound advertisement to that external peer. This is a valid solution to a different Junos situation: The team needs to make an inbound path from one external peer less attractive to another AS without changing its own internal preference. It does not directly correct the specific failure evidence here: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. The required targeted change is: Assign a higher local preference to the primary ISP routes at ingress and propagate it internally.
Trigger and verify an appropriate policy refresh or update mechanism supported by the BGP peers. This is a valid solution to a different Junos situation: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. It does not directly correct the specific failure evidence here: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. The required targeted change is: Assign a higher local preference to the primary ISP routes at ingress and propagate it internally.
An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. The proposed correction is: Assign a higher local preference to the primary ISP routes at ingress and propagate it internally. Which observation MOST directly confirms this fault is resolved?
IBGP speakers select the preferred primary egress consistently for the target prefixes. This is the direct acceptance evidence for the observed failure: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. The mechanism being validated is: LOCAL_PREF is propagated inside the AS and selects the preferred external exit among reachable paths.
The best-path display chooses ISP-A when reachability and earlier selection criteria are satisfied. That would validate a different condition: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. The decisive check for the current issue is: IBGP speakers select the preferred primary egress consistently for the target prefixes.
The remote AS sees the intended additional AS hops and its chosen inbound path changes where policy permits. That would validate a different condition: The team needs to make an inbound path from one external peer less attractive to another AS without changing its own internal preference. The decisive check for the current issue is: IBGP speakers select the preferred primary egress consistently for the target prefixes.
The downstream advertised route shows the updated community without unplanned neighbor disruption. That would validate a different condition: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. The decisive check for the current issue is: IBGP speakers select the preferred primary egress consistently for the target prefixes.
A Junos engineer proposes this response: Assign a higher local preference to the primary ISP routes at ingress and propagate it internally. The situation is: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. Which technical principle BEST justifies the response?
LOCAL_PREF is propagated inside the AS and selects the preferred external exit among reachable paths. This is the controlling mechanism in the specific case: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. It predicts the acceptance result: IBGP speakers select the preferred primary egress consistently for the target prefixes.
Junos BGP compares higher LOCAL_PREF before shorter AS-path in ordinary best-path selection. This principle explains a separate situation: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. For this issue the relevant mechanism is: LOCAL_PREF is propagated inside the AS and selects the preferred external exit among reachable paths.
AS-path prepending can influence remote path choice but does not guarantee it overrides remote local preference. This principle explains a separate situation: The team needs to make an inbound path from one external peer less attractive to another AS without changing its own internal preference. For this issue the relevant mechanism is: LOCAL_PREF is propagated inside the AS and selects the preferred external exit among reachable paths.
BGP advertisements reflect routing policy and may require controlled re-evaluation after changes. This principle explains a separate situation: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. For this issue the relevant mechanism is: LOCAL_PREF is propagated inside the AS and selects the preferred external exit among reachable paths.
An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. If the team bypasses or fails to implement the targeted correction (Assign a higher local preference to the primary ISP routes at ingress and propagate it internally.), which direct operational risk or residual exposure is MOST relevant?
Adjusting only MED on external advertisements may not control the enterprise's own outbound choice. This is the consequence linked to the observed situation: An enterprise wants every internal BGP router to favor the primary upstream even though that primary route traverses more external autonomous systems. It is prevented by: Assign a higher local preference to the primary ISP routes at ingress and propagate it internally. The underlying reason is: LOCAL_PREF is propagated inside the AS and selects the preferred external exit among reachable paths.
Ignoring local preference can produce a wrong expected egress and incorrect policy remediation. This risk belongs to a different operational problem: Two valid BGP paths for one prefix have different local preference attributes, 180 on ISP-A and 100 on ISP-B, but the operator chooses the shorter AS path on B. The stated condition instead exposes this direct risk: Adjusting only MED on external advertisements may not control the enterprise's own outbound choice. The appropriate mitigation is: Assign a higher local preference to the primary ISP routes at ingress and propagate it internally.
Assuming prepending always wins can leave traffic using the undesired upstream during congestion. This risk belongs to a different operational problem: The team needs to make an inbound path from one external peer less attractive to another AS without changing its own internal preference. The stated condition instead exposes this direct risk: Adjusting only MED on external advertisements may not control the enterprise's own outbound choice. The appropriate mitigation is: Assign a higher local preference to the primary ISP routes at ingress and propagate it internally.
Assuming a locally changed policy is already reflected remotely can conceal stale announcements. This risk belongs to a different operational problem: A new BGP policy changes outbound community values, but previously advertised routes still display old metadata at the downstream peer. The stated condition instead exposes this direct risk: Adjusting only MED on external advertisements may not control the enterprise's own outbound choice. The appropriate mitigation is: Assign a higher local preference to the primary ISP routes at ingress and propagate it internally.
Please check your mailbox for a message from support@examlabs.com and follow the directions.