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 79

Question 780

A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. What implementation step and validation result should be selected?

  1. Control: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. Accepted result: A planned switchover test documents forwarding and neighbor behavior against the HA design.
  2. Action: Evaluate BFD liveness detection with the associated routing protocol. Evidence: A controlled forwarding failure is detected within the approved target.
  3. Repair: Review VRRP virtual router roles, priority and failover behavior. Check: Only the intended master forwards for the virtual gateway under steady state.
  4. Change: Review router priorities and the nonpreemptive properties of DR elections. Test: The elected DR and BDR align with the tested election conditions.

Explanation

Correct Answer

B:

Because bFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments, the best response is to evaluate BFD liveness detection with the associated routing protocol. A reviewer can close the technical case only after confirming that a controlled forwarding failure is detected within the approved target.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. The current case specifically calls for: Evaluate BFD liveness detection with the associated routing protocol. The required observed result is: A controlled forwarding failure is detected within the approved target.

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 evaluate BFD liveness detection with the associated routing protocol; verify: A controlled forwarding failure is detected within the approved target.

D:

The alternative addresses a broadcast OSPF segment experiences repeated DR elections after interface priority changes, not the present root cause. Here the selected correction must reflect bFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Test for: A controlled forwarding failure is detected within the approved target.

Question 781

A customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. What remediation is most directly applicable?

  1. Recommended change: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.
  2. Next step: Compare root priority, bridge identifiers and current STP topology status.
  3. Corrective action: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.
  4. Apply this control: Match loop, BPDU and root protection to their different fault conditions.

Explanation

Correct Answer

A:

The critical observation is: Protective edge-port shutdown is evidence of BPDU policy enforcement. Correct it by taking this action: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. Confirm the outcome with: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

Incorrect Answers

B:

Configuration intent must be verified against the actual elected spanning-tree root 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.

C:

The proposed principle concerns another network fault: Forwarding-plane continuity does not prove control-plane routing continuity. 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.

D:

That result would be useful for a different failure, namely: An engineer uses loop protection as if it served the same purpose as BPDU protection on every port. The current case specifically calls for: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. The required observed result is: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

Question 782

A backup path becomes primary after a preference edit even though the design called for failover only. Which technical distinction best describes the observed symptom?

  1. The governing rule is: A generated route depends on its contributing-route conditions rather than mere configuration presence.
  2. The key distinction is: Preference edits can change route selection without any interface outage.
  3. Protocol behavior: Routing policy acceptance must reflect explicitly permitted destinations.
  4. Underlying principle: OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Preference edits can change route selection without any interface outage. Remedy: Restore the intended route preferences and check selected forwarding next hops. Proof: A primary-link test chooses the expected primary then fails to backup on loss.

Incorrect Answers

A:

Verify route contribution and the conditions for route generation is a relevant step for the separate scenario in which a generated route is configured but its expected contributing route is absent from the routing table. It does not directly fix this case. Instead restore the intended route preferences and check selected forwarding next hops; verify: A primary-link test chooses the expected primary then fails to backup on loss.

C:

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: Preference edits can change route selection without any interface outage. Required validation: A primary-link test chooses the expected primary then fails to backup on loss.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone, while this scenario depends on preference edits can change route selection without any interface outage. Verify the correction with: A primary-link test chooses the expected primary then fails to backup on loss.

Question 783

An NSR configuration fails commit after an operator adds graceful restart on the same device. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: Per-VLAN spanning-tree behavior can differ across VLANs.
  2. The governing rule is: Aggregated links need operational member health monitoring and suitable capacity planning.
  3. The key distinction is: VRRP provides a master and backup mechanism for a shared virtual default gateway.
  4. Protocol behavior: Conflicting local GR and NSR configuration must be resolved before activation.

Explanation

Correct Answer

D:

Underlying cause: Conflicting local GR and NSR configuration must be resolved before activation. Corrective action: remove the incompatible local mode and validate the supported HA configuration. Verify the outcome: The corrected candidate commits and the Routing Engine synchronization check passes.

