mcAfee Secure Website
exam =5
exam =6

Exam Code: JN0-364

Exam Name: Service Provider Routing and Switching, Specialist (JNCIS-SP)

Certification Provider: Juniper

Juniper JN0-364 Questions & Answers

Reliable & Actual Study Materials for JN0-364 Exam Success

69 Questions & Answers with Testing Engine

"JN0-364: Service Provider Routing and Switching, Specialist (JNCIS-SP)" Testing Engine covers all the knowledge points of the real Juniper JN0-364 exam.

The latest actual JN0-364 Questions & Answers from Pass4sure. Everything you need to prepare and get best score at JN0-364 exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Juniper Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 67

Question 660

A Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. Check: A planned switchover test documents forwarding and neighbor behavior against the HA design.
  2. Change: Check VRRP group, interface, priority, advertisements and tracking conditions. Test: The backup assumes master role and clients retain access to the virtual gateway.
  3. Implement: Review VRRP virtual router roles, priority and failover behavior. Verify: Only the intended master forwards for the virtual gateway under steady state.
  4. Control: Inspect link-state databases and SPF output on affected routers. Accepted result: A shared stable topology produces consistent path computation.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Forwarding-plane continuity does not prove control-plane routing continuity. Remedy: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. Proof: A planned switchover test documents forwarding and neighbor behavior against the HA design.

Incorrect Answers

B:

This response would target a different source scenario: A VRRP backup router does not take over when the primary gateway interface is disabled. It cannot establish the current acceptance requirement, which is: A planned switchover test documents forwarding and neighbor behavior against the HA design. The relevant action is: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.

C:

Review VRRP virtual router roles, priority and failover behavior is a relevant step for the separate scenario in which two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. It does not directly fix this case. Instead check whether GRES is paired with the intended GR or NSR support and verify protocol state; verify: A planned switchover test documents forwarding and neighbor behavior against the HA design.

D:

The alternative addresses a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency, not the present root cause. Here the selected correction must reflect forwarding-plane continuity does not prove control-plane routing continuity. Test for: A planned switchover test documents forwarding and neighbor behavior against the HA design.

Question 661

A link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. Which evidence would justify closing this troubleshooting case?

  1. Expected observation: A controlled neighbor check reaches Full after configuration correction.
  2. Verification result: The expected redistributed prefix appears with the right OSPF route type.
  3. Closeout evidence: A test packet follows the expected active forwarding next hop and interface.
  4. Acceptance check: A post-change route view selects the approved shortest path.

Explanation

Correct Answer

B:

The case turns on the distinction that oSPF route type and LSA scope depend on where routing information originates. Apply this concrete engineering step: Distinguish internal LSAs from externally originated route information. An acceptable verification outcome is: The expected redistributed prefix appears with the right OSPF route type.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is oSPF network-type and Hello compatibility can prevent adjacency formation, while this scenario depends on oSPF route type and LSA scope depend on where routing information originates. Verify the correction with: The expected redistributed prefix appears with the right OSPF route type.

C:

The proposed principle concerns another network fault: Forwarding-table and interface evidence localize faults beyond RIB reachability. Here, oSPF route type and LSA scope depend on where routing information originates. The most direct correction is to distinguish internal LSAs from externally originated route information, confirmed by the expected redistributed prefix appears with the right OSPF route type.

D:

That result would be useful for a different failure, namely: OSPF route preference changes after a new link is added and a latency-sensitive service takes the wrong path. The current case specifically calls for: Distinguish internal LSAs from externally originated route information. The required observed result is: The expected redistributed prefix appears with the right OSPF route type.

Question 662

A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. Which technical distinction best describes the observed symptom?

  1. Protocol behavior: iBGP can preserve externally learned next-hop information that internal speakers must resolve.
  2. Underlying principle: End-to-end signaling state alone cannot pinpoint a data-plane label failure.
  3. Root design issue: RSVP LSP setup can fail resource or path constraints even with valid IP reachability.
  4. The governing rule is: LDP label bindings are useful only with a functional path to the FEC next hop.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Remedy: Collect hop-local LFIB, label forwarding and interface counters along the LSP. Proof: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

Incorrect Answers

A:

Review BGP next-hop reachability and explicit next-hop handling is a relevant step for the separate scenario in which a provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. It does not directly fix this case. Instead collect hop-local LFIB, label forwarding and interface counters along the LSP; verify: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

C:

This answer would be more suitable when an RSVP-signaled LSP enters a failed state after a link bandwidth change, where the corrective action is to review reservation constraints and available resources rather than resetting all label sessions. The failure here is different: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Required validation: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

D:

This option overlooks the decisive condition. Its supporting principle is lDP label bindings are useful only with a functional path to the FEC next hop, while this scenario depends on end-to-end signaling state alone cannot pinpoint a data-plane label failure. Verify the correction with: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

Question 663

A Q-in-Q customer service leaks traffic between two tenants after the outer service VLAN is reused incorrectly. Which evidence would justify closing this troubleshooting case?

  1. Acceptance check: The overlapping customer IDs remain isolated within their designated provider services.
  2. The test confirms that the backup assumes master role and clients retain access to the virtual gateway.
  3. Expected observation: Separate tagged tests pass in both permitted VLANs.
  4. Verification result: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

Explanation

Correct Answer

D:

Underlying cause: Provider outer VLAN classification must preserve tenant isolation. Corrective action: assign distinct service encapsulation and verify edge translation rules. Verify the outcome: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

Incorrect Answers

A:

The proposed principle concerns another network fault: A customer VLAN tag can be scoped by access interface and provider service context. Here, provider outer VLAN classification must preserve tenant isolation. The most direct correction is to assign distinct service encapsulation and verify edge translation rules, confirmed by cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

B:

That result would be useful for a different failure, namely: A VRRP backup router does not take over when the primary gateway interface is disabled. The current case specifically calls for: Assign distinct service encapsulation and verify edge translation rules. The required observed result is: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

C:

This response would target a different source scenario: After a trunk change a MAC address is visible but only one of two VLANs can traverse the uplink. It cannot establish the current acceptance requirement, which is: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end. The relevant action is: Assign distinct service encapsulation and verify edge translation rules.

Question 664

An engineer modifies BGP keepalive or hold timers and the session flaps during CPU pressure. What assessment accurately links the fault to its correction?

  1. Explanation: iBGP scaling mechanisms reduce the full-mesh session requirement. Repair: Evaluate route reflection with defined cluster and client boundaries.
  2. Fault mechanism: Outer and inner labels can have distinct transport and service roles. Remediation: Inspect the full MPLS label stack and outgoing label operation.
  3. Root issue: Neighbor state must be traced through transport before modifying route policy. Correction: Verify IP reachability, routing instance context, TCP transport and session authentication.
  4. Cause: Aggressive liveness settings can magnify loss or processing delays. Response: Compare negotiated timers and protocol logs with routing-engine and packet conditions.

Explanation

Correct Answer

D:

Because aggressive liveness settings can magnify loss or processing delays, the best response is to compare negotiated timers and protocol logs with routing-engine and packet conditions. A reviewer can close the technical case only after confirming that the restored session remains stable while meeting the approved detection target.

Incorrect Answers

A:

This answer would be more suitable when a small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added, where the corrective action is to evaluate route reflection with defined cluster and client boundaries. The failure here is different: Aggressive liveness settings can magnify loss or processing delays. Required validation: The restored session remains stable while meeting the approved detection target.

B:

This option overlooks the decisive condition. Its supporting principle is outer and inner labels can have distinct transport and service roles, while this scenario depends on aggressive liveness settings can magnify loss or processing delays. Verify the correction with: The restored session remains stable while meeting the approved detection target.

C:

Neighbor state must be traced through transport before modifying route policy describes a neighboring protocol concern. In this case the controlling fact is aggressive liveness settings can magnify loss or processing delays. A correct remediation would compare negotiated timers and protocol logs with routing-engine and packet conditions and demonstrate: The restored session remains stable while meeting the approved detection target.

Question 665

An RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement. What diagnosis and engineering response are most appropriate?

  1. Diagnosis: Traditional spanning-tree root election favors the lowest bridge ID. Action: Review root bridge priority and MAC-based bridge identifier comparison.
  2. Explanation: A customer VLAN tag can be scoped by access interface and provider service context. Repair: Separate provider service identification from customer VLAN identifiers.
  3. Fault mechanism: STP instability can be secondary to physical link churn. Remediation: Inspect interface faults and control-plane events before changing STP timers.
  4. Root issue: Customer control traffic must not displace the authorized provider root. Correction: Apply supported root protection at the appropriate customer-facing boundary.

Explanation

Correct Answer

C:

The critical observation is: STP instability can be secondary to physical link churn. Correct it by taking this action: Inspect interface faults and control-plane events before changing STP timers. Confirm the outcome with: After fiber repair the port converges and remains in a stable role.

Incorrect Answers

A:

This response would target a different source scenario: A switch operator treats the highest bridge ID as the guaranteed STP root. It cannot establish the current acceptance requirement, which is: After fiber repair the port converges and remains in a stable role. The relevant action is: Inspect interface faults and control-plane events before changing STP timers.

B:

Separate provider service identification from customer VLAN identifiers is a relevant step for the separate scenario in which two network services use identical customer VLAN IDs and the team assumes their frames must share one L2 broadcast domain. It does not directly fix this case. Instead inspect interface faults and control-plane events before changing STP timers; verify: After fiber repair the port converges and remains in a stable role.

D:

This answer would be more suitable when a provider STP domain changes root when a customer sends superior BPDUs from an access port, where the corrective action is to apply supported root protection at the appropriate customer-facing boundary. The failure here is different: STP instability can be secondary to physical link churn. Required validation: After fiber repair the port converges and remains in a stable role.

Question 666

A provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. What is the most defensible network engineering correction?

  1. Corrective action: Review BGP next-hop reachability and explicit next-hop handling.
  2. Apply this control: Inspect the full MPLS label stack and outgoing label operation.
  3. Remediation: Create explicit import policy and prefix limits aligned to customer contracts.
  4. Recommended change: Split export policy by authorized customer scope and verify negative advertisements.

Explanation

Correct Answer

A:

Because iBGP can preserve externally learned next-hop information that internal speakers must resolve, the best response is to review BGP next-hop reachability and explicit next-hop handling. A reviewer can close the technical case only after confirming that the internal peer has a valid route to the BGP next hop and installs the prefix.

Incorrect Answers

B:

The proposed principle concerns another network fault: Outer and inner labels can have distinct transport and service roles. Here, iBGP can preserve externally learned next-hop information that internal speakers must resolve. The most direct correction is to review BGP next-hop reachability and explicit next-hop handling, confirmed by the internal peer has a valid route to the BGP next hop and installs the prefix.

C:

That result would be useful for a different failure, namely: A new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes. The current case specifically calls for: Review BGP next-hop reachability and explicit next-hop handling. The required observed result is: The internal peer has a valid route to the BGP next hop and installs the prefix.

D:

This response would target a different source scenario: One customer’s new prefixes are advertised to a second unrelated customer via a shared export group. It cannot establish the current acceptance requirement, which is: The internal peer has a valid route to the BGP next hop and installs the prefix. The relevant action is: Review BGP next-hop reachability and explicit next-hop handling.

Question 667

A virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed. Which underlying Junos networking principle explains the failure?

  1. Protocol behavior: Junos candidate configuration changes are not active until committed.
  2. Underlying principle: Provider outer VLAN classification must preserve tenant isolation.
  3. Root design issue: Root protection can prevent undesired superior-root claims from changing root placement.
  4. The governing rule is: A customer VLAN tag can be scoped by access interface and provider service context.

Explanation

Correct Answer

A:

The case turns on the distinction that junos candidate configuration changes are not active until committed. Apply this concrete engineering step: Compare candidate and committed configurations and confirm actual bridge membership. An acceptable verification outcome is: The active configuration and forwarding table reflect the approved VLAN change.

Incorrect Answers

B:

This answer would be more suitable when a Q-in-Q customer service leaks traffic between two tenants after the outer service VLAN is reused incorrectly, where the corrective action is to assign distinct service encapsulation and verify edge translation rules. The failure here is different: Junos candidate configuration changes are not active until committed. Required validation: The active configuration and forwarding table reflect the approved VLAN change.

C:

This option overlooks the decisive condition. Its supporting principle is root protection can prevent undesired superior-root claims from changing root placement, while this scenario depends on junos candidate configuration changes are not active until committed. Verify the correction with: The active configuration and forwarding table reflect the approved VLAN change.

D:

A customer VLAN tag can be scoped by access interface and provider service context describes a neighboring protocol concern. In this case the controlling fact is junos candidate configuration changes are not active until committed. A correct remediation would compare candidate and committed configurations and confirm actual bridge membership and demonstrate: The active configuration and forwarding table reflect the approved VLAN change.

Question 668

