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 59

Question 580

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target.
  2. Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover.
  3. Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.
  4. Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable.

Explanation

Correct Answer

C:

Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health. In the controlled acceptance rehearsal, the reported evidence is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. The intervention follows the governing fact that VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. Closure requires the corresponding specific confirmation: Failback occurs only after verified upstream reachability and virtual gateway traffic remains stable across recovery.

Incorrect Answers

A:

Use a supported combination of GRES and NSR or appropriate graceful restart to meet the control-plane continuity target. This action was designed for the separate GRES forwarding versus routing continuity case, not the controlled acceptance rehearsal being assessed. The present observation is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Its governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The narrower applicable remedy is: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.

B:

Enable and verify supported Nonstop Active Routing with the necessary routing-state synchronization before a controlled switchover. This action was designed for the separate NSR backup routing synchronization case, not the controlled acceptance rehearsal being assessed. The present observation is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Its governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The narrower applicable remedy is: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.

D:

Validate supported graceful-restart negotiation and helper capability, or choose NSR when helper dependency is unacceptable. This action was designed for the separate Graceful restart helper expectations case, not the controlled acceptance rehearsal being assessed. The present observation is: A recovering primary repeatedly retakes the VRRP role before its upstream route stabilizes, causing a brief traffic outage at each return. Its governing mechanism is: VRRP preemption policy governs whether and when a preferred primary reclaims the virtual gateway; premature takeover can disrupt traffic. The narrower applicable remedy is: Tune supported preemption timing or tracking against actual upstream readiness so role recovery follows path health.

Question 581

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.
  2. Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
  3. Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
  4. Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established.

Explanation

Correct Answer

A:

Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended. In the controlled acceptance rehearsal, the reported evidence is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. The intervention follows the governing fact that IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. Closure requires the corresponding specific confirmation: The two devices show an up adjacency at the intended level and their Level 1 link-state databases exchange reachability.

Incorrect Answers

B:

Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the controlled acceptance rehearsal being assessed. The present observation is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Its governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The narrower applicable remedy is: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.

C:

Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible. This action was designed for the separate IS-IS route export scope case, not the controlled acceptance rehearsal being assessed. The present observation is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Its governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The narrower applicable remedy is: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.

D:

Verify why the IS-IS overload state is set and clear it only after topology and routing readiness are established. This action was designed for the separate IS-IS overload-state recovery case, not the controlled acceptance rehearsal being assessed. The present observation is: Two Junos routers on the same LAN are configured for Level 1 IS-IS but use different area addresses and never establish an L1 adjacency. Its governing mechanism is: IS-IS Level 1 adjacencies require matching area addresses, whereas Level 2 provides backbone connectivity across areas. The narrower applicable remedy is: Align the intended ISO area identifiers for Level 1 neighbors or adjust level design where inter-area L2 adjacency is intended.

Question 582

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
  2. Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
  3. Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.
  4. Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

Explanation

Correct Answer

A:

Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. In the controlled acceptance rehearsal, the reported evidence is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. The intervention follows the governing fact that An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. Closure requires the corresponding specific confirmation: A controlled packet to an active more-specific prefix forwards, while a packet to an uncovered address receives the intended reject or silent-discard behavior.

Incorrect Answers

B:

Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. This action was designed for the separate Generated default route prerequisite case, not the controlled acceptance rehearsal being assessed. The present observation is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Its governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The narrower applicable remedy is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.

C:

Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix. This action was designed for the separate Martian-address acceptance case, not the controlled acceptance rehearsal being assessed. The present observation is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Its governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The narrower applicable remedy is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.

D:

Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. This action was designed for the separate Static backup blackhole case, not the controlled acceptance rehearsal being assessed. The present observation is: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. Its governing mechanism is: An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The narrower applicable remedy is: Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.

Question 583

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. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Move the access port to the approved VLAN and verify logical interface membership and learning.
  2. Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag.
  3. Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag.
  4. Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.

Explanation

Correct Answer

D:

