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 34

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.

Question 331

During production incident triage, engineers observe: Small IPv6 pings succeed over a provider path but larger sessions stall because an intermediate filter blocks Packet Too Big messages needed by IPv6 Path MTU Discovery. An engineer suggests the shortcut: "Disable all ICMPv6 control traffic for a presumed hardening improvement." Which critique explains the specific risk of that shortcut?

  1. Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency.
  2. IPv4 routing entries cannot replace the missing IPv6 prefix advertisements.
  3. Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery.
  4. IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path.

Explanation

Correct Answer

C:

Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery. In this live production incident the shortcut was explicitly proposed as: Disable all ICMPv6 control traffic for a presumed hardening improvement. It fails to resolve the underlying problem that IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU. A sound alternative is the targeted engineering action: Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.

Incorrect Answers

A:

Changing IPv4 OSPFv2 parameters does not establish an independent OSPFv3 adjacency. That critique concerns a shortcut from the unrelated OSPFv3 neighbor uses link-local case. The shortcut actually proposed in this live production incident is: Disable all ICMPv6 control traffic for a presumed hardening improvement. It should be rejected for the narrower reason that Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery. This distinction matters because IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.

B:

IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. That critique concerns a shortcut from the unrelated IS-IS IPv6 reachability TLVs case. The shortcut actually proposed in this live production incident is: Disable all ICMPv6 control traffic for a presumed hardening improvement. It should be rejected for the narrower reason that Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery. This distinction matters because IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.

D:

IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path. That critique concerns a shortcut from the unrelated IPv6 over IPv4 transit tunnel case. The shortcut actually proposed in this live production incident is: Disable all ICMPv6 control traffic for a presumed hardening improvement. It should be rejected for the narrower reason that Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery. This distinction matters because IPv6 routers do not fragment transit packets; working Path MTU Discovery relies on ICMPv6 errors when packets exceed a path MTU.

Question 332

During production incident triage, engineers observe: A provider virtual-switch routing instance is configured but one interface remains attached to the default switching context, so tenant MAC learning is fragmented. An engineer suggests the shortcut: "Create a duplicate VLAN name in the default instance instead of fixing membership." Which critique explains the specific risk of that shortcut?

  1. Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.
  2. IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong.
  3. Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.
  4. A duplicate name does not move frames into the intended instance and can increase configuration confusion.

Explanation

Correct Answer

D:

A duplicate name does not move frames into the intended instance and can increase configuration confusion. In this live production incident the shortcut was explicitly proposed as: Create a duplicate VLAN name in the default instance instead of fixing membership. It fails to resolve the underlying problem that Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned. A sound alternative is the targeted engineering action: Move the intended logical interface into the correct virtual-switch instance and align its VLAN or bridge-domain membership.

Incorrect Answers

A:

Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. That critique concerns a shortcut from the unrelated Native VLAN mismatch case. The shortcut actually proposed in this live production incident is: Create a duplicate VLAN name in the default instance instead of fixing membership. It should be rejected for the narrower reason that A duplicate name does not move frames into the intended instance and can increase configuration confusion. This distinction matters because Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.

B:

IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong. That critique concerns a shortcut from the unrelated Flexible VLAN tagging logical units case. The shortcut actually proposed in this live production incident is: Create a duplicate VLAN name in the default instance instead of fixing membership. It should be rejected for the narrower reason that A duplicate name does not move frames into the intended instance and can increase configuration confusion. This distinction matters because Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.

C:

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: Create a duplicate VLAN name in the default instance instead of fixing membership. It should be rejected for the narrower reason that A duplicate name does not move frames into the intended instance and can increase configuration confusion. This distinction matters because Virtual switch instances maintain separate Layer 2 forwarding contexts; interface membership determines where MACs and VLANs are learned.

Question 333

During production incident triage, engineers observe: A customer's MAC alternates rapidly between two provider ports after a redundant CE was cabled incorrectly, causing intermittent service loss. An engineer suggests the shortcut: "Raise the MAC aging timer while leaving both conflicting attachments active." Which critique explains the specific risk of that shortcut?

  1. Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.
  2. An aging change cannot prevent contradictory source-MAC observations on multiple ports.
  3. MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding.
  4. Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.

