Pass Your Juniper JN0-364 Exam Easy!

Juniper JN0-364 Exam Questions & Answers, Accurate & Verified By IT Experts

Instant Download, Free Fast Updates, 99.6% Pass Rate

JN0-364 Premium VCE File

Juniper JN0-364 Premium File

69 Questions & Answers

Last Update: Oct 24, 2026

$69.99

JN0-364 Bundle gives you unlimited access to "JN0-364" files. However, this does not replace the need for a .vce exam simulator. To download VCE exam simulator click here
JN0-364 Premium VCE File
Juniper JN0-364 Premium File

69 Questions & Answers

Last Update: Oct 24, 2026

$69.99

Juniper JN0-364 Exam Bundle gives you unlimited access to "JN0-364" files. However, this does not replace the need for a .vce exam simulator. To download your .vce exam simulator click here

Juniper JN0-364 Practice Test 33

Question 320

During production incident triage, engineers observe: PE-11 has a configured static route to 198.51.100.0/24, but the specified next hop 192.0.2.14 is not reachable by any active route, and traffic drops. An engineer suggests the shortcut: "Change the route description and leave the unresolved next hop unchanged." Which critique explains the specific risk of that shortcut?

  1. Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
  2. A text description has no effect on recursive route resolution and cannot install a usable forwarding entry.
  3. Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
  4. More routes in the original table do not implement selective forwarding through a different routing table.

Explanation

Correct Answer

B:

A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. In this live production incident the shortcut was explicitly proposed as: Change the route description and leave the unresolved next hop unchanged. It fails to resolve the underlying problem that A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface. A sound alternative is the targeted engineering action: Restore an active route to the specified next-hop address or replace it with a verified reachable next hop before relying on the static route.

Incorrect Answers

A:

Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. That critique concerns a shortcut from the unrelated Aggregate rejection behavior case. The shortcut actually proposed in this live production incident is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

C:

Forcing packets of one flow onto different paths can reorder packets and harm transport performance. That critique concerns a shortcut from the unrelated Per-flow hash expectation case. The shortcut actually proposed in this live production incident is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

D:

More routes in the original table do not implement selective forwarding through a different routing table. That critique concerns a shortcut from the unrelated Filter-based forwarding classification case. The shortcut actually proposed in this live production incident is: Change the route description and leave the unresolved next hop unchanged. It should be rejected for the narrower reason that A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. This distinction matters because A Junos static route is usable for forwarding only when its configured next hop can be resolved through an active route or appropriate interface.

Question 321

During production incident triage, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. An engineer suggests the shortcut: "Raise the physical MTU on a link while leaving insufficient reservable bandwidth." Which critique explains the specific risk of that shortcut?

  1. IP reachability alone does not create MPLS label switching capability on a disabled interface.
  2. Additional network-layer routes cannot substitute for the required LDP session transport.
  3. Session establishment says nothing about whether an individual FEC has a usable label mapping.
  4. Packet size settings cannot create capacity for an RSVP admission request.

Explanation

Correct Answer

D:

Packet size settings cannot create capacity for an RSVP admission request. In this live production incident the shortcut was explicitly proposed as: Raise the physical MTU on a link while leaving insufficient reservable bandwidth. It fails to resolve the underlying problem that RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. A sound alternative is the targeted engineering action: Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.

Incorrect Answers

A:

IP reachability alone does not create MPLS label switching capability on a disabled interface. That critique concerns a shortcut from the unrelated MPLS interface not enabled case. The shortcut actually proposed in this live production incident is: Raise the physical MTU on a link while leaving insufficient reservable bandwidth. It should be rejected for the narrower reason that Packet size settings cannot create capacity for an RSVP admission request. This distinction matters because RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

B:

Additional network-layer routes cannot substitute for the required LDP session transport. That critique concerns a shortcut from the unrelated LDP TCP 646 establishment case. The shortcut actually proposed in this live production incident is: Raise the physical MTU on a link while leaving insufficient reservable bandwidth. It should be rejected for the narrower reason that Packet size settings cannot create capacity for an RSVP admission request. This distinction matters because RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

C:

Session establishment says nothing about whether an individual FEC has a usable label mapping. That critique concerns a shortcut from the unrelated Missing LDP FEC label mapping case. The shortcut actually proposed in this live production incident is: Raise the physical MTU on a link while leaving insufficient reservable bandwidth. It should be rejected for the narrower reason that Packet size settings cannot create capacity for an RSVP admission request. This distinction matters because RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

Question 322

