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 24

Question 230

A network operator assumes a GRE tunnel encrypts customer packets merely because they are encapsulated. Which technical explanation and controlled action address the symptom?

  1. Root issue: Tunnel endpoint parameters must correspond to actual reachable interfaces. Correction: Verify configured tunnel source and destination and their active underlay routing.
  2. Cause: LDP signaling depends on the routing and transport state of its endpoints. Response: Check transport reachability, LDP session state and the relevant IGP routes.
  3. Diagnosis: GRE by itself does not provide encryption or authenticated confidentiality. Action: Distinguish tunneling encapsulation from confidentiality protection.
  4. Explanation: Encapsulation does not replace explicit customer route filtering and access policy. Repair: Treat tunnel decapsulation as a routing and security boundary.

Explanation

Correct Answer

C:

Because gRE by itself does not provide encryption or authenticated confidentiality, the best response is to distinguish tunneling encapsulation from confidentiality protection. A reviewer can close the technical case only after confirming that the security design adds an appropriate protected transport where needed.

Incorrect Answers

A:

Verify configured tunnel source and destination and their active underlay routing is a relevant step for the separate scenario in which a GRE tunnel interface exists but its operational state is unreliable because the source interface was changed. It does not directly fix this case. Instead distinguish tunneling encapsulation from confidentiality protection; verify: The security design adds an appropriate protected transport where needed.

B:

The alternative addresses a provider's LDP neighbors disappear after an IGP outage while physical links remain up, not the present root cause. Here the selected correction must reflect gRE by itself does not provide encryption or authenticated confidentiality. Test for: The security design adds an appropriate protected transport where needed.

D:

This option overlooks the decisive condition. Its supporting principle is encapsulation does not replace explicit customer route filtering and access policy, while this scenario depends on gRE by itself does not provide encryption or authenticated confidentiality. Verify the correction with: The security design adds an appropriate protected transport where needed.

Question 231

A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. Which evidence would justify closing this troubleshooting case?

  1. Acceptance check: The neighbor table shows the intended level and stable adjacency.
  2. The test confirms that each direction's active route matches the documented costs and design.
  3. Expected observation: An unwanted looped route is rejected in a lab before production change.
  4. Verification result: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

Explanation

Correct Answer

D:

Underlying cause: IS-IS routing levels determine topology knowledge and area reachability. Corrective action: review Level 1 and Level 2 routing roles and their intended boundaries. Verify the outcome: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

Incorrect Answers

A:

The proposed principle concerns another network fault: Compatible IS-IS levels and area information determine available adjacency types. Here, iS-IS routing levels determine topology knowledge and area reachability. The most direct correction is to review Level 1 and Level 2 routing roles and their intended boundaries, confirmed by an eligible Level 2 or L1/L2 path provides the approved interarea destination.

B:

That result would be useful for a different failure, namely: An IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted. The current case specifically calls for: Review Level 1 and Level 2 routing roles and their intended boundaries. The required observed result is: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

C:

This response would target a different source scenario: A provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. It cannot establish the current acceptance requirement, which is: An eligible Level 2 or L1/L2 path provides the approved interarea destination. The relevant action is: Review Level 1 and Level 2 routing roles and their intended boundaries.

Question 232

An equal-cost path test sends nearly all flows across one member while both links remain operational. Which underlying Junos networking principle explains the failure?

  1. The governing rule is: Instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues.
  2. The key distinction is: Load sharing should be evaluated with relevant flows rather than one ping stream.
  3. Protocol behavior: BGP MED influence is conditional on the receiving network's path selection rules.
  4. Underlying principle: Routing instances isolate routing tables unless explicit import or export mechanisms connect them.

Explanation

Correct Answer

B:

Correct diagnosis: Load sharing should be evaluated with relevant flows rather than one ping stream. The appropriate action is: Validate forwarding load-sharing configuration and run representative multi-flow traffic. The follow-up evidence required is: A documented multi-flow test matches the configured distribution policy.

Incorrect Answers

A:

This answer would be more suitable when a provider PE can ping a customer in the master instance but probes in the tenant routing instance fail, where the corrective action is to run route and connectivity checks in the explicitly intended routing instance. The failure here is different: Load sharing should be evaluated with relevant flows rather than one ping stream. Required validation: A documented multi-flow test matches the configured distribution policy.

C:

BGP MED influence is conditional on the receiving network's path selection rules describes a neighboring protocol concern. In this case the controlling fact is load sharing should be evaluated with relevant flows rather than one ping stream. A correct remediation would validate forwarding load-sharing configuration and run representative multi-flow traffic and demonstrate: A documented multi-flow test matches the configured distribution policy.

