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 67

Question 660

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

  1. Verify local SID behaviors and VRF bindings during VPN service provisioning.
  2. Monitor adjacency SID changes and invalidate stale policy segment lists.
  3. Inspect label-stack depth and disposition at each egress after LDP or BGP changes.
  4. Test locator route advertisement whenever new SRv6 functions are provisioned.

Explanation

Correct Answer

D:

Test locator route advertisement whenever new SRv6 functions are provisioned. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint.

Incorrect Answers

A:

Verify local SID behaviors and VRF bindings during VPN service provisioning. That is a sensible control for ANOTHER scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. It is less targeted to this issue than: Test locator route advertisement whenever new SRv6 functions are provisioned.

B:

Monitor adjacency SID changes and invalidate stale policy segment lists. That is a sensible control for ANOTHER scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. It is less targeted to this issue than: Test locator route advertisement whenever new SRv6 functions are provisioned.

C:

Inspect label-stack depth and disposition at each egress after LDP or BGP changes. That is a sensible control for ANOTHER scenario: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. It is less targeted to this issue than: Test locator route advertisement whenever new SRv6 functions are provisioned.

Question 661

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

  1. Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale.
  2. Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF.
  3. Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain.
  4. Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service.

Explanation

Correct Answer

B:

Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF. This directly addresses the fictional service-provider network case: 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 technical mechanism is: EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy. Verify success by: Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context.

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

C:

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

D:

Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service. This would respond to a DIFFERENT fictional service-provider network issue: Two customers use the same 10.10.0.0/16 prefix but a PE leaks VPNv4 routes into its global table, incorrectly merging their routing contexts. It does not directly address the current situation: A provider imports 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.

Question 662

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

  1. A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.
  2. Customer-specific VPN routes remain in the authorized routing context and other carrier customers cannot import them.
  3. Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context.
  4. Customers reach the approved DNS endpoint but cross-customer reachability tests fail.

Explanation

Correct Answer

C:

Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context. This confirms the approved response: Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF. It is relevant because: EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy.

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: Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF.

B:

Customer-specific VPN routes remain in the authorized routing context and other carrier customers cannot import them. This would validate ANOTHER scenario: A wholesale carrier provides carrier-supporting-carrier transport, but a subcontractor PE advertises customer routes into the infrastructure global table rather than using labeled backbone service separation. The specific correction here is: Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF.

D:

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: Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF.

Question 663

At an ISP route assurance team, an engineer examines: 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. Which technical principle is most applicable?

  1. Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.
  2. EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints.
  3. Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.
  4. EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy.

Explanation

Correct Answer

D:

EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy. This explains the investigated 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. The approved corrective response is: Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF.

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: EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy.

B:

EVPN route reachability depends on both MP-BGP control-plane exchange and usable data-plane tunnel endpoints. That explains a DIFFERENT scenario: An inter-AS EVPN service advertises Ethernet MAC routes across the border without the expected next-hop and encapsulation capabilities, leaving routes visible but unusable. The mechanism to prioritize for this question is: EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy.

C:

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: EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy.

Question 664

For an ISP route assurance team, the change record describes: 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. What preventive validation should be standard?

  1. Audit tenant RT policies for EVPN IP prefix advertisements.
  2. Contract-test route-target separation before onboarding a new tenant EVI.
  3. Check EVPN route and tunnel resolution independently in inter-AS tests.
  4. Test DR state when changing multicast LAN interfaces.

Explanation

Correct Answer

A:

Audit tenant RT policies for EVPN IP prefix advertisements. This helps prevent recurrence of the 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. Acceptance evidence should be: Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context.

Incorrect Answers

B:

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: Audit tenant RT policies for EVPN IP prefix advertisements.

C:

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: Audit tenant RT policies for EVPN IP prefix advertisements.

D:

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: Audit tenant RT policies for EVPN IP prefix advertisements.

Question 665

For a converged broadband aggregation team, the failure is: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. Which authorized correction best addresses it?

  1. Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.
  2. Use the correct multipoint E-LAN EVC or supported VPLS/EVPN service rather than an E-Line-only handoff.
  3. Match the supported pseudowire encapsulation and control-word expectations at both endpoints.
  4. Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations.

Explanation

Correct Answer

C:

Match the supported pseudowire encapsulation and control-word expectations at both endpoints. This directly addresses the fictional service-provider network case: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. The technical mechanism is: Pseudowire control-plane state alone does not ensure the two ends interpret encapsulated payloads identically. Verify success by: A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format.

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 layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ.

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 layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ.

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: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ.

Question 666

