JN0-364 Premium File
- 69 Questions & Answers
- Last Update: Nov 4, 2026
During provider troubleshooting at Firthbank Medical, this symptom is observed: A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. Which targeted inspection should precede remediation?
The check diagnoses a different layer of service. Its source issue is: An operator changes local preference on its own router expecting a remote AS to honor it, but the remote side never receives that attribute. The relevant initial check is: Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.
Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability. A session that fails at peer AS negotiation is not repaired by changing route export community or local preference.
That evidence could be normal while the reported defect persists. It is aimed at: A service route remains hidden after an eBGP-to-iBGP handoff; the internal router knows the prefix but not a path to its advertised next hop. Instead inspect: Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.
The check diagnoses a different layer of service. Its source issue is: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. The relevant initial check is: Check `show bgp neighbor` last-error/state and compare peer AS, local AS, neighbor address and TCP/179 reachability.
A production change request at Oakbend Education includes this finding: A team assumes periodic UPDATE messages keep a quiet BGP session alive, but the route table is stable and no updates are due. What should the engineer change to address it?
This action may apply to a different problem, for example: Two equal eligible BGP paths to a destination exist, but forwarding uses only the best path while the service design needs shared capacity. It does not repair the stated failure boundary. The case-specific reason is: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
The other action is relevant when A service route remains hidden after an eBGP-to-iBGP handoff; the internal router knows the prefix but not a path to its advertised next hop. The current case instead requires: Verify the BGP control-channel message exchange, including KEEPALIVEs and hold timer, and fix any filtering of required message types. The distinction is: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
Verify the BGP control-channel message exchange, including KEEPALIVEs and hold timer, and fix any filtering of required message types. The case-specific reason is: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change. A direct acceptance test is: The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed.
This action may apply to a different problem, for example: Two eBGP routes have equal earlier BGP decision attributes and the operator needs to explain why a path with fewer AS numbers is preferred. It does not repair the stated failure boundary. The case-specific reason is: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
After Oakbend Education applies its proposed fix to this problem — A team assumes periodic UPDATE messages keep a quiet BGP session alive, but the route table is stable and no updates are due. — which observation best proves the specific failure has been resolved?
The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed. BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
That check proves something else, such as: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. It could pass while the stated problem remains. The targeted evidence here is: The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed.
That check proves something else, such as: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. It could pass while the stated problem remains. The targeted evidence here is: The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed.
This would be valid for another situation: A service route remains hidden after an eBGP-to-iBGP handoff; the internal router knows the prefix but not a path to its advertised next hop. It does not establish that the failing boundary in this scenario works; verify: The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed.
An architecture review at Oakbend Education examines the following symptom: A team assumes periodic UPDATE messages keep a quiet BGP session alive, but the route table is stable and no updates are due. What Junos or protocol mechanism is most directly responsible?
That principle belongs to a different service stage: A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. The directly relevant mechanism is: BGP uses OPEN for session negotiation, KEEPALIVE for liveness, UPDATE for reachability and NOTIFICATION for error signaling.
BGP uses OPEN for session negotiation, KEEPALIVE for liveness, UPDATE for reachability and NOTIFICATION for error signaling. The key distinction is: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change. Accordingly the remedy is: Verify the BGP control-channel message exchange, including KEEPALIVEs and hold timer, and fix any filtering of required message types.
The statement can be true when A received iBGP route is visible in inet.0 but inactive because its BGP next hop cannot be resolved through the IGP. But it does not explain the reported failure. Here: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
That principle belongs to a different service stage: A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. The directly relevant mechanism is: BGP uses OPEN for session negotiation, KEEPALIVE for liveness, UPDATE for reachability and NOTIFICATION for error signaling.
The team at Oakbend Education defers a fix for this condition: A team assumes periodic UPDATE messages keep a quiet BGP session alive, but the route table is stable and no updates are due. What failure is most likely if no targeted control is applied?
That consequence is more closely associated with another deficiency, such as: A BGP speaker learns a route from one iBGP peer but does not pass it to another internal peer, causing partial prefix visibility. The described fault instead exposes: Blocking a required message class causes hold-time expiration, session resets or missing reachability updates despite an otherwise healthy link.
It is a risk in another topology or protocol state: A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. Here the most direct failure path is: Blocking a required message class causes hold-time expiration, session resets or missing reachability updates despite an otherwise healthy link.
The concern could occur elsewhere when Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. For the stated scenario, the immediate risk is: Blocking a required message class causes hold-time expiration, session resets or missing reachability updates despite an otherwise healthy link.
Blocking a required message class causes hold-time expiration, session resets or missing reachability updates despite an otherwise healthy link. The direct mitigation is: Verify the BGP control-channel message exchange, including KEEPALIVEs and hold timer, and fix any filtering of required message types.
During provider troubleshooting at Oakbend Education, this symptom is observed: A team assumes periodic UPDATE messages keep a quiet BGP session alive, but the route table is stable and no updates are due. Which targeted inspection should precede remediation?
That evidence could be normal while the reported defect persists. It is aimed at: Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. Instead inspect: Inspect neighbor flap reasons, hold timers and a TCP/179 packet trace to identify which BGP message type fails.
The check diagnoses a different layer of service. Its source issue is: A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. The relevant initial check is: Inspect neighbor flap reasons, hold timers and a TCP/179 packet trace to identify which BGP message type fails.
This check may help with another root cause, for example: The provider expects a shorter AS path to win, but another path has a deliberately higher local preference and is selected instead. It does not test the first failed condition; start with: Inspect neighbor flap reasons, hold timers and a TCP/179 packet trace to identify which BGP message type fails.
Inspect neighbor flap reasons, hold timers and a TCP/179 packet trace to identify which BGP message type fails. BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
At Northline Communications, a service provider router shows this failure: An intermittent control-plane firewall blocks one BGP packet class, and operators need to separate OPEN, KEEPALIVE, UPDATE and NOTIFICATION behavior. What is the best targeted configuration or operations action?
Verify the BGP control-channel message exchange, including KEEPALIVEs and hold timer, and fix any filtering of required message types. The case-specific reason is: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change. A direct acceptance test is: The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed.
This action may apply to a different problem, for example: The provider expects a shorter AS path to win, but another path has a deliberately higher local preference and is selected instead. It does not repair the stated failure boundary. The case-specific reason is: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
The other action is relevant when A provider changed a partner's ASN, leaving the old `peer-as` on its Junos BGP group while TCP connection attempts continue. The current case instead requires: Verify the BGP control-channel message exchange, including KEEPALIVEs and hold timer, and fix any filtering of required message types. The distinction is: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
That would address a separate configuration fault: Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. This stem identifies a different cause, corrected by: Verify the BGP control-channel message exchange, including KEEPALIVEs and hold timer, and fix any filtering of required message types.
A change auditor at Northline Communications must validate remediation of this finding: An intermittent control-plane firewall blocks one BGP packet class, and operators need to separate OPEN, KEEPALIVE, UPDATE and NOTIFICATION behavior. Which test outcome is the strongest acceptance evidence?
That check proves something else, such as: A service route remains hidden after an eBGP-to-iBGP handoff; the internal router knows the prefix but not a path to its advertised next hop. It could pass while the stated problem remains. The targeted evidence here is: The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed.
This would be valid for another situation: Two equal eligible BGP paths to a destination exist, but forwarding uses only the best path while the service design needs shared capacity. It does not establish that the failing boundary in this scenario works; verify: The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed.
The observation confirms a different component's behavior. Its source context is: A backbone operator needs to prefer a primary egress for all internal routers without changing the external partner's AS path length. In this case the success criterion is: The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed.
The BGP session remains Established with expected KEEPALIVE intervals, and legitimate UPDATE/withdrawal traffic is exchanged when needed. BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
The operations training team at Northline Communications discusses this issue: An intermittent control-plane firewall blocks one BGP packet class, and operators need to separate OPEN, KEEPALIVE, UPDATE and NOTIFICATION behavior. Which technical explanation matches the intended correction?
The statement can be true when A planned customer route appears in the partner's advertisements but Junos rejects it at an early inbound policy term. But it does not explain the reported failure. Here: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
That principle belongs to a different service stage: A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. The directly relevant mechanism is: BGP uses OPEN for session negotiation, KEEPALIVE for liveness, UPDATE for reachability and NOTIFICATION for error signaling.
BGP uses OPEN for session negotiation, KEEPALIVE for liveness, UPDATE for reachability and NOTIFICATION for error signaling. The key distinction is: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change. Accordingly the remedy is: Verify the BGP control-channel message exchange, including KEEPALIVEs and hold timer, and fix any filtering of required message types.
The statement can be true when Two paths learned inside one AS reach the same destination; the selected exit conflicts with policy despite the chosen link having fewer AS hops. But it does not explain the reported failure. Here: BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
At Northline Communications, a service acceptance review considers the unresolved issue: An intermittent control-plane firewall blocks one BGP packet class, and operators need to separate OPEN, KEEPALIVE, UPDATE and NOTIFICATION behavior. Which operational exposure follows most directly?
Blocking a required message class causes hold-time expiration, session resets or missing reachability updates despite an otherwise healthy link. The direct mitigation is: Verify the BGP control-channel message exchange, including KEEPALIVEs and hold timer, and fix any filtering of required message types.
That consequence is more closely associated with another deficiency, such as: Two neighboring providers configured for eBGP have IP reachability but the BGP session remains Active because one side uses the wrong peer AS number. The described fault instead exposes: Blocking a required message class causes hold-time expiration, session resets or missing reachability updates despite an otherwise healthy link.
It is a risk in another topology or protocol state: A router has eBGP paths with equal relevant attributes and the operations team assumes both will automatically enter the forwarding table. Here the most direct failure path is: Blocking a required message class causes hold-time expiration, session resets or missing reachability updates despite an otherwise healthy link.
The concern could occur elsewhere when A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. For the stated scenario, the immediate risk is: Blocking a required message class causes hold-time expiration, session resets or missing reachability updates despite an otherwise healthy link.
Before changing configuration at Northline Communications, an engineer investigates: An intermittent control-plane firewall blocks one BGP packet class, and operators need to separate OPEN, KEEPALIVE, UPDATE and NOTIFICATION behavior. Which first diagnostic most directly tests the suspected cause?
This check may help with another root cause, for example: Two eBGP routes have equal earlier BGP decision attributes and the operator needs to explain why a path with fewer AS numbers is preferred. It does not test the first failed condition; start with: Inspect neighbor flap reasons, hold timers and a TCP/179 packet trace to identify which BGP message type fails.
That evidence could be normal while the reported defect persists. It is aimed at: A carrier tags customer routes with a standard BGP community to drive downstream policy, but the tag never appears beyond the ingress edge. Instead inspect: Inspect neighbor flap reasons, hold timers and a TCP/179 packet trace to identify which BGP message type fails.
Inspect neighbor flap reasons, hold timers and a TCP/179 packet trace to identify which BGP message type fails. BGP liveness is maintained by KEEPALIVE even when route advertisements do not change.
This check may help with another root cause, for example: A transit customer prefix is locally active but never advertised to an approved eBGP neighbor because the export policy's final term rejects it. It does not test the first failed condition; start with: Inspect neighbor flap reasons, hold timers and a TCP/179 packet trace to identify which BGP message type fails.
Please check your mailbox for a message from support@examlabs.com and follow the directions.