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 71

Question 700

After addressing: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. Which recurring service assurance check is most useful?

  1. Test locator route advertisement whenever new SRv6 functions are provisioned.
  2. Maintain validated micro-segment encoding templates per software release.
  3. Check SR policy candidate selection and actual prefix steering in acceptance.
  4. Test the exact failure class named in each protection service objective.

Explanation

Correct Answer

B:

Maintain validated micro-segment encoding templates per software release. This helps prevent recurrence of the issue: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. Acceptance evidence should be: A test packet advances through the micro-segment sequence and exits at the intended service SID.

Incorrect Answers

A:

Test locator route advertisement whenever new SRv6 functions are provisioned. That is a sensible control for ANOTHER scenario: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. It is less targeted to this issue than: Maintain validated micro-segment encoding templates per software release.

C:

Check SR policy candidate selection and actual prefix steering in acceptance. That is a sensible control for 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. It is less targeted to this issue than: Maintain validated micro-segment encoding templates per software release.

D:

Test the exact failure class named in each protection service objective. That is a sensible control for ANOTHER scenario: An MPLS TE bypass tunnel is administratively configured but the protected service shows no local protection because node protection was requested and only link protection is available. It is less targeted to this issue than: Maintain validated micro-segment encoding templates per software release.

Question 701

A provider backbone escalation identifies: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. What should the network team implement?

  1. Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale.
  2. Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain.
  3. Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies.
  4. Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport.

Explanation

Correct Answer

D:

Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport. This directly addresses the fictional service-provider network case: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. The technical mechanism is: Customer multicast addresses need VPN-aware scoping to avoid collision across independent tenants. Verify success by: Two test customers using the same group address receive only their own authorized source streams.

Incorrect Answers

A:

Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state.

B:

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 multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state.

C:

Leak only necessary shared-service prefixes with scoped RTs and controlled return-path routing policies. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state.

Question 702

A service-provider operations test targets: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. Which result is required?

  1. Two test customers using the same group address receive only their own authorized source streams.
  2. A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.
  3. Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context.
  4. The source stream arrives over the expected incoming interface and the RPF check passes.

Explanation

Correct Answer

A:

Two test customers using the same group address receive only their own authorized source streams. This confirms the approved response: Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport. It is relevant because: Customer multicast addresses need VPN-aware scoping to avoid collision across independent tenants.

Incorrect Answers

B:

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: Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport.

C:

Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context. This would validate 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. The specific correction here is: Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport.

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: Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport.

Question 703

A provider troubleshooting note states: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. Which mechanism is central?

  1. CSC designs carry another provider's traffic through a backbone without exposing all downstream customer routes into the carrier core.
  2. Customer multicast addresses need VPN-aware scoping to avoid collision across independent tenants.
  3. EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability.
  4. Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.

Explanation

Correct Answer

B:

Customer multicast addresses need VPN-aware scoping to avoid collision across independent tenants. This explains the investigated issue: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. The approved corrective response is: Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport.

Incorrect Answers

A:

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: Customer multicast addresses need VPN-aware scoping to avoid collision across independent tenants.

C:

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: Customer multicast addresses need VPN-aware scoping to avoid collision across independent tenants.

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: Customer multicast addresses need VPN-aware scoping to avoid collision across independent tenants.

Question 704

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

  1. Check EVPN route and tunnel resolution independently in inter-AS tests.
  2. Document the selected inter-AS option and verify service labels at each boundary.
  3. Test overlapping source/group cases during multicast VPN onboarding.
  4. Maintain service-specific CFM endpoint inventories and alarm tests.

Explanation

Correct Answer

C:

Test overlapping source/group cases during multicast VPN onboarding. This helps prevent recurrence of the issue: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. Acceptance evidence should be: Two test customers using the same group address receive only their own authorized source streams.

Incorrect Answers

A:

Check EVPN route and tunnel resolution independently in inter-AS tests. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Test overlapping source/group cases during multicast VPN onboarding.

B:

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: Test overlapping source/group cases during multicast VPN onboarding.

D:

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: Test overlapping source/group cases during multicast VPN onboarding.

Question 705

At an optical transport engineering team, an engineering review finds: 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. Which change most directly corrects the service problem?

  1. Create an appropriately scoped Ethernet access EVC with the approved OVC and UNI/ENNI association.
  2. Preserve or explicitly translate the customer C-tag and provider S-tag according to the agreed QinQ demarcation.
  3. Terminate the provider backbone encapsulation at the correct I-component/B-component service edge.
  4. Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations.

Explanation

Correct Answer

A:

Create an appropriately scoped Ethernet access EVC with the approved OVC and UNI/ENNI association. This directly addresses the fictional service-provider network case: 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 technical mechanism is: E-Access targets Ethernet wholesale access connectivity with defined service demarcation and operator interfaces. Verify success by: Only the contracted retail access endpoints exchange frames while unrelated handoffs stay isolated.