After fixing the following network problem, what should the team verify: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ.

  1. A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact.
  2. Three permitted UNI sites exchange expected Ethernet frames without a full mesh of unrelated dedicated circuits.
  3. Two test customers using the same group address receive only their own authorized source streams.
  4. A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format.

Explanation

Correct Answer

D:

A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format. This confirms the approved response: Match the supported pseudowire encapsulation and control-word expectations at both endpoints. It is relevant because: Pseudowire control-plane state alone does not ensure the two ends interpret encapsulated payloads identically.

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: Match the supported pseudowire encapsulation and control-word expectations at both endpoints.

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: Match the supported pseudowire encapsulation and control-word expectations at both endpoints.

C:

Two test customers using the same group address receive only their own authorized source streams. This would validate ANOTHER scenario: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. The specific correction here is: Match the supported pseudowire encapsulation and control-word expectations at both endpoints.

Question 667

A carrier root-cause review considers: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. What underlying mechanism explains this?

  1. Pseudowire control-plane state alone does not ensure the two ends interpret encapsulated payloads identically.
  2. E-LAN provides multipoint Ethernet connectivity while E-Line connects a pair of service endpoints.
  3. E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.
  4. Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling.

Explanation

Correct Answer

A:

Pseudowire control-plane state alone does not ensure the two ends interpret encapsulated payloads identically. This explains the investigated issue: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. The approved corrective response is: Match the supported pseudowire encapsulation and control-word expectations at both endpoints.

Incorrect Answers

B:

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: Pseudowire control-plane state alone does not ensure the two ends interpret encapsulated payloads identically.

C:

E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability. That explains a DIFFERENT scenario: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. The mechanism to prioritize for this question is: Pseudowire control-plane state alone does not ensure the two ends interpret encapsulated payloads identically.

D:

Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling. That explains a DIFFERENT scenario: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. The mechanism to prioritize for this question is: Pseudowire control-plane state alone does not ensure the two ends interpret encapsulated payloads identically.

Question 668

After addressing: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. Which recurring service assurance check is most useful?

  1. Review RPL ownership and ring state during ring expansion.
  2. Test pseudowire control-word and MTU settings before activation.
  3. Include leaf-to-leaf negative tests for every E-Tree subscriber change.
  4. Validate host and router IGMPv3 compatibility before deploying SSM services.

Explanation

Correct Answer

B:

Test pseudowire control-word and MTU settings before activation. This helps prevent recurrence of the issue: A layer-2 pseudowire on two PEs is signaled Up but customer frames are dropped because local and remote pseudowire encapsulation modes differ. Acceptance evidence should be: A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format.

Incorrect Answers

A:

Review RPL ownership and ring state during ring expansion. That is a sensible control for 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. It is less targeted to this issue than: Test pseudowire control-word and MTU settings before activation.

C:

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: Test pseudowire control-word and MTU settings before activation.

D:

Validate host and router IGMPv3 compatibility before deploying SSM services. That is a sensible control for ANOTHER scenario: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. It is less targeted to this issue than: Test pseudowire control-word and MTU settings before activation.

Question 669

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

  1. Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets.
  2. Correct the VPN service label allocation and VRF binding on the egress PE.
  3. Separate EVPN route-target import/export policies by approved EVI and tenant bridge domain.
  4. Assign service-specific route targets and restrict import policy to the approved tenant set.

Explanation

Correct Answer

D:

Assign service-specific route targets and restrict import policy to the approved tenant set. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability. Verify success by: Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated.

Incorrect Answers

A:

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

B:

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

C:

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 advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally.

Question 670

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

  1. Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated.
  2. Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss.
  3. An IPv6 test prefix reaches the remote customer site without unintended mixing with IPv4-only service routing.
  4. A link-loss test forwards traffic through the surviving PE without duplicates or a transient broadcast loop.

Explanation

Correct Answer

A:

Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated. This confirms the approved response: Assign service-specific route targets and restrict import policy to the approved tenant set. It is relevant because: Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability.

Incorrect Answers

B:

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: Assign service-specific route targets and restrict import policy to the approved tenant set.

C:

An IPv6 test prefix reaches the remote customer site without unintended mixing with IPv4-only service routing. This would validate ANOTHER scenario: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. The specific correction here is: Assign service-specific route targets and restrict import policy to the approved tenant set.

D:

A link-loss test forwards traffic through the surviving PE without duplicates or a transient broadcast loop. This would validate ANOTHER scenario: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. The specific correction here is: Assign service-specific route targets and restrict import policy to the approved tenant set.