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 16

Question 150

An access port sends untagged user traffic but the engineer expects a VLAN tag from the endpoint on every frame. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Review allowed VLAN membership on both trunk endpoints. Check: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.
  2. Change: Distinguish access port traffic from trunk tagging behavior. Test: An end-host packet enters the correct VLAN without requiring endpoint tagging.
  3. Implement: Evaluate BFD liveness detection with the associated routing protocol. Verify: A controlled forwarding failure is detected within the approved target.
  4. Control: Document VLAN-aware versus flexible tagging and unit classification requirements. Accepted result: Both test logical units classify tagged traffic into their intended bridge domains.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Port mode determines which customer frames are tagged or untagged at the boundary. Remedy: Distinguish access port traffic from trunk tagging behavior. Proof: An end-host packet enters the correct VLAN without requiring endpoint tagging.

Incorrect Answers

A:

Review allowed VLAN membership on both trunk endpoints is a relevant step for the separate scenario in which a trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch. It does not directly fix this case. Instead distinguish access port traffic from trunk tagging behavior; verify: An end-host packet enters the correct VLAN without requiring endpoint tagging.

C:

This answer would be more suitable when a routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up, where the corrective action is to evaluate BFD liveness detection with the associated routing protocol. The failure here is different: Port mode determines which customer frames are tagged or untagged at the boundary. Required validation: An end-host packet enters the correct VLAN without requiring endpoint tagging.

D:

This option overlooks the decisive condition. Its supporting principle is logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model, while this scenario depends on port mode determines which customer frames are tagged or untagged at the boundary. Verify the correction with: An end-host packet enters the correct VLAN without requiring endpoint tagging.

Question 151

An IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. Which protocol behavior most directly determines the correct diagnosis?

  1. Underlying principle: Frequent topology churn can stem from physical and configuration issues rather than DIS alone.
  2. Root design issue: Structured protocol-layer evidence separates link health from routing convergence issues.
  3. The governing rule is: An adjacency can be operational while a specific family or prefix is not advertised.
  4. The key distinction is: Interarea reachability depends on the ABR's view and allowed advertisements.

Explanation

Correct Answer

B:

The critical observation is: Structured protocol-layer evidence separates link health from routing convergence issues. Correct it by taking this action: Collect protocol adjacency, LSP and routing-table outputs for the affected route. Confirm the outcome with: The report explains the fault from interface through neighbor to selected route.

Incorrect Answers

A:

The proposed principle concerns another network fault: Frequent topology churn can stem from physical and configuration issues rather than DIS alone. Here, structured protocol-layer evidence separates link health from routing convergence issues. The most direct correction is to collect protocol adjacency, LSP and routing-table outputs for the affected route, confirmed by the report explains the fault from interface through neighbor to selected route.

C:

This response would target a different source scenario: A core engineer sees that IPv6 reachability is absent despite IS-IS adjacency and concludes the adjacency itself is broken. It cannot establish the current acceptance requirement, which is: The report explains the fault from interface through neighbor to selected route. The relevant action is: Collect protocol adjacency, LSP and routing-table outputs for the affected route.

D:

Inspect ABR area configuration, route export rules and summary policy is a relevant step for the separate scenario in which an area border router stops advertising an expected summarized interarea route after a policy change. It does not directly fix this case. Instead collect protocol adjacency, LSP and routing-table outputs for the affected route; verify: The report explains the fault from interface through neighbor to selected route.

Question 152

A switch has a root port and alternate port, but the operator assumes both must forward to use all physical bandwidth. Which corrective action and confirmation pair is most appropriate?

  1. Control: Explain root and alternate roles in a loop-free spanning-tree topology. Accepted result: The alternate port transitions appropriately after the root path fails.
  2. Action: Align region identity, revision and VLAN mapping as required. Evidence: A region status check shows the intended shared instance mapping.
  3. Repair: Verify VLAN or bridge-domain membership and its L3 IRB binding. Check: The bridge domain and IRB interface share the configured gateway context.
  4. Change: Match loop, BPDU and root protection to their different fault conditions. Test: Separate fault injections trigger the intended protection per port role.

Explanation

Correct Answer

A:

This is the model-intended best choice because a redundant alternate path can remain nonforwarding until a failure changes roles. The targeted correction is to explain root and alternate roles in a loop-free spanning-tree topology. Validate it by observing that the alternate port transitions appropriately after the root path fails.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is mSTP region agreement affects how instances interoperate across links, while this scenario depends on a redundant alternate path can remain nonforwarding until a failure changes roles. Verify the correction with: The alternate port transitions appropriately after the root path fails.

