McAfee Secure

Cisco 350-501 Bundle

Exam Code: 350-501

Exam Name Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR)

Certification Provider: Cisco

Corresponding Certifications: CCIE Service Provider , CCNP Service Provider

Cisco 350-501 Bundle $28.79

100% Cisco 350-501 Guaranteed Success With Testking Training Materials

Get Real 350-501 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    350-501 Questions & Answers

    528 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual 350-501 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • 350-501 Video Course

    350-501 Training Course

    253 Video Lectures

    350-501 Video Course is developed by Cisco Professionals to help you pass the 350-501 exam.

    Description

    This course will improve your knowledge and skills required to pass Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) exam.
  • Study Guide

    350-501 Study Guide

    1160 PDF Pages

    Developed by industry experts, this 1160-page guide spells out in painstaking detail all of the information you need to ace 350-501 exam.

Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) (350-501) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $189.97
Bundle Price: $161.18

Purchase Individually

  • Questions & Answers

    Questions & Answers

    528 Questions

    $124.99
  • 350-501 Video Course

    Training Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 47

Question 460

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: Two provider data centers must extend selected customer Ethernet segments but cannot risk uncontrolled MAC flooding across the entire backbone. Which continuing control best reduces recurrence of this problem?

  1. Audit customer edge marking behavior when service contracts change.
  2. Validate every UNI and EVC membership during order fulfillment.
  3. Monitor RP availability and group-to-RP mapping consistency.
  4. Monitor MAC mobility and route-target imports after adding remote sites.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: Two provider data centers must extend selected customer Ethernet segments but cannot risk uncontrolled MAC flooding across the entire backbone. The most directly supported response is: Design EVPN control-plane advertisement with tenant-specific bridge domains and approved MAC reachability. Technical basis: EVPN distributes Ethernet reachability through BGP control-plane information and service-specific isolation. Evidence of success: Remote PEs learn eligible customer MAC reachability using EVPN routes without unrelated tenant flooding. Ongoing protection: Monitor MAC mobility and route-target imports after adding remote sites.

Incorrect Answers

A:

The alternative guards against: Carrier MPLS EXP/TC treatment must follow approved classification rather than arbitrary customer marking. The root condition for this case is: EVPN distributes Ethernet reachability through BGP control-plane information and service-specific isolation. The focused prevention check is: Monitor MAC mobility and route-target imports after adding remote sites.

B:

The alternative guards against: E-Line services are point-to-point Carrier Ethernet constructs rather than arbitrary LAN segments. The root condition for this case is: EVPN distributes Ethernet reachability through BGP control-plane information and service-specific isolation. The focused prevention check is: Monitor MAC mobility and route-target imports after adding remote sites.

C:

The alternative guards against: PIM-SM initially uses rendezvous-point mechanisms to discover multicast sources for group trees. The root condition for this case is: EVPN distributes Ethernet reachability through BGP control-plane information and service-specific isolation. The focused prevention check is: Monitor MAC mobility and route-target imports after adding remote sites.

Question 461

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A customer VPN must connect branches across two autonomous system providers while the operators disagree on label and route exchange boundaries. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Configure supported ITU-T G.8032 Ethernet Ring Protection with the intended blocked ring link.
  2. Choose a supported inter-AS VPN option and define the VPNv4/IPv4 or labeled route exchange required at the AS boundary.
  3. Align route-target imports with approved VPN membership rather than modifying the globally unique RD.
  4. Configure congestion avoidance or queue management appropriate to the best-effort class without starving reserved traffic.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A customer VPN must connect branches across two autonomous system providers while the operators disagree on label and route exchange boundaries. The most directly supported response is: Choose a supported inter-AS VPN option and define the VPNv4/IPv4 or labeled route exchange required at the AS boundary. Technical basis: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. Evidence of success: Approved customer VPN prefixes reach both sides through the engineered inter-AS path without unrelated tenant import. Ongoing protection: Test cross-AS failures, route filtering, and VPN label reachability under the chosen option.