Align intended native VLAN handling on both ends or require explicit tagging according to the approved design. In the controlled acceptance rehearsal, the reported evidence is: 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. The intervention follows the governing fact that Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. Closure requires the corresponding specific confirmation: A controlled untagged frame maps to the same intended VLAN on both ends and no unauthorized L2 reachability remains.

Incorrect Answers

A:

Move the access port to the approved VLAN and verify logical interface membership and learning. This action was designed for the separate Access VLAN membership case, not the controlled acceptance rehearsal being assessed. The present observation is: 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. Its governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The narrower applicable remedy is: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.

B:

Place them in distinct approved outer service VLAN contexts while preserving each customer's inner tag. This action was designed for the separate Provider VLAN customer isolation case, not the controlled acceptance rehearsal being assessed. The present observation is: 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. Its governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The narrower applicable remedy is: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.

C:

Correct the interface's supported VLAN tagging and logical-unit encapsulation so each service is matched to the intended tag. This action was designed for the separate Flexible VLAN tagging logical units case, not the controlled acceptance rehearsal being assessed. The present observation is: 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. Its governing mechanism is: Untagged ingress frames on a trunk are associated with the configured native VLAN; a mismatch creates inconsistent broadcast-domain mapping. The narrower applicable remedy is: Align intended native VLAN handling on both ends or require explicit tagging according to the approved design.

Question 584

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination.
  2. Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix.
  3. Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
  4. Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.

Explanation

Correct Answer

C:

Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. In the controlled acceptance rehearsal, the reported evidence is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. The intervention follows the governing fact that A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. Closure requires the corresponding specific confirmation: With the downstream fault injected, the unsuitable backup route is withdrawn or de-preferred and valid traffic moves to the tested alternate.

Incorrect Answers

A:

Set and verify the intended reject or discard handling for traffic that matches the summary but has no more-specific reachable destination. This action was designed for the separate Aggregate rejection behavior case, not the controlled acceptance rehearsal being assessed. The present observation is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Its governing mechanism is: A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. The narrower applicable remedy is: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

B:

Inspect the relevant martian and routing-policy configuration and explicitly enforce the authorized treatment of that prefix. This action was designed for the separate Martian-address acceptance case, not the controlled acceptance rehearsal being assessed. The present observation is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Its governing mechanism is: A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. The narrower applicable remedy is: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

D:

Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table. This action was designed for the separate RIB group forwarding copy case, not the controlled acceptance rehearsal being assessed. The present observation is: A static backup path remains attractive during a fiber failure even though the far-end device cannot forward onward; link-state alone is insufficient to detect reachability. Its governing mechanism is: A static next hop may appear link-reachable while the remote end-to-end path is unusable, so a tracking mechanism such as BFD can be necessary. The narrower applicable remedy is: Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.

Question 585

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.
  2. Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support.
  3. Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election.
  4. Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs.

Explanation

Correct Answer

A:

Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible. In the controlled acceptance rehearsal, the reported evidence is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. The intervention follows the governing fact that IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. Closure requires the corresponding specific confirmation: The intended prefix appears at the expected level without management or unrelated customer routes being leaked.

Incorrect Answers

B:

Use compatible wide-metric operation on participating devices and apply deliberate interface metric values after confirming support. This action was designed for the separate IS-IS narrow metric ceiling case, not the controlled acceptance rehearsal being assessed. The present observation is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Its governing mechanism is: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The narrower applicable remedy is: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.

C:

Set and validate appropriate DIS priority on the LAN participant interfaces, then observe a controlled election. This action was designed for the separate IS-IS DIS election surprise case, not the controlled acceptance rehearsal being assessed. The present observation is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Its governing mechanism is: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The narrower applicable remedy is: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.

D:

Synchronize the intended IS-IS authentication method and accepted keys on both peers, then verify accepted PDUs. This action was designed for the separate IS-IS authentication mismatch case, not the controlled acceptance rehearsal being assessed. The present observation is: A service prefix is missing from peer IS-IS tables after a customer migration because no controlled export policy permits it. Its governing mechanism is: IS-IS export policy controls which eligible non-IS-IS routes can be redistributed into the link-state domain. The narrower applicable remedy is: Create a narrowly matched export policy for the approved service prefix and confirm the originating route is eligible.

Question 586

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
  2. Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.
  3. Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
  4. Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

Explanation

Correct Answer

B:

Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform. In the controlled acceptance rehearsal, the reported evidence is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. The intervention follows the governing fact that GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. Closure requires the corresponding specific confirmation: Large application packets traverse the tunnel without blackholing, and measured payload size respects the underlay capacity.

Incorrect Answers

A:

Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation. This action was designed for the separate GRE confidentiality misconception case, not the controlled acceptance rehearsal being assessed. The present observation is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Its governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The narrower applicable remedy is: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.

C:

Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. This action was designed for the separate GRE tunnel endpoint mismatch case, not the controlled acceptance rehearsal being assessed. The present observation is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Its governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The narrower applicable remedy is: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.

D:

Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. This action was designed for the separate GRE underlay recursive loss case, not the controlled acceptance rehearsal being assessed. The present observation is: A GRE path passes small payloads but drops full-size traffic after an underlay MTU reduction because the new headers exceed available packet size. Its governing mechanism is: GRE adds encapsulation overhead, so usable payload MTU can be smaller than the underlying link MTU. The narrower applicable remedy is: Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.

Question 587

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.
  2. Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure.
  3. Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes.
  4. Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table.

Explanation

Correct Answer

A:

Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior. In the controlled acceptance rehearsal, the reported evidence is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. The intervention follows the governing fact that Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. Closure requires the corresponding specific confirmation: The generated default becomes active with the expected next hop only when the qualifying contributor exists.

Incorrect Answers

B:

Tie backup-route validity to a suitable reachability detection mechanism and test route withdrawal during downstream failure. This action was designed for the separate Static backup blackhole case, not the controlled acceptance rehearsal being assessed. The present observation is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Its governing mechanism is: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The narrower applicable remedy is: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

C:

Apply a narrowly matched ingress firewall filter action that selects the intended forwarding routing instance and verify its routes. This action was designed for the separate Filter-based forwarding classification case, not the controlled acceptance rehearsal being assessed. The present observation is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Its governing mechanism is: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The narrower applicable remedy is: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

D:

Configure and test the intended RIB group or specific controlled route import into the appropriate secondary routing table. This action was designed for the separate RIB group forwarding copy case, not the controlled acceptance rehearsal being assessed. The present observation is: A generated default route is expected to support an edge policy, but no eligible route satisfies the generation condition, so the default never becomes active. Its governing mechanism is: Generated routes depend on matching contributing routing information and generation policy, rather than merely being present in configuration text. The narrower applicable remedy is: Correct the generated-route policy or the required active contributing route, then confirm the intended next-hop behavior.

Question 588

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure.
  2. Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.
  3. Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth.
  4. Configure and validate supported RSVP link protection with a viable bypass for the affected protected link.

Explanation

Correct Answer

B:

Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers. In the controlled acceptance rehearsal, the reported evidence is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. The intervention follows the governing fact that SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. Closure requires the corresponding specific confirmation: The segment identifier is visible in the IGP database, resolves to the correct label, and traffic reaches the selected node.

Incorrect Answers

A:

Verify the intended PHP behavior and distinguish an implicit-null advertisement from an actual forwarding failure. This action was designed for the separate Penultimate hop popping case, not the controlled acceptance rehearsal being assessed. The present observation is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. Its governing mechanism is: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The narrower applicable remedy is: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.

C:

Reduce the justified bandwidth request or select a path with adequate RSVP-TE reservable bandwidth. This action was designed for the separate RSVP reservable bandwidth shortage case, not the controlled acceptance rehearsal being assessed. The present observation is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. Its governing mechanism is: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The narrower applicable remedy is: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.

D:

