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 35

Question 340

A core network change board wants to avoid: 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. Which ongoing safeguard fits best?

  1. Contract-test route-target separation before onboarding a new tenant EVI.
  2. Track provider tree membership and packet replication under subscriber growth.
  3. Include both IGMP and MLD listener tests on dual-stack access nodes.
  4. Document the selected inter-AS option and verify service labels at each boundary.

Explanation

Correct Answer

D:

Document the selected inter-AS option and verify service labels at each boundary. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.

Incorrect Answers

A:

Contract-test route-target separation before onboarding a new tenant EVI. That is a sensible control for ANOTHER scenario: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. It is less targeted to this issue than: Document the selected inter-AS option and verify service labels at each boundary.

B:

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: Document the selected inter-AS option and verify service labels at each boundary.

C:

Include both IGMP and MLD listener tests on dual-stack access nodes. That is a sensible control for ANOTHER scenario: An IPv6 multicast receiver joins an MLDv2 group, but the adjacent router polls only IGMP state and reports no listeners. It is less targeted to this issue than: Document the selected inter-AS option and verify service labels at each boundary.

Question 341

A carrier service activation check discovers: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. Which action best restores the intended behavior?

  1. Correct the CFM maintenance domain, association and MEP identifiers for the intended service.
  2. Preserve or explicitly translate the customer C-tag and provider S-tag according to the agreed QinQ demarcation.
  3. Restore the intended ERP blocking and ring protection state with verified RPL ownership.
  4. Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification.

Explanation

Correct Answer

B:

Preserve or explicitly translate the customer C-tag and provider S-tag according to the agreed QinQ demarcation. This directly addresses the fictional service-provider network case: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. The technical mechanism is: IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure. Verify success by: A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact.

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 wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances.

C:

Restore the intended ERP blocking and ring protection state with verified RPL ownership. This would respond to a DIFFERENT fictional service-provider network issue: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring. It does not directly address the current situation: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances.

D:

Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification. This would respond to a DIFFERENT fictional service-provider network issue: Two sites use identical DSCP values but only one interface applies a queue scheduler, and the team assumes packet marking alone guarantees bandwidth on both links. It does not directly address the current situation: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances.

Question 342

Following a supported configuration correction, the original issue was: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. Which observation verifies success?

  1. The lab ring carries permitted traffic with one logical blocked segment and reconverges when a ring link fails.
  2. A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers.
  3. A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact.
  4. Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective.

Explanation

Correct Answer

C:

A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact. This confirms the approved response: Preserve or explicitly translate the customer C-tag and provider S-tag according to the agreed QinQ demarcation. It is relevant because: IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure.

Incorrect Answers

A:

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: Preserve or explicitly translate the customer C-tag and provider S-tag according to the agreed QinQ demarcation.

B:

A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers. This would validate ANOTHER 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 specific correction here is: Preserve or explicitly translate the customer C-tag and provider S-tag according to the agreed QinQ demarcation.

D:

Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective. This would validate ANOTHER scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. The specific correction here is: Preserve or explicitly translate the customer C-tag and provider S-tag according to the agreed QinQ demarcation.

Question 343

At a wholesale transit provider, an engineer examines: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. Which technical principle is most applicable?

  1. E-Access targets Ethernet wholesale access connectivity with defined service demarcation and operator interfaces.
  2. Ethernet CFM operates within defined maintenance levels and identities to monitor continuity for particular services.
  3. QoS benefits depend on consistent classification, marking and queue treatment across the full path.
  4. IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure.

Explanation

Correct Answer

D:

IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure. This explains the investigated issue: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. The approved corrective response is: Preserve or explicitly translate the customer C-tag and provider S-tag according to the agreed QinQ demarcation.

Incorrect Answers

A:

E-Access targets Ethernet wholesale access connectivity with defined service demarcation and operator interfaces. That explains a DIFFERENT scenario: An E-Access wholesale demarcation connects one retail provider UNI to a distant operator UNI, but the order is provisioned as an open multipoint LAN across all sites. The mechanism to prioritize for this question is: IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure.

B:

Ethernet CFM operates within defined maintenance levels and identities to monitor continuity for particular services. That explains a DIFFERENT scenario: An Ethernet OAM continuity check reports an unexpected remote maintenance endpoint and operators trust the wrong circuit when troubleshooting an outage. The mechanism to prioritize for this question is: IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure.

C:

QoS benefits depend on consistent classification, marking and queue treatment across the full path. That explains a DIFFERENT scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. The mechanism to prioritize for this question is: IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure.

Question 344

For a wholesale transit provider, the change record describes: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. What preventive validation should be standard?

  1. Verify tag stacking and pop/push symmetry at access handoffs.
  2. Confirm product connectivity type against the customer's topology before activating the EVC.
  3. Reconcile order type, UNI and ENNI mapping during circuit handover.
  4. Require overlapping-address negative tests before new VPN attachments.

Explanation

Correct Answer

A:

Verify tag stacking and pop/push symmetry at access handoffs. This helps prevent recurrence of the issue: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. Acceptance evidence should be: A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact.

Incorrect Answers

B:

Confirm product connectivity type against the customer's topology before activating the EVC. That is a sensible control for ANOTHER scenario: 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. It is less targeted to this issue than: Verify tag stacking and pop/push symmetry at access handoffs.

C:

Reconcile order type, UNI and ENNI mapping during circuit handover. That is a sensible control for ANOTHER scenario: An E-Access wholesale demarcation connects one retail provider UNI to a distant operator UNI, but the order is provisioned as an open multipoint LAN across all sites. It is less targeted to this issue than: Verify tag stacking and pop/push symmetry at access handoffs.

D:

Require overlapping-address negative tests before new VPN attachments. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Verify tag stacking and pop/push symmetry at access handoffs.

Question 345

For a multi-region fiber backbone operator, the failure is: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. Which authorized correction best addresses it?

  1. Assign service-specific route targets and restrict import policy to the approved tenant set.
  2. Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.
  3. Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies.
  4. Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF.

Explanation

Correct Answer

C:

Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies. This directly addresses the fictional service-provider network case: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. The technical mechanism is: L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables. Verify success by: Customers reach the approved DNS endpoint but cross-customer reachability tests fail.

Incorrect Answers

A:

Assign service-specific route targets and restrict import policy to the approved tenant set. This would respond to a DIFFERENT fictional service-provider network issue: A provider advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally. It does not directly address the current situation: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity.

B:

Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity.

D:

Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity.

Question 346

After fixing the following network problem, what should the team verify: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity.

  1. Remote VRF shows the expected VPNv4 prefix and matching label while unintended VRFs remain empty.
  2. Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated.
  3. A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy.
  4. Customers reach the approved DNS endpoint but cross-customer reachability tests fail.

Explanation

Correct Answer

D:

Customers reach the approved DNS endpoint but cross-customer reachability tests fail. This confirms the approved response: Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies. It is relevant because: L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables.

Incorrect Answers

A:

Remote VRF shows the expected VPNv4 prefix and matching label while unintended VRFs remain empty. This would validate ANOTHER scenario: A customer L3VPN site is connected on a PE but the far-end VRF lacks a route because the local RD is copied from another tenant and the configured RT imports are missing. The specific correction here is: Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies.

B:

Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated. This would validate ANOTHER scenario: A provider advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally. The specific correction here is: Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies.

C:

A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy. This would validate ANOTHER scenario: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. The specific correction here is: Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies.

Question 347

A carrier root-cause review considers: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. What underlying mechanism explains this?

  1. L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables.
  2. A route distinguisher disambiguates overlapping VPN routes, whereas route targets govern VRF import policy.
  3. L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.
  4. Multicast VPN services can map customer multicast groups onto scalable provider distribution trees rather than per-receiver unicast copies.

Explanation

Correct Answer

A:

L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables. This explains the investigated issue: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. The approved corrective response is: Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies.

Incorrect Answers

B:

A route distinguisher disambiguates overlapping VPN routes, whereas route targets govern VRF import policy. That explains a DIFFERENT scenario: A customer L3VPN site is connected on a PE but the far-end VRF lacks a route because the local RD is copied from another tenant and the configured RT imports are missing. The mechanism to prioritize for this question is: L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables.

C:

L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels. That explains a DIFFERENT scenario: A customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost. The mechanism to prioritize for this question is: L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables.

D:

Multicast VPN services can map customer multicast groups onto scalable provider distribution trees rather than per-receiver unicast copies. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables.

Question 348

After addressing: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. Which recurring service assurance check is most useful?

  1. Require overlapping-address negative tests before new VPN attachments.
  2. Audit bidirectional prefix scope and service ACLs on extranet changes.
  3. Inspect per-VRF service-label mapping after platform or route-policy changes.
  4. Monitor RP reachability and failover under multicast service SLAs.

Explanation

Correct Answer

B:

Audit bidirectional prefix scope and service ACLs on extranet changes. This helps prevent recurrence of the issue: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. Acceptance evidence should be: Customers reach the approved DNS endpoint but cross-customer reachability tests fail.

Incorrect Answers

A:

Require overlapping-address negative tests before new VPN attachments. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Audit bidirectional prefix scope and service ACLs on extranet changes.

C:

Inspect per-VRF service-label mapping after platform or route-policy changes. That is a sensible control for ANOTHER scenario: An L3VPN PE advertises a VPNv4 route but the egress fails to associate the received VPN label with the correct customer VRF, causing the route to appear in the wrong context. It is less targeted to this issue than: Audit bidirectional prefix scope and service ACLs on extranet changes.

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: Audit bidirectional prefix scope and service ACLs on extranet changes.

Question 349

A provider backbone escalation identifies: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. What should the network team implement?

  1. Restore consistent PIM interface settings and designated-router election visibility on the access segment.
  2. Inspect and configure MLD listener state for IPv6 independently from IPv4 IGMP.
  3. Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.
  4. Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.

Explanation

Correct Answer

D:

Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain. This directly addresses the fictional service-provider network case: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. The technical mechanism is: Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration. Verify success by: Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding.

Incorrect Answers

A:

Restore consistent PIM interface settings and designated-router election visibility on the access segment. This would respond to a DIFFERENT fictional service-provider network issue: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. It does not directly address the current situation: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication.

B:

Inspect and configure MLD listener state for IPv6 independently from IPv4 IGMP. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 multicast receiver joins an MLDv2 group, but the adjacent router polls only IGMP state and reports no listeners. It does not directly address the current situation: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication.

C:

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 bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication.

Question 350

A service-provider operations test targets: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. Which result is required?

  1. Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding.
  2. PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery.
  3. One intended DR is elected and the shared LAN emits the expected controlled PIM behavior.
  4. Tagged frame tests map each subscriber VLAN to the intended service and restore the expected egress tag.

Explanation

Correct Answer

A:

Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding. This confirms the approved response: Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain. It is relevant because: Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration.

Incorrect Answers

B:

PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery. This would validate ANOTHER scenario: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. The specific correction here is: Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.

C:

One intended DR is elected and the shared LAN emits the expected controlled PIM behavior. This would validate ANOTHER scenario: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. The specific correction here is: Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.

D:

Tagged frame tests map each subscriber VLAN to the intended service and restore the expected egress tag. This would validate 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. The specific correction here is: Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.