Incorrect Answers

A:

The option fits a control for: G.8032 coordinates ring protection switching to maintain connectivity while preventing Ethernet loops. The present failure is caused by a different mechanism: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. The targeted implementation is: Choose a supported inter-AS VPN option and define the VPNv4/IPv4 or labeled route exchange required at the AS boundary.

C:

RDs distinguish VPN NLRI, whereas RTs express which VRFs should import routes. That principle governs the alternative intervention. The issue described here is different: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. The case-matched corrective action is: Choose a supported inter-AS VPN option and define the VPNv4/IPv4 or labeled route exchange required at the AS boundary.

D:

Congestion avoidance manages buffer occupancy and early drops, distinct from ingress classification. That principle governs the alternative intervention. The issue described here is different: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. The case-matched corrective action is: Choose a supported inter-AS VPN option and define the VPNv4/IPv4 or labeled route exchange required at the AS boundary.

Question 462

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A customer VPN must connect branches across two autonomous system providers while the operators disagree on label and route exchange boundaries. Which observable result most directly verifies that this network issue was resolved?

  1. Continuity-check and link-trace results isolate the failing Ethernet service segment.
  2. Egress traffic stays within the contractual aggregate rate while child classes maintain priorities.
  3. The access router records IPv6 multicast listener state and forwards selected groups.
  4. Approved customer VPN prefixes reach both sides through the engineered inter-AS path without unrelated tenant import.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A customer VPN must connect branches across two autonomous system providers while the operators disagree on label and route exchange boundaries. The most directly supported response is: Choose a supported inter-AS VPN option and define the VPNv4/IPv4 or labeled route exchange required at the AS boundary. Technical basis: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. Evidence of success: Approved customer VPN prefixes reach both sides through the engineered inter-AS path without unrelated tenant import. Ongoing protection: Test cross-AS failures, route filtering, and VPN label reachability under the chosen option.

Incorrect Answers

A:

The proposed test would be relevant to: Ethernet OAM can measure service connectivity independently of customer Layer 3 routing. The reported problem follows from: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. Instead, verify: Approved customer VPN prefixes reach both sides through the engineered inter-AS path without unrelated tenant import.

B:

That observation tests a different mechanism: Hierarchical QoS can combine aggregate shaping with per-class scheduling for shared access links. It cannot establish this case, whose mechanism is: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. The needed verification is: Approved customer VPN prefixes reach both sides through the engineered inter-AS path without unrelated tenant import.

C:

That observation tests a different mechanism: MLD manages IPv6 multicast listener subscriptions, playing a role analogous to IGMP for IPv4. It cannot establish this case, whose mechanism is: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. The needed verification is: Approved customer VPN prefixes reach both sides through the engineered inter-AS path without unrelated tenant import.

Question 463

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A customer VPN must connect branches across two autonomous system providers while the operators disagree on label and route exchange boundaries. Which underlying network infrastructure principle best explains the situation?

  1. Source-Specific Multicast explicitly binds receivers to a source and group, typically avoiding RP-based discovery.
  2. Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains.
  3. Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation.
  4. Hierarchical QoS can combine aggregate shaping with per-class scheduling for shared access links.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A customer VPN must connect branches across two autonomous system providers while the operators disagree on label and route exchange boundaries. The most directly supported response is: Choose a supported inter-AS VPN option and define the VPNv4/IPv4 or labeled route exchange required at the AS boundary. Technical basis: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. Evidence of success: Approved customer VPN prefixes reach both sides through the engineered inter-AS path without unrelated tenant import. Ongoing protection: Test cross-AS failures, route filtering, and VPN label reachability under the chosen option.

Incorrect Answers

A:

The alternative principle describes: Source-Specific Multicast explicitly binds receivers to a source and group, typically avoiding RP-based discovery. In this question, the decisive mechanism is: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. These are distinct technical causes, even when they share a platform.

