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 98

Question 970

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Document stub and normal area policies and validate expected LSA types.
  2. Audit external route export allowlists against approved customer prefixes.
  3. Periodically compare intended and observed SPF cost paths after bandwidth changes.
  4. Alert on repeated OSPF adjacency resets and divergent LSA conditions.

Explanation

Correct Answer

B:

Audit external route export allowlists against approved customer prefixes. The current controlled acceptance rehearsal demonstrates why this check matters: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. It monitors the mechanism that External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements. The continuing safeguard should be correlated with the specific acceptance test: The specifically allowed customer prefix appears as the expected external route on the peer, while other connected networks stay unadvertised.

Incorrect Answers

A:

Document stub and normal area policies and validate expected LSA types. This control addresses the distinct Stub area external LSA expectation operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The directly relevant continuing check is: Audit external route export allowlists against approved customer prefixes. The governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

C:

Periodically compare intended and observed SPF cost paths after bandwidth changes. This control addresses the distinct OSPF metric path preference operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The directly relevant continuing check is: Audit external route export allowlists against approved customer prefixes. The governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

D:

Alert on repeated OSPF adjacency resets and divergent LSA conditions. This control addresses the distinct OSPF LSDB discrepancy operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A PE learns a connected customer subnet, but an OSPF peer never receives it because it was not intentionally redistributed into OSPF. The directly relevant continuing check is: Audit external route export allowlists against approved customer prefixes. The governing mechanism is: External routes are not necessarily redistributed into OSPF automatically; export policy determines which non-OSPF routes become OSPF external advertisements.

Question 971

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Document intended MED comparison scope and test different-neighbor-AS cases.
  2. Verify prefix-level export allowlists during customer peering acceptance.
  3. Review inbound prefix filtering and max-route thresholds with every peer change.
  4. Check BGP negotiated families and IPv6 route policy during dual-stack migrations.

Explanation

Correct Answer

A:

Document intended MED comparison scope and test different-neighbor-AS cases. The current controlled acceptance rehearsal demonstrates why this check matters: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. It monitors the mechanism that BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking. The continuing safeguard should be correlated with the specific acceptance test: The best path matches the documented MED comparison scope and the selected inbound preference is confirmed with peer attributes.

Incorrect Answers

B:

Verify prefix-level export allowlists during customer peering acceptance. This control addresses the distinct BGP export policy omission operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The directly relevant continuing check is: Document intended MED comparison scope and test different-neighbor-AS cases. The governing mechanism is: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.

C:

Review inbound prefix filtering and max-route thresholds with every peer change. This control addresses the distinct BGP import policy leak operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The directly relevant continuing check is: Document intended MED comparison scope and test different-neighbor-AS cases. The governing mechanism is: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.

D:

Check BGP negotiated families and IPv6 route policy during dual-stack migrations. This control addresses the distinct BGP IPv6 family inactive operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An operator expects the lowest MED to win between paths received from two different neighbor autonomous systems, but the BGP selection does not follow that expectation. The directly relevant continuing check is: Document intended MED comparison scope and test different-neighbor-AS cases. The governing mechanism is: BGP MED comparison behavior depends on origin AS and configured selection policy; it is not a universal lowest-MED global ranking.

Question 972

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Alert on repeated OSPF adjacency resets and divergent LSA conditions.
  2. Test backbone adjacency and ABR inter-area route reachability on every area change.
  3. Reserve router IDs in an inventory and audit uniqueness during device provisioning.
  4. Review passive-interface policy whenever a customer-facing segment is added.

Explanation

Correct Answer

D:

Review passive-interface policy whenever a customer-facing segment is added. The current controlled acceptance rehearsal demonstrates why this check matters: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. It monitors the mechanism that Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information. The continuing safeguard should be correlated with the specific acceptance test: No OSPF neighbors form on the customer LAN, yet core routers still learn the intended LAN prefix.

Incorrect Answers

A:

Alert on repeated OSPF adjacency resets and divergent LSA conditions. This control addresses the distinct OSPF LSDB discrepancy operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The directly relevant continuing check is: Review passive-interface policy whenever a customer-facing segment is added. The governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

B:

Test backbone adjacency and ABR inter-area route reachability on every area change. This control addresses the distinct OSPF backbone connectivity operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The directly relevant continuing check is: Review passive-interface policy whenever a customer-facing segment is added. The governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