Incorrect Answers

A:

The proposed principle concerns another network fault: Per-VLAN spanning-tree behavior can differ across VLANs. Here, conflicting local GR and NSR configuration must be resolved before activation. The most direct correction is to remove the incompatible local mode and validate the supported HA configuration, confirmed by the corrected candidate commits and the Routing Engine synchronization check passes.

B:

That result would be useful for a different failure, namely: One LAG member fails silently and the service loses capacity even though the logical interface remains active. The current case specifically calls for: Remove the incompatible local mode and validate the supported HA configuration. The required observed result is: The corrected candidate commits and the Routing Engine synchronization check passes.

C:

This response would target a different source scenario: Two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. It cannot establish the current acceptance requirement, which is: The corrected candidate commits and the Routing Engine synchronization check passes. The relevant action is: Remove the incompatible local mode and validate the supported HA configuration.

Question 784

A carrier receives the same source MAC from two access ports and sees frequent forwarding-table moves. Which post-change observation most strongly confirms the correction?

  1. Expected observation: A controlled election yields the approved root with documented path changes.
  2. Verification result: The MAC table stabilizes on the authorized port after loop or miswire correction.
  3. Closeout evidence: A frame trace shows only expected domain members receive the unknown destination.
  4. Acceptance check: The service uses a valid supported customer VLAN ID.

Explanation

Correct Answer

B:

Correct diagnosis: MAC learning reflects observed source location and may churn during loops or mobility. The appropriate action is: Investigate MAC movement, loops and correct bridge-domain membership. The follow-up evidence required is: The MAC table stabilizes on the authorized port after loop or miswire correction.

Incorrect Answers

A:

This answer would be more suitable when a planned root bridge migration is configured but the operational root remains on the old switch, where the corrective action is to compare root priority, bridge identifiers and current STP topology status. The failure here is different: MAC learning reflects observed source location and may churn during loops or mobility. Required validation: The MAC table stabilizes on the authorized port after loop or miswire correction.

C:

Bridges learn source MAC locations and flood unknown destinations within a permitted domain describes a neighboring protocol concern. In this case the controlling fact is mAC learning reflects observed source location and may churn during loops or mobility. A correct remediation would investigate MAC movement, loops and correct bridge-domain membership and demonstrate: The MAC table stabilizes on the authorized port after loop or miswire correction.

D:

The proposed principle concerns another network fault: 802.1Q VLAN identifiers have reserved values and platform constraints. Here, mAC learning reflects observed source location and may churn during loops or mobility. The most direct correction is to investigate MAC movement, loops and correct bridge-domain membership, confirmed by the MAC table stabilizes on the authorized port after loop or miswire correction.

Question 785

A data center needs separate spanning trees for VLAN groupings but the plan uses a single root for every VLAN with no design review. What remediation is most directly applicable?

  1. Next step: Inspect spanning-tree loop-protection events, root path and link state.
  2. Corrective action: Match loop, BPDU and root protection to their different fault conditions.
  3. Apply this control: Evaluate MSTP instances and explicit VLAN-to-instance mapping.
  4. Remediation: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning.

Explanation

Correct Answer

C:

The critical observation is: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Correct it by taking this action: Evaluate MSTP instances and explicit VLAN-to-instance mapping. Confirm the outcome with: Each VLAN maps to its intended instance and designated root.

Incorrect Answers

A:

This response would target a different source scenario: An alternate uplink remains blocked after the primary path fails because expected BPDUs disappear. It cannot establish the current acceptance requirement, which is: Each VLAN maps to its intended instance and designated root. The relevant action is: Evaluate MSTP instances and explicit VLAN-to-instance mapping.

B:

Match loop, BPDU and root protection to their different fault conditions is a relevant step for the separate scenario in which an engineer uses loop protection as if it served the same purpose as BPDU protection on every port. It does not directly fix this case. Instead evaluate MSTP instances and explicit VLAN-to-instance mapping; verify: Each VLAN maps to its intended instance and designated root.