C:

Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated describes a neighboring protocol concern. In this case the controlling fact is a redundant alternate path can remain nonforwarding until a failure changes roles. A correct remediation would explain root and alternate roles in a loop-free spanning-tree topology and demonstrate: The alternate port transitions appropriately after the root path fails.

D:

The proposed principle concerns another network fault: Spanning-tree security mechanisms protect distinct topology and control-plane risks. Here, a redundant alternate path can remain nonforwarding until a failure changes roles. The most direct correction is to explain root and alternate roles in a loop-free spanning-tree topology, confirmed by the alternate port transitions appropriately after the root path fails.

Question 153

Several VLANs have unexpected root placement under VSTP after port membership changes. Which post-change observation most strongly confirms the correction?

  1. Acceptance check: Each tested VLAN elects its approved root and loop-free port roles.
  2. The test confirms that the ring converges with no forwarding loop and sustained connectivity.
  3. Expected observation: The alternate port transitions appropriately after the root path fails.
  4. Verification result: A member link failure leaves traffic flowing through a remaining usable member.

Explanation

Correct Answer

A:

Underlying cause: Per-VLAN spanning-tree behavior can differ across VLANs. Corrective action: inspect per-VLAN STP instances and configured priorities, not just a global STP summary. Verify the outcome: Each tested VLAN elects its approved root and loop-free port roles.

Incorrect Answers

B:

Inspect STP state and enable the approved spanning-tree protocol for that bridge domain is a relevant step for the separate scenario in which a new redundant uplink produces a broadcast storm on an access VLAN. It does not directly fix this case. Instead inspect per-VLAN STP instances and configured priorities, not just a global STP summary; verify: Each tested VLAN elects its approved root and loop-free port roles.

C:

The alternative addresses a switch has a root port and alternate port, but the operator assumes both must forward to use all physical bandwidth, not the present root cause. Here the selected correction must reflect per-VLAN spanning-tree behavior can differ across VLANs. Test for: Each tested VLAN elects its approved root and loop-free port roles.

D:

This answer would be more suitable when a failover plan relies on one physical interface carrying several links and calls it a redundant LAG, where the corrective action is to distinguish member-link redundancy from a single physical failure domain. The failure here is different: Per-VLAN spanning-tree behavior can differ across VLANs. Required validation: Each tested VLAN elects its approved root and loop-free port roles.

Question 154

A peer announces an IPv6 prefix but the operator checks only the IPv4 BGP route family. Which corrective action and confirmation pair is most appropriate?

  1. Change: Verify negotiated address families and family-specific routing tables. Test: The intended inet6 family receives and selects the IPv6 prefix.
  2. Implement: Create explicit import policy and prefix limits aligned to customer contracts. Verify: Only approved customer prefixes enter the provider's active routing table.
  3. Control: Inspect ABR area configuration, route export rules and summary policy. Accepted result: The correct summarized route appears in the receiving area's route table.
  4. Action: Compare MED use with actual prior BGP decision attributes and neighbor policy. Evidence: A captured received-path comparison explains which attribute selected the route.

Explanation

Correct Answer

A:

Because bGP transport connectivity does not guarantee every address family is negotiated and active, the best response is to verify negotiated address families and family-specific routing tables. A reviewer can close the technical case only after confirming that the intended inet6 family receives and selects the IPv6 prefix.

Incorrect Answers

B:

The proposed principle concerns another network fault: BGP route acceptance must be constrained rather than inferred from neighbor identity. Here, bGP transport connectivity does not guarantee every address family is negotiated and active. The most direct correction is to verify negotiated address families and family-specific routing tables, confirmed by the intended inet6 family receives and selects the IPv6 prefix.

C:

That result would be useful for a different failure, namely: An area border router stops advertising an expected summarized interarea route after a policy change. The current case specifically calls for: Verify negotiated address families and family-specific routing tables. The required observed result is: The intended inet6 family receives and selects the IPv6 prefix.

D:

This response would target a different source scenario: An operator changes MED and sees no route change because the target AS prioritizes other attributes. It cannot establish the current acceptance requirement, which is: The intended inet6 family receives and selects the IPv6 prefix. The relevant action is: Verify negotiated address families and family-specific routing tables.

Question 155

A link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. What diagnosis and engineering response are most appropriate?

  1. Diagnosis: Operational route troubleshooting starts with active state and resolution evidence. Action: Inspect the configuration, active route state and next-hop reachability before changing preference.
  2. Explanation: Multi-area OSPF design requires attention to backbone connectivity. Repair: Review hierarchical OSPF backbone attachment and area border placement.
  3. Fault mechanism: OSPF route type and LSA scope depend on where routing information originates. Remediation: Distinguish internal LSAs from externally originated route information.
  4. Root issue: Failover paths are governed by their actual configured metrics. Correction: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.