C:

The alternative principle describes: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. In this question, the decisive mechanism is: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. These are distinct technical causes, even when they share a platform.

D:

The alternative principle describes: Hierarchical QoS can combine aggregate shaping with per-class scheduling for shared access links. In this question, the decisive mechanism is: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. These are distinct technical causes, even when they share a platform.

Question 464

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A customer VPN must connect branches across two autonomous system providers while the operators disagree on label and route exchange boundaries. Which continuing control best reduces recurrence of this problem?

  1. Audit customer edge marking behavior when service contracts change.
  2. Audit per-VRF RT tables against the customer service registry.
  3. Validate IGMPv3 or MLDv2 source filtering at access edges.
  4. Test cross-AS failures, route filtering, and VPN label reachability under the chosen option.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A customer VPN must connect branches across two autonomous system providers while the operators disagree on label and route exchange boundaries. The most directly supported response is: Choose a supported inter-AS VPN option and define the VPNv4/IPv4 or labeled route exchange required at the AS boundary. Technical basis: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. Evidence of success: Approved customer VPN prefixes reach both sides through the engineered inter-AS path without unrelated tenant import. Ongoing protection: Test cross-AS failures, route filtering, and VPN label reachability under the chosen option.

Incorrect Answers

A:

That recurring practice manages a separate exposure: Carrier MPLS EXP/TC treatment must follow approved classification rather than arbitrary customer marking. The present case instead depends on: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. The suitable ongoing safeguard is: Test cross-AS failures, route filtering, and VPN label reachability under the chosen option.

B:

That recurring practice manages a separate exposure: L3VPN membership is controlled by route targets rather than IP prefix uniqueness alone. The present case instead depends on: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. The suitable ongoing safeguard is: Test cross-AS failures, route filtering, and VPN label reachability under the chosen option.

C:

That recurring practice manages a separate exposure: Source-Specific Multicast explicitly binds receivers to a source and group, typically avoiding RP-based discovery. The present case instead depends on: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. The suitable ongoing safeguard is: Test cross-AS failures, route filtering, and VPN label reachability under the chosen option.

Question 465

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A wholesale provider must carry a downstream carrier's VPN traffic without learning every downstream customer route in its global table. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Use a carrier-supporting-carrier VPN architecture with isolated downstream carrier reachability.
  2. Align route-target imports with approved VPN membership rather than modifying the globally unique RD.
  3. Use PIM-SSM with an appropriate source-specific membership protocol.
  4. Apply ingress remarking and a carrier-controlled MPLS class mapping at the trust boundary.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A wholesale provider must carry a downstream carrier's VPN traffic without learning every downstream customer route in its global table. The most directly supported response is: Use a carrier-supporting-carrier VPN architecture with isolated downstream carrier reachability. Technical basis: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. Evidence of success: Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated. Ongoing protection: Validate route-target separation and transport label continuity at interprovider handoffs.

Incorrect Answers

B:

RDs distinguish VPN NLRI, whereas RTs express which VRFs should import routes. That principle governs the alternative intervention. The issue described here is different: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. The case-matched corrective action is: Use a carrier-supporting-carrier VPN architecture with isolated downstream carrier reachability.

C:

The proposed option addresses this separate mechanism: Source-Specific Multicast explicitly binds receivers to a source and group, typically avoiding RP-based discovery. The stated problem instead depends on: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. The required response is: Use a carrier-supporting-carrier VPN architecture with isolated downstream carrier reachability.

D:

The proposed option addresses this separate mechanism: Carrier MPLS EXP/TC treatment must follow approved classification rather than arbitrary customer marking. The stated problem instead depends on: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. The required response is: Use a carrier-supporting-carrier VPN architecture with isolated downstream carrier reachability.