Explanation

Correct Answer

B:

An aging change cannot prevent contradictory source-MAC observations on multiple ports. In this live production incident the shortcut was explicitly proposed as: Raise the MAC aging timer while leaving both conflicting attachments active. It fails to resolve the underlying problem that Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments. A sound alternative is the targeted engineering action: Find the physical or logical loop and correct the CE's redundant attachment or approved multihoming design.

Incorrect Answers

A:

Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. That critique concerns a shortcut from the unrelated Native VLAN mismatch case. The shortcut actually proposed in this live production incident is: Raise the MAC aging timer while leaving both conflicting attachments active. It should be rejected for the narrower reason that An aging change cannot prevent contradictory source-MAC observations on multiple ports. This distinction matters because Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.

C:

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: Raise the MAC aging timer while leaving both conflicting attachments active. It should be rejected for the narrower reason that An aging change cannot prevent contradictory source-MAC observations on multiple ports. This distinction matters because Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.

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: Raise the MAC aging timer while leaving both conflicting attachments active. It should be rejected for the narrower reason that An aging change cannot prevent contradictory source-MAC observations on multiple ports. This distinction matters because Layer 2 learning continually updates a MAC address's egress port; uncontrolled MAC moves can indicate bridging loops or unstable attachments.

Question 334

During production incident triage, engineers observe: A trace shows the penultimate router removing a transport label before handing a packet to the egress, and an engineer assumes the missing final label is a fault. An engineer suggests the shortcut: "Disable every MPLS label exchange just because one label was popped near the egress." Which critique explains the specific risk of that shortcut?

  1. OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured.
  2. Additional network-layer routes cannot substitute for the required LDP session transport.
  3. Packet size settings cannot create capacity for an RSVP admission request.
  4. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.

Explanation

Correct Answer

D:

PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. In this live production incident the shortcut was explicitly proposed as: Disable every MPLS label exchange just because one label was popped near the egress. It fails to resolve the underlying problem that Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work. A sound alternative is the targeted engineering action: Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.

Incorrect Answers

A:

OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. That critique concerns a shortcut from the unrelated LDP discovery and IGP mismatch case. The shortcut actually proposed in this live production incident is: Disable every MPLS label exchange just because one label was popped near the egress. It should be rejected for the narrower reason that PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. This distinction matters because Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.

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: Disable every MPLS label exchange just because one label was popped near the egress. It should be rejected for the narrower reason that PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. This distinction matters because Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.

C:

Packet size settings cannot create capacity for an RSVP admission request. That critique concerns a shortcut from the unrelated RSVP reservable bandwidth shortage case. The shortcut actually proposed in this live production incident is: Disable every MPLS label exchange just because one label was popped near the egress. It should be rejected for the narrower reason that PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed. This distinction matters because Penultimate-hop popping removes the top transport label before the egress when implicit-null is advertised, reducing label-processing work.

Question 335

During production incident triage, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. An engineer suggests the shortcut: "Delete all more-specific routes so the aggregate is the only route." Which critique explains the specific risk of that shortcut?

  1. A text description has no effect on recursive route resolution and cannot install a usable forwarding entry.
  2. Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix.
  3. Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
  4. An unconditional default masks missing prerequisites and may direct traffic into an unintended path.

Explanation

Correct Answer

C:

Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. In this live production incident the shortcut was explicitly proposed as: Delete all more-specific routes so the aggregate is the only route. It fails to resolve the underlying problem that An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. A sound alternative is the targeted engineering action: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.

Incorrect Answers

A:

A text description has no effect on recursive route resolution and cannot install a usable forwarding entry. That critique concerns a shortcut from the unrelated Recursive next-hop resolution case. The shortcut actually proposed in this live production incident is: Delete all more-specific routes so the aggregate is the only route. It should be rejected for the narrower reason that Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. This distinction matters because An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

B:

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: Delete all more-specific routes so the aggregate is the only route. It should be rejected for the narrower reason that Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. This distinction matters because An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

D:

An unconditional default masks missing prerequisites and may direct traffic into an unintended path. That critique concerns a shortcut from the unrelated Generated default route prerequisite case. The shortcut actually proposed in this live production incident is: Delete all more-specific routes so the aggregate is the only route. It should be rejected for the narrower reason that Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. This distinction matters because An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match.

