JN0-650 Premium File
- 107 Questions & Answers
- Last Update: Nov 8, 2026
A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. If the team bypasses or fails to implement the targeted correction (Use a term-based BGP export policy that matches the authorized active route and accepted prefix.), which direct operational risk or residual exposure is MOST relevant?
An unconditional export can leak prefixes when the intended backing reachability disappears. This is the consequence linked to the observed situation: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. It is prevented by: Use a term-based BGP export policy that matches the authorized active route and accepted prefix. The underlying reason is: Junos BGP export policy controls which locally eligible routes enter peer advertisements.
A permissive final term can leak sensitive topology into external BGP advertisements. This risk belongs to a different operational problem: A BGP edge is advertising an unintended private infrastructure prefix because a catchall export policy term accepted every active route. The stated condition instead exposes this direct risk: An unconditional export can leak prefixes when the intended backing reachability disappears. The appropriate mitigation is: Use a term-based BGP export policy that matches the authorized active route and accepted prefix.
Mixing route families or virtual tables can make reachable prefixes invisible to the intended service. This risk belongs to a different operational problem: A BGP neighbor advertises prefixes but the receiving Junos instance assigns them to the wrong logical routing table because family/instance design differs. The stated condition instead exposes this direct risk: An unconditional export can leak prefixes when the intended backing reachability disappears. The appropriate mitigation is: Use a term-based BGP export policy that matches the authorized active route and accepted prefix.
A working IPv4 BGP session does not imply IPv6 unicast NLRI negotiation is enabled. This risk belongs to a different operational problem: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. The stated condition instead exposes this direct risk: An unconditional export can leak prefixes when the intended backing reachability disappears. The appropriate mitigation is: Use a term-based BGP export policy that matches the authorized active route and accepted prefix.
A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. Which targeted engineering change is MOST directly justified by the observed evidence?
Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes. This change specifically addresses the reported evidence: A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. The relevant protocol mechanism is: Junos BGP import policies filter and modify routes entering the local BGP RIB. A decisive acceptance test would be: The default is absent from eligible BGP routes while specified partner prefixes remain available.
Create a carefully scoped policy that matches the authorized community and applies the intended discard next hop. This is a valid solution to a different Junos situation: A border router receives a route tagged with an expected blackhole community, but no downstream filter implements the associated traffic-handling action. It does not directly correct the specific failure evidence here: A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. The required targeted change is: Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes.
Use a term-based BGP export policy that matches the authorized active route and accepted prefix. This is a valid solution to a different Junos situation: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. It does not directly correct the specific failure evidence here: A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. The required targeted change is: Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes.
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: A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. The required targeted change is: Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes.
A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. The proposed correction is: Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes. Which observation MOST directly confirms this fault is resolved?
The default is absent from eligible BGP routes while specified partner prefixes remain available. This is the direct acceptance evidence for the observed failure: A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. The mechanism being validated is: Junos BGP import policies filter and modify routes entering the local BGP RIB.
The targeted route is installed with a discard treatment, while unrelated routes are unaffected. That would validate a different condition: A border router receives a route tagged with an expected blackhole community, but no downstream filter implements the associated traffic-handling action. The decisive check for the current issue is: The default is absent from eligible BGP routes while specified partner prefixes remain available.
The peer receives precisely the eligible prefix and withdraws it when export conditions fail. That would validate a different condition: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. The decisive check for the current issue is: The default is absent from eligible BGP routes while specified partner prefixes remain available.
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: The default is absent from eligible BGP routes while specified partner prefixes remain available.
A Junos engineer proposes this response: Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes. The situation is: A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. Which technical principle BEST justifies the response?
Junos BGP import policies filter and modify routes entering the local BGP RIB. This is the controlling mechanism in the specific case: A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. It predicts the acceptance result: The default is absent from eligible BGP routes while specified partner prefixes remain available.
Communities signal policy intent; forwarding behavior requires an explicit local action. This principle explains a separate situation: A border router receives a route tagged with an expected blackhole community, but no downstream filter implements the associated traffic-handling action. For this issue the relevant mechanism is: Junos BGP import policies filter and modify routes entering the local BGP RIB.
BGP communities are attachable route tags used by configured routing policies. This principle explains a separate situation: A BGP policy marks customer prefixes with a specific community, but the receiving policy has no match and permits unrestricted redistribution. For this issue the relevant mechanism is: Junos BGP import policies filter and modify routes entering the local BGP RIB.
Extended communities provide structured BGP route metadata for supported applications and policies. This principle explains a separate situation: Two routers share BGP routes but their intended extended-community values are absent at a downstream policy boundary. For this issue the relevant mechanism is: Junos BGP import policies filter and modify routes entering the local BGP RIB.
A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. If the team bypasses or fails to implement the targeted correction (Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes.), which direct operational risk or residual exposure is MOST relevant?
An overly broad accept can introduce an unplanned external default route and divert all traffic. This is the consequence linked to the observed situation: A Junos border router receives a default from a supplier, but company policy requires rejecting that default while accepting partner application networks. It is prevented by: Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes. The underlying reason is: Junos BGP import policies filter and modify routes entering the local BGP RIB.
Treating a community value as a universal automatic security filter leaves unwanted traffic permitted. This risk belongs to a different operational problem: A border router receives a route tagged with an expected blackhole community, but no downstream filter implements the associated traffic-handling action. The stated condition instead exposes this direct risk: An overly broad accept can introduce an unplanned external default route and divert all traffic. The appropriate mitigation is: Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes.
An unconditional export can leak prefixes when the intended backing reachability disappears. This risk belongs to a different operational problem: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. The stated condition instead exposes this direct risk: An overly broad accept can introduce an unplanned external default route and divert all traffic. The appropriate mitigation is: Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes.
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: An overly broad accept can introduce an unplanned external default route and divert all traffic. The appropriate mitigation is: Apply a BGP import policy rejecting 0.0.0.0/0 and accepting only the planned application prefixes.
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. Which targeted engineering change is MOST directly justified by the observed evidence?
Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters. This change specifically addresses the reported evidence: 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 relevant protocol mechanism is: BGP establishes a reliable TCP transport session before exchanging routing updates. A decisive acceptance test would be: The peer establishes its TCP session and enters Established with received NLRI.
Configure appropriate EBGP multihop with reachability and the proper peer source address. This is a valid solution to a different Junos situation: An EBGP neighbor has a reachable loopback address two IP hops away, but a default one-hop peering design cannot establish the session. It does not directly correct the specific failure evidence here: 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 required targeted change is: Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters.
Inspect route hidden reasons and policy tracing before restarting the functioning BGP neighbor. This is a valid solution to a different Junos situation: After an import policy change, a received BGP route remains visible as hidden instead of installed even though the session is Established. It does not directly correct the specific failure evidence here: 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 required targeted change is: Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters.
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: 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 required targeted change is: Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters.
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 proposed correction is: Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters. Which observation MOST directly confirms this fault is resolved?
The peer establishes its TCP session and enters Established with received NLRI. This is the direct acceptance evidence for the observed failure: 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 mechanism being validated is: BGP establishes a reliable TCP transport session before exchanging routing updates.
The multihop neighbor establishes across its routed intermediary and reports expected source addresses. That would validate a different condition: An EBGP neighbor has a reachable loopback address two IP hops away, but a default one-hop peering design cannot establish the session. The decisive check for the current issue is: The peer establishes its TCP session and enters Established with received NLRI.
The affected prefix becomes eligible under a correct policy or displays an intentional reject reason. That would validate a different condition: After an import policy change, a received BGP route remains visible as hidden instead of installed even though the session is Established. The decisive check for the current issue is: The peer establishes its TCP session and enters Established with received NLRI.
The route comparison uses the expected MED logic for the set of applicable candidate paths. That would validate a different condition: A supplier sends a BGP route with a MED that is intended only for comparison among paths received from the same neighboring AS. The decisive check for the current issue is: The peer establishes its TCP session and enters Established with received NLRI.
A Junos engineer proposes this response: Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters. The situation is: 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. Which technical principle BEST justifies the response?
BGP establishes a reliable TCP transport session before exchanging routing updates. This is the controlling mechanism in the specific case: 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. It predicts the acceptance result: The peer establishes its TCP session and enters Established with received NLRI.
EBGP multihop supports peering across a routed path beyond the directly connected link. This principle explains a separate situation: An EBGP neighbor has a reachable loopback address two IP hops away, but a default one-hop peering design cannot establish the session. For this issue the relevant mechanism is: BGP establishes a reliable TCP transport session before exchanging routing updates.
A BGP Established session does not guarantee all received routes are eligible for active routing. This principle explains a separate situation: After an import policy change, a received BGP route remains visible as hidden instead of installed even though the session is Established. For this issue the relevant mechanism is: BGP establishes a reliable TCP transport session before exchanging routing updates.
BGP MED is an optional route attribute whose default comparison scope matters to route selection. This principle explains a separate situation: A supplier sends a BGP route with a MED that is intended only for comparison among paths received from the same neighboring AS. For this issue the relevant mechanism is: BGP establishes a reliable TCP transport session before exchanging routing updates.
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. If the team bypasses or fails to implement the targeted correction (Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters.), which direct operational risk or residual exposure is MOST relevant?
Changing route attributes cannot repair a transport ACL blocking BGP's TCP connection. This is the consequence linked to the observed 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. It is prevented by: Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters. The underlying reason is: BGP establishes a reliable TCP transport session before exchanging routing updates.
Failing to account for hop count and source address can prevent the intended multihop BGP session. This risk belongs to a different operational problem: An EBGP neighbor has a reachable loopback address two IP hops away, but a default one-hop peering design cannot establish the session. The stated condition instead exposes this direct risk: Changing route attributes cannot repair a transport ACL blocking BGP's TCP connection. The appropriate mitigation is: Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters.
Restarting an otherwise healthy peering cannot fix a deterministic routing policy rejection. This risk belongs to a different operational problem: After an import policy change, a received BGP route remains visible as hidden instead of installed even though the session is Established. The stated condition instead exposes this direct risk: Changing route attributes cannot repair a transport ACL blocking BGP's TCP connection. The appropriate mitigation is: Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters.
Assuming lower MED wins across all AS origins can produce invalid selection expectations. This risk belongs to a different operational problem: A supplier sends a BGP route with a MED that is intended only for comparison among paths received from the same neighboring AS. The stated condition instead exposes this direct risk: Changing route attributes cannot repair a transport ACL blocking BGP's TCP connection. The appropriate mitigation is: Allow authenticated, narrowly scoped TCP/179 between the intended EBGP endpoints and verify session parameters.
BGP session establishment fails after one side is configured for the wrong remote autonomous system number. Which targeted engineering change is MOST directly justified by the observed evidence?
Correct the neighbor's expected peer AS in the Junos BGP group configuration. This change specifically addresses the reported evidence: BGP session establishment fails after one side is configured for the wrong remote autonomous system number. The relevant protocol mechanism is: BGP OPEN messages validate negotiated peer AS identity as part of session setup. A decisive acceptance test would be: The Open exchange succeeds and neighbor state reaches Established for the intended ASN.
Inspect AS-path contents and the remote peer's loop prevention policy for repeated local AS entries. This is a valid solution to a different Junos situation: An EBGP peer unexpectedly rejects local advertisements after the enterprise appends its own AS number twice in an outbound policy. It does not directly correct the specific failure evidence here: BGP session establishment fails after one side is configured for the wrong remote autonomous system number. The required targeted change is: Correct the neighbor's expected peer AS in the Junos BGP group configuration.
Enable and verify the inet6-unicast NLRI family on both compatible peers. This is a valid solution to a different Junos situation: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. It does not directly correct the specific failure evidence here: BGP session establishment fails after one side is configured for the wrong remote autonomous system number. The required targeted change is: Correct the neighbor's expected peer AS in the Junos BGP group configuration.
Use a term-based BGP export policy that matches the authorized active route and accepted prefix. This is a valid solution to a different Junos situation: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. It does not directly correct the specific failure evidence here: BGP session establishment fails after one side is configured for the wrong remote autonomous system number. The required targeted change is: Correct the neighbor's expected peer AS in the Junos BGP group configuration.
BGP session establishment fails after one side is configured for the wrong remote autonomous system number. The proposed correction is: Correct the neighbor's expected peer AS in the Junos BGP group configuration. Which observation MOST directly confirms this fault is resolved?
The Open exchange succeeds and neighbor state reaches Established for the intended ASN. This is the direct acceptance evidence for the observed failure: BGP session establishment fails after one side is configured for the wrong remote autonomous system number. The mechanism being validated is: BGP OPEN messages validate negotiated peer AS identity as part of session setup.
The accepted received AS path no longer violates the intended AS-loop policy at the upstream peer. That would validate a different condition: An EBGP peer unexpectedly rejects local advertisements after the enterprise appends its own AS number twice in an outbound policy. The decisive check for the current issue is: The Open exchange succeeds and neighbor state reaches Established for the intended ASN.
The BGP session reports inet6 capability and advertises the expected IPv6 prefix. That would validate a different condition: An IPv6-only prefix should be exchanged over an existing BGP neighbor but the group currently negotiates only inet unicast. The decisive check for the current issue is: The Open exchange succeeds and neighbor state reaches Established for the intended ASN.
The peer receives precisely the eligible prefix and withdraws it when export conditions fail. That would validate a different condition: A partner asks a Junos edge to advertise a longer prefix only when a certain route is present in the active routing table. The decisive check for the current issue is: The Open exchange succeeds and neighbor state reaches Established for the intended ASN.
Please check your mailbox for a message from support@examlabs.com and follow the directions.