C:

Reserve router IDs in an inventory and audit uniqueness during device provisioning. This control addresses the distinct Duplicate OSPF router identifier operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A LAN prefix must be advertised into OSPF without forming unexpected adjacencies with customer devices; operators currently see stray Hellos on the LAN. The directly relevant continuing check is: Review passive-interface policy whenever a customer-facing segment is added. The governing mechanism is: Passive OSPF interfaces suppress neighbor Hello participation on the segment while their connected prefix can remain represented in the area's routing information.

Question 973

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Validate loopback reachability, source address and peer configuration during IBGP rollout.
  2. Review inbound prefix filtering and max-route thresholds with every peer change.
  3. Include AS-path comparisons in periodic interdomain routing audit reports.
  4. Check BGP negotiated families and IPv6 route policy during dual-stack migrations.

Explanation

Correct Answer

A:

Validate loopback reachability, source address and peer configuration during IBGP rollout. The current controlled acceptance rehearsal demonstrates why this check matters: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. It monitors the mechanism that IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint. The continuing safeguard should be correlated with the specific acceptance test: The session establishes using the intended loopback source and destination and stays up after a physical link fails.

Incorrect Answers

B:

Review inbound prefix filtering and max-route thresholds with every peer change. This control addresses the distinct BGP import policy leak operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. The directly relevant continuing check is: Validate loopback reachability, source address and peer configuration during IBGP rollout. The governing mechanism is: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.

C:

Include AS-path comparisons in periodic interdomain routing audit reports. This control addresses the distinct BGP AS-path comparison operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. The directly relevant continuing check is: Validate loopback reachability, source address and peer configuration during IBGP rollout. The governing mechanism is: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.

D:

Check BGP negotiated families and IPv6 route policy during dual-stack migrations. This control addresses the distinct BGP IPv6 family inactive operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: An IBGP session targets a remote loopback but the local router sources traffic from a physical interface not permitted by its peer, so the BGP connection fails. The directly relevant continuing check is: Validate loopback reachability, source address and peer configuration during IBGP rollout. The governing mechanism is: IBGP loopback peering depends on correct local address selection and recursive reachability to the configured peer endpoint.

Question 974

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes.
  2. Review STP root and backup priorities after device replacement or MAC changes.
  3. Monitor root-protection violations and keep the intended root location documented.
  4. Exercise RSTP role transition in planned failover tests.

Explanation

Correct Answer

A:

Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. The current controlled acceptance rehearsal demonstrates why this check matters: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. It monitors the mechanism that VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits. The continuing safeguard should be correlated with the specific acceptance test: Each VLAN reports its planned root and forwarding links with no loops during a controlled failover.

Incorrect Answers

B:

Review STP root and backup priorities after device replacement or MAC changes. This control addresses the distinct Root bridge election priority operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The directly relevant continuing check is: Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. The governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.

C:

Monitor root-protection violations and keep the intended root location documented. This control addresses the distinct Root protection against rogue core operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The directly relevant continuing check is: Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. The governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.

D:

Exercise RSTP role transition in planned failover tests. This control addresses the distinct RSTP alternate port activation operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: VLAN 100 and VLAN 200 are intended to use different roots, but a single shared spanning-tree topology sends both over the same constrained link. The directly relevant continuing check is: Review spanning-tree instance resource limits and per-VLAN path placement during capacity changes. The governing mechanism is: VSTP or suitable spanning-tree instances can apply VLAN-specific root and forwarding decisions, subject to platform limits.

Question 975

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Baseline metric-style compatibility before area-wide IS-IS cost adjustments.
  2. Record DIS priorities and pseudonode behavior in service-provider switching design reviews.
  3. Monitor Level 1 attached-bit or default-route availability at area boundaries.
  4. Alert on unusual LSP aging patterns and repeated adjacency churn.

Explanation

Correct Answer

B:

Record DIS priorities and pseudonode behavior in service-provider switching design reviews. The current controlled acceptance rehearsal demonstrates why this check matters: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. It monitors the mechanism that The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design. The continuing safeguard should be correlated with the specific acceptance test: The designated system matches the planned candidate, pseudonode LSPs are coherent, and LAN adjacencies remain stable.

Incorrect Answers

A:

Baseline metric-style compatibility before area-wide IS-IS cost adjustments. This control addresses the distinct IS-IS narrow metric ceiling operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. The directly relevant continuing check is: Record DIS priorities and pseudonode behavior in service-provider switching design reviews. The governing mechanism is: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

C:

Monitor Level 1 attached-bit or default-route availability at area boundaries. This control addresses the distinct IS-IS Level 1 exit default operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. The directly relevant continuing check is: Record DIS priorities and pseudonode behavior in service-provider switching design reviews. The governing mechanism is: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

D:

Alert on unusual LSP aging patterns and repeated adjacency churn. This control addresses the distinct IS-IS LSP lifetime anomaly operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: On an IS-IS broadcast LAN, an unintended router acts as the designated intermediate system because its interface priority differs from the design. The directly relevant continuing check is: Record DIS priorities and pseudonode behavior in service-provider switching design reviews. The governing mechanism is: The IS-IS DIS election on a broadcast segment considers interface priority and system ID, rather than OSPF-style DR and BDR design.

Question 976

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 ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Review generated-route contributors and policy conditions whenever edge reachability changes.
  2. Maintain a documented martian and bogon-address policy aligned with assigned network ranges.
  3. Exercise backup-path liveness detection under downstream and local failure scenarios.
  4. Test covered and uncovered address samples as part of aggregate change validation.

Explanation

Correct Answer

D:

Test covered and uncovered address samples as part of aggregate change validation. The current controlled acceptance rehearsal demonstrates why this check matters: PE-15 summarizes customer prefixes, but packets matching only the aggregate are supposed to be rejected, whereas the current forwarding behavior is unclear. It monitors the mechanism that An aggregate summary can install a reject or discard forwarding action; a valid more-specific route still takes precedence by longest-prefix match. The continuing safeguard should be correlated with the specific acceptance test: 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

A:

Review generated-route contributors and policy conditions whenever edge reachability changes. This control addresses the distinct Generated default route prerequisite operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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 directly relevant continuing check is: Test covered and uncovered address samples as part of aggregate change validation. The 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.

B:

Maintain a documented martian and bogon-address policy aligned with assigned network ranges. This control addresses the distinct Martian-address acceptance operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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 directly relevant continuing check is: Test covered and uncovered address samples as part of aggregate change validation. The 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.

C:

Exercise backup-path liveness detection under downstream and local failure scenarios. This control addresses the distinct Static backup blackhole operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here 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 directly relevant continuing check is: Test covered and uncovered address samples as part of aggregate change validation. The 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.

Question 977

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency.
  2. Review generated-route contributors and policy conditions whenever edge reachability changes.
  3. Maintain a documented martian and bogon-address policy aligned with assigned network ranges.
  4. Review import/export scope and route-copy audits when new routing instances are introduced.

Explanation

Correct Answer

A:

Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. The current controlled acceptance rehearsal demonstrates why this check matters: 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. It monitors the mechanism 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. The continuing safeguard should be correlated with the specific acceptance test: Several distinct test flows distribute across eligible next hops while each test flow remains ordered and correctly forwarded.

Incorrect Answers

B:

Review generated-route contributors and policy conditions whenever edge reachability changes. This control addresses the distinct Generated default route prerequisite operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: 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. The directly relevant continuing check is: Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. The governing mechanism is: 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:

Maintain a documented martian and bogon-address policy aligned with assigned network ranges. This control addresses the distinct Martian-address acceptance operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: 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. The directly relevant continuing check is: Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. The governing mechanism is: Per-flow load balancing preserves packet ordering by placing a given flow on one chosen member; a single flow need not span all paths.

D:

Review import/export scope and route-copy audits when new routing instances are introduced. This control addresses the distinct RIB group forwarding copy operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: 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. The directly relevant continuing check is: Use multi-flow telemetry and documented hashing expectations when evaluating ECMP efficiency. The governing mechanism is: 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 978

During a controlled acceptance rehearsal of the same defect on a separate test network, 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. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Review inbound prefix filtering and max-route thresholds with every peer change.
  2. Validate loopback reachability, source address and peer configuration during IBGP rollout.
  3. Document peer distance, TTL, and authorized transport path for remote eBGP sessions.
  4. Monitor unresolved BGP next hops separately from session establishment.

Explanation

Correct Answer

A:

Review inbound prefix filtering and max-route thresholds with every peer change. The current controlled acceptance rehearsal demonstrates why this check matters: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. It monitors the mechanism that BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice. The continuing safeguard should be correlated with the specific acceptance test: The rejected prefix does not appear as an eligible route while approved advertised prefixes remain available.

Incorrect Answers

B:

Validate loopback reachability, source address and peer configuration during IBGP rollout. This control addresses the distinct IBGP loopback source resolution operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The directly relevant continuing check is: Review inbound prefix filtering and max-route thresholds with every peer change. The governing mechanism is: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.

C:

Document peer distance, TTL, and authorized transport path for remote eBGP sessions. This control addresses the distinct EBGP multihop peering operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The directly relevant continuing check is: Review inbound prefix filtering and max-route thresholds with every peer change. The governing mechanism is: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.

D:

Monitor unresolved BGP next hops separately from session establishment. This control addresses the distinct BGP next-hop inaccessible operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A BGP feed contains private or customer-specific prefixes that should be rejected but are installed because the receiving policy accepts too broadly. The directly relevant continuing check is: Review inbound prefix filtering and max-route thresholds with every peer change. The governing mechanism is: BGP import policy controls which routes may enter the receiving route selection process, separate from the remote peer's export choice.

Question 979

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Include interface network-type checks in PE-to-PE circuit acceptance.
  2. Include OSPF interface MTU checks in transport migration validation.
  3. Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks.
  4. Test backbone adjacency and ABR inter-area route reachability on every area change.

Explanation

Correct Answer

C:

Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. The current controlled acceptance rehearsal demonstrates why this check matters: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. It monitors the mechanism that OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree. The continuing safeguard should be correlated with the specific acceptance test: Authenticated OSPF packet exchange resumes, the neighbor reaches Full and no authentication failures remain in logs.

Incorrect Answers

A:

Include interface network-type checks in PE-to-PE circuit acceptance. This control addresses the distinct Point-to-point OSPF network type operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The directly relevant continuing check is: Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. The governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

B:

Include OSPF interface MTU checks in transport migration validation. This control addresses the distinct OSPF MTU ExStart stall operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The directly relevant continuing check is: Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. The governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

D:

Test backbone adjacency and ABR inter-area route reachability on every area change. This control addresses the distinct OSPF backbone connectivity operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: After rotating an OSPFv2 authentication key on one side of a core link, Hellos fail to authenticate and the adjacency disappears. The directly relevant continuing check is: Rotate authenticated neighbor keys using synchronized maintenance and failure rollback checks. The governing mechanism is: OSPFv2 authenticated packet exchanges are rejected when the peer's configured key or authentication method does not agree.

Question 980

During a controlled acceptance rehearsal of the same defect on a separate test network, engineers observe: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. Which ongoing validation or operating control most directly prevents this specific failure from recurring?

  1. Sample FEC label bindings and forwarding resolution after prefix or IGP changes.
  2. Monitor LFIB consistency with advertised label bindings after topology convergence.
  3. Document expected label stacks at ingress, transit and penultimate hop for key services.
  4. Track reserved and unreserved bandwidth on TE links before new LSP provisioning.

Explanation

Correct Answer

D:

Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The current controlled acceptance rehearsal demonstrates why this check matters: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. It monitors the mechanism that RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability. The continuing safeguard should be correlated with the specific acceptance test: The LSP reserves its intended bandwidth end to end without exceeding the engineered link limits.

Incorrect Answers

A:

Sample FEC label bindings and forwarding resolution after prefix or IGP changes. This control addresses the distinct Missing LDP FEC label mapping operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The directly relevant continuing check is: Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

B:

Monitor LFIB consistency with advertised label bindings after topology convergence. This control addresses the distinct Incoming label missing in LFIB operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The directly relevant continuing check is: Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.

C:

Document expected label stacks at ingress, transit and penultimate hop for key services. This control addresses the distinct Penultimate hop popping operational scenario rather than preventing recurrence of the controlled acceptance rehearsal. The observed problem here is: A new RSVP LSP fails setup despite basic IP reachability because the configured requested bandwidth exceeds reservable capacity on a chosen link. The directly relevant continuing check is: Track reserved and unreserved bandwidth on TE links before new LSP provisioning. The governing mechanism is: RSVP-TE admission control uses available reservation capacity and signaled traffic-engineering constraints beyond simple route reachability.


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.