During production incident triage, engineers observe: A critical RSVP LSP briefly drops after a transit link fails because its designated bypass or fast reroute protection was never established. An engineer suggests the shortcut: "Disable LSP alarms while keeping the original unprotected path." Which critique explains the specific risk of that shortcut?

  1. Suppressing alarms cannot provide a precomputed alternate label-switched route.
  2. IP reachability alone does not create MPLS label switching capability on a disabled interface.
  3. Session establishment says nothing about whether an individual FEC has a usable label mapping.
  4. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.

Explanation

Correct Answer

A:

Suppressing alarms cannot provide a precomputed alternate label-switched route. In this live production incident the shortcut was explicitly proposed as: Disable LSP alarms while keeping the original unprotected path. It fails to resolve the underlying problem that RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost. A sound alternative is the targeted engineering action: Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

Incorrect Answers

B:

IP reachability alone does not create MPLS label switching capability on a disabled interface. That critique concerns a shortcut from the unrelated MPLS interface not enabled case. The shortcut actually proposed in this live production incident is: Disable LSP alarms while keeping the original unprotected path. It should be rejected for the narrower reason that Suppressing alarms cannot provide a precomputed alternate label-switched route. This distinction matters because RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

C:

Session establishment says nothing about whether an individual FEC has a usable label mapping. That critique concerns a shortcut from the unrelated Missing LDP FEC label mapping case. The shortcut actually proposed in this live production incident is: Disable LSP alarms while keeping the original unprotected path. It should be rejected for the narrower reason that Suppressing alarms cannot provide a precomputed alternate label-switched route. This distinction matters because RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

D:

PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. That critique concerns a shortcut from the unrelated Penultimate hop popping case. The shortcut actually proposed in this live production incident is: Disable LSP alarms while keeping the original unprotected path. It should be rejected for the narrower reason that Suppressing alarms cannot provide a precomputed alternate label-switched route. This distinction matters because RSVP-TE fast reroute can pre-establish bypass protection for a failure, reducing convergence delay when the main path is lost.

Question 323

During production incident triage, engineers observe: A filter-based forwarding policy routes all service traffic into a measurement instance because a broad first term accepts packets before the narrower intended match. An engineer suggests the shortcut: "Increase a counter without changing the overmatching term." Which critique explains the specific risk of that shortcut?

  1. Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix.
  2. BGP timers do not create the aggregate's necessary routing-table contribution.
  3. Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility.
  4. Changing accounting counters does not change first-match classification or forwarding decisions.

Explanation

Correct Answer

D:

Changing accounting counters does not change first-match classification or forwarding decisions. In this live production incident the shortcut was explicitly proposed as: Increase a counter without changing the overmatching term. It fails to resolve the underlying problem that Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules. A sound alternative is the targeted engineering action: Reorder or narrow filter terms so only the designated class receives the routing-instance action while all other classes use their intended forwarding path.

Incorrect Answers

A:

Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. That critique concerns a shortcut from the unrelated Administrative preference overrides static case. The shortcut actually proposed in this live production incident is: Increase a counter without changing the overmatching term. It should be rejected for the narrower reason that Changing accounting counters does not change first-match classification or forwarding decisions. This distinction matters because Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.

B:

BGP timers do not create the aggregate's necessary routing-table contribution. That critique concerns a shortcut from the unrelated Aggregate route contribution case. The shortcut actually proposed in this live production incident is: Increase a counter without changing the overmatching term. It should be rejected for the narrower reason that Changing accounting counters does not change first-match classification or forwarding decisions. This distinction matters because Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.

C:

Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. That critique concerns a shortcut from the unrelated Equal-cost multipath eligibility case. The shortcut actually proposed in this live production incident is: Increase a counter without changing the overmatching term. It should be rejected for the narrower reason that Changing accounting counters does not change first-match classification or forwarding decisions. This distinction matters because Ordered firewall-filter terms apply the first matching action; overbroad early terms can shadow later selective forwarding rules.

Question 324

During production incident triage, engineers observe: One OSPF router has a different LSA sequence or age for a core link and briefly computes a stale path after a topology event. An engineer suggests the shortcut: "Pin a static route to the stale next hop and ignore the LSDB discrepancy." Which critique explains the specific risk of that shortcut?

  1. Removing the interface entirely can also remove the necessary prefix advertisement.
  2. A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change.
  3. Reference bandwidth affects metric calculation, not the area ID carried in Hello packets.
  4. Blindly redistributing external information conflicts with the intended stub-area containment model.

Explanation

Correct Answer

B:

A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. In this live production incident the shortcut was explicitly proposed as: Pin a static route to the stale next hop and ignore the LSDB discrepancy. It fails to resolve the underlying problem that Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB. A sound alternative is the targeted engineering action: Investigate adjacency stability and LSA flooding, then restore consistent current link-state information before relying on SPF.

