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 74

Question 730

After fixing the following network problem, what should the team verify: 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.

  1. A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.
  2. A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable.
  3. A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format.
  4. A remote MAC route resolves to the correct border and service encapsulation and transmits a unicast frame.

Explanation

Correct Answer

D:

A remote MAC route resolves to the correct border and service encapsulation and transmits a unicast frame. This confirms the approved response: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility. It is relevant because: EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints.

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: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.

B:

A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable. This would validate 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. The specific correction here is: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.

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: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.

Question 731

A carrier root-cause review considers: 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. What underlying mechanism explains this?

  1. EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints.
  2. EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability.
  3. Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.
  4. Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures.

Explanation

Correct Answer

A:

EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints. This explains the investigated 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. The approved corrective response is: Align border-gateway EVPN route exchange, next-hop reachability and tunnel encapsulation compatibility.

Incorrect Answers

B:

EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability. That explains a DIFFERENT scenario: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. The mechanism to prioritize for this question is: EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints.

C:

Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border. That explains a DIFFERENT 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 mechanism to prioritize for this question is: EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints.

D:

Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures. That explains a DIFFERENT 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 mechanism to prioritize for this question is: EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints.

Question 732

After addressing: 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. Which recurring service assurance check is most useful?

  1. Run controlled host-movement tests after EVPN control-plane upgrades.
  2. Check EVPN route and tunnel resolution independently in inter-AS tests.
  3. Contract-test route-target separation before onboarding a new tenant EVI.
  4. Maintain separate PIM-SM and PIM-BIDIR group-range policies.

Explanation

Correct Answer

B:

Check EVPN route and tunnel resolution independently in inter-AS tests. This helps prevent recurrence of the 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. Acceptance evidence should be: A remote MAC route resolves to the correct border and service encapsulation and transmits a unicast frame.

Incorrect Answers

A:

Run controlled host-movement tests after EVPN control-plane upgrades. That is a sensible control for ANOTHER scenario: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. It is less targeted to this issue than: Check EVPN route and tunnel resolution independently in inter-AS tests.

C:

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: Check EVPN route and tunnel resolution independently in inter-AS tests.

D:

Maintain separate PIM-SM and PIM-BIDIR group-range policies. That is a sensible control for ANOTHER scenario: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. It is less targeted to this issue than: Check EVPN route and tunnel resolution independently in inter-AS tests.

Question 733

A provider backbone escalation identifies: 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. What should the network team implement?

  1. Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.
  2. Match the supported pseudowire encapsulation and control-word expectations at both endpoints.
  3. Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.
  4. Terminate the provider backbone encapsulation at the correct I-component/B-component service edge.

Explanation

Correct Answer

D:

Terminate the provider backbone encapsulation at the correct I-component/B-component service edge. This directly addresses the fictional service-provider network case: 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 technical mechanism is: IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation. Verify success by: A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers.

Incorrect Answers

A:

Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points. This would respond to a DIFFERENT fictional service-provider network issue: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. It does not directly address the current situation: 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.

B:

Match the supported pseudowire encapsulation and control-word expectations at both endpoints. This would respond to a DIFFERENT fictional service-provider network issue: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. It does not directly address the current situation: 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.

C:

Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

Question 734

A service-provider operations test targets: 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. Which result is required?

  1. A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers.
  2. Three permitted UNI sites exchange expected Ethernet frames without a full mesh of unrelated dedicated circuits.
  3. Only the contracted retail access endpoints exchange frames while unrelated handoffs stay isolated.
  4. Remote VRF shows the expected VPNv4 prefix and matching label while unintended VRFs remain empty.

Explanation

Correct Answer

A:

A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers. This confirms the approved response: Terminate the provider backbone encapsulation at the correct I-component/B-component service edge. It is relevant because: IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation.

Incorrect Answers

B:

Three permitted UNI sites exchange expected Ethernet frames without a full mesh of unrelated dedicated circuits. This would validate 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. The specific correction here is: Terminate the provider backbone encapsulation at the correct I-component/B-component service edge.

C:

Only the contracted retail access endpoints exchange frames while unrelated handoffs stay isolated. This would validate 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. The specific correction here is: Terminate the provider backbone encapsulation at the correct I-component/B-component service edge.

D:

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: Terminate the provider backbone encapsulation at the correct I-component/B-component service edge.

Question 735

A provider troubleshooting note states: 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. Which mechanism is central?

  1. IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure.
  2. IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation.
  3. Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures.
  4. Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.

Explanation

Correct Answer

B:

IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation. This explains the investigated 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. The approved corrective response is: Terminate the provider backbone encapsulation at the correct I-component/B-component service edge.

Incorrect Answers

A:

IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation.

C:

Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures. That explains a DIFFERENT 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 mechanism to prioritize for this question is: IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation.