Explanation

Correct Answer

C:

The selected response implements the principle that oSPF route type and LSA scope depend on where routing information originates. The engineer should distinguish internal LSAs from externally originated route information. Successful confirmation means: The expected redistributed prefix appears with the right OSPF route type.

Incorrect Answers

A:

The alternative addresses after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors, not the present root cause. Here the selected correction must reflect oSPF route type and LSA scope depend on where routing information originates. Test for: The expected redistributed prefix appears with the right OSPF route type.

B:

This answer would be more suitable when a router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0, where the corrective action is to review hierarchical OSPF backbone attachment and area border placement. The failure here is different: OSPF route type and LSA scope depend on where routing information originates. Required validation: The expected redistributed prefix appears with the right OSPF route type.

D:

Failover paths are governed by their actual configured metrics describes a neighboring protocol concern. In this case the controlling fact is oSPF route type and LSA scope depend on where routing information originates. A correct remediation would distinguish internal LSAs from externally originated route information and demonstrate: The expected redistributed prefix appears with the right OSPF route type.

Question 156

After enabling OSPFv3 a provider sees IPv6 neighbors but no remote IPv6 customer prefixes. Which corrective action and confirmation pair is most appropriate?

  1. Action: Validate IPv6 addressing, neighbor discovery and inet6 routing separately. Evidence: The intended IPv6 neighbor and destination routes appear and traffic succeeds.
  2. Repair: Enable and verify the intended IPv6 address-family reachability advertisements. Check: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.
  3. Change: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance. Test: The accepted OSPFv3 IPv6 routes become active in the expected routing table.
  4. Implement: Restore underlay endpoint reachability and then validate the inner tunnel route. Verify: Both outer endpoint probes and inner traffic succeed after repair.

Explanation

Correct Answer

C:

This is the model-intended best choice because neighbor establishment is distinct from prefix advertisement and installation. The targeted correction is to check OSPFv3 family enablement, LSAs and routing-policy route acceptance. Validate it by observing that the accepted OSPFv3 IPv6 routes become active in the expected routing table.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. The current case specifically calls for: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance. The required observed result is: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

B:

This response would target a different source scenario: An IS-IS backbone forms an adjacency but omits IPv6 reachability when the family is not enabled. It cannot establish the current acceptance requirement, which is: The accepted OSPFv3 IPv6 routes become active in the expected routing table. The relevant action is: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance.

D:

The alternative addresses a GRE tunnel over an IPv4 core stops passing traffic immediately after an underlay route withdraws, not the present root cause. Here the selected correction must reflect neighbor establishment is distinct from prefix advertisement and installation. Test for: The accepted OSPFv3 IPv6 routes become active in the expected routing table.

Question 157

An area border router stops advertising an expected summarized interarea route after a policy change. Which underlying Junos networking principle explains the failure?

  1. Protocol behavior: An adjacency can be operational while a specific family or prefix is not advertised.
  2. Underlying principle: Multi-area OSPF design requires attention to backbone connectivity.
  3. Root design issue: Interarea reachability depends on the ABR's view and allowed advertisements.
  4. The governing rule is: Failover paths are governed by their actual configured metrics.

Explanation

Correct Answer

C:

Underlying cause: Interarea reachability depends on the ABR's view and allowed advertisements. Corrective action: inspect ABR area configuration, route export rules and summary policy. Verify the outcome: 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 an adjacency can be operational while a specific family or prefix is not advertised, 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:

Multi-area OSPF design requires attention to backbone connectivity 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.

D:

That result would be useful for a different failure, namely: An OSPF route appears longer than expected after failover because a backup link's cost was never verified. The current case specifically calls for: Inspect ABR area configuration, route export rules and summary policy. The required observed result is: The correct summarized route appears in the receiving area's route table.

Question 158

A customer overlay fails across an MPLS core only for one service label. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: LDP label bindings are useful only with a functional path to the FEC next hop. Remediation: Review LDP dependence on reachability and routing of the transport endpoints.
  2. Root issue: An LSP cannot follow an unavailable required hop. Correction: Update the engineered path constraints and verify candidate topology availability.
  3. Cause: A healthy transport LSP does not guarantee a correct overlay label mapping. Response: Inspect outer transport and inner service label handling separately.
  4. Diagnosis: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Action: Review filter-based forwarding classification and the intended next-table selection.

Explanation