A RIB group leak forwards a VPN service toward the wrong next hop after a route update. Which underlying Junos networking principle explains the failure?

  1. The key distinction is: Route preference determines the selected route before any multipath decision.
  2. Protocol behavior: OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone.
  3. Underlying principle: Imported routes must be validated in the destination lookup context.
  4. Root design issue: Forwarding-table and interface evidence localize faults beyond RIB reachability.

Explanation

Correct Answer

C:

This is the model-intended best choice because imported routes must be validated in the destination lookup context. The targeted correction is to check import destinations, next-hop resolution and effective routes in every receiving table. Validate it by observing that the receiving instance shows the correct route and installed next hop after correction.

Incorrect Answers

A:

That result would be useful for a different failure, namely: Two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic. The current case specifically calls for: Check import destinations, next-hop resolution and effective routes in every receiving table. The required observed result is: The receiving instance shows the correct route and installed next hop after correction.

B:

This response would target a different source scenario: OSPF route preference changes after a new link is added and a latency-sensitive service takes the wrong path. It cannot establish the current acceptance requirement, which is: The receiving instance shows the correct route and installed next hop after correction. The relevant action is: Check import destinations, next-hop resolution and effective routes in every receiving table.

D:

The alternative addresses a route shows as active but the interface destination still drops traffic after an interface move, not the present root cause. Here the selected correction must reflect imported routes must be validated in the destination lookup context. Test for: The receiving instance shows the correct route and installed next hop after correction.

Question 669

A technician edits a router ID but tests immediately without accounting for established OSPF process state. Which test result would best confirm a successful fix?

  1. Closeout evidence: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.
  2. Acceptance check: All neighbors record the new unique ID and routing stability is restored.
  3. The test confirms that the forwarding entry uses the correct next hop for the active route.
  4. Expected observation: The expected redistributed prefix appears with the right OSPF route type.

Explanation

Correct Answer

B:

The case turns on the distinction that changing router identity may require controlled protocol restart or adjacency reestablishment. Apply this concrete engineering step: Apply a safe approved OSPF process refresh and verify advertised router identity. An acceptable verification outcome is: All neighbors record the new unique ID and routing stability is restored.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is authentication mismatches can reject otherwise valid OSPF protocol packets, while this scenario depends on changing router identity may require controlled protocol restart or adjacency reestablishment. Verify the correction with: All neighbors record the new unique ID and routing stability is restored.

C:

The proposed principle concerns another network fault: Control-plane route visibility and installed forwarding state are distinct evidence. Here, changing router identity may require controlled protocol restart or adjacency reestablishment. The most direct correction is to apply a safe approved OSPF process refresh and verify advertised router identity, confirmed by all neighbors record the new unique ID and routing stability is restored.

D:

That result would be useful for a different failure, namely: A link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. The current case specifically calls for: Apply a safe approved OSPF process refresh and verify advertised router identity. The required observed result is: All neighbors record the new unique ID and routing stability is restored.

Question 670

A provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. Which technical distinction best describes the observed symptom?

  1. Root design issue: Routing instances isolate routing tables unless explicit import or export mechanisms connect them.
  2. The governing rule is: Address validity and martian filtering affect which route sources are considered acceptable.
  3. The key distinction is: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches.
  4. Protocol behavior: Summary advertisements require validation against their underlying active route policy.

Explanation

Correct Answer

A:

Correct diagnosis: Routing instances isolate routing tables unless explicit import or export mechanisms connect them. The appropriate action is: Define the intended route-leaking boundary between the customer's instance and the master routing table. The follow-up evidence required is: Each customer route is visible only in the tables approved by the design.

Incorrect Answers

B:

The alternative addresses an operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian, not the present root cause. Here the selected correction must reflect routing instances isolate routing tables unless explicit import or export mechanisms connect them. Test for: Each customer route is visible only in the tables approved by the design.

C:

This answer would be more suitable when a new OSPF uplink remains down at the adjacency stage after a router replacement, where the corrective action is to compare area, interface mode, timers, authentication and physical status on both endpoints. The failure here is different: Routing instances isolate routing tables unless explicit import or export mechanisms connect them. Required validation: Each customer route is visible only in the tables approved by the design.

D:

This option overlooks the decisive condition. Its supporting principle is summary advertisements require validation against their underlying active route policy, while this scenario depends on routing instances isolate routing tables unless explicit import or export mechanisms connect them. Verify the correction with: Each customer route is visible only in the tables approved by the design.

Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests