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 31

Question 300

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. After the appropriate change, which observation would most directly establish that this particular issue was corrected?

  1. The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.
  2. Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned.
  3. An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction.
  4. The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label.

Explanation

Correct Answer

A:

The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node. This tests the actual condition identified in the live production incident: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. It is meaningful because SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels.

Incorrect Answers

B:

Expected LDP discovery packets and TCP session are present on the correct link, and relevant FEC labels are learned. This measurement may prove the unrelated LDP discovery and IGP mismatch condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. A relevant acceptance result here is: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.

C:

An LDP session reaches Operational and displays the intended neighbor label bindings after selective filter correction. This measurement may prove the unrelated LDP TCP 646 establishment condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. A relevant acceptance result here is: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.

D:

The egress receives the expected payload context and end-to-end service passes despite the absence of a top transport label. This measurement may prove the unrelated Penultimate hop popping condition, but it does not demonstrate that the current live production incident was resolved. The specific observed fault is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. A relevant acceptance result here is: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.

Question 301

During production incident triage, engineers observe: IS-IS neighbors are up for IPv4, but IPv6 routes do not appear because the IPv6 reachability information is not advertised in supported IS-IS TLVs. An engineer suggests the shortcut: "Add more IPv4 routes without enabling IPv6 IS-IS reachability." Which critique explains the specific risk of that shortcut?

  1. IPv4 routing entries cannot replace the missing IPv6 prefix advertisements.
  2. An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection.
  3. IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement.
  4. IPv6 route configuration alone cannot deliver IPv6 payload across an IPv4-only segment with no encapsulation path.

Explanation

Correct Answer

A:

IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. In this live production incident the shortcut was explicitly proposed as: Add more IPv4 routes without enabling IPv6 IS-IS reachability. It fails to resolve the underlying problem that IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information. A sound alternative is the targeted engineering action: Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.

Incorrect Answers

B:

An IPv4 route cannot supply the missing IPv6 link-local scope or next-hop selection. That critique concerns a shortcut from the unrelated IPv6 static link-local next hop case. The shortcut actually proposed in this live production incident is: Add more IPv4 routes without enabling IPv6 IS-IS reachability. It should be rejected for the narrower reason that IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. This distinction matters because IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.

C:

IPv4 path preference cannot create missing IPv6 NLRI negotiation or advertisement. That critique concerns a shortcut from the unrelated IPv6 BGP NLRI family omitted case. The shortcut actually proposed in this live production incident is: Add more IPv4 routes without enabling IPv6 IS-IS reachability. It should be rejected for the narrower reason that IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. This distinction matters because IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.

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: Add more IPv4 routes without enabling IPv6 IS-IS reachability. It should be rejected for the narrower reason that IPv4 routing entries cannot replace the missing IPv6 prefix advertisements. This distinction matters because IS-IS uses suitable TLVs for IPv6 prefix reachability; a healthy IPv4 adjacency does not alone supply IPv6 routing information.

Question 302

During production incident triage, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. An engineer suggests the shortcut: "Enable an export policy that accepts every connected route on the router." Which critique explains the specific risk of that shortcut?

  1. Blanket redistribution can expose management and unrelated customer networks and create routing instability.
  2. BGP keepalive changes do not resolve an OSPF interface timer mismatch.
  3. Reference bandwidth affects metric calculation, not the area ID carried in Hello packets.
  4. Blindly redistributing external information conflicts with the intended stub-area containment model.

Explanation

Correct Answer

A:

Blanket redistribution can expose management and unrelated customer networks and create routing instability. In this live production incident the shortcut was explicitly proposed as: Enable an export policy that accepts every connected route on the router. It fails to resolve the underlying problem that External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. A sound alternative is the targeted engineering action: Add a tightly scoped OSPF export policy for the intended prefix, preserving loop and source restrictions.

Incorrect Answers

B:

BGP keepalive changes do not resolve an OSPF interface timer mismatch. That critique concerns a shortcut from the unrelated OSPF hello dead timer mismatch case. The shortcut actually proposed in this live production incident is: Enable an export policy that accepts every connected route on the router. It should be rejected for the narrower reason that Blanket redistribution can expose management and unrelated customer networks and create routing instability. This distinction matters because External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

C:

