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 55

Question 540

After addressing: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. Which recurring service assurance check is most useful?

  1. Verify control-plane service route labels and locator reachability across interdomain handoffs.
  2. Monitor delegated LSP ownership and controller reachability.
  3. Keep segment-type validation with path computation requests.
  4. Include TE database completeness checks during IGP maintenance.

Explanation

Correct Answer

B:

Monitor delegated LSP ownership and controller reachability. This helps prevent recurrence of the issue: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. Acceptance evidence should be: The PCC installs only approved delegated candidates and reports their active state back to the PCE.

Incorrect Answers

A:

Verify control-plane service route labels and locator reachability across interdomain handoffs. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Monitor delegated LSP ownership and controller reachability.

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: Monitor delegated LSP ownership and controller reachability.

D:

Include TE database completeness checks during IGP maintenance. That is a sensible control for ANOTHER scenario: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. It is less targeted to this issue than: Monitor delegated LSP ownership and controller reachability.

Question 541

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

  1. Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain.
  2. Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport.
  3. Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service.
  4. Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale.

Explanation

Correct Answer

D:

Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Multicast VPN services can map customer multicast groups onto scalable provider distribution trees rather than per-receiver unicast copies. Verify success by: An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree.

Incorrect Answers

A:

Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain. This would respond to a DIFFERENT fictional service-provider network issue: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. It does not directly address the current situation: 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.

B:

Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport. This would respond to a DIFFERENT fictional service-provider network issue: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. It does not directly address the current situation: 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.

C:

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 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.

Question 542

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

  1. An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree.
  2. A lab MAC route from tenant A does not enter tenant B's MAC-VRF while shared authorized services remain reachable.
  3. A host migration test updates the remote PE forwarding location without persistent duplicate MAC forwarding.
  4. Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss.

Explanation

Correct Answer

A:

An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree. This confirms the approved response: Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale. It is relevant because: Multicast VPN services can map customer multicast groups onto scalable provider distribution trees rather than per-receiver unicast copies.

Incorrect Answers

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: Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale.

C:

A host migration test updates the remote PE forwarding location without persistent duplicate MAC forwarding. This would validate ANOTHER scenario: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. The specific correction here is: Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale.

D:

Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss. This would validate ANOTHER 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 specific correction here is: Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale.

Question 543

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

  1. Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.
  2. Multicast VPN services can map customer multicast groups onto scalable provider distribution trees rather than per-receiver unicast copies.
  3. EVPN MAC mobility uses sequence information to resolve competing advertisements for a moving endpoint.
  4. IGMP controls IPv4 multicast listener membership, while MLD performs the analogous role for IPv6.

Explanation

Correct Answer

B:

Multicast VPN services can map customer multicast groups onto scalable provider distribution trees rather than per-receiver unicast copies. This explains the investigated issue: 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 approved corrective response is: Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale.

Incorrect Answers

A:

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: Multicast VPN services can map customer multicast groups onto scalable provider distribution trees rather than per-receiver unicast copies.

C:

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: Multicast VPN services can map customer multicast groups onto scalable provider distribution trees rather than per-receiver unicast copies.

D:

IGMP controls IPv4 multicast listener membership, while MLD performs the analogous role for IPv6. That explains a DIFFERENT scenario: An IPv6 multicast receiver joins an MLDv2 group, but the adjacent router polls only IGMP state and reports no listeners. The mechanism to prioritize for this question is: Multicast VPN services can map customer multicast groups onto scalable provider distribution trees rather than per-receiver unicast copies.

Question 544

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

  1. Run controlled host-movement tests after EVPN control-plane upgrades.
  2. Audit tenant RT policies for EVPN IP prefix advertisements.
  3. Track provider tree membership and packet replication under subscriber growth.
  4. Test queue fairness and priority traffic caps at oversubscription.

Explanation

Correct Answer

C:

Track provider tree membership and packet replication under subscriber growth. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree.

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: Track provider tree membership and packet replication under subscriber growth.

B:

Audit tenant RT policies for EVPN IP prefix advertisements. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Track provider tree membership and packet replication under subscriber growth.

D:

Test queue fairness and priority traffic caps at oversubscription. That is a sensible control for ANOTHER scenario: A high-volume backup class is placed in the same strict-priority queue as voice, starving the provider's control and ordinary traffic. It is less targeted to this issue than: Track provider tree membership and packet replication under subscriber growth.

Question 545

At a multi-tenant data transport provider, an engineering review finds: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring. Which change most directly corrects the service problem?

  1. Restore the intended ERP blocking and ring protection state with verified RPL ownership.
  2. Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff.
  3. Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit.
  4. Add explicitly authorized VPN RT export/import policy and ensure the MP-BGP VPN family is active between PEs.

Explanation

Correct Answer

A:

Restore the intended ERP blocking and ring protection state with verified RPL ownership. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures. Verify success by: The lab ring carries permitted traffic with one logical blocked segment and reconverges when a ring link fails.

Incorrect Answers

B:

Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring.