Incorrect Answers

B:

Preserve or explicitly translate the customer C-tag and provider S-tag according to the agreed QinQ demarcation. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: 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.

C:

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

D:

Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations. This would respond to a DIFFERENT fictional service-provider network issue: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. It does not directly address the current situation: 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.

Question 706

For an optical transport engineering team, operators addressed: 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. What is the strongest acceptance evidence?

  1. A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact.
  2. Only the contracted retail access endpoints exchange frames while unrelated handoffs stay isolated.
  3. Continuity check messages resolve to the approved remote MEP and a planned path failure produces a timely defect.
  4. Mixed-traffic tests meet voice latency while other classes retain minimum forwarding service.

Explanation

Correct Answer

B:

Only the contracted retail access endpoints exchange frames while unrelated handoffs stay isolated. This confirms the approved response: Create an appropriately scoped Ethernet access EVC with the approved OVC and UNI/ENNI association. It is relevant because: E-Access targets Ethernet wholesale access connectivity with defined service demarcation and operator interfaces.

Incorrect Answers

A:

A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact. This would validate 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. The specific correction here is: Create an appropriately scoped Ethernet access EVC with the approved OVC and UNI/ENNI association.

C:

Continuity check messages resolve to the approved remote MEP and a planned path failure produces a timely defect. This would validate ANOTHER scenario: An Ethernet OAM continuity check reports an unexpected remote maintenance endpoint and operators trust the wrong circuit when troubleshooting an outage. The specific correction here is: Create an appropriately scoped Ethernet access EVC with the approved OVC and UNI/ENNI association.

D:

Mixed-traffic tests meet voice latency while other classes retain minimum forwarding service. This would validate 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. The specific correction here is: Create an appropriately scoped Ethernet access EVC with the approved OVC and UNI/ENNI association.

Question 707

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

  1. E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints.
  2. Pseudowire control-plane state alone does not ensure the two ends interpret encapsulated payloads identically.
  3. E-Access targets Ethernet wholesale access connectivity with defined service demarcation and operator interfaces.
  4. PIM designated-router election affects which router performs certain source and join responsibilities on a shared LAN.

Explanation

Correct Answer

C:

E-Access targets Ethernet wholesale access connectivity with defined service demarcation and operator interfaces. This explains the investigated issue: 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 approved corrective response is: Create an appropriately scoped Ethernet access EVC with the approved OVC and UNI/ENNI association.

Incorrect Answers

A:

E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints. That explains a DIFFERENT 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 mechanism to prioritize for this question is: E-Access targets Ethernet wholesale access connectivity with defined service demarcation and operator interfaces.

B:

Pseudowire control-plane state alone does not ensure the two ends interpret encapsulated payloads identically. That explains a DIFFERENT 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 mechanism to prioritize for this question is: E-Access targets Ethernet wholesale access connectivity with defined service demarcation and operator interfaces.

D:

PIM designated-router election affects which router performs certain source and join responsibilities on a shared LAN. That explains a DIFFERENT 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 mechanism to prioritize for this question is: E-Access targets Ethernet wholesale access connectivity with defined service demarcation and operator interfaces.

Question 708

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

  1. Test pseudowire control-word and MTU settings before activation.
  2. Verify tag stacking and pop/push symmetry at access handoffs.
  3. Test DR state when changing multicast LAN interfaces.
  4. Reconcile order type, UNI and ENNI mapping during circuit handover.

Explanation

Correct Answer

D:

Reconcile order type, UNI and ENNI mapping during circuit handover. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Only the contracted retail access endpoints exchange frames while unrelated handoffs stay isolated.

Incorrect Answers

A:

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: Reconcile order type, UNI and ENNI mapping during circuit handover.

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: Reconcile order type, UNI and ENNI mapping during circuit handover.

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: Reconcile order type, UNI and ENNI mapping during circuit handover.

Question 709

A carrier service activation check discovers: 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. 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. Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.
  3. Correct the VPN service label allocation and VRF binding on the egress PE.
  4. Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.

Explanation

Correct Answer

B:

Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation. This directly addresses the fictional service-provider network case: 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 technical mechanism is: VPN routing can preserve stale more-specific or static routes that override newly learned paths. Verify success by: A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes.

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

C:

Correct the VPN service label allocation and VRF binding on the egress PE. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

D:

Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: 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.

Question 710

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

  1. A remote VRF installs the approved CE prefix and unrelated customer VRFs show no route change.
  2. Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding.
  3. A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes.
  4. An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree.

Explanation

Correct Answer

C:

A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes. This confirms the approved response: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation. It is relevant because: VPN routing can preserve stale more-specific or static routes that override newly learned paths.

Incorrect Answers

A:

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: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.

B:

Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding. This would validate 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. The specific correction here is: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.

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: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.