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 28

Question 270

A broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. What operational check demonstrates that the intended outcome occurred?

  1. The test confirms that the tenant-specific lookup resolves and the same source-based test reaches its destination.
  2. Expected observation: All neighbors record the new unique ID and routing stability is restored.
  3. Verification result: The segment passes route and database tests with the expected neighbor states.
  4. Closeout evidence: Each router is uniquely identified and the link-state database converges.

Explanation

Correct Answer

C:

Because oSPF neighbor-state interpretation depends on multiaccess election roles, the best response is to check DR and BDR roles and expected 2-Way peers before changing a healthy segment. A reviewer can close the technical case only after confirming that the segment passes route and database tests with the expected neighbor states.

Incorrect Answers

A:

Run route and connectivity checks in the explicitly intended routing instance is a relevant step for the separate scenario in which a provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. It does not directly fix this case. Instead check DR and BDR roles and expected 2-Way peers before changing a healthy segment; verify: The segment passes route and database tests with the expected neighbor states.

B:

The alternative addresses a technician edits a router ID but tests immediately without accounting for established OSPF process state, not the present root cause. Here the selected correction must reflect oSPF neighbor-state interpretation depends on multiaccess election roles. Test for: The segment passes route and database tests with the expected neighbor states.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF identifies speakers by router ID, which must be unique inside a routing domain, while this scenario depends on oSPF neighbor-state interpretation depends on multiaccess election roles. Verify the correction with: The segment passes route and database tests with the expected neighbor states.

Question 271

Two equal-cost next hops exist but a customer assumes every successive packet must alternate between links. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: iBGP can preserve externally learned next-hop information that internal speakers must resolve.
  2. Protocol behavior: Route redistribution must be intentionally scoped to prevent cross-tenant leakage.
  3. Underlying principle: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use.
  4. Root design issue: Overlapping address classification makes precise route-filter and policy terms essential.

Explanation

Correct Answer

C:

The case turns on the distinction that multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Apply this concrete engineering step: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane. An acceptable verification outcome is: A controlled flow test verifies the selected load-sharing behavior.

Incorrect Answers

A:

The proposed principle concerns another network fault: iBGP can preserve externally learned next-hop information that internal speakers must resolve. Here, multiple eligible forwarding next hops do not guarantee per-packet round-robin use. The most direct correction is to distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane, confirmed by a controlled flow test verifies the selected load-sharing behavior.

B:

That result would be useful for a different failure, namely: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. The current case specifically calls for: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane. The required observed result is: A controlled flow test verifies the selected load-sharing behavior.

D:

Tighten the filter match and verify the next-table lookup with explicit positive and negative examples is a relevant step for the separate scenario in which a filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. It does not directly fix this case. Instead distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane; verify: A controlled flow test verifies the selected load-sharing behavior.

Question 272

A customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. Which corrective action and confirmation pair is most appropriate?

  1. Change: Review root bridge priority and MAC-based bridge identifier comparison. Test: The intended device is root under the tested priorities and tie-breakers.
  2. Implement: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. Verify: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.
  3. Control: Inspect interface faults and control-plane events before changing STP timers. Accepted result: After fiber repair the port converges and remains in a stable role.
  4. Action: Compare candidate and committed configurations and confirm actual bridge membership. Evidence: The active configuration and forwarding table reflect the approved VLAN change.

Explanation

Correct Answer

B:

Correct diagnosis: Protective edge-port shutdown is evidence of BPDU policy enforcement. The appropriate action is: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. The follow-up evidence required is: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

Incorrect Answers

A:

This answer would be more suitable when a switch operator treats the highest bridge ID as the guaranteed STP root, where the corrective action is to review root bridge priority and MAC-based bridge identifier comparison. The failure here is different: Protective edge-port shutdown is evidence of BPDU policy enforcement. Required validation: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

C:

STP instability can be secondary to physical link churn describes a neighboring protocol concern. In this case the controlling fact is protective edge-port shutdown is evidence of BPDU policy enforcement. A correct remediation would verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards and demonstrate: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

D:

The proposed principle concerns another network fault: Junos candidate configuration changes are not active until committed. Here, protective edge-port shutdown is evidence of BPDU policy enforcement. The most direct correction is to verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards, confirmed by the approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