D:

The proposed principle concerns another network fault: Routing instances isolate routing tables unless explicit import or export mechanisms connect them. Here, load sharing should be evaluated with relevant flows rather than one ping stream. The most direct correction is to validate forwarding load-sharing configuration and run representative multi-flow traffic, confirmed by a documented multi-flow test matches the configured distribution policy.

Question 233

A service provider adds a second VLAN tag to customer frames but the downstream switch treats it as an ordinary single tag. What operational check demonstrates that the intended outcome occurred?

  1. Verification result: The corrected topology converges without opening an Ethernet loop.
  2. Closeout evidence: The active configuration and forwarding table reflect the approved VLAN change.
  3. Acceptance check: An end-host packet enters the correct VLAN without requiring endpoint tagging.
  4. The test confirms that a packet capture shows the intended outer and inner VLAN tags end to end.

Explanation

Correct Answer

D:

The case turns on the distinction that stacked VLAN services require compatible tagging interpretation at both ends. Apply this concrete engineering step: Validate outer tag encapsulation and EtherType expectations across the handoff. An acceptable verification outcome is: A packet capture shows the intended outer and inner VLAN tags end to end.

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: A packet capture shows the intended outer and inner VLAN tags end to end. The relevant action is: Validate outer tag encapsulation and EtherType expectations across the handoff.

B:

Compare candidate and committed configurations and confirm actual bridge membership is a relevant step for the separate scenario in which a virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed. It does not directly fix this case. Instead validate outer tag encapsulation and EtherType expectations across the handoff; verify: A packet capture shows the intended outer and inner VLAN tags end to end.

C:

The alternative addresses an access port sends untagged user traffic but the engineer expects a VLAN tag from the endpoint on every frame, not the present root cause. Here the selected correction must reflect stacked VLAN services require compatible tagging interpretation at both ends. Test for: A packet capture shows the intended outer and inner VLAN tags end to end.

Question 234

A port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain. Which corrective action and confirmation pair is most appropriate?

  1. Action: Apply supported root protection at the appropriate customer-facing boundary. Evidence: A superior BPDU test preserves the intended root with a logged protective state.
  2. Repair: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design. Check: An ingress-to-egress capture confirms the intended stacked tagging.
  3. Change: Trace frame classification and virtual-switch bridge-domain association. Test: A tagged test frame reaches the approved remote port in the same domain.
  4. Implement: Verify VLAN or bridge-domain membership and its L3 IRB binding. Verify: The bridge domain and IRB interface share the configured gateway context.

Explanation

Correct Answer

C:

Correct diagnosis: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. The appropriate action is: Trace frame classification and virtual-switch bridge-domain association. The follow-up evidence required is: A tagged test frame reaches the approved remote port in the same domain.

Incorrect Answers

A:

Customer control traffic must not displace the authorized provider root describes a neighboring protocol concern. In this case the controlling fact is ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. A correct remediation would trace frame classification and virtual-switch bridge-domain association and demonstrate: A tagged test frame reaches the approved remote port in the same domain.

B:

The proposed principle concerns another network fault: Provider bridging can carry customer VLAN tags inside a provider service tag. Here, ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. The most direct correction is to trace frame classification and virtual-switch bridge-domain association, confirmed by a tagged test frame reaches the approved remote port in the same domain.

D:

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 tagged test frame reaches the approved remote port in the same domain. The relevant action is: Trace frame classification and virtual-switch bridge-domain association.

Question 235

An operator calls an IS-IS TLV a transport packet and ignores its role in link-state information. Which cause-and-remedy pairing reflects the observed problem?

  1. Root issue: An adjacency can be operational while a specific family or prefix is not advertised. Correction: Distinguish IS-IS adjacency from address-family reachability advertisements.
  2. Cause: Common topology information can still produce direction-dependent shortest paths. Response: Compare path metrics and each router's route selection before altering LSP state.
  3. Diagnosis: IS-IS advertises extensible routing attributes using TLV-encoded fields. Action: Identify TLVs as structured information within IS-IS protocol data units.
  4. Explanation: Unresolvable BGP next hops can make received routes unusable. Repair: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior.

Explanation

Correct Answer

C:

The selected response implements the principle that iS-IS advertises extensible routing attributes using TLV-encoded fields. The engineer should identify TLVs as structured information within IS-IS protocol data units. Successful confirmation means: A protocol decode identifies the expected advertised TLV information.

