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 22

Question 210

For a multi-tenant data transport provider, operators addressed: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. What is the strongest acceptance evidence?

  1. A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers.
  2. Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked.
  3. A double-tagged test from each customer arrives at the correct logical service with its contracted inner VLAN intact.
  4. An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree.

Explanation

Correct Answer

B:

Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked. This confirms the approved response: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points. It is relevant because: E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.

Incorrect Answers

A:

A captured customer UNI frame contains only the expected customer Ethernet header while provider core frames carry backbone identifiers. This would validate ANOTHER scenario: A carrier backbone applies provider bridging with 802.1ah MAC-in-MAC but its edge fails to strip the outer backbone header, so customer switches receive unknown backbone addresses. The specific correction here is: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.

C:

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: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.

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: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.

Question 211

Which network protocol or forwarding behavior explains the following issue: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic.

  1. Ethernet CFM operates within defined maintenance levels and identities to monitor continuity for particular services.
  2. VLAN tag manipulation at the PE defines the customer-to-provider service mapping and can change tenant isolation.
  3. E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.
  4. Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission.

Explanation

Correct Answer

C:

E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability. This explains the investigated issue: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. The approved corrective response is: Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.

Incorrect Answers

A:

Ethernet CFM operates within defined maintenance levels and identities to monitor continuity for particular services. That explains a DIFFERENT scenario: An Ethernet OAM continuity check reports an unexpected remote maintenance endpoint and operators trust the wrong circuit when troubleshooting an outage. The mechanism to prioritize for this question is: E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.

B:

VLAN tag manipulation at the PE defines the customer-to-provider service mapping and can change tenant isolation. That explains a DIFFERENT 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 mechanism to prioritize for this question is: E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.

D:

Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission. That explains a DIFFERENT scenario: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. The mechanism to prioritize for this question is: E-Tree Ethernet service enforces a rooted multipoint relationship rather than unrestricted multipoint reachability.

Question 212

A core network change board wants to avoid: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. Which ongoing safeguard fits best?

  1. Reconcile order type, UNI and ENNI mapping during circuit handover.
  2. Test pseudowire control-word and MTU settings before activation.
  3. Contract-test route-target separation before onboarding a new tenant EVI.
  4. Include leaf-to-leaf negative tests for every E-Tree subscriber change.

Explanation

Correct Answer

D:

Include leaf-to-leaf negative tests for every E-Tree subscriber change. This helps prevent recurrence of the issue: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. Acceptance evidence should be: Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked.

Incorrect Answers

A:

Reconcile order type, UNI and ENNI mapping during circuit handover. That is a sensible control for ANOTHER scenario: An E-Access wholesale demarcation connects one retail provider UNI to a distant operator UNI, but the order is provisioned as an open multipoint LAN across all sites. It is less targeted to this issue than: Include leaf-to-leaf negative tests for every E-Tree subscriber change.

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: Include leaf-to-leaf negative tests for every E-Tree subscriber change.

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: Include leaf-to-leaf negative tests for every E-Tree subscriber change.

Question 213

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

  1. Add explicitly authorized VPN RT export/import policy and ensure the MP-BGP VPN family is active between PEs.
  2. Check RD uniqueness for VPNv4 route identity and configure the intended import/export route targets for reachability.
  3. Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service.
  4. Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.

Explanation

Correct Answer

B:

Check RD uniqueness for VPNv4 route identity and configure the intended import/export route targets for reachability. This directly addresses the fictional service-provider network case: 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 technical mechanism is: A route distinguisher disambiguates overlapping VPN routes, whereas route targets govern VRF import policy. Verify success by: Remote VRF shows the expected VPNv4 prefix and matching label while unintended VRFs remain empty.

Incorrect Answers

A:

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

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

D:

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

Question 214

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

  1. Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated.
  2. Each tenant can reach its own 10.10.0.0/16 destinations without reaching the other tenant's overlapping addresses.
  3. Remote VRF shows the expected VPNv4 prefix and matching label while unintended VRFs remain empty.
  4. Customer-specific VPN routes remain in the authorized routing context and other carrier customers cannot import them.

Explanation

Correct Answer

C:

Remote VRF shows the expected VPNv4 prefix and matching label while unintended VRFs remain empty. This confirms the approved response: Check RD uniqueness for VPNv4 route identity and configure the intended import/export route targets for reachability. It is relevant because: A route distinguisher disambiguates overlapping VPN routes, whereas route targets govern VRF import policy.

Incorrect Answers

A:

Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated. This would validate ANOTHER scenario: A provider advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally. The specific correction here is: Check RD uniqueness for VPNv4 route identity and configure the intended import/export route targets for reachability.

B:

Each tenant can reach its own 10.10.0.0/16 destinations without reaching the other tenant's overlapping addresses. This would validate 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. The specific correction here is: Check RD uniqueness for VPNv4 route identity and configure the intended import/export route targets for reachability.

D:

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: Check RD uniqueness for VPNv4 route identity and configure the intended import/export route targets for reachability.

Question 215

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

  1. VPN routing can preserve stale more-specific or static routes that override newly learned paths.
  2. L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.
  3. Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.
  4. A route distinguisher disambiguates overlapping VPN routes, whereas route targets govern VRF import policy.

Explanation

Correct Answer

D:

A route distinguisher disambiguates overlapping VPN routes, whereas route targets govern VRF import policy. This explains the investigated 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. The approved corrective response is: Check RD uniqueness for VPNv4 route identity and configure the intended import/export route targets for reachability.

Incorrect Answers

A:

VPN routing can preserve stale more-specific or static routes that override newly learned paths. That explains a DIFFERENT 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 mechanism to prioritize for this question is: A route distinguisher disambiguates overlapping VPN routes, whereas route targets govern VRF import policy.

B:

L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels. That explains a DIFFERENT scenario: A customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost. The mechanism to prioritize for this question is: A route distinguisher disambiguates overlapping VPN routes, whereas route targets govern VRF 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: A route distinguisher disambiguates overlapping VPN routes, whereas route targets govern VRF import policy.

Question 216

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

  1. Verify RD and RT roles separately in provisioning templates.
  2. Validate CE route reception, VPN export and remote import as three separate checks.
  3. Include stale route and next-hop cleanup in VPN site migrations.
  4. Include DF state and failover packet captures in access certification.

Explanation

Correct Answer

A:

Verify RD and RT roles separately in provisioning templates. This helps prevent recurrence of the 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. Acceptance evidence should be: Remote VRF shows the expected VPNv4 prefix and matching label while unintended VRFs remain empty.

Incorrect Answers

B:

Validate CE route reception, VPN export and remote import as three separate checks. That is a sensible control for 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. It is less targeted to this issue than: Verify RD and RT roles separately in provisioning templates.

C:

Include stale route and next-hop cleanup in VPN site migrations. That is a sensible control for 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. It is less targeted to this issue than: Verify RD and RT roles separately in provisioning templates.

D:

Include DF state and failover packet captures in access certification. That is a sensible control for ANOTHER scenario: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. It is less targeted to this issue than: Verify RD and RT roles separately in provisioning templates.

Question 217

For a converged broadband aggregation team, the failure is: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. Which authorized correction best addresses it?

  1. Inspect and configure MLD listener state for IPv6 independently from IPv4 IGMP.
  2. Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.
  3. Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations.
  4. Correct the CFM maintenance domain, association and MEP identifiers for the intended service.

Explanation

Correct Answer

C:

Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations. This directly addresses the fictional service-provider network case: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. The technical mechanism is: PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups. Verify success by: PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery.

Incorrect Answers

A:

Inspect and configure MLD listener state for IPv6 independently from IPv4 IGMP. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 multicast receiver joins an MLDv2 group, but the adjacent router polls only IGMP state and reports no listeners. It does not directly address the current situation: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic.

B:

Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain. This would respond to a DIFFERENT fictional service-provider network issue: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. It does not directly address the current situation: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic.

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 PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic.

Question 218

After fixing the following network problem, what should the team verify: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic.

  1. One intended DR is elected and the shared LAN emits the expected controlled PIM behavior.
  2. Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding.
  3. Two test customers using the same group address receive only their own authorized source streams.
  4. PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery.

Explanation

Correct Answer

D:

PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery. This confirms the approved response: Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations. It is relevant because: PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups.

Incorrect Answers

A:

One intended DR is elected and the shared LAN emits the expected controlled PIM behavior. This would validate ANOTHER scenario: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. The specific correction here is: Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations.

B:

Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding. This would validate ANOTHER scenario: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. The specific correction here is: Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations.

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: Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations.

Question 219

A carrier root-cause review considers: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. What underlying mechanism explains this?

  1. PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups.
  2. Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration.
  3. IGMP controls IPv4 multicast listener membership, while MLD performs the analogous role for IPv6.
  4. L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.

Explanation

Correct Answer

A:

PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups. This explains the investigated issue: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. The approved corrective response is: Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations.

Incorrect Answers

B:

Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration. That explains a DIFFERENT scenario: A bidirectional multicast service accidentally enables ordinary PIM-SM source register processing for a BIDIR group, creating duplicate replication. The mechanism to prioritize for this question is: PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups.

C:

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: PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups.

D:

L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels. That explains a DIFFERENT scenario: A customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost. The mechanism to prioritize for this question is: PIM sparse mode normally uses an RP during rendezvous for Any-Source Multicast groups.

Question 220

After addressing: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. Which recurring service assurance check is most useful?

  1. Test DR state when changing multicast LAN interfaces.
  2. Monitor RP reachability and failover under multicast service SLAs.
  3. Include both IGMP and MLD listener tests on dual-stack access nodes.
  4. Include stale route and next-hop cleanup in VPN site migrations.

Explanation

Correct Answer

B:

Monitor RP reachability and failover under multicast service SLAs. This helps prevent recurrence of the issue: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. Acceptance evidence should be: PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery.

Incorrect Answers

A:

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: Monitor RP reachability and failover under multicast service SLAs.

C:

Include both IGMP and MLD listener tests on dual-stack access nodes. That is a sensible control for ANOTHER scenario: An IPv6 multicast receiver joins an MLDv2 group, but the adjacent router polls only IGMP state and reports no listeners. It is less targeted to this issue than: Monitor RP reachability and failover under multicast service SLAs.

D:

Include stale route and next-hop cleanup in VPN site migrations. That is a sensible control for 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. It is less targeted to this issue than: Monitor RP reachability and failover under multicast service SLAs.