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 76

Question 750

A router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0. Which change best corrects the failure without losing the intended design?

  1. Next step: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.
  2. Corrective action: Place the correct L1/L2 boundary and evaluate flooding scope.
  3. Apply this control: Review hierarchical OSPF backbone attachment and area border placement.
  4. Remediation: Check the expected DR/BDR versus DROther neighbor-state relationships.

Explanation

Correct Answer

C:

Because multi-area OSPF design requires attention to backbone connectivity, the best response is to review hierarchical OSPF backbone attachment and area border placement. A reviewer can close the technical case only after confirming that the planned ABR topology provides verified interarea reachability.

Incorrect Answers

A:

Confirm the explicit cost plan in a failure rehearsal using route and topology outputs is a relevant step for the separate scenario in which an OSPF route appears longer than expected after failover because a backup link's cost was never verified. It does not directly fix this case. Instead review hierarchical OSPF backbone attachment and area border placement; verify: The planned ABR topology provides verified interarea reachability.

B:

The alternative addresses a provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding, not the present root cause. Here the selected correction must reflect multi-area OSPF design requires attention to backbone connectivity. Test for: The planned ABR topology provides verified interarea reachability.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF broadcast topology reduces unnecessary full adjacency mesh formation, while this scenario depends on multi-area OSPF design requires attention to backbone connectivity. Verify the correction with: The planned ABR topology provides verified interarea reachability.

Question 751

An MPLS service fails after penultimate-hop popping is changed without reviewing the egress disposition. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: An upstream LSR can remove a label before the egress in an appropriate PHP design. Remediation: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  2. Root issue: LDP and SR-MPLS may coexist but each needs its own valid label/route state. Correction: Check SR label advertisements, segment configuration and installed MPLS forwarding.
  3. Cause: Incorrect label removal can expose payload handling that the egress does not expect. Response: Verify the label action and egress handling for the intended service stack.
  4. Diagnosis: Preference edits can change route selection without any interface outage. Action: Restore the intended route preferences and check selected forwarding next hops.

Explanation

Correct Answer

C:

The case turns on the distinction that incorrect label removal can expose payload handling that the egress does not expect. Apply this concrete engineering step: Verify the label action and egress handling for the intended service stack. An acceptable verification outcome is: A traced packet arrives at egress with the correct remaining stack or payload.

Incorrect Answers

A:

The proposed principle concerns another network fault: An upstream LSR can remove a label before the egress in an appropriate PHP design. Here, incorrect label removal can expose payload handling that the egress does not expect. The most direct correction is to verify the label action and egress handling for the intended service stack, confirmed by a traced packet arrives at egress with the correct remaining stack or payload.

B:

That result would be useful for a different failure, namely: A provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. The current case specifically calls for: Verify the label action and egress handling for the intended service stack. The required observed result is: A traced packet arrives at egress with the correct remaining stack or payload.

D:

Restore the intended route preferences and check selected forwarding next hops is a relevant step for the separate scenario in which a backup path becomes primary after a preference edit even though the design called for failover only. It does not directly fix this case. Instead verify the label action and egress handling for the intended service stack; verify: A traced packet arrives at egress with the correct remaining stack or payload.

Question 752

A virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed. Which root-cause explanation and corrective action fit the case?

  1. Explanation: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Repair: Separate customer bridge domains and validate virtual-switch membership.
  2. Fault mechanism: MAC table visibility alone does not prove trunk authorization for every VLAN. Remediation: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning.
  3. Root issue: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Correction: Evaluate BFD liveness detection with the associated routing protocol.
  4. Cause: Junos candidate configuration changes are not active until committed. Response: Compare candidate and committed configurations and confirm actual bridge membership.

Explanation

Correct Answer

D:

Because junos candidate configuration changes are not active until committed, the best response is to compare candidate and committed configurations and confirm actual bridge membership. A reviewer can close the technical case only after confirming that the active configuration and forwarding table reflect the approved VLAN change.

Incorrect Answers

A:

This answer would be more suitable when a customer bridge-domain spans two isolated customers due to reusing a virtual switch without tenant boundaries, where the corrective action is to separate customer bridge domains and validate virtual-switch membership. 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.

B:

This option overlooks the decisive condition. Its supporting principle is mAC table visibility alone does not prove trunk authorization for every VLAN, 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.

C:

BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments 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 753

A route reflector receives a new branch prefix but one iBGP client never learns it. Which technical distinction best describes the observed symptom?

  1. Root design issue: MPLS forwarding typically uses labels to select the next label-switched hop.
  2. The governing rule is: BGP transport connectivity does not guarantee every address family is negotiated and active.
  3. The key distinction is: Route reflection can fail due to session or policy scope even when the route exists centrally.
  4. Protocol behavior: Unresolvable BGP next hops can make received routes unusable.

Explanation

Correct Answer

C:

The critical observation is: Route reflection can fail due to session or policy scope even when the route exists centrally. Correct it by taking this action: Check client definitions, route-reflector session state and export policy. Confirm the outcome with: The missing client receives the correct next-hop-resolvable route.

Incorrect Answers

A:

This response would target a different source scenario: An operator expects an MPLS label to represent an entire customer IP packet header. It cannot establish the current acceptance requirement, which is: The missing client receives the correct next-hop-resolvable route. The relevant action is: Check client definitions, route-reflector session state and export policy.

B:

Verify negotiated address families and family-specific routing tables is a relevant step for the separate scenario in which a peer announces an IPv6 prefix but the operator checks only the IPv4 BGP route family. It does not directly fix this case. Instead check client definitions, route-reflector session state and export policy; verify: The missing client receives the correct next-hop-resolvable route.

D:

This answer would be more suitable when an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone, where the corrective action is to restore appropriate IGP next-hop reachability or approved next-hop-self behavior. The failure here is different: Route reflection can fail due to session or policy scope even when the route exists centrally. Required validation: The missing client receives the correct next-hop-resolvable route.

Question 754

An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. Which protocol behavior most directly determines the correct diagnosis?

  1. Underlying principle: Address validity and martian filtering affect which route sources are considered acceptable.
  2. Root design issue: Imported routes must be validated in the destination lookup context.
  3. The governing rule is: A generated route depends on its contributing-route conditions rather than mere configuration presence.
  4. The key distinction is: Neighbor state must be traced through transport before modifying route policy.

Explanation

Correct Answer

A:

Because address validity and martian filtering affect which route sources are considered acceptable, the best response is to review martian-address treatment and justify any carefully scoped exception. A reviewer can close the technical case only after confirming that the rejected address remains excluded or a documented narrowly scoped exception is applied.

Incorrect Answers

B:

The proposed principle concerns another network fault: Imported routes must be validated in the destination lookup context. Here, address validity and martian filtering affect which route sources are considered acceptable. The most direct correction is to review martian-address treatment and justify any carefully scoped exception, confirmed by the rejected address remains excluded or a documented narrowly scoped exception is applied.

C:

That result would be useful for a different failure, namely: A generated route is configured but its expected contributing route is absent from the routing table. The current case specifically calls for: Review martian-address treatment and justify any carefully scoped exception. The required observed result is: The rejected address remains excluded or a documented narrowly scoped exception is applied.

D:

This response would target a different source scenario: A BGP peer is stuck in Active after a maintenance window even though the remote address is configured. It cannot establish the current acceptance requirement, which is: The rejected address remains excluded or a documented narrowly scoped exception is applied. The relevant action is: Review martian-address treatment and justify any carefully scoped exception.

Question 755

An engineer treats a BGP community value as a standalone forwarding next hop. Which technical distinction best describes the observed symptom?

  1. Protocol behavior: Communities are policy signaling metadata and not the packet-forwarding next hop themselves.
  2. Underlying principle: Unresolvable BGP next hops can make received routes unusable.
  3. Root design issue: BGP best-path selection considers higher-priority decision attributes before AS-path length.
  4. The governing rule is: Failover paths are governed by their actual configured metrics.

Explanation

Correct Answer

A:

The case turns on the distinction that communities are policy signaling metadata and not the packet-forwarding next hop themselves. Apply this concrete engineering step: Differentiate community tags from reachability and forwarding attributes. An acceptable verification outcome is: Policy based on the intended community alters admission or preference as designed.

Incorrect Answers

B:

This answer would be more suitable when an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone, where the corrective action is to restore appropriate IGP next-hop reachability or approved next-hop-self behavior. The failure here is different: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Required validation: Policy based on the intended community alters admission or preference as designed.

C:

This option overlooks the decisive condition. Its supporting principle is bGP best-path selection considers higher-priority decision attributes before AS-path length, while this scenario depends on communities are policy signaling metadata and not the packet-forwarding next hop themselves. Verify the correction with: Policy based on the intended community alters admission or preference as designed.

D:

Failover paths are governed by their actual configured metrics describes a neighboring protocol concern. In this case the controlling fact is communities are policy signaling metadata and not the packet-forwarding next hop themselves. A correct remediation would differentiate community tags from reachability and forwarding attributes and demonstrate: Policy based on the intended community alters admission or preference as designed.

Question 756

A customer edge loses its OSPF neighbor after an authentication key rollover. Which evidence would justify closing this troubleshooting case?

  1. Acceptance check: The rejected address remains excluded or a documented narrowly scoped exception is applied.
  2. The test confirms that a post-change route view selects the approved shortest path.
  3. Expected observation: The packet trace shows each message at its appropriate adjacency stage.
  4. Verification result: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

Explanation

Correct Answer

D:

Correct diagnosis: Authentication mismatches can reject otherwise valid OSPF protocol packets. The appropriate action is: Coordinate authentication parameters and test the key change under maintenance controls. The follow-up evidence required is: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. The current case specifically calls for: Coordinate authentication parameters and test the key change under maintenance controls. The required observed result is: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

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: Authenticated adjacency returns and no fallback to unauthenticated operation occurs. The relevant action is: Coordinate authentication parameters and test the key change under maintenance controls.

C:

Differentiate neighbor discovery from database synchronization message types is a relevant step for the separate scenario in which a technician treats an OSPF Link State Request as the same message as a Hello packet. It does not directly fix this case. Instead coordinate authentication parameters and test the key change under maintenance controls; verify: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

Question 757

A Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. Which statement identifies the key design assumption that failed?

  1. The governing rule is: Forwarding-plane continuity does not prove control-plane routing continuity.
  2. The key distinction is: VRRP provides a master and backup mechanism for a shared virtual default gateway.
  3. Protocol behavior: Authentication mismatches can reject otherwise valid OSPF protocol packets.
  4. Underlying principle: Aggregated links need operational member health monitoring and suitable capacity planning.

Explanation

Correct Answer

A:

The critical observation is: Forwarding-plane continuity does not prove control-plane routing continuity. Correct it by taking this action: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. Confirm the outcome with: A planned switchover test documents forwarding and neighbor behavior against the HA design.

Incorrect Answers

B:

VRRP provides a master and backup mechanism for a shared virtual default gateway describes a neighboring protocol concern. In this case the controlling fact is forwarding-plane continuity does not prove control-plane routing continuity. A correct remediation would check whether GRES is paired with the intended GR or NSR support and verify protocol state and demonstrate: A planned switchover test documents forwarding and neighbor behavior against the HA design.

C:

The proposed principle concerns another network fault: Authentication mismatches can reject otherwise valid OSPF protocol packets. Here, forwarding-plane continuity does not prove control-plane routing continuity. The most direct correction is to check whether GRES is paired with the intended GR or NSR support and verify protocol state, confirmed by a planned switchover test documents forwarding and neighbor behavior against the HA design.

D:

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: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. The required observed result is: A planned switchover test documents forwarding and neighbor behavior against the HA design.

Question 758

A BGP prefix remains rejected after an intended route filter update because an earlier term rejects it. What remediation is most directly applicable?

  1. Apply this control: Verify the label action and egress handling for the intended service stack.
  2. Remediation: Check client definitions, route-reflector session state and export policy.
  3. Recommended change: Evaluate routing-policy local preference before later BGP path-selection attributes.
  4. Next step: Evaluate policy terms in effective order and test matching routes.

Explanation

Correct Answer

D:

This is the model-intended best choice because policy evaluation order can short-circuit later intended acceptance. The targeted correction is to evaluate policy terms in effective order and test matching routes. Validate it by observing that the approved route matches an accepting term and the denied route remains denied.

Incorrect Answers

A:

Verify the label action and egress handling for the intended service stack is a relevant step for the separate scenario in which an MPLS service fails after penultimate-hop popping is changed without reviewing the egress disposition. It does not directly fix this case. Instead evaluate policy terms in effective order and test matching routes; verify: The approved route matches an accepting term and the denied route remains denied.

B:

The alternative addresses a route reflector receives a new branch prefix but one iBGP client never learns it, not the present root cause. Here the selected correction must reflect policy evaluation order can short-circuit later intended acceptance. Test for: The approved route matches an accepting term and the denied route remains denied.

C:

This answer would be more suitable when two BGP paths have different local preferences and a technician expects the shorter AS path always to win, where the corrective action is to evaluate routing-policy local preference before later BGP path-selection attributes. The failure here is different: Policy evaluation order can short-circuit later intended acceptance. Required validation: The approved route matches an accepting term and the denied route remains denied.

Question 759

A technician treats an OSPF Link State Request as the same message as a Hello packet. Which technical explanation and controlled action address the symptom?

  1. Cause: Overlapping address classification makes precise route-filter and policy terms essential. Response: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples.
  2. Diagnosis: External OSPF redistribution must be reviewed for scope and scale. Action: Restore explicit policy matching and confirm external route advertisements.
  3. Explanation: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. Repair: Differentiate neighbor discovery from database synchronization message types.
  4. Fault mechanism: OSPF normally prefers the least accumulated metric to a destination. Remediation: Revisit additive path cost and verify SPF outcomes across alternative links.

Explanation

Correct Answer

C:

The case turns on the distinction that oSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. Apply this concrete engineering step: Differentiate neighbor discovery from database synchronization message types. An acceptable verification outcome is: The packet trace shows each message at its appropriate adjacency stage.

Incorrect Answers

A:

The proposed principle concerns another network fault: Overlapping address classification makes precise route-filter and policy terms essential. Here, oSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. The most direct correction is to differentiate neighbor discovery from database synchronization message types, confirmed by the packet trace shows each message at its appropriate adjacency stage.

B:

That result would be useful for a different failure, namely: A BGP prefix redistribution into OSPF causes a flood of routes that were not in the approved design. The current case specifically calls for: Differentiate neighbor discovery from database synchronization message types. The required observed result is: The packet trace shows each message at its appropriate adjacency stage.

D:

Revisit additive path cost and verify SPF outcomes across alternative links is a relevant step for the separate scenario in which a branch uses a higher OSPF interface cost but expects that branch to remain the preferred primary path. It does not directly fix this case. Instead differentiate neighbor discovery from database synchronization message types; verify: The packet trace shows each message at its appropriate adjacency stage.

Question 760

An engineer assumes both routers must reach Full with every speaker on a broadcast network. What remediation is most directly applicable?

  1. Next step: Separate route-selection and lookup-table changes and test each with candidate configuration.
  2. Corrective action: Coordinate authentication parameters and test the key change under maintenance controls.
  3. Apply this control: Revisit additive path cost and verify SPF outcomes across alternative links.
  4. Remediation: Check the expected DR/BDR versus DROther neighbor-state relationships.

Explanation

Correct Answer

D:

Because oSPF broadcast topology reduces unnecessary full adjacency mesh formation, the best response is to check the expected DR/BDR versus DROther neighbor-state relationships. A reviewer can close the technical case only after confirming that the neighbor states match expected DR roles and routing converges.

Incorrect Answers

A:

This answer would be more suitable when a policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit, where the corrective action is to separate route-selection and lookup-table changes and test each with candidate configuration. The failure here is different: OSPF broadcast topology reduces unnecessary full adjacency mesh formation. Required validation: The neighbor states match expected DR roles and routing converges.

B:

This option overlooks the decisive condition. Its supporting principle is authentication mismatches can reject otherwise valid OSPF protocol packets, while this scenario depends on oSPF broadcast topology reduces unnecessary full adjacency mesh formation. Verify the correction with: The neighbor states match expected DR roles and routing converges.

C:

OSPF normally prefers the least accumulated metric to a destination describes a neighboring protocol concern. In this case the controlling fact is oSPF broadcast topology reduces unnecessary full adjacency mesh formation. A correct remediation would check the expected DR/BDR versus DROther neighbor-state relationships and demonstrate: The neighbor states match expected DR roles and routing converges.

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