Incorrect Answers

A:

The alternative addresses a core engineer sees that IPv6 reachability is absent despite IS-IS adjacency and concludes the adjacency itself is broken, not the present root cause. Here the selected correction must reflect iS-IS advertises extensible routing attributes using TLV-encoded fields. Test for: A protocol decode identifies the expected advertised TLV information.

B:

This answer would be more suitable when an IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted, where the corrective action is to compare path metrics and each router's route selection before altering LSP state. The failure here is different: IS-IS advertises extensible routing attributes using TLV-encoded fields. Required validation: A protocol decode identifies the expected advertised TLV information.

D:

Unresolvable BGP next hops can make received routes unusable describes a neighboring protocol concern. In this case the controlling fact is iS-IS advertises extensible routing attributes using TLV-encoded fields. A correct remediation would identify TLVs as structured information within IS-IS protocol data units and demonstrate: A protocol decode identifies the expected advertised TLV information.

Question 236

A provider's LDP neighbors disappear after an IGP outage while physical links remain up. What is the primary routing or switching concept illustrated?

  1. The key distinction is: Labels have locally significant forwarding meaning on each LSP segment.
  2. Protocol behavior: iBGP can preserve externally learned next-hop information that internal speakers must resolve.
  3. Underlying principle: LDP signaling depends on the routing and transport state of its endpoints.
  4. Root design issue: A stale label binding cannot compensate for unusable transport forwarding.

Explanation

Correct Answer

C:

This is the model-intended best choice because lDP signaling depends on the routing and transport state of its endpoints. The targeted correction is to check transport reachability, LDP session state and the relevant IGP routes. Validate it by observing that lDP sessions recover and labeled FEC bindings reappear after underlay repair.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An ingress router imposes an MPLS label while an engineer expects the same label value to persist unchanged at every hop. The current case specifically calls for: Check transport reachability, LDP session state and the relevant IGP routes. The required observed result is: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

B:

This response would target a different source scenario: A provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. It cannot establish the current acceptance requirement, which is: LDP sessions recover and labeled FEC bindings reappear after underlay repair. The relevant action is: Check transport reachability, LDP session state and the relevant IGP routes.

D:

The alternative addresses an LDP binding exists for a remote destination but the forwarding interface points to a failed next hop, not the present root cause. Here the selected correction must reflect lDP signaling depends on the routing and transport state of its endpoints. Test for: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

Question 237

Two network services use identical customer VLAN IDs and the team assumes their frames must share one L2 broadcast domain. Which technical explanation and controlled action address the symptom?

  1. Explanation: A customer VLAN tag can be scoped by access interface and provider service context. Repair: Separate provider service identification from customer VLAN identifiers.
  2. Fault mechanism: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. Remediation: Trace frame classification and virtual-switch bridge-domain association.
  3. Root issue: Stacked VLAN services require compatible tagging interpretation at both ends. Correction: Validate outer tag encapsulation and EtherType expectations across the handoff.
  4. Cause: STP instability can be secondary to physical link churn. Response: Inspect interface faults and control-plane events before changing STP timers.

Explanation

Correct Answer

A:

The critical observation is: A customer VLAN tag can be scoped by access interface and provider service context. Correct it by taking this action: Separate provider service identification from customer VLAN identifiers. Confirm the outcome with: The overlapping customer IDs remain isolated within their designated provider services.

Incorrect Answers

B:

Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching describes a neighboring protocol concern. In this case the controlling fact is a customer VLAN tag can be scoped by access interface and provider service context. A correct remediation would separate provider service identification from customer VLAN identifiers and demonstrate: The overlapping customer IDs remain isolated within their designated provider services.

C:

The proposed principle concerns another network fault: Stacked VLAN services require compatible tagging interpretation at both ends. Here, a customer VLAN tag can be scoped by access interface and provider service context. The most direct correction is to separate provider service identification from customer VLAN identifiers, confirmed by the overlapping customer IDs remain isolated within their designated provider services.

D:

That result would be useful for a different failure, namely: An RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement. The current case specifically calls for: Separate provider service identification from customer VLAN identifiers. The required observed result is: The overlapping customer IDs remain isolated within their designated provider services.

Question 238

A failover plan relies on one physical interface carrying several links and calls it a redundant LAG. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: A redundant alternate path can remain nonforwarding until a failure changes roles.
  2. The governing rule is: Link aggregation improves availability only when member links and topology provide meaningful redundancy.
  3. The key distinction is: NSR and graceful restart on the local restarting device are different approaches and can conflict.
  4. Protocol behavior: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Link aggregation improves availability only when member links and topology provide meaningful redundancy. Remedy: Distinguish member-link redundancy from a single physical failure domain. Proof: A member link failure leaves traffic flowing through a remaining usable member.