Correct Answer

C:

Because a healthy transport LSP does not guarantee a correct overlay label mapping, the best response is to inspect outer transport and inner service label handling separately. A reviewer can close the technical case only after confirming that the test service label is retained and accepted at the target PE.

Incorrect Answers

A:

Review LDP dependence on reachability and routing of the transport endpoints is a relevant step for the separate scenario in which an LDP-signaled LSP fails when the IGP route to the remote loopback disappears. It does not directly fix this case. Instead inspect outer transport and inner service label handling separately; verify: The test service label is retained and accepted at the target PE.

B:

The alternative addresses an operator configured an explicit RSVP path through a link that is now administratively down, not the present root cause. Here the selected correction must reflect a healthy transport LSP does not guarantee a correct overlay label mapping. Test for: The test service label is retained and accepted at the target PE.

D:

This option overlooks the decisive condition. Its supporting principle is policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table, while this scenario depends on a healthy transport LSP does not guarantee a correct overlay label mapping. Verify the correction with: The test service label is retained and accepted at the target PE.

Question 159

An engineer treats a BGP community value as a standalone forwarding next hop. What is the most defensible network engineering correction?

  1. Remediation: Differentiate IP underlay reachability from LDP or RSVP control state.
  2. Recommended change: Differentiate community tags from reachability and forwarding attributes.
  3. Next step: Map inbound and outbound policy points and confirm the intended communities.
  4. Corrective action: Restore standard AS-path checks and review any justified exception with design authority.

Explanation

Correct Answer

B:

The critical observation is: Communities are policy signaling metadata and not the packet-forwarding next hop themselves. Correct it by taking this action: Differentiate community tags from reachability and forwarding attributes. Confirm the outcome with: Policy based on the intended community alters admission or preference as designed.

Incorrect Answers

A:

The proposed principle concerns another network fault: MPLS forwarding requires coordinated label signaling and forwarding entries. Here, communities are policy signaling metadata and not the packet-forwarding next hop themselves. The most direct correction is to differentiate community tags from reachability and forwarding attributes, confirmed by policy based on the intended community alters admission or preference as designed.

C:

This response would target a different source scenario: A service provider tags prefixes for selective export but applies the community-match policy to the wrong neighbor group. It cannot establish the current acceptance requirement, which is: Policy based on the intended community alters admission or preference as designed. The relevant action is: Differentiate community tags from reachability and forwarding attributes.

D:

Restore standard AS-path checks and review any justified exception with design authority is a relevant step for the separate scenario in which a provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. It does not directly fix this case. Instead differentiate community tags from reachability and forwarding attributes; verify: Policy based on the intended community alters admission or preference as designed.

Question 160

A VRRP backup router does not take over when the primary gateway interface is disabled. Which technical explanation and controlled action address the symptom?

  1. Diagnosis: Failover depends on compatible virtual router configuration and observable primary loss. Action: Check VRRP group, interface, priority, advertisements and tracking conditions.
  2. Explanation: External OSPF redistribution must be reviewed for scope and scale. Repair: Restore explicit policy matching and confirm external route advertisements.
  3. Fault mechanism: BFD HA behavior depends on platform processing placement and timer tolerances. Remediation: Review session type, supported distributed behavior and switchover-appropriate intervals.
  4. Root issue: Link aggregation improves availability only when member links and topology provide meaningful redundancy. Correction: Distinguish member-link redundancy from a single physical failure domain.

Explanation

Correct Answer

A:

This is the model-intended best choice because failover depends on compatible virtual router configuration and observable primary loss. The targeted correction is to check VRRP group, interface, priority, advertisements and tracking conditions. Validate it by observing that the backup assumes master role and clients retain access to the virtual gateway.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is external OSPF redistribution must be reviewed for scope and scale, while this scenario depends on failover depends on compatible virtual router configuration and observable primary loss. Verify the correction with: The backup assumes master role and clients retain access to the virtual gateway.

C:

BFD HA behavior depends on platform processing placement and timer tolerances describes a neighboring protocol concern. In this case the controlling fact is failover depends on compatible virtual router configuration and observable primary loss. A correct remediation would check VRRP group, interface, priority, advertisements and tracking conditions and demonstrate: The backup assumes master role and clients retain access to the virtual gateway.

D:

The proposed principle concerns another network fault: Link aggregation improves availability only when member links and topology provide meaningful redundancy. Here, failover depends on compatible virtual router configuration and observable primary loss. The most direct correction is to check VRRP group, interface, priority, advertisements and tracking conditions, confirmed by the backup assumes master role and clients retain access to the virtual gateway.

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