Question 273

After a trunk change a MAC address is visible but only one of two VLANs can traverse the uplink. Which next action best resolves this observed routing or switching failure?

  1. Apply this control: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning.
  2. Remediation: Validate the usable VLAN-ID range and reserved tag values.
  3. Recommended change: Verify VLAN-to-IRB interface binding, addresses and active route entries.
  4. Next step: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.

Explanation

Correct Answer

A:

Underlying cause: MAC table visibility alone does not prove trunk authorization for every VLAN. Corrective action: inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning. Verify the outcome: Separate tagged tests pass in both permitted VLANs.

Incorrect Answers

B:

Validate the usable VLAN-ID range and reserved tag values is a relevant step for the separate scenario in which a customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. It does not directly fix this case. Instead inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning; verify: Separate tagged tests pass in both permitted VLANs.

C:

The alternative addresses a router-on-a-stick replacement with IRB stops reachability between a bridge domain and an L3 subnet, not the present root cause. Here the selected correction must reflect mAC table visibility alone does not prove trunk authorization for every VLAN. Test for: Separate tagged tests pass in both permitted VLANs.

D:

This answer would be more suitable when two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP, where the corrective action is to compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. The failure here is different: MAC table visibility alone does not prove trunk authorization for every VLAN. Required validation: Separate tagged tests pass in both permitted VLANs.

Question 274

An LDP-signaled LSP fails when the IGP route to the remote loopback disappears. Which underlying Junos networking principle explains the failure?

  1. Underlying principle: Incorrect label removal can expose payload handling that the egress does not expect.
  2. Root design issue: Labels have locally significant forwarding meaning on each LSP segment.
  3. The governing rule is: LDP label bindings are useful only with a functional path to the FEC next hop.
  4. The key distinction is: Routing instances isolate routing tables unless explicit import or export mechanisms connect them.

Explanation

Correct Answer

C:

Correct diagnosis: LDP label bindings are useful only with a functional path to the FEC next hop. The appropriate action is: Review LDP dependence on reachability and routing of the transport endpoints. The follow-up evidence required is: The restored IGP path permits LDP forwarding to the remote endpoint.

Incorrect Answers

A:

Incorrect label removal can expose payload handling that the egress does not expect describes a neighboring protocol concern. In this case the controlling fact is lDP label bindings are useful only with a functional path to the FEC next hop. A correct remediation would review LDP dependence on reachability and routing of the transport endpoints and demonstrate: The restored IGP path permits LDP forwarding to the remote endpoint.

B:

The proposed principle concerns another network fault: Labels have locally significant forwarding meaning on each LSP segment. Here, lDP label bindings are useful only with a functional path to the FEC next hop. The most direct correction is to review LDP dependence on reachability and routing of the transport endpoints, confirmed by the restored IGP path permits LDP forwarding to the remote endpoint.

D:

This response would target a different source scenario: A provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. It cannot establish the current acceptance requirement, which is: The restored IGP path permits LDP forwarding to the remote endpoint. The relevant action is: Review LDP dependence on reachability and routing of the transport endpoints.

Question 275

An IRB interface is present but an operator assumes it creates a bridge domain automatically. Which next action best resolves this observed routing or switching failure?

  1. Next step: Validate the usable VLAN-ID range and reserved tag values.
  2. Corrective action: Trace frame classification and virtual-switch bridge-domain association.
  3. Apply this control: Apply supported root protection at the appropriate customer-facing boundary.
  4. Remediation: Verify VLAN or bridge-domain membership and its L3 IRB binding.

Explanation

Correct Answer

D:

The critical observation is: Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Correct it by taking this action: Verify VLAN or bridge-domain membership and its L3 IRB binding. Confirm the outcome with: The bridge domain and IRB interface share the configured gateway context.

Incorrect Answers

A:

The alternative addresses a customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs, not the present root cause. Here the selected correction must reflect integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Test for: The bridge domain and IRB interface share the configured gateway context.

B:

This answer would be more suitable when a port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain, where the corrective action is to trace frame classification and virtual-switch bridge-domain association. The failure here is different: Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Required validation: The bridge domain and IRB interface share the configured gateway context.

C:

This option overlooks the decisive condition. Its supporting principle is customer control traffic must not displace the authorized provider root, while this scenario depends on integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Verify the correction with: The bridge domain and IRB interface share the configured gateway context.

Question 276

A customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. Which underlying Junos networking principle explains the failure?

  1. The key distinction is: 802.1Q VLAN identifiers have reserved values and platform constraints.
  2. Protocol behavior: Spanning-tree security mechanisms protect distinct topology and control-plane risks.
  3. Underlying principle: Port mode determines which customer frames are tagged or untagged at the boundary.
  4. Root design issue: Junos candidate configuration changes are not active until committed.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: 802.1Q VLAN identifiers have reserved values and platform constraints. Remedy: Validate the usable VLAN-ID range and reserved tag values. Proof: The service uses a valid supported customer VLAN ID.

Incorrect Answers

B:

This response would target a different source scenario: An engineer uses loop protection as if it served the same purpose as BPDU protection on every port. It cannot establish the current acceptance requirement, which is: The service uses a valid supported customer VLAN ID. The relevant action is: Validate the usable VLAN-ID range and reserved tag values.

C:

Distinguish access port traffic from trunk tagging behavior is a relevant step for the separate scenario in which an access port sends untagged user traffic but the engineer expects a VLAN tag from the endpoint on every frame. It does not directly fix this case. Instead validate the usable VLAN-ID range and reserved tag values; verify: The service uses a valid supported customer VLAN ID.

D:

The alternative addresses a virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed, not the present root cause. Here the selected correction must reflect 802.1Q VLAN identifiers have reserved values and platform constraints. Test for: The service uses a valid supported customer VLAN ID.

Question 277

A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. Which change best corrects the failure without losing the intended design?

  1. Remediation: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  2. Recommended change: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane.
  3. Next step: Add a precise prefix and instance match, then inspect effective imports.
  4. Corrective action: Run route and connectivity checks in the explicitly intended routing instance.

Explanation

Correct Answer

D:

The selected response implements the principle that instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. The engineer should run route and connectivity checks in the explicitly intended routing instance. Successful confirmation means: The tenant-specific lookup resolves and the same source-based test reaches its destination.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is bGP sessions require sustained TCP connectivity independent of physical interface health, while this scenario depends on instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Verify the correction with: The tenant-specific lookup resolves and the same source-based test reaches its destination.

B:

Multiple eligible forwarding next hops do not guarantee per-packet round-robin use describes a neighboring protocol concern. In this case the controlling fact is instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. A correct remediation would run route and connectivity checks in the explicitly intended routing instance and demonstrate: The tenant-specific lookup resolves and the same source-based test reaches its destination.

C:

The proposed principle concerns another network fault: Routing policy acceptance must reflect explicitly permitted destinations. Here, instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. The most direct correction is to run route and connectivity checks in the explicitly intended routing instance, confirmed by the tenant-specific lookup resolves and the same source-based test reaches its destination.

Question 278

A provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. Which root-cause explanation and corrective action fit the case?

  1. Diagnosis: A learned LSP does not ensure a destination is selected into the active routing table. Action: Inspect route import policy and forwarding selection separately from LSP presence.
  2. Explanation: BGP sessions require sustained TCP connectivity independent of physical interface health. Repair: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  3. Fault mechanism: A backup path requires functional forwarding, not merely topology presence. Remediation: Rehearse the failure and inspect active next hops and IS-IS route changes.
  4. Root issue: Compatible IS-IS levels and area information determine available adjacency types. Correction: Compare interface level settings and area configuration.

Explanation

Correct Answer

C:

Because a backup path requires functional forwarding, not merely topology presence, the best response is to rehearse the failure and inspect active next hops and IS-IS route changes. A reviewer can close the technical case only after confirming that the backup next hop resolves and carries test traffic after the primary link fails.

Incorrect Answers

A:

Inspect route import policy and forwarding selection separately from LSP presence is a relevant step for the separate scenario in which an IS-IS route disappears after a policy update while the LSP database still contains the topology. It does not directly fix this case. Instead rehearse the failure and inspect active next hops and IS-IS route changes; verify: The backup next hop resolves and carries test traffic after the primary link fails.

B:

The alternative addresses an EBGP peer drops repeatedly after a firewall change despite clean interface counters, not the present root cause. Here the selected correction must reflect a backup path requires functional forwarding, not merely topology presence. Test for: The backup next hop resolves and carries test traffic after the primary link fails.

D:

This option overlooks the decisive condition. Its supporting principle is compatible IS-IS levels and area information determine available adjacency types, while this scenario depends on a backup path requires functional forwarding, not merely topology presence. Verify the correction with: The backup next hop resolves and carries test traffic after the primary link fails.

Question 279

A provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. Which cause-and-remedy pairing reflects the observed problem?

  1. Cause: LDP label bindings are useful only with a functional path to the FEC next hop. Response: Review LDP dependence on reachability and routing of the transport endpoints.
  2. Diagnosis: LDP and SR-MPLS may coexist but each needs its own valid label/route state. Action: Check SR label advertisements, segment configuration and installed MPLS forwarding.
  3. Explanation: A stale label binding cannot compensate for unusable transport forwarding. Repair: Compare label bindings with the active IGP next hop and installed forwarding entries.
  4. Fault mechanism: Unresolvable BGP next hops can make received routes unusable. Remediation: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior.

Explanation

Correct Answer

B:

The critical observation is: LDP and SR-MPLS may coexist but each needs its own valid label/route state. Correct it by taking this action: Check SR label advertisements, segment configuration and installed MPLS forwarding. Confirm the outcome with: The intended SR transport path forwards without unintended dependence on the retired LDP path.

Incorrect Answers

A:

The proposed principle concerns another network fault: LDP label bindings are useful only with a functional path to the FEC next hop. Here, lDP and SR-MPLS may coexist but each needs its own valid label/route state. The most direct correction is to check SR label advertisements, segment configuration and installed MPLS forwarding, confirmed by the intended SR transport path forwards without unintended dependence on the retired LDP path.

C:

This response would target a different source scenario: An LDP binding exists for a remote destination but the forwarding interface points to a failed next hop. It cannot establish the current acceptance requirement, which is: The intended SR transport path forwards without unintended dependence on the retired LDP path. The relevant action is: Check SR label advertisements, segment configuration and installed MPLS forwarding.

D:

Restore appropriate IGP next-hop reachability or approved next-hop-self behavior is a relevant step for the separate scenario in which an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone. It does not directly fix this case. Instead check SR label advertisements, segment configuration and installed MPLS forwarding; verify: The intended SR transport path forwards without unintended dependence on the retired LDP path.

Question 280

An OSPF packet capture shows Link State Updates but the route remains hidden from the active table. Which corrective action and confirmation pair is most appropriate?

  1. Control: Add a precise prefix and instance match, then inspect effective imports. Accepted result: The allowed service routes import and the forbidden more-specific prefixes do not.
  2. Action: Select the correct network-type behavior and inspect the neighbor-state model. Evidence: The point-to-point adjacency forms without an unnecessary DR election.
  3. Repair: Compare received LSAs with route selection, area eligibility and next-hop resolution. Check: The routing table exposes the selection reason and the intended route is installed.
  4. Change: Apply a safe approved OSPF process refresh and verify advertised router identity. Test: All neighbors record the new unique ID and routing stability is restored.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: Receiving topology data does not guarantee a route becomes active and installed. Remedy: Compare received LSAs with route selection, area eligibility and next-hop resolution. Proof: The routing table exposes the selection reason and the intended route is installed.

Incorrect Answers

A:

This answer would be more suitable when a route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant, where the corrective action is to add a precise prefix and instance match, then inspect effective imports. The failure here is different: Receiving topology data does not guarantee a route becomes active and installed. Required validation: The routing table exposes the selection reason and the intended route is installed.

B:

This option overlooks the decisive condition. Its supporting principle is dR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links, while this scenario depends on receiving topology data does not guarantee a route becomes active and installed. Verify the correction with: The routing table exposes the selection reason and the intended route is installed.

D:

The proposed principle concerns another network fault: Changing router identity may require controlled protocol restart or adjacency reestablishment. Here, receiving topology data does not guarantee a route becomes active and installed. The most direct correction is to compare received LSAs with route selection, area eligibility and next-hop resolution, confirmed by the routing table exposes the selection reason and the intended route is installed.

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