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 39

Question 380

During production incident triage, engineers observe: A provider calls a GRE tunnel secure against eavesdropping merely because customers cannot see its inner packet headers on the underlay. An engineer suggests the shortcut: "Rely on GRE encapsulation alone as if it were end-to-end encryption." Which critique explains the specific risk of that shortcut?

  1. Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer.
  2. Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path.
  3. Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon.
  4. Larger packets increase the encapsulation MTU violation and do not solve delivery.

Explanation

Correct Answer

A:

Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. In this live production incident the shortcut was explicitly proposed as: Rely on GRE encapsulation alone as if it were end-to-end encryption. It fails to resolve the underlying problem that GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls. A sound alternative is the targeted engineering action: Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.

Incorrect Answers

B:

Changing inner routing parameters does not repair an incorrectly addressed outer GRE encapsulation path. That critique concerns a shortcut from the unrelated GRE tunnel endpoint mismatch case. The shortcut actually proposed in this live production incident is: Rely on GRE encapsulation alone as if it were end-to-end encryption. It should be rejected for the narrower reason that Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. This distinction matters because GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.

C:

Circular resolution sends the tunnel's transport traffic back into the overlay it depends upon. That critique concerns a shortcut from the unrelated GRE underlay recursive loss case. The shortcut actually proposed in this live production incident is: Rely on GRE encapsulation alone as if it were end-to-end encryption. It should be rejected for the narrower reason that Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. This distinction matters because GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.

D:

Larger packets increase the encapsulation MTU violation and do not solve delivery. That critique concerns a shortcut from the unrelated GRE encapsulation MTU overhead case. The shortcut actually proposed in this live production incident is: Rely on GRE encapsulation alone as if it were end-to-end encryption. It should be rejected for the narrower reason that Encapsulation hides protocol framing but provides no cryptographic confidentiality or integrity against an observer. This distinction matters because GRE encapsulates packets but does not inherently encrypt payloads or authenticate peers; security needs separate controls.

Question 381

During production incident triage, engineers observe: Two IBGP-learned transit exits have equal basic attributes but the operator wants a designated egress router to be selected throughout the AS. An engineer suggests the shortcut: "Apply the same MED to routes sent to an unrelated external neighbor." Which critique explains the specific risk of that shortcut?

  1. MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS.
  2. Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable.
  3. Unbounded export may disclose internal prefixes or become a source of accidental Internet route leaks.
  4. Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.

Explanation

Correct Answer

A:

MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. In this live production incident the shortcut was explicitly proposed as: Apply the same MED to routes sent to an unrelated external neighbor. It fails to resolve the underlying problem that Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility. A sound alternative is the targeted engineering action: Use a controlled import policy to assign the desired BGP local preference to the selected exit paths.

Incorrect Answers

B:

Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable. That critique concerns a shortcut from the unrelated BGP peer autonomous system mismatch case. The shortcut actually proposed in this live production incident is: Apply the same MED to routes sent to an unrelated external neighbor. It should be rejected for the narrower reason that MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. This distinction matters because Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.

C:

Unbounded export may disclose internal prefixes or become a source of accidental Internet route leaks. That critique concerns a shortcut from the unrelated BGP export policy omission case. The shortcut actually proposed in this live production incident is: Apply the same MED to routes sent to an unrelated external neighbor. It should be rejected for the narrower reason that MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. This distinction matters because Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.

D:

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: Apply the same MED to routes sent to an unrelated external neighbor. It should be rejected for the narrower reason that MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. This distinction matters because Within an AS, a BGP path with higher local preference is preferred over one with lower local preference, subject to route eligibility.

Question 382

During production incident triage, engineers observe: A downstream tenant switch begins sending superior BPDUs toward the provider's designated port and threatens to become root for the provider spanning tree. An engineer suggests the shortcut: "Reduce Ethernet MTU on the provider uplink to influence BPDU root election." Which critique explains the specific risk of that shortcut?

  1. Descriptions do not participate in MSTP region identification or instance mapping.
  2. MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election.
  3. Making redundant ports forward simultaneously can introduce a Layer 2 loop and broadcast storm.
  4. Removing STP protection can permit the unauthorized bridge to create a forwarding loop.

Explanation

Correct Answer

B:

MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. In this live production incident the shortcut was explicitly proposed as: Reduce Ethernet MTU on the provider uplink to influence BPDU root election. It fails to resolve the underlying problem that Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path. A sound alternative is the targeted engineering action: Enable root protection on the designated administrative boundary port where superior BPDUs must not be accepted.

Incorrect Answers

A:

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: Reduce Ethernet MTU on the provider uplink to influence BPDU root election. It should be rejected for the narrower reason that MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. This distinction matters because Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.

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 live production incident is: Reduce Ethernet MTU on the provider uplink to influence BPDU root election. It should be rejected for the narrower reason that MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. This distinction matters because Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.

D:

Removing STP protection can permit the unauthorized bridge to create a forwarding loop. That critique concerns a shortcut from the unrelated Unexpected BPDU on edge port case. The shortcut actually proposed in this live production incident is: Reduce Ethernet MTU on the provider uplink to influence BPDU root election. It should be rejected for the narrower reason that MTU is not the STP bridge-ID control and does not prevent superior BPDUs from winning election. This distinction matters because Root protection blocks a port that unexpectedly receives superior BPDUs and prevents it from becoming the root path.

Question 383

During production incident triage, 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. MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding.
  2. Removing MAC learning generally prolongs unknown-destination flooding rather than creating targeted forwarding.
  3. Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic.
  4. Loopback addressing does not determine how untagged trunk traffic is mapped into VLANs.

Explanation

Correct Answer

C:

Sharing the outer service VLAN removes the intended customer isolation and can mix their traffic. In this live production incident 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

A:

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: 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.

B:

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: 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:

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: 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 384

During production incident triage, engineers observe: PE-72 has IP reachability across a link but no LDP adjacency; the IGP runs over the link while LDP was enabled on another interface. An engineer suggests the shortcut: "Increase the OSPF reference bandwidth without enabling LDP on the missing interface." 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. Session establishment says nothing about whether an individual FEC has a usable label mapping.
  3. IP addressing does not repair the label operation needed at a transit LSR.
  4. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.

Explanation

Correct Answer

A:

OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. In this live production incident the shortcut was explicitly proposed as: Increase the OSPF reference bandwidth without enabling LDP on the missing interface. It fails to resolve the underlying problem that LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation. A sound alternative is the targeted engineering action: Enable and validate LDP on the intended interfaces that share IGP reachability with participating neighbors.

Incorrect Answers

B:

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: Increase the OSPF reference bandwidth without enabling LDP on the missing interface. It should be rejected for the narrower reason that OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. This distinction matters because LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.

C:

IP addressing does not repair the label operation needed at a transit LSR. That critique concerns a shortcut from the unrelated Incoming label missing in LFIB case. The shortcut actually proposed in this live production incident is: Increase the OSPF reference bandwidth without enabling LDP on the missing interface. It should be rejected for the narrower reason that OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. This distinction matters because LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.

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: Increase the OSPF reference bandwidth without enabling LDP on the missing interface. It should be rejected for the narrower reason that OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured. This distinction matters because LDP distributes labels over protocol sessions built on top of an IGP-reachable core and needs proper interface participation.

Question 385

During production incident triage, engineers observe: A Junos static IPv6 route points to a link-local next-hop address but omits the outgoing interface, so the router cannot unambiguously resolve the path. An engineer suggests the shortcut: "Add an arbitrary IPv4 gateway address to the inet.0 table only." Which critique explains the specific risk of that shortcut?

  1. An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection.
  2. IPv4 routing entries cannot replace the missing IPv6 prefix advertisements.
  3. IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path.
  4. Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery.

Explanation

Correct Answer

A:

An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. In this live production incident the shortcut was explicitly proposed as: Add an arbitrary IPv4 gateway address to the inet.0 table only. It fails to resolve the underlying problem that An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop. A sound alternative is the targeted engineering action: Specify the intended outgoing interface together with the link-local next hop and confirm the route is usable.

Incorrect Answers

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: Add an arbitrary IPv4 gateway address to the inet.0 table only. It should be rejected for the narrower reason that An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. This distinction matters because An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.

C:

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: Add an arbitrary IPv4 gateway address to the inet.0 table only. It should be rejected for the narrower reason that An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. This distinction matters because An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.

D:

Blocking needed ICMPv6 breaks IPv6 control mechanisms including Path MTU Discovery. That critique concerns a shortcut from the unrelated ICMPv6 packet-too-big handling case. The shortcut actually proposed in this live production incident is: Add an arbitrary IPv4 gateway address to the inet.0 table only. It should be rejected for the narrower reason that An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. This distinction matters because An IPv6 link-local address is scoped to an interface; identifying the outgoing link is necessary to disambiguate a link-local next hop.

Question 386

During production incident triage, engineers observe: A provider BFD session drops under transient control-plane load, withdrawing routes despite no physical failure because the detect interval is impractically tight. An engineer suggests the shortcut: "Set the minimum possible BFD interval everywhere regardless of platform capacity." Which critique explains the specific risk of that shortcut?

  1. VLAN membership does not make incompatible LACP peers join a single forwarding aggregate.
  2. Unreasonably small intervals can cause false liveness failures and repeated routing churn.
  3. Routing metrics in OSPF do not directly determine VRRP primary election.
  4. Aggressive preemption repeats the same transient blackhole while the upstream path remains unready.

Explanation

Correct Answer

B:

Unreasonably small intervals can cause false liveness failures and repeated routing churn. In this live production incident the shortcut was explicitly proposed as: Set the minimum possible BFD interval everywhere regardless of platform capacity. It fails to resolve the underlying problem that BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure. A sound alternative is the targeted engineering action: Choose a supported BFD interval and detection multiplier appropriate for network scale and peer capacity, then test fault response.

Incorrect Answers

A:

VLAN membership does not make incompatible LACP peers join a single forwarding aggregate. That critique concerns a shortcut from the unrelated LACP partner mismatch case. The shortcut actually proposed in this live production incident is: Set the minimum possible BFD interval everywhere regardless of platform capacity. It should be rejected for the narrower reason that Unreasonably small intervals can cause false liveness failures and repeated routing churn. This distinction matters because BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.

C:

Routing metrics in OSPF do not directly determine VRRP primary election. That critique concerns a shortcut from the unrelated VRRP master priority failover case. The shortcut actually proposed in this live production incident is: Set the minimum possible BFD interval everywhere regardless of platform capacity. It should be rejected for the narrower reason that Unreasonably small intervals can cause false liveness failures and repeated routing churn. This distinction matters because BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.

D:

Aggressive preemption repeats the same transient blackhole while the upstream path remains unready. That critique concerns a shortcut from the unrelated VRRP preemption oscillation case. The shortcut actually proposed in this live production incident is: Set the minimum possible BFD interval everywhere regardless of platform capacity. It should be rejected for the narrower reason that Unreasonably small intervals can cause false liveness failures and repeated routing churn. This distinction matters because BFD uses rapid periodic control packets and negotiated timing; overly aggressive timers can mistake transient loss for peer failure.

Question 387

During production incident triage, engineers observe: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. An engineer suggests the shortcut: "Configure only an RSVP bandwidth request without addressing missing SR segment information." Which critique explains the specific risk of that shortcut?

  1. RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping.
  2. OSPF metric calculations cannot cause LDP to participate on an interface where it is not configured.
  3. Additional network-layer routes cannot substitute for the required LDP session transport.
  4. PHP is a normal label disposition behavior and not evidence that the entire LSP should be removed.

Explanation

Correct Answer

A:

RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. In this live production incident the shortcut was explicitly proposed as: Configure only an RSVP bandwidth request without addressing missing SR segment information. It fails to resolve the underlying problem that SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. A sound alternative is the targeted engineering action: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.

Incorrect Answers

B:

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: Configure only an RSVP bandwidth request without addressing missing SR segment information. It should be rejected for the narrower reason that RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. This distinction matters because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

C:

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: Configure only an RSVP bandwidth request without addressing missing SR segment information. It should be rejected for the narrower reason that RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. This distinction matters because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

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: Configure only an RSVP bandwidth request without addressing missing SR segment information. It should be rejected for the narrower reason that RSVP reservable bandwidth is independent of whether the source has a valid SR-MPLS SID mapping. This distinction matters because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

Question 388

During production incident triage, engineers observe: An ingress router has routes to the LSP egress but its core-facing interface is not participating in MPLS, so label forwarding is absent. An engineer suggests the shortcut: "Add a plain IPv4 static route and assume the labeled data path now exists." 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. LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint.
  4. Packet size settings cannot create capacity for an RSVP admission request.

Explanation

Correct Answer

A:

IP reachability alone does not create MPLS label switching capability on a disabled interface. In this live production incident the shortcut was explicitly proposed as: Add a plain IPv4 static route and assume the labeled data path now exists. It fails to resolve the underlying problem that MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path. A sound alternative is the targeted engineering action: Enable MPLS on the intended eligible core-facing interface and verify forwarding capability along the path.

