JN0-364

Practice JN0-364 Exam

Is it difficult for you to decide to purchase Juniper JN0-364 exam dumps questions? CertQueen provides FREE online Service Provider Routing and Switching - Specialist (JNCIS-SP) JN0-364 exam questions below, and you can test your JN0-364 skills first, and then decide whether to buy the full version or not. We promise you get the following advantages after purchasing our JN0-364 exam dumps questions.
1.Free update in ONE year from the date of your purchase.
2.Full payment fee refund if you fail JN0-364 exam with the dumps

Full JN0-364 Exam Dump Here

Latest JN0-364 Exam Dumps Questions

The dumps for JN0-364 exam was last updated on May 10,2026 .

Viewing page 1 out of 1 pages.

Viewing questions 1 out of 9 questions

Question#1

Which OSPF packet type is used to initiate and maintain neighbor relationships?

A. Hello

B. Database Description

C. Link-State Update

D. Link-State Acknowledgment

Explanation:
The Hello packet is the most basic, yet most vital, component of the OSPF protocol. It serves as the primary mechanism for neighbor discovery, parameter negotiation, and "keepalive" functionality. Per Juniper Networks' routing documentation, OSPF routers use the Hello protocol to dynamically discover other OSPF-enabled routers on their directly connected segments.
When OSPF is enabled on a Junos interface, the router begins multicasting Hello packets (typically to the 224.0.0.5"All OSPF Routers" address). This initiates the neighbor relationship. For two routers to move beyond the Init state and become neighbors, they must agree on several critical parameters contained within the Hello packet:
Area ID: Routers must be in the same OSPF area.
Authentication: Passwords or keys must match.
Timers: The Hello and Dead intervals must be identical.
Options: Such as Stub area flags.
Beyond the initial "initiation, " the Hello packet is used to maintain the relationship. By continuously sending these packets at a fixed interval (the Hello interval), a router signals to its peers that it is still functional. If a router stops receiving Hello packets from a neighbor for a duration exceeding the Dead Interval, it declares the neighbor "down, " flushes the associated LSAs from the database, and triggers a new SPF calculation.
Furthermore, on multi-access networks like Ethernet, the Hello packet is the vehicle for the election of the Designated Router (DR) and Backup Designated Router (BDR). By exchanging priority values and Router IDs within the Hello packets, the segment can elect a central point of contact to minimize the number of adjacencies required on the wire.

Question#2

What information is determined by using the AS path attribute included in the BGP update message? (Choose two.)

A. the origin of a route from IGP or EGP

B. the presence of a routing loop

C. the shortest AS path to reach a prefix

D. the total number of next-hop devices to reach a prefix

Explanation:
The AS_PATH attribute is a "well-known mandatory" attribute in BGP, meaning it must be present in every BGP Update message exchanged between External BGP (eBGP) peers. It records the sequence of Autonomous System numbers that a route has traversed. Per Juniper Networks Service Provider documentation, this attribute serves two fundamental purposes:

Question#3

Referring to the exhibit.

Which protocol would automatically create a full mesh of label-switched paths between MPLS-enabled routers?

A. LDP

B. BFD

C. BGP

D. RSVP

Explanation:
In Juniper Networks Junos OS, the Label Distribution Protocol (LDP) is specifically designed to automate the creation of Label Switched Paths (LSPs) based on the information provided by the underlying Interior Gateway Protocol (IGP), such as OSPF or IS-IS. When LDP is enabled on a set of interfaces within an OSPF area (as shown in the exhibit with Area 0.0.0.0), it automatically discovers neighbors and exchanges label mappings for all known unicast routes in the routing table.
The defining characteristic of LDP in this context is its "topology-driven" nature. Unlike RSVP (Resource Reservation Protocol), which typically requires the manual configuration of each LSP ingress point and destination, LDP follows the IGP's shortest path tree to automatically build a full mesh of LSPs between all participating routers. This means that every Provider Edge (PE) and Provider (P) router in the exhibit―PE1, PE2, PE3, P1, P2, and P3―will establish label-switched connectivity to every other router without the administrator having to define individual tunnels.
LDP accomplishes this through a downstream-unsolicited label distribution mode by default in Junos. Each router assigns a local label for its loopback address and other prefixes and advertises these to its neighbors. Because every router is performing this action for every reachable prefix in the OSPF domain, a complete fabric of label-switched paths is formed. While RSVP is more robust for traffic engineering and bandwidth reservation, LDP is the preferred protocol for creating a simple, scalable full mesh of LSPs for applications like Layer 3 VPNs or internal BGP tunneling where complex path manipulation is not required. BFD is a failure detection protocol, and BGP is used for service signaling, making LDP the only correct choice for automatic mesh creation.

Question#4

Which feature allows Junos OS to perform recursive lookups for static route next hops?

A. resolve

B. discard

C. reject

D. next-table

Explanation:
In standard routing, astatic route is typically considered valid only if the specified next-hop IP address is directly reachable on a local subnet. However, in complex service provider designs, the next-hop might be a "distant" IP address that is reachable through another route (such as a BGP route or another static route). This process of looking up a next-hop within another routing entry is called recursive lookup.
In Junos OS, the resolve (Option A) parameter is explicitly used to enable this behavior for static routes. According to Juniper technical documentation, when you append the resolve keyword to a static route configuration, you are instructing the Routing Engine to search the routing table to find a path to that distant next-hop.
For example:
set routing-options static route 10.1.1.0/24 next-hop 192.168.100.1 resolve
If 192.168.100.1 is not on a local interface but is reachable via an OSPF route, the router will "resolve" the path and install the 10.1.1.0/24 route into the forwarding table using the OSPF path's exit interface.
Why other options are incorrect:
Discard (Option B) and Reject (Option C) are "next-hop types" used to drop traffic, either silently (discard) or by sending an ICMP unreachable message (reject).
Next-table (Option D) is used for Inter-VRF routing, where the router is told to look up the destination in a completely different routing instance (like a VRF table), which is a different architectural function than a recursive next-hop lookup within the same table.

Question#5

The MPLS Label Information Base (LIB) is stored in which table?

A. inet6.0

B. mpls.0

C. inet.3

D. inet.0

Explanation:
In Junos OS, the Routing Engine maintains several different tables to manage various types of reachability and forwarding information. When a router is running MPLS, it must track both IP routes and label-to-label mappings.
Thempls.0table is the primary repository for the Label Information Base (LIB) and the Label Forwarding Information Base (LFIB). According to Juniper Networks documentation, mpls.0 is used by transit and egress routers to perform label lookups. When a labeled packet arrives at an interface, the router looks at the top label and references the mpls.0 table to determine the next action. This table stores the mapping of incoming labels to their corresponding operations: Pop (remove the label), Swap (replace the label), or Push (add an additional label).
It is crucial to understand the roles of the other tables to avoid confusion:
inet.0 (Option D): This is the default unicast routing table for IPv4, used for standard IP-to-IP forwarding.
inet.3 (Option C): This is the MPLS Path Table. It stores the egress loopback addresses of LSPs and is used by BGP for next-hop resolution to determine if a destination can be reached via an MPLS tunnel. While inet.3 knows about LSPs, the actual label-switching instructions reside in mpls.0.
inet6.0 (Option A): This is the default unicast routing table for IPv6.
Therefore, for the specific purpose of storing the label base used for transit switching operations, mpls.0is the correct and only table used in the Junos architecture.

Exam Code: JN0-364 Q & A: 65 Q&As Updated: May 10,2026

Full JN0-364 Exam Dumps Here

Exam Code: JN0-364
Q & A: 65 Q&As
Updated: May 10,2026

About JN0-364 Dumps