Question 466

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A wholesale provider must carry a downstream carrier's VPN traffic without learning every downstream customer route in its global table. Which observable result most directly verifies that this network issue was resolved?

  1. Participating sources and receivers use the intended bidirectional shared distribution structure.
  2. Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated.
  3. Frame capture confirms intended customer VLAN preservation and service-specific outer tag mapping.
  4. Under full load, traffic receives the planned queue share and premium latency stays within SLA.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A wholesale provider must carry a downstream carrier's VPN traffic without learning every downstream customer route in its global table. The most directly supported response is: Use a carrier-supporting-carrier VPN architecture with isolated downstream carrier reachability. Technical basis: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. Evidence of success: Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated. Ongoing protection: Validate route-target separation and transport label continuity at interprovider handoffs.

Incorrect Answers

A:

That observation tests a different mechanism: PIM-BIDIR supports a bidirectional shared-tree multicast model suited to appropriate many-to-many scenarios. It cannot establish this case, whose mechanism is: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. The needed verification is: Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated.

C:

VLAN tag manipulation determines which customer frames map to each Ethernet service. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. A passing check should show: Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated.

D:

Marking identifies classes; enforcement comes from queueing, shaping, and policer configuration. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. A passing check should show: Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated.

Question 467

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A wholesale provider must carry a downstream carrier's VPN traffic without learning every downstream customer route in its global table. Which underlying network infrastructure principle best explains the situation?

  1. Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing.
  2. Marking identifies classes; enforcement comes from queueing, shaping, and policer configuration.
  3. MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution.
  4. PIM-SM initially uses rendezvous-point mechanisms to discover multicast sources for group trees.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A wholesale provider must carry a downstream carrier's VPN traffic without learning every downstream customer route in its global table. The most directly supported response is: Use a carrier-supporting-carrier VPN architecture with isolated downstream carrier reachability. Technical basis: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. Evidence of success: Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated. Ongoing protection: Validate route-target separation and transport label continuity at interprovider handoffs.

Incorrect Answers

B:

Marking identifies classes; enforcement comes from queueing, shaping, and policer configuration. That is not the causal relationship tested by the current facts. The relevant principle is: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing.

C:

MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. That is not the causal relationship tested by the current facts. The relevant principle is: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing.

D:

PIM-SM initially uses rendezvous-point mechanisms to discover multicast sources for group trees. That is not the causal relationship tested by the current facts. The relevant principle is: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing.

Question 468

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A wholesale provider must carry a downstream carrier's VPN traffic without learning every downstream customer route in its global table. Which continuing control best reduces recurrence of this problem?

  1. Validate route-target separation and transport label continuity at interprovider handoffs.
  2. Keep RD and RT roles separate in configuration reviews.
  3. Monitor latency, loss and queue depth under representative demand.
  4. Regression-test tag rewriting for stacked and untagged traffic after configuration changes.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A wholesale provider must carry a downstream carrier's VPN traffic without learning every downstream customer route in its global table. The most directly supported response is: Use a carrier-supporting-carrier VPN architecture with isolated downstream carrier reachability. Technical basis: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. Evidence of success: Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated. Ongoing protection: Validate route-target separation and transport label continuity at interprovider handoffs.

Incorrect Answers

B:

RDs distinguish VPN NLRI, whereas RTs express which VRFs should import routes. Maintaining that control would not track the failure described here. The relevant risk is: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. Review this instead: Validate route-target separation and transport label continuity at interprovider handoffs.

C:

Congestion avoidance manages buffer occupancy and early drops, distinct from ingress classification. Maintaining that control would not track the failure described here. The relevant risk is: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. Review this instead: Validate route-target separation and transport label continuity at interprovider handoffs.

D:

The alternative guards against: VLAN tag manipulation determines which customer frames map to each Ethernet service. The root condition for this case is: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. The focused prevention check is: Validate route-target separation and transport label continuity at interprovider handoffs.

