{"id":15324,"date":"2026-09-17T11:40:00","date_gmt":"2026-09-17T11:40:00","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15324"},"modified":"2026-09-17T11:40:00","modified_gmt":"2026-09-17T11:40:00","slug":"cisco-ccnp-service-provider-350-501-practice-test-questions-and-exam-dumps-part15-q281-q300","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cisco-ccnp-service-provider-350-501-practice-test-questions-and-exam-dumps-part15-q281-q300\/","title":{"rendered":"Cisco CCNP Service Provider 350-501 Practice Test Questions and Exam Dumps Part15 Q281-Q300"},"content":{"rendered":"<h1><\/h1>\n<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/350-501-exam-dumps\"><b>Cisco CCNP Service Provider 350-501 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 281<\/b><\/h3>\n<p><b>Which BGP attribute is primarily used to influence outbound traffic within an autonomous system?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MED<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Local Preference<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Origin<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AS_PATH<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">BGP Local Preference is used within an autonomous system to influence which exit point should be selected for outbound traffic. A higher Local Preference value is generally preferred by BGP when comparing eligible paths. Because the attribute is propagated through iBGP within the AS, it can provide consistent outbound path-selection policy across multiple routers. MED is commonly used to influence how neighboring autonomous systems enter a network, while ORIGIN and AS_PATH are other BGP path attributes used during best-path selection. Therefore, Local Preference is the correct answer for influencing outbound traffic.<\/span><\/p>\n<h3><b>Question 282<\/b><\/h3>\n<p><b>Which BGP attribute is commonly used to influence how a neighboring autonomous system enters your network?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MED<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Local Preference<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Weight<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router ID<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The Multi-Exit Discriminator (MED) is commonly used to influence the path that a neighboring autonomous system selects when entering the advertising AS. When multiple links exist between two autonomous systems, an operator can advertise different MED values to suggest a preferred entry point. Lower MED values are generally preferred when the attribute is considered during BGP path selection. Local Preference primarily influences outbound traffic within an AS, while Weight is Cisco-specific and locally significant. Router ID identifies a BGP speaker. Therefore, MED is correct.<\/span><\/p>\n<h3><b>Question 283<\/b><\/h3>\n<p><b>Which BGP attribute is commonly used to prevent routing loops between autonomous systems?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MED<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">NEXT_HOP<\/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;\">LOCAL_PREF<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The AS_PATH attribute records the autonomous systems that a BGP route has traversed. When an AS receives a route containing its own AS number in the AS_PATH, it normally rejects that route because accepting it could create a routing loop. This provides an important loop-prevention mechanism in inter-AS BGP routing. NEXT_HOP identifies the next-hop address, Local Preference influences outbound path selection, and MED can influence inbound path selection between neighboring autonomous systems. Therefore, AS_PATH is the correct attribute for BGP loop prevention.<\/span><\/p>\n<h3><b>Question 284<\/b><\/h3>\n<p><b>Which BGP feature allows multiple routers to share routes without requiring a full-mesh of iBGP sessions?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BGP Confederation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Reflector<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BFD<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Graceful Restart<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A BGP Route Reflector reduces the requirement for a full mesh of iBGP sessions. Instead of every iBGP router establishing a session with every other router, clients establish sessions with one or more route reflectors. The route reflector then redistributes eligible routes between clients according to BGP route-reflection rules. This significantly simplifies BGP scalability in large service-provider networks. BGP Confederations also address scalability but use sub-autonomous-system structures. BFD provides rapid failure detection, while Graceful Restart assists during certain control-plane restart events. Therefore, Route Reflector is correct.<\/span><\/p>\n<h3><b>Question 285<\/b><\/h3>\n<p><b>Which BGP scalability technique divides one autonomous system into multiple internal sub-autonomous systems?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Reflector<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Confederation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Add-Path<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Refresh<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">BGP Confederations divide a large autonomous system into multiple internal sub-autonomous systems. These sub-ASes can use eBGP-like relationships internally while presenting the overall network externally as a single autonomous system. Confederations can reduce the complexity associated with large iBGP deployments and provide additional control over internal routing relationships. Route Reflectors solve scalability by concentrating route distribution, while Add-Path advertises multiple paths and Route Refresh allows routes to be requested again without resetting the session. Therefore, BGP Confederation is correct.<\/span><\/p>\n<h3><b>Question 286<\/b><\/h3>\n<p><b>Which BGP attribute identifies the IP address that should be used to reach the advertised destination?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">NEXT_HOP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ORIGIN<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MED<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">COMMUNITY<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The BGP NEXT_HOP attribute identifies the IP address that a router should use as the next hop toward the advertised destination. The receiving router must have reachability to that next-hop address for the BGP route to be usable. In service-provider networks, next-hop handling is especially important when routes are exchanged between PE routers, route reflectors, or external BGP neighbors. ORIGIN identifies how the route entered BGP, MED can influence path selection, and COMMUNITY carries policy tags. Therefore, NEXT_HOP is the correct attribute.<\/span><\/p>\n<h3><b>Question 287<\/b><\/h3>\n<p><b>Which BGP capability allows a router to maintain forwarding during a temporary control-plane restart when both peers support the feature?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Graceful Restart<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Dampening<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MED<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Add-Path<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">BGP Graceful Restart is designed to help maintain forwarding during certain control-plane restart events. When supported and negotiated by neighboring devices, routing information can be retained temporarily while the restarting BGP process recovers and re-establishes its sessions. This can reduce traffic disruption during planned or unplanned control-plane events. Route Dampening addresses unstable routes, MED influences certain BGP path-selection decisions, and Add-Path allows multiple paths to be advertised. Therefore, Graceful Restart is the correct BGP capability for this scenario.<\/span><\/p>\n<h3><b>Question 288<\/b><\/h3>\n<p><b>Which BGP configuration can protect a router from receiving an unexpectedly large number of prefixes from a neighbor?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Maximum-prefix limit<\/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;\">Next-Hop-Self<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Local Preference<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">A BGP maximum-prefix limit allows an operator to define the maximum number of prefixes that can be accepted from a particular BGP neighbor. If the number of received routes exceeds the configured threshold, the router can take a predefined action, such as warning, shutting down the session, or applying another supported response. This helps protect device resources and provides an operational safeguard against routing mistakes or unexpected advertisements. Route Targets control VPN route import and export, Next-Hop-Self modifies next-hop handling, and Local Preference influences outbound path selection.<\/span><\/p>\n<h3><b>Question 289<\/b><\/h3>\n<p><b>Which BGP mechanism allows an eBGP route to be accepted when the local AS appears in the AS_PATH under controlled circumstances?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AS Override<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Allowas-in<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Reflector<\/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: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The <\/span><span style=\"font-weight: 400;\">allowas-in<\/span><span style=\"font-weight: 400;\"> feature permits a BGP router to accept a route even when its own autonomous system number appears in the AS_PATH. Normally, BGP rejects such a route as a loop-prevention measure. Allowas-in can be useful in specific network designs where the same AS is legitimately present in different routing locations. AS Override performs a different function and is commonly used in MPLS VPN environments to replace customer AS numbers in certain advertisements. Route Reflectors address iBGP scalability, while MED influences path selection. Therefore, allowas-in is correct.<\/span><\/p>\n<h3><b>Question 290<\/b><\/h3>\n<p><b>Which BGP VPN feature can replace a customer&#8217;s AS number in the AS_PATH when advertising routes toward another customer site?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AS Override<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Add-Path<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Graceful Restart<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Refresh<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">AS Override is used in certain MPLS VPN designs when customer sites use the same autonomous system number. A PE router can replace the customer&#8217;s AS number in the AS_PATH before advertising the route toward another customer site. This prevents the receiving customer router from rejecting the route because it sees its own AS number and interprets it as a routing loop. Add-Path provides multiple BGP paths, Graceful Restart supports control-plane recovery, and Route Refresh requests route re-advertisement. Therefore, AS Override is correct.<\/span><\/p>\n<h3><b>Question 291<\/b><\/h3>\n<p><b>Which MPLS label is commonly used to request that the upstream router perform Penultimate Hop Popping?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Explicit Null<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Implicit Null<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VPN Label<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Service Label<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The Implicit Null label is commonly used to signal Penultimate Hop Popping. When the penultimate router receives this instruction, it removes the outer transport label before forwarding the packet toward the egress router. This reduces label-processing work at the egress PE. Explicit Null also causes the outer label to be retained but uses a special label value, which can be useful when preserving certain QoS or TTL information. VPN and service labels identify service-specific forwarding contexts. Therefore, Implicit Null is correct.<\/span><\/p>\n<h3><b>Question 292<\/b><\/h3>\n<p><b>Which MPLS label is commonly used when the egress router needs the outer label to remain present for processing?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Implicit Null<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Explicit Null<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Untagged<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Local Preference<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The Explicit Null label allows the outer MPLS label to remain on the packet until it reaches the egress router. This differs from Implicit Null, where the penultimate router removes the outer transport label. Explicit Null can be useful when preserving QoS-related information or MPLS TTL behavior through the final hop. The label value is a special reserved MPLS label rather than an ordinary dynamically assigned forwarding label. Therefore, Explicit Null is the correct choice when the outer label should remain until the egress router.<\/span><\/p>\n<h3><b>Question 293<\/b><\/h3>\n<p><b>Which MPLS troubleshooting mechanism can verify connectivity across a Label Switched Path?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MPLS LSP Ping<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DHCP Discover<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BGP UPDATE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IGMP Report<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">MPLS LSP Ping is an OAM mechanism used to verify connectivity across an MPLS Label Switched Path. It can help determine whether an LSP is operational and can provide useful diagnostic information when MPLS forwarding is not functioning as expected. MPLS LSP Traceroute can provide additional hop-by-hop troubleshooting information. DHCP Discover is used for address configuration, BGP UPDATE messages carry routing information, and IGMP Reports signal multicast group membership. Therefore, MPLS LSP Ping is the correct mechanism for testing MPLS LSP connectivity.<\/span><\/p>\n<h3><b>Question 294<\/b><\/h3>\n<p><b>Which MPLS table contains label-to-forwarding information used for actual packet forwarding?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LFIB<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LSDB<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARP table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BGP RIB only<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The Label Forwarding Information Base (LFIB) contains information used to forward MPLS-labeled packets. It maps incoming labels to forwarding actions such as swapping, popping, or other label operations and identifies the appropriate outgoing interface or next hop. The routing information base and IGP databases help determine reachability and paths, but the LFIB is specifically associated with MPLS forwarding. The LSDB contains link-state information, while ARP resolves IPv4 addresses to MAC addresses. Therefore, LFIB is the correct table for MPLS label forwarding.<\/span><\/p>\n<h3><b>Question 295<\/b><\/h3>\n<p><b>Which MPLS VPN label stack arrangement normally uses an outer transport label and an inner VPN service label?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Two-label stack<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Single Ethernet tag<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IPv6 extension stack<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TCP option stack<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">An MPLS Layer 3 VPN packet commonly uses a two-label stack. The outer transport label directs the packet across the provider core toward the egress PE. The inner VPN or service label identifies the appropriate customer forwarding context at the egress PE. This separation allows core P routers to forward traffic without maintaining individual customer VRFs while still enabling the egress PE to deliver traffic into the correct VPN. The labels are independent of Ethernet VLAN tags and TCP options. Therefore, the two-label stack is correct.<\/span><\/p>\n<h3><b>Question 296<\/b><\/h3>\n<p><b>Which EVPN route type advertises MAC and IP address reachability information?<\/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 4<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">EVPN Route Type 2 is the MAC\/IP Advertisement route. It provides MAC address reachability information and can also include an associated IP address. This route type is fundamental to EVPN because it allows PE routers to advertise endpoint reachability through the BGP EVPN control plane. Type 1 is used for Ethernet Auto-Discovery, Type 3 is the Inclusive Multicast Ethernet Tag route, and Type 4 is Ethernet Segment discovery. Therefore, Type 2 is the correct EVPN route type for MAC\/IP reachability advertisements.<\/span><\/p>\n<h3><b>Question 297<\/b><\/h3>\n<p><b>Which EVPN route type is used to advertise an Ethernet Segment for multihoming-related control-plane procedures?<\/b><\/p>\n<ol>\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 4<\/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: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">EVPN Route Type 4 is the Ethernet Segment route. It is used in EVPN multihoming environments to advertise information about Ethernet Segments and support procedures such as Designated Forwarder election and Ethernet Segment discovery. This control-plane information allows multiple PE routers connected to the same customer segment to coordinate their forwarding behavior. Type 2 handles MAC\/IP advertisements, Type 3 carries IMET information, and Type 5 advertises IP prefixes. Therefore, Route Type 4 is correct.<\/span><\/p>\n<h3><b>Question 298<\/b><\/h3>\n<p><b>Which EVPN route type is designed to advertise IP prefixes independently of individual MAC addresses?<\/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 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 4<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">EVPN Route Type 5 is the IP Prefix route. It allows EVPN to advertise IP prefix reachability independently of a specific MAC\/IP host advertisement. This makes Type 5 particularly useful for integrated routing and bridging architectures where IP prefixes need to be exchanged across an EVPN control plane. Type 1 is Ethernet Auto-Discovery, Type 2 advertises MAC\/IP reachability, and Type 4 provides Ethernet Segment information. Therefore, Type 5 is the correct route type for advertising IP prefixes.<\/span><\/p>\n<h3><b>Question 299<\/b><\/h3>\n<p><b>Which EVPN mechanism helps suppress unnecessary ARP flooding by distributing IP-to-MAC bindings through the control plane?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ARP suppression<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Dampening<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BGP Confederation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PHP<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">EVPN ARP suppression reduces unnecessary ARP flooding by allowing PE devices to use IP-to-MAC binding information learned through the EVPN control plane. When a device needs to resolve an IP address, the local PE may already know the corresponding MAC information and can respond locally instead of flooding the ARP request throughout the Layer 2 domain. This improves efficiency and reduces broadcast traffic. Route Dampening addresses BGP instability, BGP Confederations improve scalability, and PHP is an MPLS forwarding operation. Therefore, ARP suppression is correct.<\/span><\/p>\n<h3><b>Question 300<\/b><\/h3>\n<p><b>Which multicast technology is designed to allow a receiver to explicitly request traffic from a specific multicast source?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Anycast-RP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SSM<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MSDP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PIM-DM<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Source-Specific Multicast (SSM) allows a receiver to identify both the multicast group and the specific source from which it wants to receive traffic. This eliminates the need for a shared Rendezvous Point for the multicast flow and creates a source-specific forwarding tree. SSM is especially useful for applications where receivers already know the intended source. Anycast-RP provides RP redundancy, MSDP exchanges multicast source information between domains or RPs, and PIM-DM uses a flood-and-prune model. Therefore, SSM is the correct multicast technology.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Cisco CCNP Service Provider 350-501 Exam Dumps and Practice Test Dumps. &nbsp; Question 281 Which BGP attribute is primarily used to influence outbound traffic within an autonomous system? MED Local Preference Origin AS_PATH Correct Answer: 2 Explanation BGP Local Preference is used within an autonomous system to influence which exit point should be [&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\/15324"}],"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=15324"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15324\/revisions"}],"predecessor-version":[{"id":15336,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15324\/revisions\/15336"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15324"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15324"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15324"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}