Incorrect Answers

A:

Removing the interface entirely can also remove the necessary prefix advertisement. That critique concerns a shortcut from the unrelated OSPF passive interface case. The shortcut actually proposed in this live production incident is: Pin a static route to the stale next hop and ignore the LSDB discrepancy. It should be rejected for the narrower reason that A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. This distinction matters because Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.

C:

Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. That critique concerns a shortcut from the unrelated OSPF area ID mismatch case. The shortcut actually proposed in this live production incident is: Pin a static route to the stale next hop and ignore the LSDB discrepancy. It should be rejected for the narrower reason that A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. This distinction matters because Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.

D:

Blindly redistributing external information conflicts with the intended stub-area containment model. That critique concerns a shortcut from the unrelated Stub area external LSA expectation case. The shortcut actually proposed in this live production incident is: Pin a static route to the stale next hop and ignore the LSDB discrepancy. It should be rejected for the narrower reason that A static workaround can mask an unresolved control-plane synchronization problem and fail during another topology change. This distinction matters because Link-state routing depends on timely, consistent LSA flooding so routers can run SPF over a coherent LSDB.

Question 325

During production incident triage, engineers observe: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. An engineer suggests the shortcut: "Tune OSPF DR priority on that link instead of IS-IS DIS priority." Which critique explains the specific risk of that shortcut?

  1. An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility.
  2. Route preference affects installation of received routes, not which IS-IS levels can form an adjacency.
  3. Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
  4. OSPF election settings are unrelated to IS-IS DIS selection on the LAN.

Explanation

Correct Answer

D:

OSPF election settings are unrelated to IS-IS DIS selection on the LAN. In this live production incident the shortcut was explicitly proposed as: Tune OSPF DR priority on that link instead of IS-IS DIS priority. It fails to resolve the underlying problem that The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. A sound alternative is the targeted engineering action: Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.

Incorrect Answers

A:

An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. That critique concerns a shortcut from the unrelated IS-IS level-one area mismatch case. The shortcut actually proposed in this live production incident is: Tune OSPF DR priority on that link instead of IS-IS DIS priority. It should be rejected for the narrower reason that OSPF election settings are unrelated to IS-IS DIS selection on the LAN. This distinction matters because The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

B:

Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. That critique concerns a shortcut from the unrelated IS-IS level capability mismatch case. The shortcut actually proposed in this live production incident is: Tune OSPF DR priority on that link instead of IS-IS DIS priority. It should be rejected for the narrower reason that OSPF election settings are unrelated to IS-IS DIS selection on the LAN. This distinction matters because The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

C:

Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. That critique concerns a shortcut from the unrelated IS-IS narrow metric ceiling case. The shortcut actually proposed in this live production incident is: Tune OSPF DR priority on that link instead of IS-IS DIS priority. It should be rejected for the narrower reason that OSPF election settings are unrelated to IS-IS DIS selection on the LAN. This distinction matters because The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

Question 326

During production incident triage, engineers observe: PE-13 is configured to advertise 203.0.113.0/22 as an aggregate, but no eligible more-specific contributing prefix is active and the summary is absent. An engineer suggests the shortcut: "Increase BGP keepalive frequency while no contributor route exists." Which critique explains the specific risk of that shortcut?

  1. Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
  2. More routes in the original table do not implement selective forwarding through a different routing table.
  3. BGP timers do not create the aggregate's necessary routing-table contribution.
  4. Changing accounting counters does not change first-match classification or forwarding decisions.

Explanation

Correct Answer

C:

BGP timers do not create the aggregate's necessary routing-table contribution. In this live production incident the shortcut was explicitly proposed as: Increase BGP keepalive frequency while no contributor route exists. It fails to resolve the underlying problem that A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active. A sound alternative is the targeted engineering action: Verify the intended contributing routes and activate an eligible more-specific route before depending on the aggregate advertisement.

Incorrect Answers

A:

Forcing packets of one flow onto different paths can reorder packets and harm transport performance. That critique concerns a shortcut from the unrelated Per-flow hash expectation case. The shortcut actually proposed in this live production incident is: Increase BGP keepalive frequency while no contributor route exists. It should be rejected for the narrower reason that BGP timers do not create the aggregate's necessary routing-table contribution. This distinction matters because A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.

B:

More routes in the original table do not implement selective forwarding through a different routing table. That critique concerns a shortcut from the unrelated Filter-based forwarding classification case. The shortcut actually proposed in this live production incident is: Increase BGP keepalive frequency while no contributor route exists. It should be rejected for the narrower reason that BGP timers do not create the aggregate's necessary routing-table contribution. This distinction matters because A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.

