McAfee-Secured Website

Exam 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 Video 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

    Video Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 8

Question 70

Following a supported configuration correction, the original issue was: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. Which observation verifies success?

  1. A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments.
  2. FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF.
  3. Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels.
  4. Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path.

Explanation

Correct Answer

C:

Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels. This confirms the approved response: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly. It is relevant because: Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.

Incorrect Answers

A:

A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments. This would validate ANOTHER scenario: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. The specific correction here is: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.

B:

FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF. This would validate ANOTHER scenario: A Segment Routing policy is installed but no customer route is steered to its binding SID, so measured traffic still follows ordinary IGP shortest paths. The specific correction here is: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.

D:

Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path. This would validate ANOTHER scenario: A router's MPLS TTL propagation policy differs from its neighboring core nodes, and traceroute unexpectedly exposes or hides provider hops relative to the service contract. The specific correction here is: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.

Question 71

At a metro Ethernet service provider, an engineer examines: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. Which technical principle is most applicable?

  1. Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.
  2. SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point.
  3. MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU.
  4. Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.

Explanation

Correct Answer

D:

Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values. This explains the investigated issue: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. The approved corrective response is: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.

Incorrect Answers

A:

Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding. That explains a DIFFERENT scenario: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. The mechanism to prioritize for this question is: Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.

B:

SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point. That explains a DIFFERENT scenario: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. The mechanism to prioritize for this question is: Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.

C:

MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU. That explains a DIFFERENT scenario: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. The mechanism to prioritize for this question is: Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.

Question 72

For a metro Ethernet service provider, the change record describes: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. What preventive validation should be standard?

  1. Validate SID index and SRGB advertisements during node onboarding.
  2. Monitor adjacency SID changes and invalidate stale policy segment lists.
  3. Keep segment-type validation with path computation requests.
  4. Validate explicit-route hops against TE capability data before committing.

Explanation

Correct Answer

A:

Validate SID index and SRGB advertisements during node onboarding. This helps prevent recurrence of the issue: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. Acceptance evidence should be: Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels.

Incorrect Answers

B:

Monitor adjacency SID changes and invalidate stale policy segment lists. That is a sensible control for ANOTHER scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. It is less targeted to this issue than: Validate SID index and SRGB advertisements during node onboarding.

C:

Keep segment-type validation with path computation requests. That is a sensible control for ANOTHER scenario: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. It is less targeted to this issue than: Validate SID index and SRGB advertisements during node onboarding.

D:

Validate explicit-route hops against TE capability data before committing. That is a sensible control for ANOTHER scenario: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. It is less targeted to this issue than: Validate SID index and SRGB advertisements during node onboarding.

Question 73

For a global tier-one IP transit carrier, the failure is: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. Which authorized correction best addresses it?

  1. Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.
  2. Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures.
  3. Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain.
  4. Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service.

Explanation

Correct Answer

C:

Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain. This directly addresses the fictional service-provider network case: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. The technical mechanism is: EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability. Verify success by: A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable.

Incorrect Answers

A:

Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility. This would respond to a DIFFERENT fictional service-provider network issue: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable. It does not directly address the current situation: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion.

B:

Validate EVPN MAC mobility extended communities and accept the newer sequence state under supported mobility procedures. This would respond to a DIFFERENT fictional service-provider network issue: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. It does not directly address the current situation: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion.

D:

Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service. This would respond to a DIFFERENT fictional service-provider network issue: Two customers use the same 10.10.0.0/16 prefix but a PE leaks VPNv4 routes into its global table, incorrectly merging their routing contexts. It does not directly address the current situation: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion.

Question 74

After fixing the following network problem, what should the team verify: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion.

  1. A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.
  2. Two test customers using the same group address receive only their own authorized source streams.
  3. The lab ring carries permitted traffic with one logical blocked segment and reconverges when a ring link fails.
  4. A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable.

Explanation

Correct Answer

D:

A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable. This confirms the approved response: Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain. It is relevant because: EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability.

Incorrect Answers

A:

A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes. This would validate ANOTHER scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. The specific correction here is: Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain.

B:

Two test customers using the same group address receive only their own authorized source streams. This would validate ANOTHER scenario: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. The specific correction here is: Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain.

C:

The lab ring carries permitted traffic with one logical blocked segment and reconverges when a ring link fails. This would validate ANOTHER scenario: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring. The specific correction here is: Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain.

Question 75

A carrier root-cause review considers: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. What underlying mechanism explains this?

  1. EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability.
  2. CSC designs carry another provider's traffic through a backbone without exposing all downstream customer routes into the carrier core.
  3. EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy.
  4. PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups.

Explanation

Correct Answer

A:

EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability. This explains the investigated issue: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. The approved corrective response is: Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain.

Incorrect Answers

B:

CSC designs carry another provider's traffic through a backbone without exposing all downstream customer routes into the carrier core. That explains a DIFFERENT scenario: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. The mechanism to prioritize for this question is: EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability.

C:

EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy. That explains a DIFFERENT scenario: A provider imports an EVPN Type-5 IP prefix into the wrong VRF because a route-target policy matches a customer label instead of the service's approved tenant RT. The mechanism to prioritize for this question is: EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability.

D:

PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups. That explains a DIFFERENT scenario: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. The mechanism to prioritize for this question is: EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability.

Question 76

After addressing: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. Which recurring service assurance check is most useful?

  1. Review route leaking and label transport boundaries for every wholesale peer.
  2. Contract-test route-target separation before onboarding a new tenant EVI.
  3. Document the selected inter-AS option and verify service labels at each boundary.
  4. Monitor RP reachability and failover under multicast service SLAs.