Incorrect Answers

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: Add a plain IPv4 static route and assume the labeled data path now exists. It should be rejected for the narrower reason that IP reachability alone does not create MPLS label switching capability on a disabled interface. This distinction matters because MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.

C:

LDP discovery on an unrelated peer does not satisfy a broken RSVP explicit-hop constraint. That critique concerns a shortcut from the unrelated RSVP-TE constrained path missing case. The shortcut actually proposed in this live production incident is: Add a plain IPv4 static route and assume the labeled data path now exists. It should be rejected for the narrower reason that IP reachability alone does not create MPLS label switching capability on a disabled interface. This distinction matters because MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.

D:

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: Add a plain IPv4 static route and assume the labeled data path now exists. It should be rejected for the narrower reason that IP reachability alone does not create MPLS label switching capability on a disabled interface. This distinction matters because MPLS label forwarding requires compatible MPLS participation on the forwarding interfaces along the intended label-switched path.

Question 389

During production incident triage, engineers observe: Two peering routers have matching AS and neighbor addresses but the BGP session never leaves Connect because traffic to TCP port 179 is blocked along the underlay. An engineer suggests the shortcut: "Add an extra prefix advertisement to the export policy while the TCP session is blocked." Which critique explains the specific risk of that shortcut?

  1. A higher preference cannot create a missing recursive path to a BGP next hop.
  2. OSPF LAN DR election settings do not modify the BGP path attributes being compared.
  3. Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
  4. Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session.

Explanation

Correct Answer

D:

Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. In this live production incident the shortcut was explicitly proposed as: Add an extra prefix advertisement to the export policy while the TCP session is blocked. It fails to resolve the underlying problem that BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering. A sound alternative is the targeted engineering action: Permit the intended peer-to-peer TCP 179 control connection through the applicable filter and verify bidirectional reachability.

Incorrect Answers

A:

A higher preference cannot create a missing recursive path to a BGP next hop. That critique concerns a shortcut from the unrelated BGP next-hop inaccessible case. The shortcut actually proposed in this live production incident is: Add an extra prefix advertisement to the export policy while the TCP session is blocked. It should be rejected for the narrower reason that Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. This distinction matters because BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.

B:

OSPF LAN DR election settings do not modify the BGP path attributes being compared. That critique concerns a shortcut from the unrelated BGP AS-path comparison case. The shortcut actually proposed in this live production incident is: Add an extra prefix advertisement to the export policy while the TCP session is blocked. It should be rejected for the narrower reason that Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. This distinction matters because BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.

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: Add an extra prefix advertisement to the export policy while the TCP session is blocked. It should be rejected for the narrower reason that Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session. This distinction matters because BGP peers establish a TCP session before exchanging OPEN, KEEPALIVE and UPDATE messages; blocked TCP connectivity prevents peering.

Question 390

During production incident triage, engineers observe: Two provider switches have a working physical trunk, but VLAN 340 traffic is missing because VLAN 340 is not permitted on the receiving trunk port. An engineer suggests the shortcut: "Turn every trunk into an unrestricted all-VLAN connection." Which critique explains the specific risk of that shortcut?

  1. A duplicate name does not move frames into the intended instance and can increase configuration confusion.
  2. Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership.
  3. An aging change cannot prevent contradictory source-MAC observations on multiple ports.
  4. MAC aging does not create a Layer 3 interface or provide inter-subnet forwarding.

Explanation

Correct Answer

B:

Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. In this live production incident the shortcut was explicitly proposed as: Turn every trunk into an unrestricted all-VLAN connection. It fails to resolve the underlying problem that A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers. A sound alternative is the targeted engineering action: Add only the authorized VLAN to the relevant tagged-trunk membership and verify tagging end to end.

Incorrect Answers

A:

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: Turn every trunk into an unrestricted all-VLAN connection. It should be rejected for the narrower reason that Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. This distinction matters because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.

C:

An aging change cannot prevent contradictory source-MAC observations on multiple ports. That critique concerns a shortcut from the unrelated MAC move instability case. The shortcut actually proposed in this live production incident is: Turn every trunk into an unrestricted all-VLAN connection. It should be rejected for the narrower reason that Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. This distinction matters because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.

D:

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: Turn every trunk into an unrestricted all-VLAN connection. It should be rejected for the narrower reason that Opening all VLANs expands the Layer 2 service boundary rather than fixing the specific missing membership. This distinction matters because A trunk transports tagged VLANs only when both ends consistently permit and recognize the VLAN identifiers.


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.