Question 469

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A video distribution provider uses a standard unicast L3VPN for multicast subscribers and finds no multicast state at the receiving PEs. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Use PIM-SSM with an appropriate source-specific membership protocol.
  2. Align route-target imports with approved VPN membership rather than modifying the globally unique RD.
  3. Select an appropriate E-LAN multipoint Ethernet service with approved bridge-domain isolation.
  4. Design supported multicast VPN service signaling and forwarding for the affected customer VRFs.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A video distribution provider uses a standard unicast L3VPN for multicast subscribers and finds no multicast state at the receiving PEs. The most directly supported response is: Design supported multicast VPN service signaling and forwarding for the affected customer VRFs. Technical basis: mVPN requires multicast-capable control and forwarding information beyond ordinary unicast VPN prefixes. Evidence of success: The receiving PEs show appropriate multicast VPN state and receive only authorized multicast groups. Ongoing protection: Test membership transitions and multicast replication scale across VPN PEs.

Incorrect Answers

A:

The proposed option addresses this separate mechanism: Source-Specific Multicast explicitly binds receivers to a source and group, typically avoiding RP-based discovery. The stated problem instead depends on: mVPN requires multicast-capable control and forwarding information beyond ordinary unicast VPN prefixes. The required response is: Design supported multicast VPN service signaling and forwarding for the affected customer VRFs.

B:

The proposed option addresses this separate mechanism: RDs distinguish VPN NLRI, whereas RTs express which VRFs should import routes. The stated problem instead depends on: mVPN requires multicast-capable control and forwarding information beyond ordinary unicast VPN prefixes. The required response is: Design supported multicast VPN service signaling and forwarding for the affected customer VRFs.

C:

The option fits a control for: E-LAN provides multipoint Ethernet membership whereas E-Line has two service endpoints. The present failure is caused by a different mechanism: mVPN requires multicast-capable control and forwarding information beyond ordinary unicast VPN prefixes. The targeted implementation is: Design supported multicast VPN service signaling and forwarding for the affected customer VRFs.

Question 470

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A video distribution provider uses a standard unicast L3VPN for multicast subscribers and finds no multicast state at the receiving PEs. Which observable result most directly verifies that this network issue was resolved?

  1. The access router reports permitted source and group memberships under the intended filter mode.
  2. The interoperator handoff carries only the agreed service VLANs and UNI attributes.
  3. The receiving PEs show appropriate multicast VPN state and receive only authorized multicast groups.
  4. Egress traffic stays within the contractual aggregate rate while child classes maintain priorities.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A video distribution provider uses a standard unicast L3VPN for multicast subscribers and finds no multicast state at the receiving PEs. The most directly supported response is: Design supported multicast VPN service signaling and forwarding for the affected customer VRFs. Technical basis: mVPN requires multicast-capable control and forwarding information beyond ordinary unicast VPN prefixes. Evidence of success: The receiving PEs show appropriate multicast VPN state and receive only authorized multicast groups. Ongoing protection: Test membership transitions and multicast replication scale across VPN PEs.

Incorrect Answers

A:

IGMPv3 extends group membership to source-specific reception; older IGMP versions differ. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: mVPN requires multicast-capable control and forwarding information beyond ordinary unicast VPN prefixes. A passing check should show: The receiving PEs show appropriate multicast VPN state and receive only authorized multicast groups.

B:

The proposed test would be relevant to: E-Access is intended for wholesale Ethernet access arrangements involving operator connectivity. The reported problem follows from: mVPN requires multicast-capable control and forwarding information beyond ordinary unicast VPN prefixes. Instead, verify: The receiving PEs show appropriate multicast VPN state and receive only authorized multicast groups.

D:

The proposed test would be relevant to: Hierarchical QoS can combine aggregate shaping with per-class scheduling for shared access links. The reported problem follows from: mVPN requires multicast-capable control and forwarding information beyond ordinary unicast VPN prefixes. Instead, verify: The receiving PEs show appropriate multicast VPN state and receive only authorized multicast groups.