D:

Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks. That explains a DIFFERENT scenario: 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. The mechanism to prioritize for this question is: IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation.

Question 736

To prevent recurrence of this 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. Which control should be retained?

  1. Include leaf-to-leaf negative tests for every E-Tree subscriber change.
  2. Test pseudowire control-word and MTU settings before activation.
  3. Inspect header encapsulation at both service demarcations after provider bridge changes.
  4. Run controlled host-movement tests after EVPN control-plane upgrades.

Explanation

Correct Answer

C:

Inspect header encapsulation at both service demarcations after provider bridge changes. This helps prevent recurrence of the 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. Acceptance evidence should be: A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers.

Incorrect Answers

A:

Include leaf-to-leaf negative tests for every E-Tree subscriber change. That is a sensible control for 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. It is less targeted to this issue than: Inspect header encapsulation at both service demarcations after provider bridge changes.

B:

Test pseudowire control-word and MTU settings before activation. That is a sensible control for 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. It is less targeted to this issue than: Inspect header encapsulation at both service demarcations after provider bridge changes.

D:

Run controlled host-movement tests after EVPN control-plane upgrades. That is a sensible control for ANOTHER scenario: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. It is less targeted to this issue than: Inspect header encapsulation at both service demarcations after provider bridge changes.

Question 737

At a multi-region fiber backbone operator, an engineering review finds: 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. Which change most directly corrects the service problem?

  1. Apply customer-specific BGP policy reflecting primary/backup preference and validate failure-state reroute.
  2. Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets.
  3. Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.
  4. Correct the CFM maintenance domain, association and MEP identifiers for the intended service.

Explanation

Correct Answer

A:

Apply customer-specific BGP policy reflecting primary/backup preference and validate failure-state reroute. This directly addresses the fictional service-provider network case: 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 technical mechanism is: L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels. Verify success by: Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss.

Incorrect Answers

B:

Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets. This would respond to a DIFFERENT fictional service-provider network issue: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. It does not directly address the current situation: 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.

C:

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 customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost.

D:

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 customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost.

Question 738

For a multi-region fiber backbone operator, operators addressed: 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. What is the strongest acceptance evidence?

  1. Customers reach the approved DNS endpoint but cross-customer reachability tests fail.
  2. Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss.
  3. A remote VRF installs the approved CE prefix and unrelated customer VRFs show no route change.
  4. Only the contracted retail access endpoints exchange frames while unrelated handoffs stay isolated.

Explanation

Correct Answer

B:

Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss. This confirms the approved response: Apply customer-specific BGP policy reflecting primary/backup preference and validate failure-state reroute. It is relevant because: L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.

Incorrect Answers

A:

Customers reach the approved DNS endpoint but cross-customer reachability tests fail. This would validate ANOTHER scenario: 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 specific correction here is: Apply customer-specific BGP policy reflecting primary/backup preference and validate failure-state reroute.

C:

A remote VRF installs the approved CE prefix and unrelated customer VRFs show no route change. This would validate ANOTHER scenario: A CE-PE BGP session successfully exchanges routes but a newly provisioned customer VRF has no route targets and none of its routes propagate to distant PEs. The specific correction here is: Apply customer-specific BGP policy reflecting primary/backup preference and validate failure-state reroute.

D:

Only the contracted retail access endpoints exchange frames while unrelated handoffs stay isolated. This would validate 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. The specific correction here is: Apply customer-specific BGP policy reflecting primary/backup preference and validate failure-state reroute.

Question 739

Which network protocol or forwarding behavior explains the following issue: 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.

  1. MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes.
  2. Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability.
  3. L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.
  4. EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint.

Explanation

Correct Answer

C:

L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels. This explains the investigated issue: 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 approved corrective response is: Apply customer-specific BGP policy reflecting primary/backup preference and validate failure-state reroute.

Incorrect Answers

A:

MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.

B:

Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability. That explains a DIFFERENT 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 mechanism to prioritize for this question is: L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.

D:

EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint. That explains a DIFFERENT scenario: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. The mechanism to prioritize for this question is: L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.

Question 740

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

  1. Inspect per-VRF service-label mapping after platform or route-policy changes.
  2. Require overlapping-address negative tests before new VPN attachments.
  3. Test DR state when changing multicast LAN interfaces.
  4. Retest primary and backup preference whenever CE prefixes change.

Explanation

Correct Answer

D:

Retest primary and backup preference whenever CE prefixes change. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss.

Incorrect Answers

A:

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: Retest primary and backup preference whenever CE prefixes change.

B:

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: Retest primary and backup preference whenever CE prefixes change.

C:

Test DR state when changing multicast LAN interfaces. That is a sensible control for 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. It is less targeted to this issue than: Retest primary and backup preference whenever CE prefixes change.