Incorrect Answers

A:

Explain root and alternate roles in a loop-free spanning-tree topology is a relevant step for the separate scenario in which a switch has a root port and alternate port, but the operator assumes both must forward to use all physical bandwidth. It does not directly fix this case. Instead distinguish member-link redundancy from a single physical failure domain; verify: A member link failure leaves traffic flowing through a remaining usable member.

C:

This answer would be more suitable when a provider tries to enable nonstop active routing and graceful-restart mode simultaneously on the same Junos device, where the corrective action is to review supported mutual exclusivity and select the intended HA control-plane method. The failure here is different: Link aggregation improves availability only when member links and topology provide meaningful redundancy. Required validation: A member link failure leaves traffic flowing through a remaining usable member.

D:

This option overlooks the decisive condition. Its supporting principle is layer 3 routing HA does not automatically guarantee L2 bridge-control continuity, while this scenario depends on link aggregation improves availability only when member links and topology provide meaningful redundancy. Verify the correction with: A member link failure leaves traffic flowing through a remaining usable member.

Question 239

A router-on-a-stick replacement with IRB stops reachability between a bridge domain and an L3 subnet. What remediation is most directly applicable?

  1. Corrective action: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design.
  2. Apply this control: Distinguish member-link redundancy from a single physical failure domain.
  3. Remediation: Verify VLAN-to-IRB interface binding, addresses and active route entries.
  4. Recommended change: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning.

Explanation

Correct Answer

C:

The case turns on the distinction that iRB depends on both L2 membership and a valid L3 gateway configuration. Apply this concrete engineering step: Verify VLAN-to-IRB interface binding, addresses and active route entries. An acceptable verification outcome is: A test host ARPs or discovers its gateway and routes to the intended subnet.

Incorrect Answers

A:

The proposed principle concerns another network fault: Provider bridging can carry customer VLAN tags inside a provider service tag. Here, iRB depends on both L2 membership and a valid L3 gateway configuration. The most direct correction is to verify VLAN-to-IRB interface binding, addresses and active route entries, confirmed by a test host ARPs or discovers its gateway and routes to the intended subnet.

B:

That result would be useful for a different failure, namely: A failover plan relies on one physical interface carrying several links and calls it a redundant LAG. The current case specifically calls for: Verify VLAN-to-IRB interface binding, addresses and active route entries. The required observed result is: A test host ARPs or discovers its gateway and routes to the intended subnet.

D:

Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning is a relevant step for the separate scenario in which after a trunk change a MAC address is visible but only one of two VLANs can traverse the uplink. It does not directly fix this case. Instead verify VLAN-to-IRB interface binding, addresses and active route entries; verify: A test host ARPs or discovers its gateway and routes to the intended subnet.

Question 240

Two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent. Which statement identifies the key design assumption that failed?

  1. Protocol behavior: OSPF adjacency requires compatible area and interface parameters.
  2. Underlying principle: Summary advertisements require validation against their underlying active route policy.
  3. Root design issue: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches.
  4. The governing rule is: OSPF identifies speakers by router ID, which must be unique inside a routing domain.

Explanation

Correct Answer

D:

Because oSPF identifies speakers by router ID, which must be unique inside a routing domain, the best response is to assign distinct stable router IDs and clear stale protocol state using an approved procedure. A reviewer can close the technical case only after confirming that each router is uniquely identified and the link-state database converges.

Incorrect Answers

A:

This answer would be more suitable when two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship, where the corrective action is to align the area membership and verify OSPF interface settings on both sides. The failure here is different: OSPF identifies speakers by router ID, which must be unique inside a routing domain. Required validation: Each router is uniquely identified and the link-state database converges.

B:

This option overlooks the decisive condition. Its supporting principle is summary advertisements require validation against their underlying active route policy, while this scenario depends on oSPF identifies speakers by router ID, which must be unique inside a routing domain. Verify the correction with: Each router is uniquely identified and the link-state database converges.

C:

Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches describes a neighboring protocol concern. In this case the controlling fact is oSPF identifies speakers by router ID, which must be unique inside a routing domain. A correct remediation would assign distinct stable router IDs and clear stale protocol state using an approved procedure and demonstrate: Each router is uniquely identified and the link-state database converges.

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