D:

Changing accounting counters does not change first-match classification or forwarding decisions. That critique concerns a shortcut from the unrelated Filter policy overmatch case. The shortcut actually proposed in this live production incident is: Increase BGP keepalive frequency while no contributor route exists. It should be rejected for the narrower reason that BGP timers do not create the aggregate's necessary routing-table contribution. This distinction matters because A Junos aggregate route is derived from contributing more-specific routes; an aggregate configured without a valid contributor may not become active.

Question 327

During production incident triage, engineers observe: A blocking switch port abruptly stops receiving BPDUs after a one-way failure and risks moving into forwarding even though a redundant topology still exists. An engineer suggests the shortcut: "Enable root protection instead while expecting it to detect missing BPDUs." Which critique explains the specific risk of that shortcut?

  1. Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link.
  2. Descriptions do not participate in MSTP region identification or instance mapping.
  3. Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles.
  4. OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election.

Explanation

Correct Answer

A:

Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link. In this live production incident the shortcut was explicitly proposed as: Enable root protection instead while expecting it to detect missing BPDUs. It fails to resolve the underlying problem that Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection. A sound alternative is the targeted engineering action: Use loop protection where BPDU loss on non-designated ports could cause an unsafe transition, after verifying platform support.

Incorrect Answers

B:

Descriptions do not participate in MSTP region identification or instance mapping. That critique concerns a shortcut from the unrelated MSTP region mismatch case. The shortcut actually proposed in this live production incident is: Enable root protection instead while expecting it to detect missing BPDUs. It should be rejected for the narrower reason that Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link. This distinction matters because Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.

C:

Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles. That critique concerns a shortcut from the unrelated Per-VLAN spanning-tree path case. The shortcut actually proposed in this live production incident is: Enable root protection instead while expecting it to detect missing BPDUs. It should be rejected for the narrower reason that Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link. This distinction matters because Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.

D:

OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election. That critique concerns a shortcut from the unrelated Root bridge election priority case. The shortcut actually proposed in this live production incident is: Enable root protection instead while expecting it to detect missing BPDUs. It should be rejected for the narrower reason that Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link. This distinction matters because Loop protection guards against a blocked interface incorrectly forwarding when expected BPDUs vanish, distinct from blocking superior BPDUs with root protection.

Question 328

During production incident triage, engineers observe: A provider-facing Ethernet port must carry multiple distinct tagged logical units, but one unit uses the wrong VLAN encapsulation and traffic enters the wrong service. An engineer suggests the shortcut: "Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping." Which critique explains the specific risk of that shortcut?

  1. IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong.
  2. MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding.
  3. A duplicate name does not move frames into the intended instance and can increase configuration confusion.
  4. Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.

Explanation

Correct Answer

A:

IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. In this live production incident the shortcut was explicitly proposed as: Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping. It fails to resolve the underlying problem that Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit. A sound alternative is the targeted engineering action: Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.

Incorrect Answers

B:

MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. That critique concerns a shortcut from the unrelated IRB routed gateway missing case. The shortcut actually proposed in this live production incident is: Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping. It should be rejected for the narrower reason that IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. This distinction matters because Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.

C:

A duplicate name does not move frames into the intended instance and can increase configuration confusion. That critique concerns a shortcut from the unrelated Virtual switch instance membership case. The shortcut actually proposed in this live production incident is: Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping. It should be rejected for the narrower reason that IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. This distinction matters because Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.

D:

Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding. That critique concerns a shortcut from the unrelated Unknown unicast flooding behavior case. The shortcut actually proposed in this live production incident is: Add more IPv4 static routes without fixing the VLAN-tag-to-unit mapping. It should be rejected for the narrower reason that IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. This distinction matters because Junos logical-interface tag matching and encapsulation determine which tagged frames are classified into a particular service unit.

Question 329

During production incident triage, engineers observe: A prefix is received from a valid BGP peer but remains unusable because the advertised BGP next hop has no resolving route in the local table. An engineer suggests the shortcut: "Increase BGP local preference on a route whose next hop remains unreachable." Which critique explains the specific risk of that shortcut?

  1. Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session.
  2. ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing.
  3. Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
  4. A higher preference cannot create a missing recursive path to a BGP next hop.

Explanation

Correct Answer

D:

A higher preference cannot create a missing recursive path to a BGP next hop. In this live production incident the shortcut was explicitly proposed as: Increase BGP local preference on a route whose next hop remains unreachable. It fails to resolve the underlying problem that BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection. A sound alternative is the targeted engineering action: Restore IGP or static reachability for the intended BGP next hop, or apply the correct next-hop policy where design requires it.

