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 61

Question 600

A Q-in-Q customer service leaks traffic between two tenants after the outer service VLAN is reused incorrectly. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: Provider outer VLAN classification must preserve tenant isolation.
  2. Protocol behavior: Provider bridging service tags must be applied and removed at the designed boundaries.
  3. Underlying principle: RSTP can converge faster using explicit roles and handshakes where conditions allow.
  4. Root design issue: A trunk carries only its configured authorized VLANs.

Explanation

Correct Answer

A:

This is the model-intended best choice because provider outer VLAN classification must preserve tenant isolation. The targeted correction is to assign distinct service encapsulation and verify edge translation rules. Validate it by observing that cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is provider bridging service tags must be applied and removed at the designed boundaries, while this scenario depends on provider outer VLAN classification must preserve tenant isolation. Verify the correction with: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

C:

RSTP can converge faster using explicit roles and handshakes where conditions allow describes a neighboring protocol concern. In this case the controlling fact is provider outer VLAN classification must preserve tenant isolation. A correct remediation would assign distinct service encapsulation and verify edge translation rules and demonstrate: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

D:

The proposed principle concerns another network fault: A trunk carries only its configured authorized VLANs. 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.

Question 601

A Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. Which corrective action and confirmation pair is most appropriate?

  1. Action: Compare interface level settings and area configuration. Evidence: The neighbor table shows the intended level and stable adjacency.
  2. Repair: Rehearse the failure and inspect active next hops and IS-IS route changes. Check: The backup next hop resolves and carries test traffic after the primary link fails.
  3. Change: Inspect IS-IS interface enablement, levels, area identifiers and link type. Test: The corrected circuit shows the expected neighbor and link-state entries.
  4. Implement: Verify IP reachability, routing instance context, TCP transport and session authentication. Verify: The TCP peering session reaches Established and remains stable.

Explanation

Correct Answer

C:

The critical observation is: An operational interface is not evidence of matching IS-IS protocol configuration. Correct it by taking this action: Inspect IS-IS interface enablement, levels, area identifiers and link type. Confirm the outcome with: The corrected circuit shows the expected neighbor and link-state entries.

Incorrect Answers

A:

This response would target a different source scenario: An IS-IS neighbor appears only at Level 2 even though the design expects a Level 1 core segment. It cannot establish the current acceptance requirement, which is: The corrected circuit shows the expected neighbor and link-state entries. The relevant action is: Inspect IS-IS interface enablement, levels, area identifiers and link type.

B:

Rehearse the failure and inspect active next hops and IS-IS route changes is a relevant step for the separate scenario in which a provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. It does not directly fix this case. Instead inspect IS-IS interface enablement, levels, area identifiers and link type; verify: The corrected circuit shows the expected neighbor and link-state entries.

D:

This answer would be more suitable when a BGP peer is stuck in Active after a maintenance window even though the remote address is configured, where the corrective action is to verify IP reachability, routing instance context, TCP transport and session authentication. The failure here is different: An operational interface is not evidence of matching IS-IS protocol configuration. Required validation: The corrected circuit shows the expected neighbor and link-state entries.

Question 602

A provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy. Which combined repair and acceptance criterion is strongest?

  1. Control: Distinguish internal LSAs from externally originated route information. Accepted result: The expected redistributed prefix appears with the right OSPF route type.
  2. Action: Verify recursive next-hop reachability before relying on the static route. Evidence: A route lookup shows an active reachable next hop and traffic reaches the customer.
  3. Repair: Compare area, interface mode, timers, authentication and physical status on both endpoints. Check: The corrected link reaches stable Full adjacency and exchanges the intended routes.
  4. Change: Constrain redistribution and test route policy acceptance for the intended prefixes. Test: Only approved external prefixes appear in the OSPF domain.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Routing policy controls which external reachability is injected into OSPF. Remedy: Constrain redistribution and test route policy acceptance for the intended prefixes. Proof: Only approved external prefixes appear in the OSPF domain.

Incorrect Answers

A:

OSPF route type and LSA scope depend on where routing information originates describes a neighboring protocol concern. In this case the controlling fact is routing policy controls which external reachability is injected into OSPF. A correct remediation would constrain redistribution and test route policy acceptance for the intended prefixes and demonstrate: Only approved external prefixes appear in the OSPF domain.

B:

The proposed principle concerns another network fault: A configured static route need not become usable forwarding state when its next hop cannot resolve. Here, routing policy controls which external reachability is injected into OSPF. The most direct correction is to constrain redistribution and test route policy acceptance for the intended prefixes, confirmed by only approved external prefixes appear in the OSPF domain.

C:

That result would be useful for a different failure, namely: A new OSPF uplink remains down at the adjacency stage after a router replacement. The current case specifically calls for: Constrain redistribution and test route policy acceptance for the intended prefixes. The required observed result is: Only approved external prefixes appear in the OSPF domain.

Question 603

A site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency. What assessment accurately links the fault to its correction?

  1. Fault mechanism: External OSPF redistribution must be reviewed for scope and scale. Remediation: Restore explicit policy matching and confirm external route advertisements.
  2. Root issue: OSPF route type and LSA scope depend on where routing information originates. Correction: Distinguish internal LSAs from externally originated route information.
  3. Cause: OSPF route selection follows each router's synchronized topology view. Response: Inspect link-state databases and SPF output on affected routers.
  4. Diagnosis: IS-IS shortest-path output depends on effective metrics across the route. Action: Measure end-to-end route choices and review configured interface metrics.

Explanation

Correct Answer

C:

The selected response implements the principle that oSPF route selection follows each router's synchronized topology view. The engineer should inspect link-state databases and SPF output on affected routers. Successful confirmation means: A shared stable topology produces consistent path computation.

Incorrect Answers

A:

The alternative addresses a BGP prefix redistribution into OSPF causes a flood of routes that were not in the approved design, not the present root cause. Here the selected correction must reflect oSPF route selection follows each router's synchronized topology view. Test for: A shared stable topology produces consistent path computation.

B:

This answer would be more suitable when a link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy, where the corrective action is to distinguish internal LSAs from externally originated route information. The failure here is different: OSPF route selection follows each router's synchronized topology view. Required validation: A shared stable topology produces consistent path computation.

D:

IS-IS shortest-path output depends on effective metrics across the route describes a neighboring protocol concern. In this case the controlling fact is oSPF route selection follows each router's synchronized topology view. A correct remediation would inspect link-state databases and SPF output on affected routers and demonstrate: A shared stable topology produces consistent path computation.

Question 604

Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. Which protocol behavior most directly determines the correct diagnosis?

  1. The governing rule is: Routing policy controls which external reachability is injected into OSPF.
  2. The key distinction is: The designated system serves LAN pseudonode advertisement and election semantics.
  3. Protocol behavior: OSPF adjacency requires compatible area and interface parameters.
  4. Underlying principle: Changing router identity may require controlled protocol restart or adjacency reestablishment.

Explanation

Correct Answer

C:

This is the model-intended best choice because oSPF adjacency requires compatible area and interface parameters. The targeted correction is to align the area membership and verify OSPF interface settings on both sides. Validate it by observing that the peers progress to the expected adjacency state and exchange LSAs.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy. The current case specifically calls for: Align the area membership and verify OSPF interface settings on both sides. The required observed result is: The peers progress to the expected adjacency state and exchange LSAs.

B:

This response would target a different source scenario: An IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node. It cannot establish the current acceptance requirement, which is: The peers progress to the expected adjacency state and exchange LSAs. The relevant action is: Align the area membership and verify OSPF interface settings on both sides.

D:

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 adjacency requires compatible area and interface parameters. Test for: The peers progress to the expected adjacency state and exchange LSAs.

Question 605

Two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. Which change best corrects the failure without losing the intended design?

  1. Apply this control: Distinguish member-link redundancy from a single physical failure domain.
  2. Remediation: Review VRRP virtual router roles, priority and failover behavior.
  3. Recommended change: Align the area membership and verify OSPF interface settings on both sides.
  4. Next step: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.

Explanation

Correct Answer

B:

The case turns on the distinction that vRRP provides a master and backup mechanism for a shared virtual default gateway. Apply this concrete engineering step: Review VRRP virtual router roles, priority and failover behavior. An acceptable verification outcome is: Only the intended master forwards for the virtual gateway under steady state.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is link aggregation improves availability only when member links and topology provide meaningful redundancy, while this scenario depends on vRRP provides a master and backup mechanism for a shared virtual default gateway. Verify the correction with: Only the intended master forwards for the virtual gateway under steady state.

C:

The proposed principle concerns another network fault: OSPF adjacency requires compatible area and interface parameters. Here, vRRP provides a master and backup mechanism for a shared virtual default gateway. The most direct correction is to review VRRP virtual router roles, priority and failover behavior, confirmed by only the intended master forwards for the virtual gateway under steady state.