D:

This answer would be more suitable when after a trunk change a MAC address is visible but only one of two VLANs can traverse the uplink, where the corrective action is to inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning. The failure here is different: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Required validation: Each VLAN maps to its intended instance and designated root.

Question 786

A route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes. What operational check demonstrates that the intended outcome occurred?

  1. Acceptance check: A hop-by-hop labeled test locates and corrects the failing label action.
  2. The test confirms that the transport endpoint again resolves and a labeled probe succeeds.
  3. Expected observation: Policy based on the intended community alters admission or preference as designed.
  4. Verification result: A segment trace follows the desired prefix or explicit adjacency.

Explanation

Correct Answer

B:

This is the model-intended best choice because mPLS relies on selected underlay transport reachability and policy eligibility. The targeted correction is to restore the required transport route and inspect label-signaling and next-hop state. Validate it by observing that the transport endpoint again resolves and a labeled probe succeeds.

Incorrect Answers

A:

Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults describes a neighboring protocol concern. In this case the controlling fact is mPLS relies on selected underlay transport reachability and policy eligibility. A correct remediation would restore the required transport route and inspect label-signaling and next-hop state and demonstrate: The transport endpoint again resolves and a labeled probe succeeds.

C:

That result would be useful for a different failure, namely: An engineer treats a BGP community value as a standalone forwarding next hop. The current case specifically calls for: Restore the required transport route and inspect label-signaling and next-hop state. The required observed result is: The transport endpoint again resolves and a labeled probe succeeds.

D:

This response would target a different source scenario: A segment routing node uses a prefix segment but the operator treats it as a local adjacency segment. It cannot establish the current acceptance requirement, which is: The transport endpoint again resolves and a labeled probe succeeds. The relevant action is: Restore the required transport route and inspect label-signaling and next-hop state.

Question 787

A GRE tunnel interface exists but its operational state is unreliable because the source interface was changed. What should the operations engineer do first to address the stated fault?

  1. Remediation: Distinguish tunneling encapsulation from confidentiality protection.
  2. Recommended change: Verify configured tunnel source and destination and their active underlay routing.
  3. Next step: Check SR label advertisements, segment configuration and installed MPLS forwarding.
  4. Corrective action: Restore underlay endpoint reachability and then validate the inner tunnel route.

Explanation

Correct Answer

B:

Underlying cause: Tunnel endpoint parameters must correspond to actual reachable interfaces. Corrective action: verify configured tunnel source and destination and their active underlay routing. Verify the outcome: The tunnel endpoints pass test traffic after source correction.

Incorrect Answers

A:

The alternative addresses a network operator assumes a GRE tunnel encrypts customer packets merely because they are encapsulated, not the present root cause. Here the selected correction must reflect tunnel endpoint parameters must correspond to actual reachable interfaces. Test for: The tunnel endpoints pass test traffic after source correction.

C:

This option overlooks the decisive condition. Its supporting principle is lDP and SR-MPLS may coexist but each needs its own valid label/route state, while this scenario depends on tunnel endpoint parameters must correspond to actual reachable interfaces. Verify the correction with: The tunnel endpoints pass test traffic after source correction.

D:

GRE has no independent path if its outer transport becomes unreachable describes a neighboring protocol concern. In this case the controlling fact is tunnel endpoint parameters must correspond to actual reachable interfaces. A correct remediation would verify configured tunnel source and destination and their active underlay routing and demonstrate: The tunnel endpoints pass test traffic after source correction.

Question 788

Two BGP paths have different local preferences and a technician expects the shorter AS path always to win. What is the most defensible network engineering correction?

  1. Apply this control: Separate session liveness from prefix acceptance and RIB installation.
  2. Remediation: Restore the required transport route and inspect label-signaling and next-hop state.
  3. Recommended change: Evaluate routing-policy local preference before later BGP path-selection attributes.
  4. Next step: Verify IP reachability, routing instance context, TCP transport and session authentication.