Explanation

Correct Answer

B:

Contract-test route-target separation before onboarding a new tenant EVI. This helps prevent recurrence of the issue: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. Acceptance evidence should be: A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable.

Incorrect Answers

A:

Review route leaking and label transport boundaries for every wholesale peer. That is a sensible control for ANOTHER scenario: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. It is less targeted to this issue than: Contract-test route-target separation before onboarding a new tenant EVI.

C:

Document the selected inter-AS option and verify service labels at each boundary. That is a sensible control for ANOTHER scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. It is less targeted to this issue than: Contract-test route-target separation before onboarding a new tenant EVI.

D:

Monitor RP reachability and failover under multicast service SLAs. That is a sensible control for ANOTHER scenario: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. It is less targeted to this issue than: Contract-test route-target separation before onboarding a new tenant EVI.

Question 77

A provider backbone escalation identifies: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service. What should the network team implement?

  1. Correct the CFM maintenance domain, association and MEP identifiers for the intended service.
  2. Terminate the provider backbone encapsulation at the correct I-component/B-component service edge.
  3. Correct multicast reverse-path reachability or the supported explicit RPF override consistent with topology.
  4. Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff.

Explanation

Correct Answer

D:

Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff. This directly addresses the fictional service-provider network case: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service. The technical mechanism is: E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints. Verify success by: Three permitted UNI sites exchange expected Ethernet frames without a full mesh of unrelated dedicated circuits.

Incorrect Answers

A:

Correct the CFM maintenance domain, association and MEP identifiers for the intended service. This would respond to a DIFFERENT fictional service-provider network issue: An Ethernet OAM continuity check reports an unexpected remote maintenance endpoint and operators trust the wrong circuit when troubleshooting an outage. It does not directly address the current situation: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service.

B:

Terminate the provider backbone encapsulation at the correct I-component/B-component service edge. This would respond to a DIFFERENT fictional service-provider network issue: A carrier backbone applies provider bridging with 802.1ah MAC-in-MAC but its edge fails to strip the outer backbone header, so customer switches receive unknown backbone addresses. It does not directly address the current situation: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service.

C:

Correct multicast reverse-path reachability or the supported explicit RPF override consistent with topology. This would respond to a DIFFERENT fictional service-provider network issue: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure. It does not directly address the current situation: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service.

Question 78

A service-provider operations test targets: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service. Which result is required?

  1. Three permitted UNI sites exchange expected Ethernet frames without a full mesh of unrelated dedicated circuits.
  2. Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked.
  3. A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format.
  4. A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes.

Explanation

Correct Answer

A:

Three permitted UNI sites exchange expected Ethernet frames without a full mesh of unrelated dedicated circuits. This confirms the approved response: Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff. It is relevant because: E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints.

Incorrect Answers

B:

Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked. This would validate ANOTHER scenario: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. The specific correction here is: Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff.

C:

A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format. This would validate ANOTHER scenario: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. The specific correction here is: Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff.

D:

A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes. This would validate ANOTHER scenario: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. The specific correction here is: Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff.

Question 79

A provider troubleshooting note states: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service. Which mechanism is central?

  1. IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation.
  2. E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints.
  3. E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.
  4. EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints.

Explanation

Correct Answer

B:

E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints. This explains the investigated issue: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service. The approved corrective response is: Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff.

Incorrect Answers

A:

IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation. That explains a DIFFERENT scenario: A carrier backbone applies provider bridging with 802.1ah MAC-in-MAC but its edge fails to strip the outer backbone header, so customer switches receive unknown backbone addresses. The mechanism to prioritize for this question is: E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints.

C:

E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability. That explains a DIFFERENT scenario: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. The mechanism to prioritize for this question is: E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints.

D:

EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints. That explains a DIFFERENT scenario: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable. The mechanism to prioritize for this question is: E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints.

Question 80

To prevent recurrence of this provider network issue: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service. Which control should be retained?

  1. Maintain service-specific CFM endpoint inventories and alarm tests.
  2. Validate VLAN rewrite rules bidirectionally with representative tags.
  3. Confirm product connectivity type against the customer's topology before activating the EVC.
  4. Track provider tree membership and packet replication under subscriber growth.

Explanation

Correct Answer

C:

Confirm product connectivity type against the customer's topology before activating the EVC. This helps prevent recurrence of the issue: A carrier provisions an E-LAN product using a point-to-point E-Line circuit, so a third branch cannot communicate with the others in the service. Acceptance evidence should be: Three permitted UNI sites exchange expected Ethernet frames without a full mesh of unrelated dedicated circuits.

Incorrect Answers

A:

Maintain service-specific CFM endpoint inventories and alarm tests. That is a sensible control for ANOTHER scenario: An Ethernet OAM continuity check reports an unexpected remote maintenance endpoint and operators trust the wrong circuit when troubleshooting an outage. It is less targeted to this issue than: Confirm product connectivity type against the customer's topology before activating the EVC.

B:

Validate VLAN rewrite rules bidirectionally with representative tags. That is a sensible control for ANOTHER scenario: A provider bridges a customer pseudowire into a service where the incoming access VLAN must be rewritten, but the PE maps the customer tag to an unrelated EVC. It is less targeted to this issue than: Confirm product connectivity type against the customer's topology before activating the EVC.

D:

Track provider tree membership and packet replication under subscriber growth. That is a sensible control for ANOTHER scenario: A provider deploys mVPN for an IPTV customer but replicates each source stream individually to every access PE even when a shared provider multicast tree is available. It is less targeted to this issue than: Confirm product connectivity type against the customer's topology before activating the EVC.