D:

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: Review VRRP virtual router roles, priority and failover behavior. The required observed result is: Only the intended master forwards for the virtual gateway under steady state.

Question 606

A provider configures an IPv6 static route but assumes IPv4 ARP will resolve its IPv6 neighbor. What diagnosis and engineering response are most appropriate?

  1. Cause: More-specific routes can override an otherwise healthy IPv6 fallback. Response: Inspect longest-match results and forwarding routes for the specific destination.
  2. Diagnosis: IS-IS adjacency and IPv6 prefix exchange are separate operational concerns. Action: Enable and verify the intended IPv6 address-family reachability advertisements.
  3. Explanation: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Repair: Distinguish the inner routed payload from outer unicast encapsulation.
  4. Fault mechanism: IPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. Remediation: Distinguish IPv6 Neighbor Discovery from IPv4 ARP.

Explanation

Correct Answer

D:

This is the model-intended best choice because iPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. The targeted correction is to distinguish IPv6 Neighbor Discovery from IPv4 ARP. Validate it by observing that the neighbor cache resolves the IPv6 next hop and traffic passes.

Incorrect Answers

A:

Inspect longest-match results and forwarding routes for the specific destination is a relevant step for the separate scenario in which a new IPv6 static backup route is configured but a more-specific route points into a blackhole. It does not directly fix this case. Instead distinguish IPv6 Neighbor Discovery from IPv4 ARP; verify: The neighbor cache resolves the IPv6 next hop and traffic passes.

B:

The alternative addresses an IS-IS backbone forms an adjacency but omits IPv6 reachability when the family is not enabled, not the present root cause. Here the selected correction must reflect iPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. Test for: The neighbor cache resolves the IPv6 next hop and traffic passes.

C:

This answer would be more suitable when an operator sends a multicast routing-protocol packet over a GRE tunnel and assumes all physical transit routers must process the inner multicast, where the corrective action is to distinguish the inner routed payload from outer unicast encapsulation. The failure here is different: IPv6 link-layer neighbor resolution uses ICMPv6 Neighbor Discovery. Required validation: The neighbor cache resolves the IPv6 next hop and traffic passes.

Question 607

A policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit. Which test result would best confirm a successful fix?

  1. The test confirms that the TCP peering session reaches Established and remains stable.
  2. Expected observation: The allowed service routes import and the forbidden more-specific prefixes do not.
  3. Verification result: The rollback and candidate checks show the exact intended RIB and FIB outcomes.
  4. Closeout evidence: Each customer route is visible only in the tables approved by the design.

Explanation

Correct Answer

C:

The case turns on the distinction that small reversible route-policy changes simplify troubleshooting and rollback. Apply this concrete engineering step: Separate route-selection and lookup-table changes and test each with candidate configuration. An acceptable verification outcome is: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

Incorrect Answers

A:

The proposed principle concerns another network fault: Neighbor state must be traced through transport before modifying route policy. Here, small reversible route-policy changes simplify troubleshooting and rollback. The most direct correction is to separate route-selection and lookup-table changes and test each with candidate configuration, confirmed by the rollback and candidate checks show the exact intended RIB and FIB outcomes.

B:

That result would be useful for a different failure, namely: A route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. The current case specifically calls for: Separate route-selection and lookup-table changes and test each with candidate configuration. The required observed result is: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

D:

Define the intended route-leaking boundary between the customer's instance and the master routing table is a relevant step for the separate scenario in which a provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. It does not directly fix this case. Instead separate route-selection and lookup-table changes and test each with candidate configuration; verify: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

Question 608

An LDP binding exists for a remote destination but the forwarding interface points to a failed next hop. Which combined repair and acceptance criterion is strongest?

  1. Implement: Inspect the full MPLS label stack and outgoing label operation. Verify: A capture identifies the label used at each transit stage.
  2. Control: Compare label bindings with the active IGP next hop and installed forwarding entries. Accepted result: The selected LDP label uses a live next-hop interface after convergence.
  3. Action: Compare negotiated timers and protocol logs with routing-engine and packet conditions. Evidence: The restored session remains stable while meeting the approved detection target.
  4. Repair: Collect hop-local LFIB, label forwarding and interface counters along the LSP. Check: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

Explanation

Correct Answer

B:

Correct diagnosis: A stale label binding cannot compensate for unusable transport forwarding. The appropriate action is: Compare label bindings with the active IGP next hop and installed forwarding entries. The follow-up evidence required is: The selected LDP label uses a live next-hop interface after convergence.

Incorrect Answers

A:

This answer would be more suitable when a router sees multiple labels on a packet but an engineer only examines the innermost label when troubleshooting transit transport, where the corrective action is to inspect the full MPLS label stack and outgoing label operation. The failure here is different: A stale label binding cannot compensate for unusable transport forwarding. Required validation: The selected LDP label uses a live next-hop interface after convergence.

C:

Aggressive liveness settings can magnify loss or processing delays describes a neighboring protocol concern. In this case the controlling fact is a stale label binding cannot compensate for unusable transport forwarding. A correct remediation would compare label bindings with the active IGP next hop and installed forwarding entries and demonstrate: The selected LDP label uses a live next-hop interface after convergence.

D:

The proposed principle concerns another network fault: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Here, a stale label binding cannot compensate for unusable transport forwarding. The most direct correction is to compare label bindings with the active IGP next hop and installed forwarding entries, confirmed by the selected LDP label uses a live next-hop interface after convergence.

Question 609

A VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain. What diagnosis and engineering response are most appropriate?

  1. 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.
  2. Fault mechanism: Spanning tree prevents forwarding loops by selecting a loop-free active topology. Remediation: Enable the appropriate spanning-tree protection and verify the blocked redundant path.
  3. Root issue: MAC table visibility alone does not prove trunk authorization for every VLAN. Correction: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning.
  4. 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.

Explanation

Correct Answer

D:

The case turns on the distinction that layer 2 bridging does not by itself provide IP intersubnet routing. Apply this concrete engineering step: Deploy or validate an integrated routing and bridging L3 interface and gateway. An acceptable verification outcome is: A test host reaches its gateway and an authorized remote subnet through IRB.

Incorrect Answers

A:

This response would target a different source scenario: An IRB interface is present but an operator assumes it creates a bridge domain automatically. It cannot establish the current acceptance requirement, which is: A test host reaches its gateway and an authorized remote subnet through IRB. The relevant action is: Deploy or validate an integrated routing and bridging L3 interface and gateway.

B:

Enable the appropriate spanning-tree protection and verify the blocked redundant path is a relevant step for the separate scenario in which a Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected. It does not directly fix this case. Instead deploy or validate an integrated routing and bridging L3 interface and gateway; verify: A test host reaches its gateway and an authorized remote subnet through IRB.

C:

The alternative addresses after a trunk change a MAC address is visible but only one of two VLANs can traverse the uplink, not the present root cause. Here the selected correction must reflect layer 2 bridging does not by itself provide IP intersubnet routing. Test for: A test host reaches its gateway and an authorized remote subnet through IRB.

Question 610

An operator changes MED and sees no route change because the target AS prioritizes other attributes. Which statement identifies the key design assumption that failed?

  1. Root design issue: MED is not guaranteed to override local policy or earlier attributes.
  2. The governing rule is: iBGP scaling mechanisms reduce the full-mesh session requirement.
  3. The key distinction is: OSPF adjacency requires compatible area and interface parameters.
  4. Protocol behavior: BGP sessions require sustained TCP connectivity independent of physical interface health.

Explanation

Correct Answer

A:

Because mED is not guaranteed to override local policy or earlier attributes, the best response is to compare MED use with actual prior BGP decision attributes and neighbor policy. A reviewer can close the technical case only after confirming that a captured received-path comparison explains which attribute selected the route.

Incorrect Answers

B:

The proposed principle concerns another network fault: iBGP scaling mechanisms reduce the full-mesh session requirement. Here, mED is not guaranteed to override local policy or earlier attributes. The most direct correction is to compare MED use with actual prior BGP decision attributes and neighbor policy, confirmed by a captured received-path comparison explains which attribute selected the route.

C:

That result would be useful for a different failure, namely: Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. The current case specifically calls for: Compare MED use with actual prior BGP decision attributes and neighbor policy. The required observed result is: A captured received-path comparison explains which attribute selected the route.

D:

This response would target a different source scenario: An EBGP peer drops repeatedly after a firewall change despite clean interface counters. It cannot establish the current acceptance requirement, which is: A captured received-path comparison explains which attribute selected the route. The relevant action is: Compare MED use with actual prior BGP decision attributes and neighbor policy.

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