JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
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.
A Junos engineer proposes this response: Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term. The situation is: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. Which technical principle BEST justifies the response?
Routing policy matches route attributes and explicitly controls redistribution acceptance. This is the controlling mechanism in the specific case: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. It predicts the acceptance result: Only the two authorized loopbacks appear as externally originated routes downstream.
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: Routing policy matches route attributes and explicitly controls redistribution acceptance.
OSPF export policy controls which eligible non-OSPF routes are injected into the OSPF domain. This principle explains a separate situation: The OSPF database contains an external /24 that operations never intended to leak from a branch redistribution boundary. For this issue the relevant mechanism is: Routing policy matches route attributes and explicitly controls redistribution acceptance.
OSPF uses its own IP protocol for routing messages rather than TCP port sessions. This principle explains a separate situation: A control-plane policy blocks OSPF IP protocol 89 on one link even though TCP and ICMP connectivity are healthy. For this issue the relevant mechanism is: Routing policy matches route attributes and explicitly controls redistribution acceptance.
A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. If the team bypasses or fails to implement the targeted correction (Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term.), which direct operational risk or residual exposure is MOST relevant?
Using a catchall accept may accidentally advertise static routes used for management or blackholes. This is the consequence linked to the observed situation: A routing engineer wants to export exactly two loopback prefixes from static routes into OSPF, not the entire static route table. It is prevented by: Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term. The underlying reason is: Routing policy matches route attributes and explicitly controls redistribution acceptance.
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: Using a catchall accept may accidentally advertise static routes used for management or blackholes. The appropriate mitigation is: Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term.
Unrestricted redistribution can advertise unintended infrastructure reachability to every attached area. This risk belongs to a different operational problem: The OSPF database contains an external /24 that operations never intended to leak from a branch redistribution boundary. The stated condition instead exposes this direct risk: Using a catchall accept may accidentally advertise static routes used for management or blackholes. The appropriate mitigation is: Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term.
A firewall that allows only TCP and ICMP can block OSPF while giving misleading reachability tests. This risk belongs to a different operational problem: A control-plane policy blocks OSPF IP protocol 89 on one link even though TCP and ICMP connectivity are healthy. The stated condition instead exposes this direct risk: Using a catchall accept may accidentally advertise static routes used for management or blackholes. The appropriate mitigation is: Build a term-based export policy matching those exact prefix filters and add a rejecting terminal term.
An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. Which targeted engineering change is MOST directly justified by the observed evidence?
Examine the responsible ABR area-range configuration and the contributing active routes. This change specifically addresses the reported evidence: An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. The relevant protocol mechanism is: Inter-area summary generation depends on area boundary configuration and eligible contributors. A decisive acceptance test would be: The partner sees an aggregate covering precisely the intended networks, with valid contributors.
Design a supported OSPF virtual link over the common nonstub transit area and document its operational dependence. This is a valid solution to a different Junos situation: A remote OSPF area has no physical connection to backbone area 0, and a permitted common transit area exists between its ABR and a backbone ABR. It does not directly correct the specific failure evidence here: An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. The required targeted change is: Examine the responsible ABR area-range configuration and the contributing active routes.
Change the topology design to a compatible NSSA and originate permitted external routes there. This is a valid solution to a different Junos situation: A branch OSPF stub area must import selected external routes from its local ASBR without carrying all external type-5 LSAs. It does not directly correct the specific failure evidence here: An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. The required targeted change is: Examine the responsible ABR area-range configuration and the contributing active routes.
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: An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. The required targeted change is: Examine the responsible ABR area-range configuration and the contributing active routes.
An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. The proposed correction is: Examine the responsible ABR area-range configuration and the contributing active routes. Which observation MOST directly confirms this fault is resolved?
The partner sees an aggregate covering precisely the intended networks, with valid contributors. This is the direct acceptance evidence for the observed failure: An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. The mechanism being validated is: Inter-area summary generation depends on area boundary configuration and eligible contributors.
Adjacent areas learn the expected aggregate while specific routes remain visible inside the originating area. That would validate a different condition: An enterprise intends to carry summarized inter-area OSPF reachability rather than thousands of individual branch loopback routes. The decisive check for the current issue is: The partner sees an aggregate covering precisely the intended networks, with valid contributors.
A permitted candidate installs in inet.0 or reveals an explicit, intended policy rejection. That would validate a different condition: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. The decisive check for the current issue is: The partner sees an aggregate covering precisely the intended networks, with valid contributors.
Only the allowlisted external prefixes appear in downstream external LSAs. That would validate a different condition: The OSPF database contains an external /24 that operations never intended to leak from a branch redistribution boundary. The decisive check for the current issue is: The partner sees an aggregate covering precisely the intended networks, with valid contributors.
A Junos engineer proposes this response: Examine the responsible ABR area-range configuration and the contributing active routes. The situation is: An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. Which technical principle BEST justifies the response?
Inter-area summary generation depends on area boundary configuration and eligible contributors. This is the controlling mechanism in the specific case: An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. It predicts the acceptance result: The partner sees an aggregate covering precisely the intended networks, with valid contributors.
OSPF virtual links can logically connect an area to the backbone through a qualifying transit area. This principle explains a separate situation: A remote OSPF area has no physical connection to backbone area 0, and a permitted common transit area exists between its ABR and a backbone ABR. For this issue the relevant mechanism is: Inter-area summary generation depends on area boundary configuration and eligible contributors.
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: Inter-area summary generation depends on area boundary configuration and eligible contributors.
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: Inter-area summary generation depends on area boundary configuration and eligible contributors.
An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. If the team bypasses or fails to implement the targeted correction (Examine the responsible ABR area-range configuration and the contributing active routes.), which direct operational risk or residual exposure is MOST relevant?
Announcing a summary with no valid covered next hops can create forwarding black holes. This is the consequence linked to the observed situation: An OSPFv2 adjacency to an external partner remains Full, but the partner expects a summarized route that the ABR is not advertising. It is prevented by: Examine the responsible ABR area-range configuration and the contributing active routes. The underlying reason is: Inter-area summary generation depends on area boundary configuration and eligible contributors.
Overly broad summaries can blackhole addresses if reachability coverage is not verified. This risk belongs to a different operational problem: An enterprise intends to carry summarized inter-area OSPF reachability rather than thousands of individual branch loopback routes. The stated condition instead exposes this direct risk: Announcing a summary with no valid covered next hops can create forwarding black holes. The appropriate mitigation is: Examine the responsible ABR area-range configuration and the contributing active routes.
Restarting healthy neighbors cannot correct a routing policy that rejects desired learned routes. This risk belongs to a different operational problem: After a maintenance change, OSPFv2 routes vanish from inet.0 but the protocol neighbor remains Full and LSAs are present. The stated condition instead exposes this direct risk: Announcing a summary with no valid covered next hops can create forwarding black holes. The appropriate mitigation is: Examine the responsible ABR area-range configuration and the contributing active routes.
Unrestricted redistribution can advertise unintended infrastructure reachability to every attached area. This risk belongs to a different operational problem: The OSPF database contains an external /24 that operations never intended to leak from a branch redistribution boundary. The stated condition instead exposes this direct risk: Announcing a summary with no valid covered next hops can create forwarding black holes. The appropriate mitigation is: Examine the responsible ABR area-range configuration and the contributing active routes.
A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. Which targeted engineering change is MOST directly justified by the observed evidence?
Constrain the ASBR's export policy to defined route families and inspect the changed LSA database. This change specifically addresses the reported evidence: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. The relevant protocol mechanism is: Type-5 external LSAs distribute AS-external reachability across eligible OSPF areas. A decisive acceptance test would be: The area LSDB includes only approved external advertisements after flooding settles.
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 core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. The required targeted change is: Constrain the ASBR's export policy to defined route families and inspect the changed LSA database.
Inspect Junos route preference values and the candidate route flags before manipulating OSPF protocol cost. This is a valid solution to a different Junos situation: A router receives an OSPF external route but the design requires preferring a directly connected duplicate destination from a separate source. It does not directly correct the specific failure evidence here: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. The required targeted change is: Constrain the ASBR's export policy to defined route families and inspect the changed LSA database.
Make the stub-area configuration consistent across every router attached to that area. This is a valid solution to a different Junos situation: An OSPFv2 area is designed as stub but one internal router still treats it as a normal area, preventing stable neighbor operation. It does not directly correct the specific failure evidence here: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. The required targeted change is: Constrain the ASBR's export policy to defined route families and inspect the changed LSA database.
A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. The proposed correction is: Constrain the ASBR's export policy to defined route families and inspect the changed LSA database. Which observation MOST directly confirms this fault is resolved?
The area LSDB includes only approved external advertisements after flooding settles. This is the direct acceptance evidence for the observed failure: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. The mechanism being validated is: Type-5 external LSAs distribute AS-external reachability across eligible OSPF areas.
Only the allowlisted external prefixes appear in downstream external LSAs. That would validate a different condition: The OSPF database contains an external /24 that operations never intended to leak from a branch redistribution boundary. The decisive check for the current issue is: The area LSDB includes only approved external advertisements after flooding settles.
The active RIB route and forwarding entry identify the intended preferred protocol origin. That would validate a different condition: A router receives an OSPF external route but the design requires preferring a directly connected duplicate destination from a separate source. The decisive check for the current issue is: The area LSDB includes only approved external advertisements after flooding settles.
Neighbor adjacencies are Full and the stub area avoids the prohibited external LSA advertisements. That would validate a different condition: An OSPFv2 area is designed as stub but one internal router still treats it as a normal area, preventing stable neighbor operation. The decisive check for the current issue is: The area LSDB includes only approved external advertisements after flooding settles.
A Junos engineer proposes this response: Constrain the ASBR's export policy to defined route families and inspect the changed LSA database. The situation is: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. Which technical principle BEST justifies the response?
Type-5 external LSAs distribute AS-external reachability across eligible OSPF areas. This is the controlling mechanism in the specific case: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. It predicts the acceptance result: The area LSDB includes only approved external advertisements after flooding settles.
OSPF export policy controls which eligible non-OSPF routes are injected into the OSPF domain. This principle explains a separate situation: The OSPF database contains an external /24 that operations never intended to leak from a branch redistribution boundary. For this issue the relevant mechanism is: Type-5 external LSAs distribute AS-external reachability across eligible OSPF areas.
Junos chooses the active route across protocols by route preference before forwarding installation. This principle explains a separate situation: A router receives an OSPF external route but the design requires preferring a directly connected duplicate destination from a separate source. For this issue the relevant mechanism is: Type-5 external LSAs distribute AS-external reachability across eligible OSPF areas.
The OSPF stub capability must agree among routers in the same area. This principle explains a separate situation: An OSPFv2 area is designed as stub but one internal router still treats it as a normal area, preventing stable neighbor operation. For this issue the relevant mechanism is: Type-5 external LSAs distribute AS-external reachability across eligible OSPF areas.
A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. If the team bypasses or fails to implement the targeted correction (Constrain the ASBR's export policy to defined route families and inspect the changed LSA database.), which direct operational risk or residual exposure is MOST relevant?
Failing to filter redistributed routes expands LSDB size and may expose undesired routes. This is the consequence linked to the observed situation: A core OSPF area receives far too many type-5 external advertisements after a redistribution expansion. It is prevented by: Constrain the ASBR's export policy to defined route families and inspect the changed LSA database. The underlying reason is: Type-5 external LSAs distribute AS-external reachability across eligible OSPF areas.
Unrestricted redistribution can advertise unintended infrastructure reachability to every attached area. This risk belongs to a different operational problem: The OSPF database contains an external /24 that operations never intended to leak from a branch redistribution boundary. The stated condition instead exposes this direct risk: Failing to filter redistributed routes expands LSDB size and may expose undesired routes. The appropriate mitigation is: Constrain the ASBR's export policy to defined route families and inspect the changed LSA database.
Changing OSPF cost alone cannot override a more preferred connected route for the same prefix. This risk belongs to a different operational problem: A router receives an OSPF external route but the design requires preferring a directly connected duplicate destination from a separate source. The stated condition instead exposes this direct risk: Failing to filter redistributed routes expands LSDB size and may expose undesired routes. The appropriate mitigation is: Constrain the ASBR's export policy to defined route families and inspect the changed LSA database.
A mismatched area capability or external LSA leakage prevents intended stub operation. This risk belongs to a different operational problem: An OSPFv2 area is designed as stub but one internal router still treats it as a normal area, preventing stable neighbor operation. The stated condition instead exposes this direct risk: Failing to filter redistributed routes expands LSDB size and may expose undesired routes. The appropriate mitigation is: Constrain the ASBR's export policy to defined route families and inspect the changed LSA database.
Please check your mailbox for a message from support@examlabs.com and follow the directions.