C:

Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring.

D:

Add explicitly authorized VPN RT export/import policy and ensure the MP-BGP VPN family is active between PEs. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring.

Question 546

For a multi-tenant data transport provider, operators addressed: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring. What is the strongest acceptance evidence?

  1. A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format.
  2. The lab ring carries permitted traffic with one logical blocked segment and reconverges when a ring link fails.
  3. Tagged frame tests map each subscriber VLAN to the intended service and restore the expected egress tag.
  4. An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree.

Explanation

Correct Answer

B:

The lab ring carries permitted traffic with one logical blocked segment and reconverges when a ring link fails. This confirms the approved response: Restore the intended ERP blocking and ring protection state with verified RPL ownership. It is relevant because: Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures.

Incorrect Answers

A:

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: Restore the intended ERP blocking and ring protection state with verified RPL ownership.

C:

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: Restore the intended ERP blocking and ring protection state with verified RPL ownership.

D:

An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree. This would validate 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. The specific correction here is: Restore the intended ERP blocking and ring protection state with verified RPL ownership.

Question 547

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

  1. IEEE 802.1ah separates backbone provider MAC addressing from customer MAC addressing through encapsulation.
  2. E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.
  3. Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures.
  4. L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables.

Explanation

Correct Answer

C:

Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures. This explains the investigated 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. The approved corrective response is: Restore the intended ERP blocking and ring protection state with verified RPL ownership.

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: Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures.

B:

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: Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures.

D:

L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Ethernet Ring Protection Switching prevents persistent L2 loops while enabling restoration after single link failures.

Question 548

A core network change board wants to avoid: A G.8032 Ethernet ring sees a broadcast storm after a ring protection link is accidentally forwarding on both sides of a stable ring. Which ongoing safeguard fits best?

  1. Validate VLAN rewrite rules bidirectionally with representative tags.
  2. Verify tag stacking and pop/push symmetry at access handoffs.
  3. Audit bidirectional prefix scope and service ACLs on extranet changes.
  4. Review RPL ownership and ring state during ring expansion.

Explanation

Correct Answer

D:

Review RPL ownership and ring state during ring expansion. This helps prevent recurrence of the 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. Acceptance evidence should be: The lab ring carries permitted traffic with one logical blocked segment and reconverges when a ring link fails.

Incorrect Answers

A:

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: Review RPL ownership and ring state during ring expansion.

B:

Verify tag stacking and pop/push symmetry at access handoffs. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Review RPL ownership and ring state during ring expansion.

C:

Audit bidirectional prefix scope and service ACLs on extranet changes. That is a sensible control for 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. It is less targeted to this issue than: Review RPL ownership and ring state during ring expansion.

Question 549

A carrier service activation check discovers: 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. Which action best restores the intended behavior?

  1. Check RD uniqueness for VPNv4 route identity and configure the intended import/export route targets for reachability.
  2. Correct the VPN service label allocation and VRF binding on the egress PE.
  3. Provide the contracted return routing or NAT path for the shared Internet access design while preserving tenant isolation.
  4. Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.

Explanation

Correct Answer

B:

Correct the VPN service label allocation and VRF binding on the egress PE. This directly addresses the fictional service-provider network case: 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. The technical mechanism is: MPLS VPN service labels identify the egress service context separately from outer backbone transport labels. Verify success by: Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding.

Incorrect Answers

A:

Check RD uniqueness for VPNv4 route identity and configure the intended import/export route targets for reachability. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: 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.

C:

Provide the contracted return routing or NAT path for the shared Internet access design while preserving tenant isolation. This would respond to a DIFFERENT fictional service-provider network issue: A remote customer site can send packets toward the Internet exit in a shared services VRF but the exit has no return route for the private customer prefix. It does not directly address the current situation: 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.

D:

Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class. This would respond to a DIFFERENT fictional service-provider network issue: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. It does not directly address the current situation: 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.

Question 550

Following a supported configuration correction, the original issue was: 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. Which observation verifies success?

  1. A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes.
  2. An approved Internet test flow completes both directions without exposing other tenants' internal networks.
  3. Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding.
  4. The source stream arrives over the expected incoming interface and the RPF check passes.

Explanation

Correct Answer

C:

Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding. This confirms the approved response: Correct the VPN service label allocation and VRF binding on the egress PE. It is relevant because: MPLS VPN service labels identify the egress service context separately from outer backbone transport labels.

Incorrect Answers

A:

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: Correct the VPN service label allocation and VRF binding on the egress PE.

B:

An approved Internet test flow completes both directions without exposing other tenants' internal networks. This would validate ANOTHER scenario: A remote customer site can send packets toward the Internet exit in a shared services VRF but the exit has no return route for the private customer prefix. The specific correction here is: Correct the VPN service label allocation and VRF binding on the egress PE.

D:

The source stream arrives over the expected incoming interface and the RPF check passes. This would validate ANOTHER scenario: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure. The specific correction here is: Correct the VPN service label allocation and VRF binding on the egress PE.