Question 336

During production incident triage, engineers observe: On a shared broadcast LAN, a router configured with OSPF priority zero is expected to become designated router but never wins election. An engineer suggests the shortcut: "Increase the OSPF interface metric to make the priority-zero router electable." Which critique explains the specific risk of that shortcut?

  1. Removing the interface entirely can also remove the necessary prefix advertisement.
  2. Reference bandwidth affects metric calculation, not the area ID carried in Hello packets.
  3. SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility.
  4. Blindly redistributing external information conflicts with the intended stub-area containment model.

Explanation

Correct Answer

C:

SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. In this live production incident the shortcut was explicitly proposed as: Increase the OSPF interface metric to make the priority-zero router electable. It fails to resolve the underlying problem that OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links. A sound alternative is the targeted engineering action: Set a nonzero eligible interface priority where DR candidacy is intended and re-evaluate election behavior with the network design.

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: Increase the OSPF interface metric to make the priority-zero router electable. It should be rejected for the narrower reason that SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. This distinction matters because OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

B:

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: Increase the OSPF interface metric to make the priority-zero router electable. It should be rejected for the narrower reason that SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. This distinction matters because OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

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: Increase the OSPF interface metric to make the priority-zero router electable. It should be rejected for the narrower reason that SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. This distinction matters because OSPF priority zero makes a router ineligible to become designated or backup designated router on broadcast multiaccess links.

Question 337

During production incident triage, engineers observe: A customer edge-facing port configured as an endpoint connection receives BPDUs from a bridged device, raising loop exposure. An engineer suggests the shortcut: "Disable all spanning-tree processing on the edge network to stop the BPDU alerts." Which critique explains the specific risk of that shortcut?

  1. OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election.
  2. Descriptions do not participate in MSTP region identification or instance mapping.
  3. Removing STP protection can permit the unauthorized bridge to create a forwarding loop.
  4. Layer 3 route preference does not determine Layer 2 spanning-tree root or port roles.

Explanation

Correct Answer

C:

Removing STP protection can permit the unauthorized bridge to create a forwarding loop. In this live production incident the shortcut was explicitly proposed as: Disable all spanning-tree processing on the edge network to stop the BPDU alerts. It fails to resolve the underlying problem that Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action. A sound alternative is the targeted engineering action: Apply the supported BPDU protection policy on true edge ports and investigate the unauthorized bridge attachment.

Incorrect Answers

A:

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: Disable all spanning-tree processing on the edge network to stop the BPDU alerts. It should be rejected for the narrower reason that Removing STP protection can permit the unauthorized bridge to create a forwarding loop. This distinction matters because Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.

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: Disable all spanning-tree processing on the edge network to stop the BPDU alerts. It should be rejected for the narrower reason that Removing STP protection can permit the unauthorized bridge to create a forwarding loop. This distinction matters because Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.

D:

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: Disable all spanning-tree processing on the edge network to stop the BPDU alerts. It should be rejected for the narrower reason that Removing STP protection can permit the unauthorized bridge to create a forwarding loop. This distinction matters because Edge ports assume they are connected to end stations; received BPDUs can signal an unexpected switch and trigger protective action.

Question 338

During production incident triage, engineers observe: A provider expects LDP-labeled service traffic to follow an RSVP-TE tunnel but traffic follows the ordinary IGP path because LDP tunneling was not enabled for the chosen RSVP LSP. An engineer suggests the shortcut: "Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP." Which critique explains the specific risk of that shortcut?

  1. Additional network-layer routes cannot substitute for the required LDP session transport.
  2. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.
  3. BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP.
  4. Suppressing alarms cannot provide a precomputed alternate label-switched route.

Explanation

Correct Answer

C:

BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP. In this live production incident the shortcut was explicitly proposed as: Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP. It fails to resolve the underlying problem that LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport. A sound alternative is the targeted engineering action: Configure supported LDP-over-RSVP tunneling for the intended LSP and validate the resulting label-stack and FEC resolution.

Incorrect Answers

A:

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: Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP. It should be rejected for the narrower reason that BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP. This distinction matters because LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.