Reference bandwidth affects metric calculation, not the area ID carried in Hello packets. That critique concerns a shortcut from the unrelated OSPF area ID mismatch case. The shortcut actually proposed in this live production incident is: Enable an export policy that accepts every connected route on the router. It should be rejected for the narrower reason that Blanket redistribution can expose management and unrelated customer networks and create routing instability. This distinction matters because External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

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: Enable an export policy that accepts every connected route on the router. It should be rejected for the narrower reason that Blanket redistribution can expose management and unrelated customer networks and create routing instability. This distinction matters because External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

Question 303

During production incident triage, engineers observe: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. An engineer suggests the shortcut: "Rely on upstream filtering alone and leave local import rules open." Which critique explains the specific risk of that shortcut?

  1. Remote-side policy is outside local control and does not enforce an explicit receiving security boundary.
  2. Routing policy is evaluated for routes after a session forms; it cannot make an invalid peer-AS OPEN exchange acceptable.
  3. Advertising more prefixes is irrelevant until the peers can negotiate their underlying transport session.
  4. Local preference governs route choice and does not change TCP source address or peer reachability.

Explanation

Correct Answer

A:

Remote-side policy is outside local control and does not enforce an explicit receiving security boundary. In this live production incident the shortcut was explicitly proposed as: Rely on upstream filtering alone and leave local import rules open. It fails to resolve the underlying problem that BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. A sound alternative is the targeted engineering action: Install a narrowly scoped BGP import policy rejecting prohibited prefixes before accepting the intended announced routes.

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: Rely on upstream filtering alone and leave local import rules open. It should be rejected for the narrower reason that Remote-side policy is outside local control and does not enforce an explicit receiving security boundary. This distinction matters because BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.

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 live production incident is: Rely on upstream filtering alone and leave local import rules open. It should be rejected for the narrower reason that Remote-side policy is outside local control and does not enforce an explicit receiving security boundary. This distinction matters because BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.

D:

Local preference governs route choice and does not change TCP source address or peer reachability. That critique concerns a shortcut from the unrelated IBGP loopback source resolution case. The shortcut actually proposed in this live production incident is: Rely on upstream filtering alone and leave local import rules open. It should be rejected for the narrower reason that Remote-side policy is outside local control and does not enforce an explicit receiving security boundary. This distinction matters because BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.

Question 304

During production incident triage, engineers observe: An AE bundle loses one physical member but monitoring still shows the logical interface up, and traffic exceeds the remaining member's capacity. An engineer suggests the shortcut: "Judge success solely from the AE interface's up status while ignoring member utilization." Which critique explains the specific risk of that shortcut?

  1. Logical link state does not certify available bandwidth after a partial member failure.
  2. Routing metrics in OSPF do not directly determine VRRP primary election.
  3. A gateway-election priority has no role in preserving the chassis routing protocol state across RE change.
  4. LAG link redundancy cannot substitute for backup RE routing protocol state synchronization.

Explanation

Correct Answer

A:

Logical link state does not certify available bandwidth after a partial member failure. In this live production incident the shortcut was explicitly proposed as: Judge success solely from the AE interface's up status while ignoring member utilization. It fails to resolve the underlying problem that A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime. A sound alternative is the targeted engineering action: Check active LAG members and traffic distribution, then reduce load or restore capacity while preserving forwarding continuity.

Incorrect Answers

B:

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: Judge success solely from the AE interface's up status while ignoring member utilization. It should be rejected for the narrower reason that Logical link state does not certify available bandwidth after a partial member failure. This distinction matters because A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.

C:

A gateway-election priority has no role in preserving the chassis routing protocol state across RE change. That critique concerns a shortcut from the unrelated GRES forwarding versus routing continuity case. The shortcut actually proposed in this live production incident is: Judge success solely from the AE interface's up status while ignoring member utilization. It should be rejected for the narrower reason that Logical link state does not certify available bandwidth after a partial member failure. This distinction matters because A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.

D:

LAG link redundancy cannot substitute for backup RE routing protocol state synchronization. That critique concerns a shortcut from the unrelated NSR backup routing synchronization case. The shortcut actually proposed in this live production incident is: Judge success solely from the AE interface's up status while ignoring member utilization. It should be rejected for the narrower reason that Logical link state does not certify available bandwidth after a partial member failure. This distinction matters because A LAG can remain operational with surviving members while its usable capacity shrinks, creating congestion despite logical interface uptime.

Question 305

During production incident triage, 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. Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design.
  2. Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix.
  3. Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility.
  4. More routes in the original table do not implement selective forwarding through a different routing table.

Explanation

Correct Answer

B:

Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. In this live production incident 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:

Removing valid specifics would disrupt actual destinations and does not establish a correct summary-fallback design. That critique concerns a shortcut from the unrelated Aggregate rejection behavior case. The shortcut actually proposed in this live production incident is: Change 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:

Administrative descriptions and physical speeds do not establish equal routing cost or multipath eligibility. That critique concerns a shortcut from the unrelated Equal-cost multipath eligibility case. The shortcut actually proposed in this live production incident is: 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.

D:

More routes in the original table do not implement selective forwarding through a different routing table. That critique concerns a shortcut from the unrelated Filter-based forwarding classification case. The shortcut actually proposed in this live production incident is: Change 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 306

During production incident triage, engineers observe: A customer reports that one large TCP transfer uses only one link of a two-member equal-cost path, calling it an ECMP defect despite other flows sharing both paths. An engineer suggests the shortcut: "Enable arbitrary per-packet splitting on the production service without checking reordering risk." 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. BGP timers do not create the aggregate's necessary routing-table contribution.
  3. An unconditional default masks missing prerequisites and may direct traffic into an unintended path.
  4. Forcing packets of one flow onto different paths can reorder packets and harm transport performance.

Explanation

Correct Answer

D:

Forcing packets of one flow onto different paths can reorder packets and harm transport performance. In this live production incident the shortcut was explicitly proposed as: Enable arbitrary per-packet splitting on the production service without checking reordering risk. It fails to resolve the underlying problem that Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths. A sound alternative is the targeted engineering action: Explain and verify per-flow hashing behavior, then test with multiple independent flows before considering a design change.

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: Enable arbitrary per-packet splitting on the production service without checking reordering risk. It should be rejected for the narrower reason that Forcing packets of one flow onto different paths can reorder packets and harm transport performance. This distinction matters because Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.

B:

BGP timers do not create the aggregate's necessary routing-table contribution. That critique concerns a shortcut from the unrelated Aggregate route contribution case. The shortcut actually proposed in this live production incident is: Enable arbitrary per-packet splitting on the production service without checking reordering risk. It should be rejected for the narrower reason that Forcing packets of one flow onto different paths can reorder packets and harm transport performance. This distinction matters because Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.

C:

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: Enable arbitrary per-packet splitting on the production service without checking reordering risk. It should be rejected for the narrower reason that Forcing packets of one flow onto different paths can reorder packets and harm transport performance. This distinction matters because Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.

Question 307

During production incident triage, engineers observe: A provider intends one traffic class to use a different routing instance, but all packets still follow inet.0 because the ingress forwarding filter never selects the alternate table. An engineer suggests the shortcut: "Add a static route to inet.0 for every destination, ignoring the ingress filter." 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. More routes in the original table do not implement selective forwarding through a different routing table.
  3. BGP timers do not create the aggregate's necessary routing-table contribution.
  4. Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk.

Explanation

Correct Answer

B:

More routes in the original table do not implement selective forwarding through a different routing table. In this live production incident the shortcut was explicitly proposed as: Add a static route to inet.0 for every destination, ignoring the ingress filter. It fails to resolve the underlying problem that Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route. A sound alternative is the targeted engineering action: Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.

Incorrect Answers

A:

Changing OSPF cost does not normally displace a lower-preference static route for the identical prefix. That critique concerns a shortcut from the unrelated Administrative preference overrides static case. The shortcut actually proposed in this live production incident is: Add a static route to inet.0 for every destination, ignoring the ingress filter. It should be rejected for the narrower reason that More routes in the original table do not implement selective forwarding through a different routing table. This distinction matters because Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.

C:

BGP timers do not create the aggregate's necessary routing-table contribution. That critique concerns a shortcut from the unrelated Aggregate route contribution case. The shortcut actually proposed in this live production incident is: Add a static route to inet.0 for every destination, ignoring the ingress filter. It should be rejected for the narrower reason that More routes in the original table do not implement selective forwarding through a different routing table. This distinction matters because Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.

D:

Global relaxation hides a routing or addressing error and exposes unrelated prefixes to the same risk. That critique concerns a shortcut from the unrelated Martian-address acceptance case. The shortcut actually proposed in this live production incident is: Add a static route to inet.0 for every destination, ignoring the ingress filter. It should be rejected for the narrower reason that More routes in the original table do not implement selective forwarding through a different routing table. This distinction matters because Filter-based forwarding selects a routing table based on matched packet fields at the ingress point; the selected table must contain a usable destination route.

Question 308

During production incident triage, engineers observe: Two participating IS-IS routers stop exchanging valid LSPs after a key rotation applied to only one side. An engineer suggests the shortcut: "Disable all IS-IS authentication in the area to bypass the mismatched key." 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. Broad deactivation removes protections and can expose the link-state domain to untrusted control packets.
  3. Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
  4. OSPF election settings are unrelated to IS-IS DIS selection on the LAN.

Explanation

Correct Answer

B:

Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. In this live production incident the shortcut was explicitly proposed as: Disable all IS-IS authentication in the area to bypass the mismatched key. It fails to resolve the underlying problem that When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted. A sound alternative is the targeted engineering action: Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.

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: Disable all IS-IS authentication in the area to bypass the mismatched key. It should be rejected for the narrower reason that Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. This distinction matters because When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.

C:

Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. That critique concerns a shortcut from the unrelated IS-IS narrow metric ceiling case. The shortcut actually proposed in this live production incident is: Disable all IS-IS authentication in the area to bypass the mismatched key. It should be rejected for the narrower reason that Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. This distinction matters because When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.

D:

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 live production incident is: Disable all IS-IS authentication in the area to bypass the mismatched key. It should be rejected for the narrower reason that Broad deactivation removes protections and can expose the link-state domain to untrusted control packets. This distinction matters because When IS-IS authentication is enabled, authenticated messages must pass validation before control-plane information is accepted.

Question 309

During production incident triage, engineers observe: An eBGP IPv4 session is Established and carries inet routes, but expected IPv6 prefixes never appear because inet6 unicast is not enabled for the peering design. An engineer suggests the shortcut: "Add an IPv6 address to the physical interface but leave BGP family negotiation unchanged." 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. Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI.
  3. MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS.
  4. OSPF LAN DR election settings do not modify the BGP path attributes being compared.

Explanation

Correct Answer

B:

Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. In this live production incident the shortcut was explicitly proposed as: Add an IPv6 address to the physical interface but leave BGP family negotiation unchanged. It fails to resolve the underlying problem that BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session. A sound alternative is the targeted engineering action: Enable and verify the intended BGP IPv6 unicast family and IPv6 next-hop reachability on the appropriate peer context.

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 IPv6 address to the physical interface but leave BGP family negotiation unchanged. It should be rejected for the narrower reason that Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. This distinction matters because BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.

C:

MED is normally used to influence inbound choice by neighbors, not internal egress preference across the local AS. That critique concerns a shortcut from the unrelated BGP local preference egress case. The shortcut actually proposed in this live production incident is: Add an IPv6 address to the physical interface but leave BGP family negotiation unchanged. It should be rejected for the narrower reason that Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. This distinction matters because BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.

D:

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 IPv6 address to the physical interface but leave BGP family negotiation unchanged. It should be rejected for the narrower reason that Interface IPv6 addressing alone does not authorize or exchange BGP inet6 unicast NLRI. This distinction matters because BGP address-family configuration controls IPv6 route exchange independently of a healthy IPv4 unicast session.

Question 310

During production incident triage, 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. An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility.
  2. Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style.
  3. Route preference affects installation of received routes, not which IS-IS levels can form an adjacency.
  4. Additional IPv4 addresses do not provide the ISO interface family needed for IS-IS signaling.

Explanation

Correct Answer

B:

Documentation cannot extend a protocol metric's encoding or cause routers to use a new metric style. In this live production incident 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:

An IP subnet change alone cannot resolve IS-IS Level 1 NET area incompatibility. That critique concerns a shortcut from the unrelated IS-IS level-one area mismatch case. The shortcut actually proposed in this live production incident is: 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:

Route preference affects installation of received routes, not which IS-IS levels can form an adjacency. That critique concerns a shortcut from the unrelated IS-IS level capability mismatch case. The shortcut actually proposed in this live production incident is: 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.

D:

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


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.