{"id":15319,"date":"2026-09-17T11:41:22","date_gmt":"2026-09-17T11:41:22","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=15319"},"modified":"2026-09-17T11:41:22","modified_gmt":"2026-09-17T11:41:22","slug":"cisco-ccnp-service-provider-350-501-practice-test-questions-and-exam-dumps-part10-q181-q200","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/cisco-ccnp-service-provider-350-501-practice-test-questions-and-exam-dumps-part10-q181-q200\/","title":{"rendered":"Cisco CCNP Service Provider 350-501 Practice Test Questions and Exam Dumps Part10 Q181-Q200"},"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 181<\/b><\/h3>\n<p><b>Which OSPF LSA type is originated by an ABR to describe networks within an area to other OSPF areas?<\/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: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">OSPF Type 3 LSAs, also called Summary LSAs, are originated by an Area Border Router (ABR) to advertise networks from one OSPF area into another area. They allow routers in different areas to learn about inter-area destinations while maintaining the hierarchical OSPF architecture. Type 1 LSAs describe routers within an area, while Type 2 LSAs describe multiaccess networks and are originated by the DR. Type 5 LSAs advertise external routes introduced by an ASBR. Therefore, Type 3 is the correct LSA type for inter-area network advertisements.<\/span><\/p>\n<h3><b>Question 182<\/b><\/h3>\n<p><b>Which OSPF calculation algorithm determines the shortest path tree from a router&#8217;s perspective?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Bellman-Ford<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dijkstra SPF<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Path Vector<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Distance Vector<\/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;\">OSPF uses the Dijkstra Shortest Path First (SPF) algorithm to calculate the shortest path tree from the router&#8217;s perspective. The calculation uses information contained in the OSPF Link-State Database (LSDB) and considers interface costs when determining paths. After calculating the shortest path tree, the router installs appropriate routes into its routing table. BGP uses a path-vector approach, while traditional distance-vector protocols use different algorithms. Therefore, Dijkstra SPF is the correct algorithm associated with OSPF path calculation.<\/span><\/p>\n<h3><b>Question 183<\/b><\/h3>\n<p><b>Which OSPF parameter is primarily used to influence the preferred path through an OSPF network?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Interface cost<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Router ID<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Area ID<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LSA sequence number<\/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;\">OSPF interface cost is used to influence path selection. OSPF calculates the total cost of a path by adding the costs of the interfaces along that path. When multiple routes to the same destination exist, the path with the lower total OSPF cost is generally preferred. Router ID identifies an OSPF router, Area ID identifies an OSPF area, and LSA sequence numbers help determine the freshness of link-state information. Therefore, interface cost is the correct parameter for influencing OSPF path selection.<\/span><\/p>\n<h3><b>Question 184<\/b><\/h3>\n<p><b>Which OSPF router type connects an OSPF area to another OSPF area?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ASBR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Internal router<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ABR<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DR<\/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;\">An Area Border Router (ABR) connects one OSPF area to another and maintains link-state information for the areas to which it is connected. ABRs are important to OSPF&#8217;s hierarchical design because they can summarize routes between areas and help contain the scope of topology changes. An ASBR connects OSPF to external routing domains through route redistribution. An internal router has interfaces within a single area, while a DR is elected on certain multiaccess networks. Therefore, ABR is the correct router type for connecting OSPF areas.<\/span><\/p>\n<h3><b>Question 185<\/b><\/h3>\n<p><b>Which IS-IS feature allows a router to advertise routes from one IS-IS level into another level?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route leaking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LSP flooding<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DIS election<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Overload bit<\/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;\">IS-IS route leaking allows selected routes to be advertised between Level 1 and Level 2 routing domains. This can provide more granular control over which prefixes are visible across the hierarchical IS-IS topology. For example, specific Level 2 routes can be leaked into Level 1 areas when more detailed reachability information is required. LSP flooding distributes link-state information, DIS election identifies the designated intermediate system on certain networks, and the overload bit can discourage transit traffic through a router. Therefore, route leaking is correct.<\/span><\/p>\n<h3><b>Question 186<\/b><\/h3>\n<p><b>What is the primary purpose of the IS-IS Designated Intermediate System on a broadcast network?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Assign IP addresses<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Reduce the number of adjacencies and LSP flooding overhead<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Provide BGP route reflection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Allocate MPLS VPN labels<\/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 IS-IS Designated Intermediate System (DIS) helps reduce the amount of adjacency and link-state flooding overhead on broadcast networks. The DIS creates a pseudonode representation for the broadcast segment and originates a pseudonode LSP describing the participating routers. This approach simplifies the topology representation and reduces the need for every router to establish a full set of equivalent relationships with every other router on the segment. The DIS does not assign IP addresses, perform BGP route reflection, or allocate VPN labels. Therefore, reducing topology and flooding overhead is correct.<\/span><\/p>\n<h3><b>Question 187<\/b><\/h3>\n<p><b>Which BGP attribute indicates how a route was originally introduced into BGP?<\/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;\">ORIGIN<\/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;\">LOCAL_PREF<\/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 BGP ORIGIN attribute indicates how a route was introduced into BGP. Common origin values include IGP, EGP, and incomplete, with IGP generally preferred over EGP and incomplete during the relevant stage of BGP best-path selection. The attribute helps BGP compare otherwise eligible paths. MED influences route selection between neighboring autonomous systems, NEXT_HOP identifies the next-hop address, and LOCAL_PREF influences outbound path selection within an autonomous system. Therefore, ORIGIN is the correct attribute for identifying the route&#8217;s origin type.<\/span><\/p>\n<h3><b>Question 188<\/b><\/h3>\n<p><b>Which BGP mechanism can reduce the impact of frequent route flapping by temporarily suppressing unstable routes?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route Refresh<\/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 Dampening<\/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: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">BGP Route Dampening is designed to reduce the impact of unstable routes that repeatedly withdraw and reappear. When a route flaps frequently, penalties can accumulate and the route may be suppressed temporarily according to configured thresholds. This can reduce unnecessary processing and propagation of unstable routing information. Route Refresh allows routing information to be requested again, Graceful Restart helps maintain forwarding during certain restarts, and Add-Path allows multiple paths to be advertised. Therefore, Route Dampening is the correct mechanism for handling frequent route instability.<\/span><\/p>\n<h3><b>Question 189<\/b><\/h3>\n<p><b>Which BGP feature can allow a router to accept a route containing its own AS number 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;\">Allowas-in<\/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<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<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">The BGP <\/span><span style=\"font-weight: 400;\">allowas-in<\/span><span style=\"font-weight: 400;\"> feature allows a router to accept routes containing its own autonomous system number in the AS_PATH. Normally, BGP rejects such routes to prevent routing loops. In specific designs, such as networks using the same AS number at multiple locations, controlled use of allowas-in may be necessary. Because it weakens the normal AS_PATH loop-prevention behavior, it should be configured carefully and with appropriate policy controls. Next-Hop-Self changes the next-hop attribute, while Local Preference and MED influence path selection. Therefore, allowas-in is correct.<\/span><\/p>\n<h3><b>Question 190<\/b><\/h3>\n<p><b>Which BGP feature can provide different route policies to different peer groups while simplifying configuration?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BGP Communities<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MPLS Labels<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OSPF Areas<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IS-IS TLVs<\/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 Communities allow routes to be tagged with policy information that can later be matched and acted upon by routing policies. Operators can use communities to identify routes belonging to particular customers, regions, services, or policy categories. This allows a common community value to trigger consistent actions across multiple routers or peer relationships. MPLS labels perform forwarding functions, OSPF Areas organize link-state routing, and IS-IS TLVs carry protocol information. Therefore, BGP Communities are the appropriate mechanism for simplifying policy classification and application.<\/span><\/p>\n<h3><b>Question 191<\/b><\/h3>\n<p><b>Which MPLS VPN component makes identical customer IPv4 prefixes unique within the provider&#8217;s VPN routing system?<\/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;\">MPLS TC<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BGP Community<\/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 Route Distinguisher (RD) makes otherwise identical IPv4 prefixes unique within an MPLS VPN environment. For example, two customers can both use the same IPv4 prefix, but different RDs create distinct VPNv4 routes. This allows the provider to maintain overlapping customer address spaces without ambiguity in the VPN control plane. Route Targets serve a different function by controlling which VRFs import and export VPN routes. MPLS TC is related to traffic classification, while BGP Communities communicate policy information. Therefore, the Route Distinguisher is correct.<\/span><\/p>\n<h3><b>Question 192<\/b><\/h3>\n<p><b>Which MPLS VPN attribute determines whether a VPN route should be imported into a particular VRF?<\/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;\">MPLS TTL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BGP Weight<\/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;\">Route Targets (RTs) control the import and export of VPN routes between PE routers and VRFs. An exported VPN route is associated with one or more Route Targets, and a receiving VRF imports routes whose Route Targets match its configured import policy. This provides flexible control over which customer VPN routes are reachable from a particular VRF. The Route Distinguisher makes VPN routes unique but does not determine their import policy. MPLS TTL controls packet lifetime, while BGP Weight is a local path-selection attribute. Therefore, Route Target is correct.<\/span><\/p>\n<h3><b>Question 193<\/b><\/h3>\n<p><b>Which MPLS forwarding component is responsible for associating incoming labels with outgoing labels and interfaces?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">RIB<\/span><\/li>\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;\">ARP cache<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LSDB<\/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 Label Forwarding Information Base (LFIB) contains the forwarding information needed to process MPLS-labeled packets. It can specify actions such as swapping an incoming label for an outgoing label, popping a label, and forwarding traffic through a particular interface or next hop. The RIB contains IP routing information, while the ARP cache contains IPv4-to-MAC mappings. An LSDB contains link-state routing information used by protocols such as OSPF or IS-IS. Therefore, LFIB is the correct component for MPLS label forwarding.<\/span><\/p>\n<h3><b>Question 194<\/b><\/h3>\n<p><b>Which MPLS OAM tool can help identify individual hops along an MPLS LSP?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MPLS LSP Traceroute<\/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;\">SNMP SET<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">IGMP<\/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 Traceroute is an OAM and troubleshooting mechanism that can help identify the routers or hops involved in an MPLS Label Switched Path. It provides more detailed information than a simple connectivity test and can help operators locate where an LSP may be failing. MPLS LSP Ping can be used to test LSP connectivity, while DHCP provides host configuration, SNMP SET changes supported management objects, and IGMP handles multicast membership. Therefore, MPLS LSP Traceroute is the correct tool for identifying LSP hops.<\/span><\/p>\n<h3><b>Question 195<\/b><\/h3>\n<p><b>Which Segment Routing SID identifies a specific node or its associated prefix in the network?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Node-SID<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Adj-SID<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Binding SID<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Service SID<\/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 Node-SID identifies a node in a Segment Routing domain and is commonly associated with the node&#8217;s loopback or another advertised prefix. When a packet is instructed to follow a Node-SID, the network forwards it toward the corresponding node according to the Segment Routing topology. An Adj-SID represents a specific adjacency, while a Binding SID can represent a segment-routing policy or set of instructions. Service SIDs are associated with service-specific functions in relevant Segment Routing architectures. Therefore, Node-SID is the correct answer.<\/span><\/p>\n<h3><b>Question 196<\/b><\/h3>\n<p><b>What is the primary purpose of a Binding SID in Segment Routing Traffic Engineering?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Identify an SNMP object<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Represent an SR policy as a segment<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Identify an OSPF area<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Allocate an IPv4 address<\/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 Binding Segment Identifier (BSID) can represent a Segment Routing policy as a single segment. When traffic is steered using the BSID, the associated SR policy can determine the sequence of segments that should be applied to the traffic. This abstraction simplifies policy invocation because an external mechanism does not necessarily need to know the entire internal segment list. BSIDs are therefore useful in SR Traffic Engineering and policy-based forwarding. They are unrelated to SNMP objects, OSPF area identifiers, or IPv4 address allocation. Therefore, representing an SR policy as a segment is correct.<\/span><\/p>\n<h3><b>Question 197<\/b><\/h3>\n<p><b>Which QoS scheduling mechanism assigns bandwidth to multiple traffic classes according to configured weights?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CBWFQ<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LLQ<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Policing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">WRED<\/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;\">Class-Based Weighted Fair Queuing (CBWFQ) allows administrators to define traffic classes and allocate bandwidth to those classes during congestion. Each class can be configured with bandwidth or other scheduling parameters, enabling predictable resource allocation among different traffic types. LLQ adds a strict priority queue for delay-sensitive traffic, while policing enforces traffic-rate limits. WRED is a congestion-avoidance mechanism that can selectively drop packets before a queue becomes full. Therefore, CBWFQ is the appropriate scheduling mechanism for allocating bandwidth among configured traffic classes.<\/span><\/p>\n<h3><b>Question 198<\/b><\/h3>\n<p><b>Which QoS mechanism is specifically designed to provide strict priority service to a selected traffic class?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">WRED<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LLQ<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CBWFQ<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shaping<\/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;\">Low Latency Queuing (LLQ) provides a strict priority queue for selected traffic classes. This is particularly useful for real-time applications such as voice and other delay-sensitive traffic. During congestion, packets in the priority queue receive preferential service, helping reduce latency and jitter. CBWFQ provides bandwidth-based scheduling for classes but does not inherently provide the same strict priority treatment. WRED manages congestion through selective packet dropping, while shaping controls the transmission rate. Therefore, LLQ is the correct QoS mechanism for strict priority service.<\/span><\/p>\n<h3><b>Question 199<\/b><\/h3>\n<p><b>Which multicast routing protocol is commonly used to build multicast distribution trees independently of the underlying unicast routing protocol?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PIM<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LACP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">LDP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">BFD<\/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;\">Protocol Independent Multicast (PIM) uses the existing unicast routing table for Reverse Path Forwarding decisions while providing multicast routing functionality. It is called protocol independent because it can operate with different underlying unicast routing protocols, such as OSPF, IS-IS, or BGP. PIM has multiple operating modes, including Sparse Mode and Source-Specific Multicast. LACP provides link aggregation, LDP distributes MPLS labels, and BFD provides rapid failure detection. Therefore, PIM is the correct multicast routing protocol in this scenario.<\/span><\/p>\n<h3><b>Question 200<\/b><\/h3>\n<p><b>Which multicast feature allows a receiver to join a multicast stream for a specific source rather than using a shared Rendezvous Point tree?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">PIM-DM<\/span><\/li>\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<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<h3><b>Explanation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Source-Specific Multicast (SSM) allows receivers to request multicast traffic from a specific source and multicast group. This creates a source-specific channel and eliminates the need for a traditional shared-tree Rendezvous Point architecture for the multicast flow. SSM is commonly associated with IGMPv3 for IPv4 and MLDv2 for IPv6 receiver signaling. Anycast-RP provides redundant Rendezvous Points, MSDP exchanges multicast source information, and PIM-DM uses dense-mode forwarding behavior. Therefore, SSM is the correct multicast feature for source-specific stream selection.<\/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 181 Which OSPF LSA type is originated by an ABR to describe networks within an area to other OSPF areas? Type 1 Type 2 Type 3 Type 5 Correct Answer: 3 Explanation OSPF Type 3 LSAs, also called Summary LSAs, [&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\/15319"}],"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=15319"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15319\/revisions"}],"predecessor-version":[{"id":15341,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/15319\/revisions\/15341"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=15319"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=15319"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=15319"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}