{"id":15675,"date":"2026-09-18T06:21:32","date_gmt":"2026-09-18T06:21:32","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15675"},"modified":"2026-09-18T06:21:32","modified_gmt":"2026-09-18T06:21:32","slug":"juniper-jn0-664-practice-test-questions-and-exam-dumps-part18-q341-360","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/juniper-jn0-664-practice-test-questions-and-exam-dumps-part18-q341-360\/","title":{"rendered":"Juniper JN0-664 Practice Test Questions and Exam Dumps Part18 Q341-360"},"content":{"rendered":"<h1><\/h1>\n<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/jn0-664-exam-dumps\"><b>Juniper JN0-664 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h2><b>Question 341<\/b><\/h2>\n<p><b>Which IPv6 mechanism verifies an address is not duplicated?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router Advertisement<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Neighbor Solicitation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Prefix Delegation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Duplicate Address Detection<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Duplicate Address Detection, commonly abbreviated DAD, verifies that an IPv6 address is not already being used by another node on the local network. Before an address becomes fully usable, the IPv6 node can send Neighbor Solicitation messages to determine whether another device responds for that address. If another node indicates ownership, the address is considered duplicated and should not be used normally. Router Advertisements provide configuration information, while Prefix Delegation distributes network prefixes. DAD is therefore specifically responsible for detecting duplicate IPv6 addresses before they create an addressing conflict.<\/span><\/p>\n<h2><b>Question 342<\/b><\/h2>\n<p><b>Which IPv6 message requests configuration information from local routers?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Neighbor Solicitation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router Solicitation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router Advertisement<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Neighbor Advertisement<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Router Solicitation is an ICMPv6 Neighbor Discovery message used by an IPv6 host to request router information from routers on the local network. A host can send a Router Solicitation instead of waiting for the next periodic Router Advertisement. The router may then respond with configuration information such as network prefixes and other parameters. Neighbor Solicitation and Neighbor Advertisement primarily support neighbor discovery and address resolution functions, while Router Advertisement carries information from routers toward hosts. Router Solicitation therefore provides the mechanism for hosts to actively request local router configuration information.<\/span><\/p>\n<h2><b>Question 343<\/b><\/h2>\n<p><b>Which IPv6 message announces router configuration to hosts?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router Advertisement<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router Solicitation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Neighbor Solicitation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Redirect<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Router Advertisement messages communicate IPv6 router and prefix information to hosts on a local network. They are part of the ICMPv6 Neighbor Discovery framework and can provide information used for automatic IPv6 configuration. Hosts can receive advertisements periodically or after sending Router Solicitation messages. Neighbor Solicitation is used for neighbor-related operations, while Redirect messages provide more specific routing guidance to hosts. Router Advertisement is therefore the message responsible for announcing router availability and relevant IPv6 network configuration information.<\/span><\/p>\n<h2><b>Question 344<\/b><\/h2>\n<p><b>Which IPv6 address category is intended for temporary privacy?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Link-local address<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Global address<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Temporary address<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Multicast address<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">IPv6 temporary addresses are designed to reduce the ability to track a host based on a stable interface identifier. Privacy mechanisms can generate temporary addresses that change periodically while allowing the host to maintain normal IPv6 communication. Link-local addresses are used for communication on the local link, global addresses provide broader IPv6 reachability, and multicast addresses identify groups of receivers. Temporary addresses therefore serve a privacy-oriented purpose rather than defining a particular routing scope or multicast membership. Their use can help reduce long-term exposure of a stable host identifier.<\/span><\/p>\n<h2><b>Question 345<\/b><\/h2>\n<p><b>Which IPv6 mechanism advertises prefix information without DHCPv6?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router Advertisement<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Neighbor Advertisement<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router Solicitation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DHCP Relay<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">IPv6 Router Advertisement messages can provide hosts with prefix information needed for stateless address configuration. This allows a host to construct an IPv6 address using information received from the local router without requiring DHCPv6 for the address-generation process. Router Solicitation is used by hosts to request advertisements, while Neighbor Advertisement supports neighbor discovery. DHCP Relay forwards DHCP-related traffic between clients and servers. Router Advertisement is therefore the key mechanism for distributing IPv6 prefix information in stateless configurations.<\/span><\/p>\n<h2><b>Question 346<\/b><\/h2>\n<p><b>Which multicast version supports source filtering by receivers?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IGMPv1<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IGMPv2<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IGMPv3<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IGMPv4<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">IGMPv3 introduces source filtering capabilities that allow IPv4 multicast receivers to express interest in traffic from specific sources. This capability supports source-specific multicast models and gives receivers greater control over which multicast streams they accept. Earlier IGMP versions provide simpler group-membership functionality and do not offer the same source-selection capabilities. IGMPv4 is not a standard version used for this purpose. IGMPv3 is therefore the appropriate version when source filtering and source-specific receiver behavior are required in IPv4 multicast networks.<\/span><\/p>\n<h2><b>Question 347<\/b><\/h2>\n<p><b>Which switching feature restricts forwarding based on learned MAC addresses?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAC limiting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route summarization<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DHCP snooping<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Prefix delegation<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">MAC limiting controls the number or set of MAC addresses that can be learned or used on a switching interface, depending on the configured Junos feature and policy. It can help restrict unauthorized devices and reduce certain Layer 2 security risks. Route summarization operates at the routing-table level, DHCP-related mechanisms concern host configuration, and prefix delegation concerns IPv6 network prefixes. MAC limiting therefore addresses Ethernet switching behavior by controlling acceptable MAC-address learning or usage on an interface. Its exact enforcement behavior depends on the configured limits and associated switching policies.<\/span><\/p>\n<h2><b>Question 348<\/b><\/h2>\n<p><b>Which Layer 2 feature prevents unauthorized switch connections?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Root protection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Port security<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Link aggregation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Traffic shaping<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Port security mechanisms can restrict which devices are permitted to use a switch interface by controlling acceptable MAC addresses or related access conditions. This can help prevent unauthorized endpoints from connecting to protected network ports. Root protection serves a different Layer 2 control-plane purpose by protecting spanning-tree topology, link aggregation combines physical links, and traffic shaping controls packet transmission rates. Port security therefore addresses endpoint access at the switch-port level. Proper configuration can help administrators enforce expected device connectivity while reducing the risk of unauthorized Layer 2 access.<\/span><\/p>\n<h2><b>Question 349<\/b><\/h2>\n<p><b>Which spanning-tree protection feature blocks unexpected root BPDUs?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BPDU filter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Loop protection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Root protection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAC limiting<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Root protection helps prevent a designated spanning-tree port from becoming influenced by unexpected superior BPDUs that could attempt to establish a different spanning-tree root. This protects the intended Layer 2 topology from unauthorized or unexpected root changes. BPDU filtering controls the handling of BPDUs, while loop protection addresses certain conditions involving missing BPDUs and Layer 2 loop prevention. MAC limiting concerns endpoint MAC-address restrictions rather than spanning-tree root selection. Root protection is therefore specifically associated with defending the intended root topology from inappropriate spanning-tree information.<\/span><\/p>\n<h2><b>Question 350<\/b><\/h2>\n<p><b>Which spanning-tree feature suppresses BPDU transmission or reception?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BPDU filter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Root protection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Loop protection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storm control<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">BPDU filtering controls the handling of Bridge Protocol Data Units on configured switch interfaces. Depending on the specific configuration and platform behavior, it can prevent BPDUs from being processed or transmitted on selected ports. This differs from root protection, which is designed to prevent unexpected devices from influencing the spanning-tree root, and loop protection, which addresses certain loss-of-BPDU conditions. Storm control manages excessive Layer 2 traffic. BPDU filtering should therefore be used deliberately because suppressing spanning-tree control traffic can affect loop-prevention behavior.<\/span><\/p>\n<h2><b>Question 351<\/b><\/h2>\n<p><b>Which spanning-tree mechanism detects missing BPDUs on protected ports?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BPDU filter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Loop protection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Root protection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAC limiting<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Loop protection helps protect Layer 2 networks when expected BPDUs stop arriving on interfaces participating in spanning-tree operation. Under appropriate conditions, the feature can place a port into a protective state rather than allowing it to transition in a way that could create a forwarding loop. BPDU filtering serves a different purpose by controlling BPDU handling, while root protection focuses on preventing an unexpected superior root from influencing the topology. MAC limiting addresses endpoint restrictions. Loop protection is therefore specifically associated with detecting abnormal loss of expected spanning-tree control information.<\/span><\/p>\n<h2><b>Question 352<\/b><\/h2>\n<p><b>Which Ethernet service transports frames across a provider network?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPLS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VRF<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DHCP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RADIUS<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Virtual Private LAN Service, or VPLS, provides Layer 2 connectivity between customer sites across a provider network. It allows geographically separated Ethernet segments to appear as part of a common virtual Layer 2 service. Customer frames can therefore traverse the provider infrastructure while maintaining Ethernet service characteristics. VRF provides separated Layer 3 routing tables, DHCP provides host configuration, and RADIUS handles centralized authentication. VPLS is consequently associated with delivering Layer 2 VPN connectivity across a provider network.<\/span><\/p>\n<h2><b>Question 353<\/b><\/h2>\n<p><b>Which EVPN identifier represents an Ethernet Segment?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Distinguisher<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ethernet Segment Identifier<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Target<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Virtual Network Identifier<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Ethernet Segment Identifier, or ESI, identifies an Ethernet segment in EVPN environments, particularly where multihoming is involved. It allows participating devices to recognize the same customer-facing Ethernet segment and coordinate forwarding behavior across redundant provider-edge connections. A Route Distinguisher separates VPN routes within routing tables, while a Route Target controls route import and export policy. A Virtual Network Identifier is associated with other virtual-network technologies. The ESI therefore has a specific role in identifying an Ethernet segment within EVPN architectures.<\/span><\/p>\n<h2><b>Question 354<\/b><\/h2>\n<p><b>Which EVPN route type advertises MAC and IP reachability?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Type 1<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Type 2<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Type 3<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Type 5<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">EVPN Route Type 2 is used for MAC\/IP Advertisement routes. These routes provide information about Ethernet endpoint reachability and can associate a MAC address with an IP address when applicable. Other EVPN route types perform different functions: Type 1 supports Ethernet Auto-Discovery, Type 3 handles inclusive multicast Ethernet-tag information, and Type 5 provides IP Prefix routes. Understanding EVPN route types is important when troubleshooting control-plane learning and determining how endpoint information is distributed between participating provider-edge devices.<\/span><\/p>\n<h2><b>Question 355<\/b><\/h2>\n<p><b>Which EVPN route type advertises IP prefixes independently of MACs?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Type 5<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Type 2<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Type 3<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Type 1<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">EVPN Route Type 5 is used to advertise IP Prefix routes. Unlike Type 2 MAC\/IP Advertisement routes, Type 5 routes allow IP prefix reachability to be distributed through the EVPN control plane without requiring the route to represent a specific MAC\/IP endpoint advertisement. Type 1 is associated with Ethernet Auto-Discovery, while Type 3 carries Inclusive Multicast Ethernet Tag information. Type 5 is therefore particularly relevant to integrated Layer 2 and Layer 3 EVPN designs where routed prefixes need to be advertised through the EVPN control plane.<\/span><\/p>\n<h2><b>Question 356<\/b><\/h2>\n<p><b>Which VPN attribute distinguishes identical customer prefixes?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Target<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Distinguisher<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Community<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cluster List<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Route Distinguisher, or RD, makes otherwise identical VPN prefixes unique within the provider&#8217;s VPN routing infrastructure. This is especially important when different customers use overlapping address spaces. By adding the RD to a customer prefix, the resulting VPN route becomes distinguishable from an identical prefix belonging to another VPN. Route Targets serve a different purpose by controlling which VPN routes are imported or exported. Community and Cluster List are BGP-related attributes with other policy and route-reflection functions. The RD therefore provides uniqueness rather than controlling route distribution policy.<\/span><\/p>\n<h2><b>Question 357<\/b><\/h2>\n<p><b>Which VPN attribute controls import and export membership?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Target<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Distinguisher<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AS Path<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MED<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Route Target, or RT, is used to control which VPN routes are imported into or exported from particular VPN routing instances. By assigning compatible Route Target values, administrators can determine which customer sites or VPN instances should share specific routes. This differs from the Route Distinguisher, which primarily makes overlapping VPN prefixes unique. AS Path and MED are BGP path attributes serving different purposes. Route Targets are therefore central to controlling VPN route distribution and defining which routing instances participate in particular VPN connectivity relationships.<\/span><\/p>\n<h2><b>Question 358<\/b><\/h2>\n<p><b>Which MPLS mode retains labels learned from alternate next hops?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Conservative retention<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Liberal retention<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Strict retention<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Selective retention<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Liberal label retention allows an MPLS router to retain label bindings learned from neighboring label distribution peers even when those bindings are not currently associated with the router&#8217;s selected next hop. Keeping these bindings can make label information immediately available if the preferred path changes. Conservative label retention keeps a narrower set of label bindings associated with active forwarding requirements. The distinction affects label availability and resource usage. Liberal retention can provide faster readiness after topology changes because previously learned alternate label information does not necessarily need to be relearned.<\/span><\/p>\n<h2><b>Question 359<\/b><\/h2>\n<p><b>Which LDP distribution method sends labels without explicit requests?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Downstream on Demand<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Downstream Unsolicited<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Upstream Requested<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Selective Advertisement<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">In Downstream Unsolicited label distribution, an LDP router can advertise label bindings to its neighbors without first receiving an explicit request for each binding. This allows label information to be distributed proactively and is a common concept in MPLS label distribution. Downstream on Demand follows a different model in which label information is requested when needed. The distinction affects how quickly label bindings become available and how signaling exchanges are performed. Downstream Unsolicited therefore represents proactive label advertisement rather than request-driven label distribution.<\/span><\/p>\n<h2><b>Question 360<\/b><\/h2>\n<p><b>Which MPLS concept identifies packets receiving identical forwarding treatment?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Label Binding<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Forwarding Equivalence Class<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Label Space<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LDP Session<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Forwarding Equivalence Class, or FEC, groups packets that receive the same forwarding treatment through an MPLS network. Packets belonging to the same FEC can therefore be assigned and handled using common forwarding information. A label binding associates an MPLS label with a particular forwarding context, while label space refers to the scope in which labels are meaningful. An LDP session provides the control-plane relationship used to exchange label information. The FEC is therefore the concept that defines which packets should receive equivalent forwarding behavior.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Juniper JN0-664 Exam Dumps and Practice Test Dumps. &nbsp; Question 341 Which IPv6 mechanism verifies an address is not duplicated? Router Advertisement Neighbor Solicitation Prefix Delegation Duplicate Address Detection Correct Answer: 4 Explanation: Duplicate Address Detection, commonly abbreviated DAD, verifies that an IPv6 address is not already being used by another node on [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15675"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=15675"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15675\/revisions"}],"predecessor-version":[{"id":15698,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15675\/revisions\/15698"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15675"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15675"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15675"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}