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 17

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.

Question 161

An input firewall filter diverts all transit traffic to a management routing instance by mistake. Which test result would best confirm a successful fix?

  1. Expected observation: A neighbor advertising test shows precisely the allowed tagged prefixes.
  2. Verification result: Only approved traffic uses the alternate table while ordinary transit remains on its path.
  3. Closeout evidence: The allowed service routes import and the forbidden more-specific prefixes do not.
  4. Acceptance check: The imported route resolves and forwarding behavior matches the intended instance.

Explanation

Correct Answer

B:

The selected response implements the principle that filter-based routing policy requires explicit match conditions and a safe default behavior. The engineer should narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes. Successful confirmation means: Only approved traffic uses the alternate table while ordinary transit remains on its path.

Incorrect Answers

A:

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: Only approved traffic uses the alternate table while ordinary transit remains on its path. The relevant action is: Narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes.

C:

The alternative addresses a route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant, not the present root cause. Here the selected correction must reflect filter-based routing policy requires explicit match conditions and a safe default behavior. Test for: Only approved traffic uses the alternate table while ordinary transit remains on its path.

D:

This answer would be more suitable when a route leaked to a second routing table unexpectedly carries a next hop that cannot be resolved there, where the corrective action is to evaluate routing-table relationships and next-hop resolution when using RIB groups. The failure here is different: Filter-based routing policy requires explicit match conditions and a safe default behavior. Required validation: Only approved traffic uses the alternate table while ordinary transit remains on its path.

Question 162

A service provider tags prefixes for selective export but applies the community-match policy to the wrong neighbor group. Which underlying Junos networking principle explains the failure?

  1. Protocol behavior: BGP MED influence is conditional on the receiving network's path selection rules.
  2. Underlying principle: OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone.
  3. Root design issue: BGP group inheritance and policy direction govern which advertisements are modified.
  4. The governing rule is: Route reflection can fail due to session or policy scope even when the route exists centrally.

Explanation

Correct Answer

C:

Correct diagnosis: BGP group inheritance and policy direction govern which advertisements are modified. The appropriate action is: Map inbound and outbound policy points and confirm the intended communities. The follow-up evidence required is: A neighbor advertising test shows precisely the allowed tagged prefixes.

Incorrect Answers

A:

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 bGP group inheritance and policy direction govern which advertisements are modified. A correct remediation would map inbound and outbound policy points and confirm the intended communities and demonstrate: A neighbor advertising test shows precisely the allowed tagged prefixes.

B:

The proposed principle concerns another network fault: OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone. Here, bGP group inheritance and policy direction govern which advertisements are modified. The most direct correction is to map inbound and outbound policy points and confirm the intended communities, confirmed by a neighbor advertising test shows precisely the allowed tagged prefixes.

D:

This response would target a different source scenario: A route reflector receives a new branch prefix but one iBGP client never learns it. It cannot establish the current acceptance requirement, which is: A neighbor advertising test shows precisely the allowed tagged prefixes. The relevant action is: Map inbound and outbound policy points and confirm the intended communities.

Question 163

A backup path becomes primary after a preference edit even though the design called for failover only. What should the operations engineer do first to address the stated fault?

  1. Recommended change: Differentiate community tags from reachability and forwarding attributes.
  2. Next step: Verify recursive next-hop reachability before relying on the static route.
  3. Corrective action: Restore the intended route preferences and check selected forwarding next hops.
  4. Apply this control: Compare installed forwarding entries with interface operational status and adjacency resolution.

Explanation

Correct Answer

C:

The selected response implements the principle that preference edits can change route selection without any interface outage. The engineer should restore the intended route preferences and check selected forwarding next hops. Successful confirmation means: A primary-link test chooses the expected primary then fails to backup on loss.

Incorrect Answers

A:

The alternative addresses an engineer treats a BGP community value as a standalone forwarding next hop, not the present root cause. Here the selected correction must reflect preference edits can change route selection without any interface outage. Test for: A primary-link test chooses the expected primary then fails to backup on loss.

