JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
Two OSPF links carry the same prefix and traffic should use the lower-cost interface rather than the higher-bandwidth interface selected by intuition. If the team bypasses or fails to implement the targeted correction (Compare configured OSPF interface metrics and choose the intended shortest-path costs explicitly.), which direct operational risk or residual exposure is MOST relevant?
Leaving inconsistent costs can steer traffic onto a congested or operationally unintended path. This is the consequence linked to the observed situation: Two OSPF links carry the same prefix and traffic should use the lower-cost interface rather than the higher-bandwidth interface selected by intuition. It is prevented by: Compare configured OSPF interface metrics and choose the intended shortest-path costs explicitly. The underlying reason is: OSPF's SPF route selection uses accumulated link costs rather than nominal interface speed alone.
Assuming a changed priority immediately preempts the existing DR can leave the old election result unchanged. This risk belongs to a different operational problem: A multiaccess OSPF LAN has the wrong device acting as designated router after an access switch was replaced. The stated condition instead exposes this direct risk: Leaving inconsistent costs can steer traffic onto a congested or operationally unintended path. The appropriate mitigation is: Compare configured OSPF interface metrics and choose the intended shortest-path costs explicitly.
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: Leaving inconsistent costs can steer traffic onto a congested or operationally unintended path. The appropriate mitigation is: Compare configured OSPF interface metrics and choose the intended shortest-path costs explicitly.
Troubleshooting only the OSPFv2 IPv4 instance can miss an entirely absent OSPFv3 adjacency. This risk belongs to a different operational problem: OSPFv3 interfaces advertise IPv6 prefixes, but the operator checks only IPv4 OSPFv2 state while the IPv6 neighbor never appears. The stated condition instead exposes this direct risk: Leaving inconsistent costs can steer traffic onto a congested or operationally unintended path. The appropriate mitigation is: Compare configured OSPF interface metrics and choose the intended shortest-path costs explicitly.
An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. Which targeted engineering change is MOST directly justified by the observed evidence?
Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link. This change specifically addresses the reported evidence: An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. The relevant protocol mechanism is: OSPFv3 neighbors normally exchange control messages using IPv6 link-local addressing. A decisive acceptance test would be: A capture shows IPv6 link-local Hellos and an OSPFv3 peer appears as expected.
Verify OSPFv3 protocol and interface participation using IPv6-aware neighbor and route output. This is a valid solution to a different Junos situation: OSPFv3 interfaces advertise IPv6 prefixes, but the operator checks only IPv4 OSPFv2 state while the IPv6 neighbor never appears. It does not directly correct the specific failure evidence here: An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. The required targeted change is: Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link.
Check inter-area prefix LSAs and ABR route policy rather than assuming the missing prefixes are in router LSAs. This is a valid solution to a different Junos situation: OSPFv3 has a stable neighbor but IPv6 destination prefixes learned from another area never appear in routing output. It does not directly correct the specific failure evidence here: An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. The required targeted change is: Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link.
Match the Hello and Dead interval values across both ends of the intended OSPF adjacency. This is a valid solution to a different Junos situation: A pair of OSPFv2 routers on the same broadcast segment receive Hellos but remain unable to form an adjacency because one uses a 5-second Hello interval and the other 10 seconds. It does not directly correct the specific failure evidence here: An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. The required targeted change is: Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link.
An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. The proposed correction is: Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link. Which observation MOST directly confirms this fault is resolved?
A capture shows IPv6 link-local Hellos and an OSPFv3 peer appears as expected. This is the direct acceptance evidence for the observed failure: An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. The mechanism being validated is: OSPFv3 neighbors normally exchange control messages using IPv6 link-local addressing.
Each peer appears under a distinct router ID and its link-state advertisements remain unambiguous. That would validate a different condition: Two OSPFv3 peers have valid routed IPv6 connectivity but advertise duplicate router IDs during adjacency startup. The decisive check for the current issue is: A capture shows IPv6 link-local Hellos and an OSPFv3 peer appears as expected.
The NSSA advertises its approved type-7 externals and ABR translation behaves as designed. That would validate a different condition: A branch OSPF stub area must import selected external routes from its local ASBR without carrying all external type-5 LSAs. The decisive check for the current issue is: A capture shows IPv6 link-local Hellos and an OSPFv3 peer appears as expected.
Authenticated OSPF Hellos are accepted and the peer database reaches Full. That would validate a different condition: A secure OSPFv2 transit link stops accepting neighbor packets after a key-roll event; captures show incompatible configured authentication secrets. The decisive check for the current issue is: A capture shows IPv6 link-local Hellos and an OSPFv3 peer appears as expected.
A Junos engineer proposes this response: Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link. The situation is: An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. Which technical principle BEST justifies the response?
OSPFv3 neighbors normally exchange control messages using IPv6 link-local addressing. This is the controlling mechanism in the specific case: An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. It predicts the acceptance result: A capture shows IPv6 link-local Hellos and an OSPFv3 peer appears as expected.
OSPFv3 uses an IPv4-formatted 32-bit router ID even when exchanging IPv6 routes. This principle explains a separate situation: Two OSPFv3 peers have valid routed IPv6 connectivity but advertise duplicate router IDs during adjacency startup. For this issue the relevant mechanism is: OSPFv3 neighbors normally exchange control messages using IPv6 link-local addressing.
NSSA supports controlled external route origination using type-7 LSAs in a stub-like area. This principle explains a separate situation: A branch OSPF stub area must import selected external routes from its local ASBR without carrying all external type-5 LSAs. For this issue the relevant mechanism is: OSPFv3 neighbors normally exchange control messages using IPv6 link-local addressing.
OSPFv2 authenticated adjacencies validate received packet authentication before using them. This principle explains a separate situation: A secure OSPFv2 transit link stops accepting neighbor packets after a key-roll event; captures show incompatible configured authentication secrets. For this issue the relevant mechanism is: OSPFv3 neighbors normally exchange control messages using IPv6 link-local addressing.
An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. If the team bypasses or fails to implement the targeted correction (Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link.), which direct operational risk or residual exposure is MOST relevant?
Global IPv6 reachability by itself does not establish an OSPFv3 routing adjacency. This is the consequence linked to the observed situation: An OSPFv3 edge interface has a valid global IPv6 address but no exchange of OSPFv3 Hellos is observed. It is prevented by: Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link. The underlying reason is: OSPFv3 neighbors normally exchange control messages using IPv6 link-local addressing.
Troubleshooting only the OSPFv2 IPv4 instance can miss an entirely absent OSPFv3 adjacency. This risk belongs to a different operational problem: OSPFv3 interfaces advertise IPv6 prefixes, but the operator checks only IPv4 OSPFv2 state while the IPv6 neighbor never appears. The stated condition instead exposes this direct risk: Global IPv6 reachability by itself does not establish an OSPFv3 routing adjacency. The appropriate mitigation is: Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link.
Looking only for IPv6 prefixes in OSPFv3 router LSAs can hide the actual prefix propagation problem. This risk belongs to a different operational problem: OSPFv3 has a stable neighbor but IPv6 destination prefixes learned from another area never appear in routing output. The stated condition instead exposes this direct risk: Global IPv6 reachability by itself does not establish an OSPFv3 routing adjacency. The appropriate mitigation is: Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link.
An unresolved Hello interval mismatch prevents the routers exchanging a synchronized LSDB. This risk belongs to a different operational problem: A pair of OSPFv2 routers on the same broadcast segment receive Hellos but remain unable to form an adjacency because one uses a 5-second Hello interval and the other 10 seconds. The stated condition instead exposes this direct risk: Global IPv6 reachability by itself does not establish an OSPFv3 routing adjacency. The appropriate mitigation is: Verify OSPFv3 activation and permitted IPv6 link-local multicast signaling on that link.
After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. Which targeted engineering change is MOST directly justified by the observed evidence?
Check Junos OSPF import policy and route hidden/inactive reasons in the routing table. This change specifically addresses the reported evidence: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. The relevant protocol mechanism is: Junos import policies and route selection can affect installation independently of LSDB adjacency. A decisive acceptance test would be: A permitted candidate installs in inet.0 or reveals an explicit, intended policy rejection.
Check inter-area prefix LSAs and ABR route policy rather than assuming the missing prefixes are in router LSAs. This is a valid solution to a different Junos situation: OSPFv3 has a stable neighbor but IPv6 destination prefixes learned from another area never appear in routing output. It does not directly correct the specific failure evidence here: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. The required targeted change is: Check Junos OSPF import policy and route hidden/inactive reasons in the routing table.
Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term. This is a valid solution to a different Junos situation: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. It does not directly correct the specific failure evidence here: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. The required targeted change is: Check Junos OSPF import policy and route hidden/inactive reasons in the routing table.
Synchronize the supported OSPF authentication type, key identifier, and shared secret on both sides. This is a valid solution to a different Junos situation: A secure OSPFv2 transit link stops accepting neighbor packets after a key-roll event; captures show incompatible configured authentication secrets. It does not directly correct the specific failure evidence here: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. The required targeted change is: Check Junos OSPF import policy and route hidden/inactive reasons in the routing table.
After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. The proposed correction is: Check Junos OSPF import policy and route hidden/inactive reasons in the routing table. Which observation MOST directly confirms this fault is resolved?
A permitted candidate installs in inet.0 or reveals an explicit, intended policy rejection. This is the direct acceptance evidence for the observed failure: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. The mechanism being validated is: Junos import policies and route selection can affect installation independently of LSDB adjacency.
The appropriate inter-area-prefix LSAs and accepted IPv6 routes appear for target networks. That would validate a different condition: OSPFv3 has a stable neighbor but IPv6 destination prefixes learned from another area never appear in routing output. The decisive check for the current issue is: A permitted candidate installs in inet.0 or reveals an explicit, intended policy rejection.
Only the two authorized loopbacks appear as externally originated routes downstream. That would validate a different condition: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. The decisive check for the current issue is: A permitted candidate installs in inet.0 or reveals an explicit, intended policy rejection.
Authenticated OSPF Hellos are accepted and the peer database reaches Full. That would validate a different condition: A secure OSPFv2 transit link stops accepting neighbor packets after a key-roll event; captures show incompatible configured authentication secrets. The decisive check for the current issue is: A permitted candidate installs in inet.0 or reveals an explicit, intended policy rejection.
A Junos engineer proposes this response: Check Junos OSPF import policy and route hidden/inactive reasons in the routing table. The situation is: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. Which technical principle BEST justifies the response?
Junos import policies and route selection can affect installation independently of LSDB adjacency. This is the controlling mechanism in the specific case: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. It predicts the acceptance result: A permitted candidate installs in inet.0 or reveals an explicit, intended policy rejection.
OSPFv3 separates topology information from IPv6 prefix information in dedicated LSA types. This principle explains a separate situation: OSPFv3 has a stable neighbor but IPv6 destination prefixes learned from another area never appear in routing output. For this issue the relevant mechanism is: Junos import policies and route selection can affect installation independently of LSDB adjacency.
Routing policy matches route attributes and explicitly controls redistribution acceptance. This principle explains a separate situation: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. For this issue the relevant mechanism is: Junos import policies and route selection can affect installation independently of LSDB adjacency.
OSPFv2 authenticated adjacencies validate received packet authentication before using them. This principle explains a separate situation: A secure OSPFv2 transit link stops accepting neighbor packets after a key-roll event; captures show incompatible configured authentication secrets. For this issue the relevant mechanism is: Junos import policies and route selection can affect installation independently of LSDB adjacency.
After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. If the team bypasses or fails to implement the targeted correction (Check Junos OSPF import policy and route hidden/inactive reasons in the routing table.), which direct operational risk or residual exposure is MOST relevant?
Restarting healthy neighbors cannot correct a routing policy that rejects desired learned routes. This is the consequence linked to the observed situation: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. It is prevented by: Check Junos OSPF import policy and route hidden/inactive reasons in the routing table. The underlying reason is: Junos import policies and route selection can affect installation independently of LSDB adjacency.
Looking only for IPv6 prefixes in OSPFv3 router LSAs can hide the actual prefix propagation problem. This risk belongs to a different operational problem: OSPFv3 has a stable neighbor but IPv6 destination prefixes learned from another area never appear in routing output. The stated condition instead exposes this direct risk: Restarting healthy neighbors cannot correct a routing policy that rejects desired learned routes. The appropriate mitigation is: Check Junos OSPF import policy and route hidden/inactive reasons in the routing table.
Using a catchall accept may accidentally advertise static routes used for management or blackholes. This risk belongs to a different operational problem: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. The stated condition instead exposes this direct risk: Restarting healthy neighbors cannot correct a routing policy that rejects desired learned routes. The appropriate mitigation is: Check Junos OSPF import policy and route hidden/inactive reasons in the routing table.
Changing interface metrics does not repair authentication failures and can leave routing disconnected. This risk belongs to a different operational problem: A secure OSPFv2 transit link stops accepting neighbor packets after a key-roll event; captures show incompatible configured authentication secrets. The stated condition instead exposes this direct risk: Restarting healthy neighbors cannot correct a routing policy that rejects desired learned routes. The appropriate mitigation is: Check Junos OSPF import policy and route hidden/inactive reasons in the routing table.
A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. Which targeted engineering change is MOST directly justified by the observed evidence?
Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term. This change specifically addresses the reported evidence: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. The relevant protocol mechanism is: Routing policy matches route attributes and explicitly controls redistribution acceptance. A decisive acceptance test would be: Only the two authorized loopbacks appear as externally originated routes downstream.
Check inter-area prefix LSAs and ABR route policy rather than assuming the missing prefixes are in router LSAs. This is a valid solution to a different Junos situation: OSPFv3 has a stable neighbor but IPv6 destination prefixes learned from another area never appear in routing output. It does not directly correct the specific failure evidence here: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. The required targeted change is: Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term.
Apply an explicit Junos export policy to select and reject the appropriate redistributed routes at the ASBR. This is a valid solution to a different Junos situation: The OSPF database contains an external /24 that operations never intended to leak from a branch redistribution boundary. It does not directly correct the specific failure evidence here: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. The required targeted change is: Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term.
Permit the narrowly scoped OSPF control protocol traffic between authorized adjacent routers. This is a valid solution to a different Junos situation: A control-plane policy blocks OSPF IP protocol 89 on one link even though TCP and ICMP connectivity are healthy. It does not directly correct the specific failure evidence here: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. The required targeted change is: Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term.
A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. The proposed correction is: Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term. Which observation MOST directly confirms this fault is resolved?
Only the two authorized loopbacks appear as externally originated routes downstream. This is the direct acceptance evidence for the observed failure: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. The mechanism being validated is: Routing policy matches route attributes and explicitly controls redistribution acceptance.
The appropriate inter-area-prefix LSAs and accepted IPv6 routes appear for target networks. That would validate a different condition: OSPFv3 has a stable neighbor but IPv6 destination prefixes learned from another area never appear in routing output. The decisive check for the current issue is: Only the two authorized loopbacks appear as externally originated routes downstream.
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: Only the two authorized loopbacks appear as externally originated routes downstream.
The access subnet appears in the LSDB and no OSPF neighbors form on the edge-facing LAN. That would validate a different condition: A branch requires OSPF reachability to its attached access LAN but must not form router adjacencies with random hosts on that LAN. The decisive check for the current issue is: Only the two authorized loopbacks appear as externally originated routes downstream.
Please check your mailbox for a message from support@examlabs.com and follow the directions.