Configure and validate supported RSVP link protection with a viable bypass for the affected protected link. This action was designed for the separate RSVP link protection plan case, not the controlled acceptance rehearsal being assessed. The present observation is: An SR-MPLS shortest-path LSP is expected, but the source has no usable advertised segment identifier for the target core node. Its governing mechanism is: SR-MPLS forwarding depends on consistent segment identification and an IGP-distributed mapping from segments to MPLS labels. The narrower applicable remedy is: Verify the intended node or prefix SID advertisement in the participating IGP and the label allocation on the source and transit routers.

Question 589

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.
  2. Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path.
  3. Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation.
  4. Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform.

Explanation

Correct Answer

A:

Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself. In the controlled acceptance rehearsal, the reported evidence is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. The intervention follows the governing fact that GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. Closure requires the corresponding specific confirmation: An underlay path reaches the outer peer without circular routing and inner GRE packets are successfully decapsulated.

Incorrect Answers

B:

Correct the GRE source and destination endpoint pairs, then verify the approved encapsulation path. This action was designed for the separate GRE tunnel endpoint mismatch case, not the controlled acceptance rehearsal being assessed. The present observation is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Its governing mechanism is: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The narrower applicable remedy is: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

C:

Add an appropriate encryption mechanism such as supported IPsec where confidentiality is required, while treating GRE as encapsulation. This action was designed for the separate GRE confidentiality misconception case, not the controlled acceptance rehearsal being assessed. The present observation is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Its governing mechanism is: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The narrower applicable remedy is: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

D:

Correct tunnel MTU or MSS considerations and verify fragmentation or PMTU behavior for the specific supported platform. This action was designed for the separate GRE encapsulation MTU overhead case, not the controlled acceptance rehearsal being assessed. The present observation is: A GRE interface remains administratively up while tunneled traffic fails because the outer destination is unreachable through the underlying IPv4 table. Its governing mechanism is: GRE is a stateless overlay requiring outer endpoint reachability and generally does not bring the interface down merely because a remote endpoint is unreachable. The narrower applicable remedy is: Restore a valid underlay route to the GRE destination and verify that the route does not recursively depend on the tunnel itself.

Question 590

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. Which narrowly targeted action best resolves the demonstrated condition without introducing unrelated changes?

  1. Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops.
  2. Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database.
  3. Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.
  4. Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path.

Explanation

Correct Answer

C:

Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel. In the controlled acceptance rehearsal, the reported evidence is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. The intervention follows the governing fact that An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. Closure requires the corresponding specific confirmation: An IPv6 trace crosses the intended tunnel, while outer IPv4 packets reach the peer endpoints and encapsulation counters increment.

Incorrect Answers

A:

Enable and verify the BGP inet6 unicast family with permitted IPv6 export/import policy and resolvable next hops. This action was designed for the separate IPv6 BGP NLRI family omitted case, not the controlled acceptance rehearsal being assessed. The present observation is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. Its governing mechanism is: An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. The narrower applicable remedy is: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.

B:

Enable the intended IS-IS IPv6 address-family or reachability support and validate the IPv6 prefixes in the IS-IS database. This action was designed for the separate IS-IS IPv6 reachability TLVs case, not the controlled acceptance rehearsal being assessed. The present observation is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. Its governing mechanism is: An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. The narrower applicable remedy is: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.

D:

Permit required ICMPv6 Packet Too Big signaling and align encapsulation MTU with the supported end-to-end path. This action was designed for the separate ICMPv6 packet-too-big handling case, not the controlled acceptance rehearsal being assessed. The present observation is: Two IPv6-only customer islands must communicate across an IPv4 underlay, but no tunnel endpoints have been configured for their routed IPv6 traffic. Its governing mechanism is: An encapsulating tunnel can transport IPv6 payload packets over an IPv4 underlay when endpoint and route mapping are correct. The narrower applicable remedy is: Configure a supported IPv6-over-IPv4 tunnel with reachable outer IPv4 endpoints and correct IPv6 routing into the tunnel.


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.