B:

This answer would be more suitable when a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route, where the corrective action is to verify recursive next-hop reachability before relying on the static route. The failure here is different: Preference edits can change route selection without any interface outage. Required validation: A primary-link test chooses the expected primary then fails to backup on loss.

D:

Forwarding-table and interface evidence localize faults beyond RIB reachability describes a neighboring protocol concern. In this case the controlling fact is preference edits can change route selection without any interface outage. A correct remediation would restore the intended route preferences and check selected forwarding next hops and demonstrate: A primary-link test chooses the expected primary then fails to backup on loss.

Question 164

A new redundant uplink produces a broadcast storm on an access VLAN. What is the primary routing or switching concept illustrated?

  1. The governing rule is: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments.
  2. The key distinction is: Per-VLAN spanning-tree behavior can differ across VLANs.
  3. Protocol behavior: Spanning-tree security mechanisms protect distinct topology and control-plane risks.
  4. Underlying principle: Loop prevention depends on compatible STP participation across redundant Ethernet links.

Explanation

Correct Answer

D:

Correct diagnosis: Loop prevention depends on compatible STP participation across redundant Ethernet links. The appropriate action is: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain. The follow-up evidence required is: The ring converges with no forwarding loop and sustained connectivity.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. The current case specifically calls for: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain. The required observed result is: The ring converges with no forwarding loop and sustained connectivity.

B:

This response would target a different source scenario: Several VLANs have unexpected root placement under VSTP after port membership changes. It cannot establish the current acceptance requirement, which is: The ring converges with no forwarding loop and sustained connectivity. The relevant action is: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain.

C:

Match loop, BPDU and root protection to their different fault conditions is a relevant step for the separate scenario in which an engineer uses loop protection as if it served the same purpose as BPDU protection on every port. It does not directly fix this case. Instead inspect STP state and enable the approved spanning-tree protocol for that bridge domain; verify: The ring converges with no forwarding loop and sustained connectivity.

Question 165

A broadcast OSPF segment experiences repeated DR elections after interface priority changes. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: Multi-area OSPF design requires attention to backbone connectivity.
  2. The governing rule is: A learned LSP does not ensure a destination is selected into the active routing table.
  3. The key distinction is: OSPF DR selection depends on eligible routers and the current election event.
  4. Protocol behavior: Protocol timers need reliable packet delivery and should not mask an unstable link.

Explanation

Correct Answer

C:

Underlying cause: OSPF DR selection depends on eligible routers and the current election event. Corrective action: review router priorities and the nonpreemptive properties of DR elections. Verify the outcome: The elected DR and BDR align with the tested election conditions.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is multi-area OSPF design requires attention to backbone connectivity, while this scenario depends on oSPF DR selection depends on eligible routers and the current election event. Verify the correction with: The elected DR and BDR align with the tested election conditions.

B:

A learned LSP does not ensure a destination is selected into the active routing table describes a neighboring protocol concern. In this case the controlling fact is oSPF DR selection depends on eligible routers and the current election event. A correct remediation would review router priorities and the nonpreemptive properties of DR elections and demonstrate: The elected DR and BDR align with the tested election conditions.

D:

That result would be useful for a different failure, namely: Several routers report intermittent OSPF neighbor resets on a saturated transit circuit. The current case specifically calls for: Review router priorities and the nonpreemptive properties of DR elections. The required observed result is: The elected DR and BDR align with the tested election conditions.

Question 166

An operator calls an IS-IS TLV a transport packet and ignores its role in link-state information. What operational check demonstrates that the intended outcome occurred?

  1. Expected observation: The allowed prefixes are present and denied test prefixes are absent.
  2. Verification result: The chosen path matches the configured preference and applicable attributes.
  3. Closeout evidence: A protocol decode identifies the expected advertised TLV information.
  4. Acceptance check: The forwarding route follows the lowest intended metric path.

