The JN0-364 exam validates your expertise in service provider routing and switching technologies as part of the Juniper Service Provider Routing & Switching Certification program. This exam is designed for network professionals who configure, deploy, and troubleshoot routing and switching solutions in service provider environments. This landing page guides you through the exam syllabus, question formats, and effective preparation strategies to help you succeed. Whether you're advancing your career or deepening your Juniper knowledge, understanding the exam structure and content domains is essential for confident test day performance.
Use this topic map to guide your study for Juniper JN0-364 (Service Provider Routing and Switching, Specialist) within the Juniper Service Provider Routing & Switching Certification path.
The JN0-364 exam uses multiple question types to assess both theoretical knowledge and practical decision-making skills in real-world service provider scenarios.
Questions progress in difficulty and emphasize practical application, ensuring candidates can not only explain concepts but also apply them to complex, multi-feature service provider networks.
An effective study routine maps exam topics to weekly milestones and balances conceptual learning with hands-on practice. Allocate time proportionally to BGP, MPLS, and High Availability, as these domains typically carry significant weight. Supplement reading with lab exercises and question reviews to reinforce weak areas and build confidence.
Explore other Juniper certifications: view all Juniper exams.
Strengthen your preparation with up-to-date resources from validexamdumps.com. These materials align to JN0-364 and cover practical scenarios with clear explanations.
Visit the exam page to download the PDF, Online Practice Test, or get a Bundle Discount offer for both formats: Service Provider Routing and Switching, Specialist.
BGP, MPLS, and High Availability typically account for a significant portion of the exam, reflecting their importance in modern service provider networks. Protocol-Independent Routing fundamentals and OSPF also appear frequently. Review the official exam blueprint to confirm current topic weightings and adjust your study plan accordingly.
OSPF and IS-IS handle interior routing within a service provider's autonomous system, while BGP manages interdomain routing with other carriers. In practice, BGP route policies often influence which OSPF or IS-IS paths are preferred, and MPLS tunnels built on top of IGP paths carry BGP-selected traffic. Understanding these interactions is critical for exam success.
Ideally, you should have practical experience configuring and troubleshooting at least three to four of the major topics, particularly BGP and MPLS. If hands-on access is limited, focus on virtual labs, packet tracer simulations, or vendor-provided sandbox environments to practice configuration syntax and observe protocol behavior. This bridges the gap between theory and real-world application.
Common pitfalls include confusing OSPF and IS-IS metric calculations, misunderstanding BGP best path selection criteria, and overlooking High Availability failover timing. Many candidates also underestimate the depth of MPLS and tunnel configuration questions. Careful review of explanations during practice tests helps catch these patterns early.
In the final week, shift focus from new topics to review and pacing. Take a full-length practice test in exam conditions, review all incorrect answers, and drill weak areas for 30 minutes daily. Avoid cramming new material; instead, reinforce your understanding of BGP policies, MPLS tunnel setup, and High Availability mechanisms. Get adequate sleep the night before the exam to ensure mental clarity.
How are routing loops prevented in internal BGP networks?
The prevention of routing loops within an Autonomous System (AS) is handled differently than loop prevention between ASes. While External BGP (EBGP) uses the AS_PATH attribute to detect loops, Internal BGP (IBGP) does not modify the AS_PATH. Therefore, a different mechanism is required to ensure that a route does not circulate infinitely inside the network.
This mechanism is known as the IBGP Split Horizon rule. According to Juniper Networks documentation and the BGP standard (RFC 4271), a BGP speaker must not advertise a route learned via an IBGP peer to any other IBGP peer. In simpler terms, 'what is learned internally, stays local.' This rule ensures that a route only travels one 'hop' inside the AS---from the router that learned it from an external source to all other internal routers.
Because of this rule, IBGP routers do not naturally propagate routes through each other. This creates a requirement for a full mesh of IBGP sessions, where every BGP-speaking router in the AS must have a direct peering session with every other BGP-speaking router. To mitigate the scaling issues of a full mesh in large service provider networks, architects use Route Reflectors or Confederations, which are authorized exceptions to the Split Horizon rule.
Option B is incorrect because EBGP peers do advertise EBGP routes to other EBGP peers (this is how the internet works). Option C is incorrect because EBGP-learned routes must be sent to IBGP peers so the internal network knows how to reach the outside world. Option D is incorrect because internal routes must be sent to external peers to advertise your network to the internet.
You are evaluating BGP between two Juniper routers and the BGP session is stuck in the Idle state. What would cause this behavior?
In the BGP Finite State Machine (FSM), the Idle state is the first stage of any BGP connection. When a BGP session is 'stuck' in Idle, it typically indicates that the router is unable to even begin the process of establishing a TCP connection with its neighbor. According to Juniper Networks documentation, before BGP can transition to the Connect or Active states, it must have a valid route to the neighbor's IP address in the routing table and be able to initiate a three-way TCP handshake on port 179.
If the peer IP address is incorrect (Option D), the router may not have a route to that destination, or it may be attempting to connect to a non-existent or unreachable host. In many Junos configurations, if the underlying IGP (OSPF/IS-IS) or static routing cannot provide reachability to the neighbor address defined in the BGP configuration, the BGP process will remain in the Idle state and periodically retry the connection.
Regarding the other options:
The local AS number is missing (Option C): In Junos, you cannot commit a BGP configuration if the local autonomous system is not defined at either the [edit routing-options] level or within the BGP group itself. The commit check would fail before the session could even attempt to start.
The BGP group type (Option B): Having a mismatch in group type (internal vs. external) usually results in the session reaching the OpenSent or OpenConfirm state before failing due to an 'unacceptable AS' error in the OPEN message.
BGP hold time (Option A): Issues with hold timers or keepalives generally cause a session that is already in the Established state to drop; they do not prevent the session from leaving the Idle state.
In the exhibit, Site A is sending traffic to Site B. R1 adds MPLS label 7166 to direct the traffic to R5. Which two criteria did R1 use to determine which label number to add to the traffic? (Choose two.)
In a Juniper Networks MPLS environment, the process by which a router determines how to forward traffic involves both the control plane and the data plane. When R1 (acting as an Ingress Label Edge Router, or LER) receives an IP packet from Site A destined for Site B, it must perform a lookup to decide whether to forward the packet via standard IP routing or via an MPLS Label Switched Path (LSP).
The first criterion R1 uses is the destination address of the traffic (Option C). Upon receiving the native IP packet, R1 looks up the destination IP in its routing table (typically inet.0). If the destination matches a prefix that is associated with an LSP---such as the loopback address of R5 or a prefix reachable via R5---the router identifies the appropriate Forwarding Equivalence Class (FEC). The FEC essentially groups packets that should be forwarded in the same manner over the same path. Without identifying the destination, the router cannot map the traffic to the correct MPLS tunnel.
The second criterion is the label number advertisement received from R2 (Option D). MPLS relies on downstream label allocation. In this topology, R2 is the immediate downstream 'next hop' for R1 on the path to Site B. For the LSP to be established, R2 must signal a label to R1 using a protocol like LDP (Label Distribution Protocol) or RSVP (Resource Reservation Protocol). This label (in this case, 7166) tells R1: 'If you want to send traffic to the destination associated with this LSP, wrap it in this specific label so I know how to process it.'
R1 does not use the source address (Option A) for standard label mapping, nor does it receive the label directly from R5 (Option B) in a hop-by-hop signaling model; it must use the label provided by its direct neighbor, R2. Therefore, by combining the destination IP (to find the path) and the label provided by the next hop (to encapsulate the packet), R1 successfully directs the traffic through the MPLS core.
How are routing loops prevented in external BGP networks?
BGP is a path-vector protocol, and its primary mechanism for ensuring a loop-free topology across the global internet is the AS_PATH attribute. This attribute is a 'well-known mandatory' attribute that records every Autonomous System (AS) a prefix has passed through.
According to Juniper Networks Service Provider documentation, the loop prevention rule for External BGP (EBGP) is straightforward: when a router receives a BGP Update from an EBGP peer, it examines the AS_PATH list. If the router's own local AS number is already present in the list, it indicates that the advertisement has already traversed the local AS and has returned. To prevent a routing loop, the router will not use the route and will implicitly discard the update (Option D).
This behavior is a default, hard-coded function of the BGP protocol and does not require the administrator to write manual routing policies (Options B and C) to achieve basic loop prevention. While there are advanced features like as-path-expand or allow-as-in that can modify this behavior for specific design requirements (such as in certain Hub-and-Spoke MPLS VPN topologies), the standard operational default is to reject any route where the local AS is detected in the path. This ensures that traffic does not circulate infinitely between Autonomous Systems.
You are a network architect designing a brand new network. You want to deploy RSVP LSPs in this network. You are currently in the process of choosing whether to run OSPF or IS-IS as your interior gateway protocol. In this scenario, which two statements are correct about IGP traffic engineering extensions in an RSVP network? (Choose two.)
In a Juniper Networks environment, deploying RSVP-signaled LSPs requires a functional Traffic Engineering Database (TED). This database is populated by the Interior Gateway Protocol (IGP) using specific extensions that carry link-state information beyond simple reachability, such as available bandwidth, administrative groups (link coloring), and Maximum Reservable Bandwidth.
The behavior of these extensions differs between OSPF and IS-IS in Junos OS:
OSPF (Option C): By default, OSPF is a 'pure' routing protocol. To support RSVP-TE, it must carry Opaque LSAs (Type 10). According to Juniper documentation, you must explicitly configure traffic engineering within the OSPF protocol hierarchy using the set protocols ospf traffic-engineering command. Without this command, OSPF will not flood the TE information required by the Constrained Shortest Path First (CSPF) algorithm, and LSPs will fail to establish.
IS-IS (Option D): IS-IS was designed to be extensible through the use of TLVs (Type, Length, Value). In Junos OS, IS-IS traffic engineering extensions are enabled by default once the protocol is active. As soon as you enable IS-IS on an interface, it begins to advertise the wide metrics and TE TLVs (like TLV 22 and 135) necessary for building the TED.
This distinction is a common design consideration for network architects. While IS-IS simplifies the rollout of MPLS by having TE enabled 'out of the box,' OSPF requires that extra configuration step to transition from a standard IGP to a TE-aware protocol.