Incorrect Answers

A:

Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. That critique concerns a shortcut from the unrelated BGP TCP transport blocked case. The shortcut actually proposed in this live production incident is: Increase BGP local preference on a route whose next hop remains unreachable. It should be rejected for the narrower reason that A higher preference cannot create a missing recursive path to a BGP next hop. This distinction matters because BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.

B:

ECMP settings do not allow an eBGP session to cross an intermediate hop when multihop is missing. That critique concerns a shortcut from the unrelated EBGP multihop peering case. The shortcut actually proposed in this live production incident is: Increase BGP local preference on a route whose next hop remains unreachable. It should be rejected for the narrower reason that A higher preference cannot create a missing recursive path to a BGP next hop. This distinction matters because BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.

C:

Remote-side policy is outside local control and does not enforce an explicit receiving security boundary. That critique concerns a shortcut from the unrelated BGP import policy leak case. The shortcut actually proposed in this live production incident is: Increase BGP local preference on a route whose next hop remains unreachable. It should be rejected for the narrower reason that A higher preference cannot create a missing recursive path to a BGP next hop. This distinction matters because BGP next-hop reachability is a prerequisite to making a received route eligible for active forwarding and path selection.

Question 330

During production incident triage, engineers observe: After cloning a PE template, two routers use the same OSPF router ID and the topology shows conflicting advertisements. An engineer suggests the shortcut: "Change the syslog hostname but keep the duplicate router IDs." Which critique explains the specific risk of that shortcut?

  1. Removing the interface entirely can also remove the necessary prefix advertisement.
  2. Blindly redistributing external information conflicts with the intended stub-area containment model.
  3. Router-ID identity is not an OSPF path-cost control knob.
  4. Syslog names are not OSPF originator identifiers, so the underlying conflict remains.

Explanation

Correct Answer

D:

Syslog names are not OSPF originator identifiers, so the underlying conflict remains. In this live production incident the shortcut was explicitly proposed as: Change the syslog hostname but keep the duplicate router IDs. It fails to resolve the underlying problem that OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain. A sound alternative is the targeted engineering action: Assign and verify a unique stable OSPF router ID for each router, then refresh affected neighbor state.

Incorrect Answers

A:

Removing the interface entirely can also remove the necessary prefix advertisement. That critique concerns a shortcut from the unrelated OSPF passive interface case. The shortcut actually proposed in this live production incident is: Change the syslog hostname but keep the duplicate router IDs. It should be rejected for the narrower reason that Syslog names are not OSPF originator identifiers, so the underlying conflict remains. This distinction matters because OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.

B:

Blindly redistributing external information conflicts with the intended stub-area containment model. That critique concerns a shortcut from the unrelated Stub area external LSA expectation case. The shortcut actually proposed in this live production incident is: Change the syslog hostname but keep the duplicate router IDs. It should be rejected for the narrower reason that Syslog names are not OSPF originator identifiers, so the underlying conflict remains. This distinction matters because OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.

C:

Router-ID identity is not an OSPF path-cost control knob. That critique concerns a shortcut from the unrelated OSPF metric path preference case. The shortcut actually proposed in this live production incident is: Change the syslog hostname but keep the duplicate router IDs. It should be rejected for the narrower reason that Syslog names are not OSPF originator identifiers, so the underlying conflict remains. This distinction matters because OSPF router IDs uniquely identify LSA originators and participating routers within the routing domain.


Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests

Purchase Individually

JN0-364 Premium File

Premium File
JN0-364 Premium File
69 Q&A
$76.99$69.99

Site Search:

 

VISA, MasterCard, AmericanExpress, UnionPay

SPECIAL OFFER: GET 10% OFF

ExamCollection Premium

ExamCollection Premium Files

Pass your Exam with ExamCollection's PREMIUM files!

  • ExamCollection Certified Safe Files
  • Guaranteed to have ACTUAL Exam Questions
  • Up-to-Date Exam Study Material - Verified by Experts
  • Instant Downloads
Enter Your Email Address to Receive Your 10% Off Discount Code
A Confirmation Link will be sent to this email address to verify your login
We value your privacy. We will not rent or sell your email address

SPECIAL OFFER: GET 10% OFF

Use Discount Code:

MIN10OFF

A confirmation link was sent to your e-mail.
Please check your mailbox for a message from support@examcollection.com and follow the directions.

Next

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your e-mail address below to get started with our interactive software demo of your free trial.

Free Demo Limits: In the demo version you will be able to access only first 5 questions from exam.