Explanation

Correct Answer

C:

Because iS-IS advertises extensible routing attributes using TLV-encoded fields, the best response is to identify TLVs as structured information within IS-IS protocol data units. A reviewer can close the technical case only after confirming that a protocol decode identifies the expected advertised TLV information.

Incorrect Answers

A:

Apply and verify supported route policy at the intended routing import or export boundary is a relevant step for the separate scenario in which an engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context. It does not directly fix this case. Instead identify TLVs as structured information within IS-IS protocol data units; verify: A protocol decode identifies the expected advertised TLV information.

B:

The alternative addresses a router learns the same prefix from peers in distinct autonomous systems but the engineer compares only BGP hop count, 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.

D:

This option overlooks the decisive condition. Its supporting principle is iS-IS path selection is based on link-state topology and metrics, while this scenario depends on iS-IS advertises extensible routing attributes using TLV-encoded fields. Verify the correction with: A protocol decode identifies the expected advertised TLV information.

Question 167

An engineer chooses an IPv6 route based on the printed address alone without comparing prefix length. Which combined repair and acceptance criterion is strongest?

  1. Control: Apply and verify supported route policy at the intended routing import or export boundary. Accepted result: The allowed prefixes are present and denied test prefixes are absent.
  2. Action: Apply longest-prefix-match route lookup to the IPv6 destination. Evidence: A destination lookup chooses the intended most specific valid route.
  3. Repair: Review the IPv6 OSPFv3 address-family and interface adjacency model. Check: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.
  4. Change: Validate IPv6 addressing, neighbor discovery and inet6 routing separately. Test: The intended IPv6 neighbor and destination routes appear and traffic succeeds.

Explanation

Correct Answer

B:

The critical observation is: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Correct it by taking this action: Apply longest-prefix-match route lookup to the IPv6 destination. Confirm the outcome with: A destination lookup chooses the intended most specific valid route.

Incorrect Answers

A:

The proposed principle concerns another network fault: Policy placement determines which prefixes influence a routing table or advertisement. Here, iPv6 route selection follows prefix matching and route eligibility, not textual address order. The most direct correction is to apply longest-prefix-match route lookup to the IPv6 destination, confirmed by a destination lookup chooses the intended most specific valid route.

C:

This response would target a different source scenario: An operator assumes OSPFv3 must form using the same interface and address settings as OSPFv2. It cannot establish the current acceptance requirement, which is: A destination lookup chooses the intended most specific valid route. The relevant action is: Apply longest-prefix-match route lookup to the IPv6 destination.

D:

Validate IPv6 addressing, neighbor discovery and inet6 routing separately is a relevant step for the separate scenario in which a new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. It does not directly fix this case. Instead apply longest-prefix-match route lookup to the IPv6 destination; verify: A destination lookup chooses the intended most specific valid route.

Question 168

An Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation. Which evidence would justify closing this troubleshooting case?

  1. Acceptance check: The bridge domain and IRB interface share the configured gateway context.
  2. The test confirms that both test logical units classify tagged traffic into their intended bridge domains.
  3. Expected observation: A cross-customer unknown-unicast probe remains isolated from the other tenant.
  4. Verification result: Each tested VLAN elects its approved root and loop-free port roles.

Explanation

Correct Answer

B:

Correct diagnosis: Logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. The appropriate action is: Document VLAN-aware versus flexible tagging and unit classification requirements. The follow-up evidence required is: Both test logical units classify tagged traffic into their intended bridge domains.

Incorrect Answers

A:

This answer would be more suitable when an IRB interface is present but an operator assumes it creates a bridge domain automatically, where the corrective action is to verify VLAN or bridge-domain membership and its L3 IRB binding. The failure here is different: Logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. Required validation: Both test logical units classify tagged traffic into their intended bridge domains.

C:

Layer 2 isolation depends on bridge-domain and logical switch boundaries describes a neighboring protocol concern. In this case the controlling fact is logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. A correct remediation would document VLAN-aware versus flexible tagging and unit classification requirements and demonstrate: Both test logical units classify tagged traffic into their intended bridge domains.

D:

The proposed principle concerns another network fault: Per-VLAN spanning-tree behavior can differ across VLANs. Here, logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. The most direct correction is to document VLAN-aware versus flexible tagging and unit classification requirements, confirmed by both test logical units classify tagged traffic into their intended bridge domains.

Question 169

A remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation. What action-and-test pairing directly resolves the case?

  1. Change: Review segment identifiers and forwarding under SR-MPLS. Test: A test packet follows its segment list through installed SR forwarding.
  2. Implement: Differentiate community tags from reachability and forwarding attributes. Verify: Policy based on the intended community alters admission or preference as designed.
  3. Control: Confirm the configured local and peer AS values with the authoritative design. Accepted result: The session reaches Established only with the documented correct peer AS.
  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

C:

The critical observation is: BGP OPEN negotiation includes AS identity that must match peering intent. Correct it by taking this action: Confirm the configured local and peer AS values with the authoritative design. Confirm the outcome with: The session reaches Established only with the documented correct peer AS.

Incorrect Answers

A:

This response would target a different source scenario: A provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state. It cannot establish the current acceptance requirement, which is: The session reaches Established only with the documented correct peer AS. The relevant action is: Confirm the configured local and peer AS values with the authoritative design.

B:

Differentiate community tags from reachability and forwarding attributes is a relevant step for the separate scenario in which an engineer treats a BGP community value as a standalone forwarding next hop. It does not directly fix this case. Instead confirm the configured local and peer AS values with the authoritative design; verify: The session reaches Established only with the documented correct peer AS.

D:

This answer would be more suitable when an operator changes MED and sees no route change because the target AS prioritizes other attributes, where the corrective action is to compare MED use with actual prior BGP decision attributes and neighbor policy. The failure here is different: BGP OPEN negotiation includes AS identity that must match peering intent. Required validation: The session reaches Established only with the documented correct peer AS.

Question 170

A technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. Which root-cause explanation and corrective action fit the case?

  1. Diagnosis: IPv4 BGP session liveness does not prove IPv6 family route exchange. Action: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.
  2. Explanation: IS-IS advertises extensible routing attributes using TLV-encoded fields. Repair: Identify TLVs as structured information within IS-IS protocol data units.
  3. Fault mechanism: Structured protocol-layer evidence separates link health from routing convergence issues. Remediation: Collect protocol adjacency, LSP and routing-table outputs for the affected route.
  4. Root issue: IS-IS packet exchange and transport differ from OSPF over IP. Correction: Recognize IS-IS as a link-layer routing protocol with its own PDUs.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: IS-IS packet exchange and transport differ from OSPF over IP. Remedy: Recognize IS-IS as a link-layer routing protocol with its own PDUs. Proof: A link-level packet trace observes the relevant IS-IS PDUs.

Incorrect Answers

A:

IPv4 BGP session liveness does not prove IPv6 family route exchange describes a neighboring protocol concern. In this case the controlling fact is iS-IS packet exchange and transport differ from OSPF over IP. A correct remediation would recognize IS-IS as a link-layer routing protocol with its own PDUs and demonstrate: A link-level packet trace observes the relevant IS-IS PDUs.

B:

The proposed principle concerns another network fault: IS-IS advertises extensible routing attributes using TLV-encoded fields. Here, iS-IS packet exchange and transport differ from OSPF over IP. The most direct correction is to recognize IS-IS as a link-layer routing protocol with its own PDUs, confirmed by a link-level packet trace observes the relevant IS-IS PDUs.

C:

That result would be useful for a different failure, namely: An IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. The current case specifically calls for: Recognize IS-IS as a link-layer routing protocol with its own PDUs. The required observed result is: A link-level packet trace observes the relevant IS-IS PDUs.

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