B:

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: Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP. It should be rejected for the narrower reason that BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP. This distinction matters because LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.

D:

Suppressing alarms cannot provide a precomputed alternate label-switched route. That critique concerns a shortcut from the unrelated RSVP link protection plan case. The shortcut actually proposed in this live production incident is: Set an unrelated BGP MED and assume LDP sessions will use the RSVP LSP. It should be rejected for the narrower reason that BGP route advertisement hints do not turn on LDP tunneling over a particular RSVP LSP. This distinction matters because LDP FEC transport can be carried over RSVP-established LSPs where explicitly configured, combining hop-by-hop label distribution with traffic-engineered transport.

Question 339

During production incident triage, engineers observe: Two cloned provider routers use the same IS-IS system identifier and generate conflicting LSP origins inside the link-state database. An engineer suggests the shortcut: "Rename the interfaces without changing the duplicate NET system IDs." Which critique explains the specific risk of that shortcut?

  1. Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling.
  2. Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
  3. Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes.
  4. Changing interface labels cannot repair conflicting protocol system identities.

Explanation

Correct Answer

D:

Changing interface labels cannot repair conflicting protocol system identities. In this live production incident the shortcut was explicitly proposed as: Rename the interfaces without changing the duplicate NET system IDs. It fails to resolve the underlying problem that IS-IS relies on a unique system ID to identify LSP originators and topology nodes. A sound alternative is the targeted engineering action: Allocate unique system identifiers in the NET on each router and refresh the affected IS-IS topology state.

Incorrect Answers

A:

Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling. That critique concerns a shortcut from the unrelated IS-IS ISO family missing case. The shortcut actually proposed in this live production incident is: Rename the interfaces without changing the duplicate NET system IDs. It should be rejected for the narrower reason that Changing interface labels cannot repair conflicting protocol system identities. This distinction matters because IS-IS relies on a unique system ID to identify LSP originators and topology nodes.

B:

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: Rename the interfaces without changing the duplicate NET system IDs. It should be rejected for the narrower reason that Changing interface labels cannot repair conflicting protocol system identities. This distinction matters because IS-IS relies on a unique system ID to identify LSP originators and topology nodes.

C:

Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes. That critique concerns a shortcut from the unrelated IS-IS LSP lifetime anomaly case. The shortcut actually proposed in this live production incident is: Rename the interfaces without changing the duplicate NET system IDs. It should be rejected for the narrower reason that Changing interface labels cannot repair conflicting protocol system identities. This distinction matters because IS-IS relies on a unique system ID to identify LSP originators and topology nodes.

Question 340

During production incident triage, engineers observe: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. An engineer suggests the shortcut: "Disable authentication permanently on one neighbor to force the adjacency up." Which critique explains the specific risk of that shortcut?

  1. Blindly redistributing external information conflicts with the intended stub-area containment model.
  2. SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility.
  3. Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection.
  4. DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link.

Explanation

Correct Answer

C:

Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. In this live production incident the shortcut was explicitly proposed as: Disable authentication permanently on one neighbor to force the adjacency up. It fails to resolve the underlying problem that OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. A sound alternative is the targeted engineering action: Coordinate compatible OSPFv2 authentication method, key identifier and active secret on both peers before cutover.

Incorrect Answers

A:

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: Disable authentication permanently on one neighbor to force the adjacency up. It should be rejected for the narrower reason that Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. This distinction matters because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

B:

SPF path cost is distinct from the DR election priority; changing cost does not reverse priority-zero ineligibility. That critique concerns a shortcut from the unrelated DR priority zero misconception case. The shortcut actually proposed in this live production incident is: Disable authentication permanently on one neighbor to force the adjacency up. It should be rejected for the narrower reason that Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. This distinction matters because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

D:

DR election priority does not remove a broadcast network-type assumption from a dedicated point-to-point link. That critique concerns a shortcut from the unrelated Point-to-point OSPF network type case. The shortcut actually proposed in this live production incident is: Disable authentication permanently on one neighbor to force the adjacency up. It should be rejected for the narrower reason that Unilateral removal of authentication does not establish a trusted matching configuration and weakens control-plane protection. This distinction matters because OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.


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.