For two or more switches to participate in the same MSTP region, which parameter must match?
Answer(s): A
Multiple Spanning Tree Protocol (MSTP), as defined in IEEE 802.1s and implemented in Juniper Networks Junos OS, allows for the grouping of VLANs into specific spanning tree instances. This provides significant scalability and load-balancing advantages over traditional STP or RSTP. To achieve this, switches must be grouped into logical "Regions."According to Juniper documentation, for two or more switches to be considered part of the same MSTP Region, they must possess an identical MSTP Configuration Identifier. This identifier consists of three specific attributes that must match exactly across all participating switches:MSTI Name (Region Name): A descriptive string (up to 32 characters) that identifies the region.MSTI Revision Level: A numerical value (0–65535) used to track configuration changes.VLAN-to-Instance Mapping: The specific table that defines which VLAN IDs are associated with which Multiple Spanning Tree Instances (MSTIs).If even one of these parameters—such as the Region name (Option A)—differs, the switches will treat each other as being in separate regions. When switches are in different regions, they interact using the Common Spanning Tree (CST), effectively seeing the other region as a single "virtual bridge," which limits the granularity of traffic engineering.The Extended system ID (Option B) is a component of the Bridge ID used to carry VLAN information in PVST+ but is not a region-matching requirement. Root bridge priority (Option C) and Root bridge ID (Option D) are variables used during the STP election process to determine the topology's root, but they do not define the boundaries of an MSTP region itself.
You are using EBGP to connect to two upstream peers in the same AS. You want to make one of the links less preferred for traffic entering your network from the peer's AS. Which feature should you use to achieve this goal?
Answer(s): C
In the world of BGP, controlling inbound traffic (traffic entering your network) is significantly more challenging than controlling outbound traffic because it requires influencing a decision made by an external Autonomous System (AS). According to Juniper Networks documentation, when you have multiple links to the same AS or even different ASes, the BGP path selection process is used by the upstream neighbor to decide which path to take to reach your prefixes.AS-Path Prepending is the standard technique used to make a path appear less attractive to external peers. By artificially lengthening the AS_PATH attribute on the BGP advertisements sent over a specific link, you exploit the BGP best-path algorithm rule that prefers a shorter AS path. When you prepend your own AS number multiple times to the update sent to the "less preferred" peer, that peer’s BGP routers will see a longer path compared to the alternative link and will naturally prefer the shorter, unprepended route.It is important to distinguish why other options are incorrect for this specific goal:Local Preference (Option D): This is a well-known discretionary attribute used to influence outbound traffic. It is not advertised to EBGP peers; therefore, your upstream neighbor cannot see your local preference settings.Origin Code (Option B): While the origin code (IGP, EGP, or Incomplete) is a tie-breaker in the selection process, it is rarely used for traffic engineering and lacks the granular control provided by prepending.Route Reflector (Option A): This is an Internal BGP (IBGP) scaling mechanism used to reduce the need for a full mesh of peers within an AS; it does not directly influence external path selection by an upstream provider.Junos OS allows you to easily implement prepending via routing policies applied as an "export" policy to the EBGP neighbor. By using the as-path-prepend action within a policy term, you can selectively degrade a path's attractiveness to manage your inbound bandwidth.
By default, which MPLS operation is performed by the penultimate router in an LSP on the transport label?
Answer(s): D
In a Multiprotocol Label Switching (MPLS) environment, label operations are categorized into three primary actions: Push (adding a label), Swap (replacing a label), and Pop (removing a label). The specific behavior described in the question refers to a mechanism called Penultimate Hop Popping (PHP).According to Juniper Networks technical documentation, the goal of PHP is to improve forwarding efficiency at the egress point of a Label-Switched Path (LSP). The Egress Label Edge Router (LER), which is the final destination for the LSP, would normally have to perform two lookups if it received a labeled packet: first, it would look up the label in its MPLS table to see it is the destination, and second, it would look up the underlying IP payload in its IP routing table (inet.0) to forward the packet.To alleviate this burden, the Egress LER signals a special label value called Implicit Null (Label 3) to its upstream neighbor (the penultimate router) during the signaling process (RSVP or LDP). When the penultimate router receives a packet destined for that egress LER, it sees the instruction to pop the transport label. Consequently, the penultimate router performs a Pop operation, stripping away the outer MPLS label and sending the raw IP packet (or the remaining inner service label) to the Egress LER.This allows the Egress LER to perform only a single lookup. If the transport label was the only label, the Egress LER simply performs a standard IP lookup. If there is a VPN label remaining, it performs a single MPLS lookup for the VRF. This "default" behavior in Junos OS optimizes the performance of the egress router by offloading the final label removal to the penultimate hop. Note that if Ultimate HopPopping (UHP) were configured (via the explicit-null command), the penultimate router would perform a Swap to Label 0 instead of a Pop.
You are designing a high availability solution for a Juniper router with dual Routing Engines (RE). You want to ensure that the routing protocol state is preserved during an RE switchover. You have already enabled graceful Routing Engine switchover (GRES) and you want to avoid relying on helper routers to maintain the routing protocol state. In this scenario, which feature would accomplish this behavior?
When designing High Availability (HA) for Juniper Service Provider routers, understanding the interaction between the control plane and data plane is vital. The user has already enabled Graceful Routing Engine Switchover (GRES), which synchronizes the interface and kernel state between the primary and backup Routing Engines (REs). However, GRES by itself does not preserve the routing protocol state (like OSPF adjacencies or BGP sessions).To achieve the preservation of the routing protocol state without relying on external "helper" routers, you must implement Non-Stop Active Routing (NSR). According to Juniper Networks documentation, NSR uses the infrastructure provided by GRES to also synchronize the routing protocol process (rpd) information. Under NSR, the backup RE maintains a "hot" standby state of all routing protocols. If the primary RE fails, the backup RE takes over immediately. Because it already possesses the full routing table and peer session states, the peering neighbors are unaware that a switchover occurred. No protocol adjacency resets occur, and traffic continues to flow uninterrupted.It is crucial to differentiate NSR from Graceful Restart (Option C). While Graceful Restart also aims to maintain traffic flow during a switchover, it does require help from neighboring routers (known as "helper mode"). If the neighbors do not support or are not configured for Graceful Restart, the sessions will drop. Since the user explicitly stated they want to "avoid relying on helper routers," Graceful Restart is not the correct solution.Non-stop Active Bridging (Option A) provides a similar "hitless" failover but specifically for Layer 2 environments (STP/VLANs) rather than Layer 3 routing protocols. BFD (Option B) is a failure detection protocol used to speed up convergence but does not preserve state during an RE failover; in fact, without NSR, BFD would likely trigger a faster teardown of the session during a switchover. Therefore, NSR is the only feature that meets the requirement for independent control-plane preservation.
Which two statements regarding GRE and IP-IP tunnels are correct? (Choose two.)
Answer(s): A,D
In Juniper Networks Junos OS, Generic Routing Encapsulation (GRE) and IP-in-IP (IP-IP) are common tunneling mechanisms used to transport packets across a network by encapsulating them within another protocol. Understanding the header structure and the limitations of these protocols is essential for proper MTU (Maximum Transmission Unit) management and security design.Overhead (Option A):Both GRE and IP-IP tunnels operate by adding an additional IP header to the original packet. An IP-IP tunnel (Protocol 4) adds a 20-byte IPv4 header. A GRE tunnel (Protocol 47) adds the same 20-byte delivery IP header plus a minimum 4-byte GRE header (totaling 24 bytes, which can increase if keys or sequencing are used). Because these headers are added to the payload, the total size of the packet increases. This "overhead" means that if the original packet was already at the MTU limit (e.g., 1500 bytes), the encapsulated packet will exceed it, potentially leading to fragmentation or the need to adjust the TCP MSS (Maximum Segment Size).Encryption (Option D):Crucially, according to Juniper Service Provider documentation, neither GRE nor IP-IP provides native encryption or data confidentiality. They are encapsulation protocols, not security protocols. The payload remains in cleartext and is visible to any device along the path. If security and encryption are required for data traversing these tunnels, they must be combined with IPsec (IP Security). While GRE is often used as the "carrier" for IPsec (to allow multicast or dynamic routing protocols which IPsec alone does not support), the GRE protocol itself remains an unencrypted delivery mechanism. Therefore, statements A and D accurately describe the architectural behavior of these tunnel types.
What is the default export behavior of IS-IS in the Junos OS?
In the Junos OS, routing policy behavior is governed by default import and export rules that vary significantly between different protocols. For IS-IS (Intermediate System to Intermediate System), the default export policy is "reject all." This means that, by default, an IS-IS process will export nothing from the routing table into the IS-IS database.According to Juniper Networks technical documentation, IS-IS automatically advertises its own direct interfaces that are configured under the [edit protocols isis] hierarchy. However, it does not automatically redistribute routes learned from other sources—such as Static routes, OSPF, or BGP— into the IS-IS domain. This is a safety mechanism designed to prevent accidental routing loops or the flooding of unnecessary prefixes into the link-state database (LSDB), which could impact the stability of the SPF (Shortest Path First) algorithm.To move routes from the routing table (inet.0) into IS-IS, an administrator must explicitly create a routing policy and apply it as an export policy within the IS-IS configuration. For example:Code snippet set policy-options policy-statement REDIST-STATIC term 1 from protocol static set policy-options policy-statement REDIST-STATIC term 1 then accept set protocols isis export REDIST-STATICWithout such a policy, the IS-IS LSPs (Link-State PDUs) will only contain information about the IS-IS enabled interfaces and the reachability of other IS-IS neighbors. This behavior contrasts with protocols like BGP, which has different default rules for exporting active BGP routes to EBGP peers. In the context of IS-IS in a Juniper environment, "export nothing" is the standard operational baseline.
Which two statements are correct about TLVs in IS-IS? (Choose two.)
Answer(s): C,D
In the IS-IS protocol, TLVs (Type, Length, Value) are the fundamental building blocks used to carry information within Link-State PDUs (LSPs). Unlike some other protocols that have a fixed, rigid packet format, IS-IS was designed from the ground up to be modular and extensible. This extensibility is achieved through the use of TLVs, which allow the protocol to carry different types of data without requiring changes to the core protocol state machine.According to Juniper Networks technical documentation, TLVs allow flexible encoding of routing information (Option C). Each TLV specifies the "Type" of information it carries (such as neighbor information or IP reachability), the "Length" of that information, and the "Value" (the actual data). This architecture is what allowed IS-IS to easily support IPv6 by simply adding new TLVs (like TLV 236 for IPv6 reachability) without redesigning the protocol. It also supports Traffic Engineering (TE) extensions used in MPLS environments by adding TLVs that describe link bandwidth and administrative groups.Furthermore, a single LSP can contain multiple TLVs (Option D). When a Juniper router generates an LSP, it packs all the necessary information—such as the router's area addresses, its neighbors, and its local interface prefixes—into various TLVs and places them into a single PDU. If the amount of information exceeds the Maximum Transmission Unit (MTU) of the interface, the router will generate additional LSPs (fragmented LSPs) to carry the remaining TLVs.Options A and B are incorrect because restricting an LSP to a single TLV would make the protocol incredibly inefficient, and the very nature of IS-IS is its ability to support multiple network layer protocols (not just IPv4) through its agnostic TLV-based transport.
You are asked to add next-hop redundancy using VRRP for an IPv6 enabled service. The configured primary router must always be active when available, and the servers connected to the network must be able to ping their gateway. Which VRRP element is required to accomplish this requirement?
In Virtual Router Redundancy Protocol (VRRP), the primary goal is to provide a highly available default gateway for end hosts. However, there is a specific operational behavior in the VRRP standard (RFC 3768/RFC 5798) regarding how the "Virtual Router" responds to traffic destined for its own Virtual IP (VIP).According to Juniper Networks documentation, by default, a VRRP router that is in the Master state will only respond to packets destined for the VIP if that router is the IP Address Owner (meaning its physical interface IP matches the VIP). If the router is a "non-owner" (a common configuration in many networks), it will forward traffic on behalf of the VIP but will not respond to management traffic, such as ICMP Echo Requests (Pings), directed at the VIP itself.To satisfy the requirement that "servers connected to the network must be able to ping their gateway," the accept-data (Option D) parameter must be configured. In Junos OS, the accept-data statement allows the VRRP Master to respond to traffic destined for the virtual IP address even if it is not the address owner. This includes responding to Pings and allowing other management connections like SSH or Telnet to the VIP.Regarding the other options:Preempt (Option B): While preempt is often used to ensure the primary router regains control, in Junos, a router with the highest priority (255) defaults to preemptive behavior, and accept-data is specifically what solves the "pinging the gateway" requirement.Track (Option A): Tracking is used for failover logic but doesn't affect the ability to ping the VIP.Static ARP (Option C): This is unnecessary as VRRP uses a virtual MAC address to ensure hosts can resolve the VIP via standard NDP (for IPv6) or ARP (for IPv4).
Share your comments for Juniper JN0-364 exam with other users:
its really good to eventuate knowledge before appearing for the actual exam.
this is great
please i want the questions to pass the exam
i need to pass exam
great, i appreciate it.
please could you upload (isc)2 certified in cybersecurity (cc) exam questions
good questions, wrong answers
im preparing for exams
question no: 42 isnt azure vm an iaas solution? so, shouldnt the answer be "no"?
im study azure
i need this now
i took the aws saa-c03 test and scored 935/1000. it has all the exam dumps and important info.
good questions
well explained
i got the full version and it helped me pass the exam. pdf version is very good.
provide the download link, please
please upload thank.
please can you share 1z0-1055-22 dump pls
i will wait impatiently. thank youu
is it possible to clear the exam if we focus on only these 156 questions instead of 623 questions? kindly help!
really helped with preparation of my scrum exam
very informative and through explanations
prep for exam
thanks for helping us
i prepared for the eccouncil 350-401 exam. i scored 92% on the test.
aba questions to practice
great content
how do i get the remaining questions?
well formatted pdf and the test engine software is free. well worth the money i sept.
looking for 1z0-116
in question 22, shouldnt be in the data (option a) layer?
the questions are incredibly close to real exam. you people are amazing.
q15. answer is b. simple
great practice
Keeping this site free takes real effort. We constantly battle automated scraping and unauthorized content copying. A quick account helps us protect the community and keep the site free.
To continue studying for your JN0-364, please sign in or create a free account.