Explanation

Correct Answer

C:

This is the model-intended best choice because bGP best-path selection considers higher-priority decision attributes before AS-path length. The targeted correction is to evaluate routing-policy local preference before later BGP path-selection attributes. Validate it by observing that the intended local preference policy selects the approved egress.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An eBGP peer sends frequent KEEPALIVEs but the operator assumes this proves the best route is installed. The current case specifically calls for: Evaluate routing-policy local preference before later BGP path-selection attributes. The required observed result is: The intended local preference policy selects the approved egress.

B:

This response would target a different source scenario: A route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes. It cannot establish the current acceptance requirement, which is: The intended local preference policy selects the approved egress. The relevant action is: Evaluate routing-policy local preference before later BGP path-selection attributes.

D:

The alternative addresses a BGP peer is stuck in Active after a maintenance window even though the remote address is configured, not the present root cause. Here the selected correction must reflect bGP best-path selection considers higher-priority decision attributes before AS-path length. Test for: The intended local preference policy selects the approved egress.

Question 789

An area border router stops advertising an expected summarized interarea route after a policy change. What should the operations engineer do first to address the stated fault?

  1. Corrective action: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.
  2. Apply this control: Rehearse the failure and inspect active next hops and IS-IS route changes.
  3. Remediation: Review router priorities and the nonpreemptive properties of DR elections.
  4. Recommended change: Inspect ABR area configuration, route export rules and summary policy.

Explanation

Correct Answer

D:

The selected response implements the principle that interarea reachability depends on the ABR's view and allowed advertisements. The engineer should inspect ABR area configuration, route export rules and summary policy. Successful confirmation means: The correct summarized route appears in the receiving area's route table.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is failover paths are governed by their actual configured metrics, while this scenario depends on interarea reachability depends on the ABR's view and allowed advertisements. Verify the correction with: The correct summarized route appears in the receiving area's route table.

B:

A backup path requires functional forwarding, not merely topology presence describes a neighboring protocol concern. In this case the controlling fact is interarea reachability depends on the ABR's view and allowed advertisements. A correct remediation would inspect ABR area configuration, route export rules and summary policy and demonstrate: The correct summarized route appears in the receiving area's route table.

C:

The proposed principle concerns another network fault: OSPF DR selection depends on eligible routers and the current election event. Here, interarea reachability depends on the ABR's view and allowed advertisements. The most direct correction is to inspect ABR area configuration, route export rules and summary policy, confirmed by the correct summarized route appears in the receiving area's route table.

Question 790

An IRB interface is present but an operator assumes it creates a bridge domain automatically. What diagnosis and engineering response are most appropriate?

  1. Root issue: Forwarding-plane continuity does not prove control-plane routing continuity. Correction: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.
  2. Cause: Layer 2 bridging does not by itself provide IP intersubnet routing. Response: Deploy or validate an integrated routing and bridging L3 interface and gateway.
  3. Diagnosis: Junos candidate configuration changes are not active until committed. Action: Compare candidate and committed configurations and confirm actual bridge membership.
  4. Explanation: Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Repair: Verify VLAN or bridge-domain membership and its L3 IRB binding.

Explanation

Correct Answer

D:

This is the model-intended best choice because integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. The targeted correction is to verify VLAN or bridge-domain membership and its L3 IRB binding. Validate it by observing that the bridge domain and IRB interface share the configured gateway context.

Incorrect Answers

A:

Check whether GRES is paired with the intended GR or NSR support and verify protocol state is a relevant step for the separate scenario in which a Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. It does not directly fix this case. Instead verify VLAN or bridge-domain membership and its L3 IRB binding; verify: The bridge domain and IRB interface share the configured gateway context.

B:

The alternative addresses a VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain, 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.

C:

This answer would be more suitable when a virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed, where the corrective action is to compare candidate and committed configurations and confirm actual bridge membership. 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.

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