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 90

Question 890

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An engineer sees a route in the routing protocol database and assumes data packets must use it, but the route is hidden or inactive relative to an alternative. An engineer suggests the shortcut: "Treat a route's mere appearance in a protocol database as evidence of successful forwarding." 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. Presence in a control-plane view does not prove active route selection or packet forwarding installation.
  3. Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility.
  4. An unconditional default masks missing prerequisites and may direct traffic into an unintended path.

Explanation

Correct Answer

B:

Presence in a control-plane view does not prove active route selection or packet forwarding installation. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Treat a route's mere appearance in a protocol database as evidence of successful forwarding. It fails to resolve the underlying problem that Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base. A sound alternative is the targeted engineering action: Inspect the active route and forwarding-table next hop, then resolve the preference, policy or next-hop condition suppressing the expected 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 controlled acceptance rehearsal is: Treat a route's mere appearance in a protocol database as evidence of successful forwarding. It should be rejected for the narrower reason that Presence in a control-plane view does not prove active route selection or packet forwarding installation. This distinction matters because Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.

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 controlled acceptance rehearsal is: Treat a route's mere appearance in a protocol database as evidence of successful forwarding. It should be rejected for the narrower reason that Presence in a control-plane view does not prove active route selection or packet forwarding installation. This distinction matters because Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.

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 controlled acceptance rehearsal is: Treat a route's mere appearance in a protocol database as evidence of successful forwarding. It should be rejected for the narrower reason that Presence in a control-plane view does not prove active route selection or packet forwarding installation. This distinction matters because Junos can retain candidate and inactive routes in routing tables while forwarding uses only the selected active route installed in the forwarding information base.

Question 891

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-12 learns an OSPF route and a static route for the same destination; operations expect the dynamic path, but the static route wins because its Junos preference is lower. An engineer suggests the shortcut: "Change OSPF interface cost without examining the static route preference." Which critique explains the specific risk of that shortcut?

  1. More routes in the original table do not implement selective forwarding through a different routing table.
  2. Changing accounting counters does not change first-match classification or forwarding decisions.
  3. Forcing packets of one flow onto different paths can reorder packets and harm transport performance.
  4. Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix.

Explanation

Correct Answer

D:

Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Change OSPF interface cost without examining the static route preference. It fails to resolve the underlying problem that For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference. A sound alternative is the targeted engineering action: Adjust the specific route's preference or remove the unintended static route after confirming the intended failover design.

Incorrect Answers

A:

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 controlled acceptance rehearsal is: Change OSPF interface cost without examining the static route preference. It should be rejected for the narrower reason that Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. This distinction matters because For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.

B:

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 controlled acceptance rehearsal is: Change OSPF interface cost without examining the static route preference. It should be rejected for the narrower reason that Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. This distinction matters because For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.

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 controlled acceptance rehearsal is: Change OSPF interface cost without examining the static route preference. It should be rejected for the narrower reason that Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. This distinction matters because For equal prefixes in the Junos routing table, the lower routing preference is generally selected as active ahead of a route with higher preference.

Question 892

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. OSPF router identity is unrelated to the Layer 2 bridge ID used in STP root election.
  2. Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link.
  3. Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm.
  4. MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election.

Explanation

Correct Answer

B:

Root protection reacts to superior BPDUs, not the absence of expected BPDUs on a blocked link. In this controlled acceptance rehearsal 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

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 controlled acceptance rehearsal 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:

Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm. That critique concerns a shortcut from the unrelated RSTP alternate port activation case. The shortcut actually proposed in this controlled acceptance rehearsal 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:

MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. That critique concerns a shortcut from the unrelated Root protection against rogue core case. The shortcut actually proposed in this controlled acceptance rehearsal 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 893

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: One peer permits only Level 1 and the other only Level 2 on a link, so neither forms an IS-IS adjacency despite reachable Ethernet. An engineer suggests the shortcut: "Raise the IP routing preference for all IS-IS routes without changing level configuration." Which critique explains the specific risk of that shortcut?

  1. OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
  2. Static routes conceal incomplete flooding and can become incorrect during legitimate topology changes.
  3. Changing interface labels cannot repair conflicting protocol system identities.
  4. Route preference affects installation of received routes, not which IS-IS levels can form an adjacency.

Explanation

Correct Answer

D:

Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Raise the IP routing preference for all IS-IS routes without changing level configuration. It fails to resolve the underlying problem that An IS-IS adjacency needs compatible protocol levels as well as link reachability. A sound alternative is the targeted engineering action: Configure a common allowed IS-IS level on the two interfaces in accordance with the area and backbone design.

Incorrect Answers

A:

OSPF election settings are unrelated to IS-IS DIS selection on the LAN. That critique concerns a shortcut from the unrelated IS-IS DIS election surprise case. The shortcut actually proposed in this controlled acceptance rehearsal is: Raise the IP routing preference for all IS-IS routes without changing level configuration. It should be rejected for the narrower reason that Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. This distinction matters because An IS-IS adjacency needs compatible protocol levels as well as link reachability.

B:

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 controlled acceptance rehearsal is: Raise the IP routing preference for all IS-IS routes without changing level configuration. It should be rejected for the narrower reason that Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. This distinction matters because An IS-IS adjacency needs compatible protocol levels as well as link reachability.

C:

Changing interface labels cannot repair conflicting protocol system identities. That critique concerns a shortcut from the unrelated Duplicate IS-IS system ID case. The shortcut actually proposed in this controlled acceptance rehearsal is: Raise the IP routing preference for all IS-IS routes without changing level configuration. It should be rejected for the narrower reason that Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. This distinction matters because An IS-IS adjacency needs compatible protocol levels as well as link reachability.

Question 894

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A labeled packet reaches a transit router, but its advertised incoming label has no valid forwarding action in the label forwarding table. An engineer suggests the shortcut: "Change only the packet's IP source address and keep the invalid incoming-label mapping." Which critique explains the specific risk of that shortcut?

  1. Packet size settings cannot create capacity for an RSVP admission request.
  2. One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP.
  3. IP addressing does not repair the label operation needed at a transit LSR.
  4. Renumbering a destination node SID does not inherently specify a new intermediate route sequence.

Explanation

Correct Answer

C:

IP addressing does not repair the label operation needed at a transit LSR. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Change only the packet's IP source address and keep the invalid incoming-label mapping. It fails to resolve the underlying problem that MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions. A sound alternative is the targeted engineering action: Check the label binding and route resolution and restore the correct MPLS forwarding entry for that FEC.

Incorrect Answers

A:

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 controlled acceptance rehearsal is: Change only the packet's IP source address and keep the invalid incoming-label mapping. It should be rejected for the narrower reason that IP addressing does not repair the label operation needed at a transit LSR. This distinction matters because MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.

B:

One-way RSVP signaling does not establish reverse-path label forwarding through the same LSP. That critique concerns a shortcut from the unrelated RSVP LSP directionality case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change only the packet's IP source address and keep the invalid incoming-label mapping. It should be rejected for the narrower reason that IP addressing does not repair the label operation needed at a transit LSR. This distinction matters because MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.

D:

Renumbering a destination node SID does not inherently specify a new intermediate route sequence. That critique concerns a shortcut from the unrelated SR-MPLS node-SID shortest path case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change only the packet's IP source address and keep the invalid incoming-label mapping. It should be rejected for the narrower reason that IP addressing does not repair the label operation needed at a transit LSR. This distinction matters because MPLS forwarding depends on matching the incoming label against label-switching entries that specify swap, pop or forwarding actions.

Question 895

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two customers happen to use the same inner VLAN 100 but should remain separate over the provider switching network. An engineer suggests the shortcut: "Bridge both customer connections into one shared provider VLAN because their inner tags match." Which critique explains the specific risk of that shortcut?

  1. Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic.
  2. Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.
  3. IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong.
  4. A duplicate name does not move frames into the intended instance and can increase configuration confusion.

Explanation

Correct Answer

A:

Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Bridge both customer connections into one shared provider VLAN because their inner tags match. It fails to resolve the underlying problem that Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers. A sound alternative is the targeted engineering action: Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.

Incorrect Answers

B:

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 controlled acceptance rehearsal is: Bridge both customer connections into one shared provider VLAN because their inner tags match. It should be rejected for the narrower reason that Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic. This distinction matters because Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.

C:

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 controlled acceptance rehearsal is: Bridge both customer connections into one shared provider VLAN because their inner tags match. It should be rejected for the narrower reason that Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic. This distinction matters because Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.

D:

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 controlled acceptance rehearsal is: Bridge both customer connections into one shared provider VLAN because their inner tags match. It should be rejected for the narrower reason that Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic. This distinction matters because Q-in-Q provider bridging uses an outer service identifier to isolate customers even when they reuse identical inner VLAN numbers.

Question 896

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An eBGP neighbor remains Active after its partner changed autonomous system numbers, while the Junos peer still specifies the previous remote AS. An engineer suggests the shortcut: "Increase BGP import policy acceptance without correcting the remote AS." Which critique explains the specific risk of that shortcut?

  1. Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable.
  2. Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
  3. Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session.
  4. Session liveness timers do not change IBGP route propagation rules.

Explanation

Correct Answer

A:

Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase BGP import policy acceptance without correcting the remote AS. It fails to resolve the underlying problem that BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session. A sound alternative is the targeted engineering action: Correct the explicitly configured neighbor peer AS to match the authorized remote routing domain and verify the session parameters.

Incorrect Answers

B:

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 controlled acceptance rehearsal is: Increase BGP import policy acceptance without correcting the remote AS. It should be rejected for the narrower reason that Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. This distinction matters because BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.

C:

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 controlled acceptance rehearsal is: Increase BGP import policy acceptance without correcting the remote AS. It should be rejected for the narrower reason that Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. This distinction matters because BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.

D:

Session liveness timers do not change IBGP route propagation rules. That critique concerns a shortcut from the unrelated IBGP transit split horizon case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase BGP import policy acceptance without correcting the remote AS. It should be rejected for the narrower reason that Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. This distinction matters because BGP OPEN messages carry AS information and a mismatch with the expected remote autonomous system can prevent a valid session.

Question 897

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An untagged frame arriving on an interswitch trunk is classified into VLAN 10 at one end and VLAN 20 at the other, creating traffic leakage. An engineer suggests the shortcut: "Change a loopback IPv4 address without altering trunk native VLAN definitions." Which critique explains the specific risk of that shortcut?

  1. Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames.
  2. Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.
  3. Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic.
  4. IP routes cannot classify a frame into the correct logical subinterface when tagging is wrong.

Explanation

Correct Answer

B:

Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Change a loopback IPv4 address without altering trunk native VLAN definitions. It fails to resolve the underlying problem that Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. A sound alternative is the targeted engineering action: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.

Incorrect Answers

A:

Layer 3 route changes cannot change the Layer 2 VLAN assignment of untagged frames. That critique concerns a shortcut from the unrelated Access VLAN membership case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change a loopback IPv4 address without altering trunk native VLAN definitions. It should be rejected for the narrower reason that Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. This distinction matters because Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.

C:

Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic. That critique concerns a shortcut from the unrelated Provider VLAN customer isolation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Change a loopback IPv4 address without altering trunk native VLAN definitions. It should be rejected for the narrower reason that Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. This distinction matters because Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.

D:

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 controlled acceptance rehearsal is: Change a loopback IPv4 address without altering trunk native VLAN definitions. It should be rejected for the narrower reason that Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs. This distinction matters because Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping.

Question 898

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A service requires the MPLS EXP/traffic-class indication to reach the egress but implicit-null PHP removes the outer transport label. An engineer suggests the shortcut: "Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header." Which critique explains the specific risk of that shortcut?

  1. Packet size settings cannot create capacity for an RSVP admission request.
  2. IP TTL does not control implicit-null versus explicit-null label disposition.
  3. Suppressing alarms cannot provide a precomputed alternate label-switched route.
  4. RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping.

Explanation

Correct Answer

B:

IP TTL does not control implicit-null versus explicit-null label disposition. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header. It fails to resolve the underlying problem that Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping. A sound alternative is the targeted engineering action: Apply supported explicit-null disposition where the QoS design requires a labeled packet to reach the egress.

Incorrect Answers

A:

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 controlled acceptance rehearsal is: Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header. It should be rejected for the narrower reason that IP TTL does not control implicit-null versus explicit-null label disposition. This distinction matters because Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.

C:

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 controlled acceptance rehearsal is: Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header. It should be rejected for the narrower reason that IP TTL does not control implicit-null versus explicit-null label disposition. This distinction matters because Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.

D:

RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. That critique concerns a shortcut from the unrelated Segment routing SID advertisement case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase the IPv4 packet TTL in an attempt to preserve the MPLS label header. It should be rejected for the narrower reason that IP TTL does not control implicit-null versus explicit-null label disposition. This distinction matters because Explicit-null can preserve an MPLS label header to the egress rather than relying on penultimate-hop implicit-null popping.

Question 899

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A designed IS-IS path cost is too large for the old narrow metric scheme, causing metrics to be interpreted incorrectly after an upgrade. An engineer suggests the shortcut: "Keep legacy narrow metrics but set a higher impossible value in planning documents." 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. Changing interface labels cannot repair conflicting protocol system identities.
  3. OSPF election settings are unrelated to IS-IS DIS selection on the LAN.
  4. Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.

Explanation

Correct Answer

D:

Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Keep legacy narrow metrics but set a higher impossible value in planning documents. It fails to resolve the underlying problem that IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering. A sound alternative is the targeted engineering action: Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.

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 controlled acceptance rehearsal is: Keep legacy narrow metrics but set a higher impossible value in planning documents. It should be rejected for the narrower reason that Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. This distinction matters because IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.

B:

Changing interface labels cannot repair conflicting protocol system identities. That critique concerns a shortcut from the unrelated Duplicate IS-IS system ID case. The shortcut actually proposed in this controlled acceptance rehearsal is: Keep legacy narrow metrics but set a higher impossible value in planning documents. It should be rejected for the narrower reason that Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. This distinction matters because IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.

C:

OSPF election settings are unrelated to IS-IS DIS selection on the LAN. That critique concerns a shortcut from the unrelated IS-IS DIS election surprise case. The shortcut actually proposed in this controlled acceptance rehearsal is: Keep legacy narrow metrics but set a higher impossible value in planning documents. It should be rejected for the narrower reason that Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. This distinction matters because IS-IS TLVs and metric styles affect the expressible path costs; wide metrics support modern larger costs and traffic engineering.

Question 900

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Hosts in a VLAN can bridge to each other but cannot reach a different subnet because the VLAN has no correctly attached integrated routing and bridging interface. An engineer suggests the shortcut: "Increase MAC learning timeout and assume routing between VLANs will start." Which critique explains the specific risk of that shortcut?

  1. Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved.
  2. Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic.
  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

C:

MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. In this controlled acceptance rehearsal the shortcut was explicitly proposed as: Increase MAC learning timeout and assume routing between VLANs will start. It fails to resolve the underlying problem that An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching. A sound alternative is the targeted engineering action: Configure and bind the intended IRB Layer 3 interface to the VLAN and verify IP forwarding and gateway addressing.

Incorrect Answers

A:

Changing customer tags can disrupt their VLAN separation and leaves the provider's outer-tag contract unresolved. That critique concerns a shortcut from the unrelated Q-in-Q outer tag mismatch case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase MAC learning timeout and assume routing between VLANs will start. It should be rejected for the narrower reason that MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. This distinction matters because An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.

B:

Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic. That critique concerns a shortcut from the unrelated Provider VLAN customer isolation case. The shortcut actually proposed in this controlled acceptance rehearsal is: Increase MAC learning timeout and assume routing between VLANs will start. It should be rejected for the narrower reason that MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. This distinction matters because An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.

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 controlled acceptance rehearsal is: Increase MAC learning timeout and assume routing between VLANs will start. It should be rejected for the narrower reason that MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding. This distinction matters because An IRB logical interface provides the routed gateway for a bridge domain, distinct from pure Layer 2 MAC switching.


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.