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 56

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.

Question 551

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

  1. Dual-stack VPN services require address-family-specific interfaces and MP-BGP signaling.
  2. L3VPN shared services are built with intentional route leaking and must not automatically merge entire tenant routing tables.
  3. Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings.
  4. MPLS VPN service labels identify the egress service context separately from outer backbone transport labels.

Explanation

Correct Answer

D:

MPLS VPN service labels identify the egress service context separately from outer backbone transport labels. This explains the investigated 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. The approved corrective response is: Correct the VPN service label allocation and VRF binding on the egress PE.

Incorrect Answers

A:

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: MPLS VPN service labels identify the egress service context separately from outer backbone transport labels.

B:

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: MPLS VPN service labels identify the egress service context separately from outer backbone transport labels.

C:

Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings. That explains a DIFFERENT scenario: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. The mechanism to prioritize for this question is: MPLS VPN service labels identify the egress service context separately from outer backbone transport labels.

Question 552

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

  1. Inspect per-VRF service-label mapping after platform or route-policy changes.
  2. Validate VPNv4 and VPNv6 service route counts independently.
  3. Include stale route and next-hop cleanup in VPN site migrations.
  4. Confirm product connectivity type against the customer's topology before activating the EVC.

Explanation

Correct Answer

A:

Inspect per-VRF service-label mapping after platform or route-policy changes. This helps prevent recurrence of the 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. Acceptance evidence should be: Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding.

Incorrect Answers

B:

Validate VPNv4 and VPNv6 service route counts independently. That is a sensible control for ANOTHER scenario: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. It is less targeted to this issue than: Inspect per-VRF service-label mapping after platform or route-policy changes.

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: Inspect per-VRF service-label mapping after platform or route-policy changes.

D:

Confirm product connectivity type against the customer's topology before activating the EVC. That is a sensible control for 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. It is less targeted to this issue than: Inspect per-VRF service-label mapping after platform or route-policy changes.

Question 553

For a converged broadband aggregation team, the failure is: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure. Which authorized correction best addresses it?

  1. Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.
  2. Restore consistent PIM interface settings and designated-router election visibility on the access segment.
  3. Correct multicast reverse-path reachability or the supported explicit RPF override consistent with topology.
  4. Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment.

Explanation

Correct Answer

C:

Correct multicast reverse-path reachability or the supported explicit RPF override consistent with topology. This directly addresses the fictional service-provider network case: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure. The technical mechanism is: Multicast forwarding uses Reverse Path Forwarding checks to avoid loops by selecting a valid path toward the source. Verify success by: The source stream arrives over the expected incoming interface and the RPF check passes.

Incorrect Answers

A:

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 multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure.

B:

Restore consistent PIM interface settings and designated-router election visibility on the access segment. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure.

D:

Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment. This would respond to a DIFFERENT fictional service-provider network issue: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. It does not directly address the current situation: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure.

Question 554

After fixing the following network problem, what should the team verify: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure.

  1. PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery.
  2. One intended DR is elected and the shared LAN emits the expected controlled PIM behavior.
  3. A remote VRF installs the approved CE prefix and unrelated customer VRFs show no route change.
  4. The source stream arrives over the expected incoming interface and the RPF check passes.

Explanation

Correct Answer

D:

The source stream arrives over the expected incoming interface and the RPF check passes. This confirms the approved response: Correct multicast reverse-path reachability or the supported explicit RPF override consistent with topology. It is relevant because: Multicast forwarding uses Reverse Path Forwarding checks to avoid loops by selecting a valid path toward the source.

Incorrect Answers

A:

PIM neighbor and multicast route views show RP reachability and correct shared-tree traffic delivery. This would validate ANOTHER scenario: A PIM-SM receiver router has no route to the configured rendezvous point, and (*,G) state never forms for ASM traffic. The specific correction here is: Correct multicast reverse-path reachability or the supported explicit RPF override consistent with topology.

B:

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: Correct multicast reverse-path reachability or the supported explicit RPF override consistent with topology.

C:

A remote VRF installs the approved CE prefix and unrelated customer VRFs show no route change. This would validate ANOTHER scenario: A CE-PE BGP session successfully exchanges routes but a newly provisioned customer VRF has no route targets and none of its routes propagate to distant PEs. The specific correction here is: Correct multicast reverse-path reachability or the supported explicit RPF override consistent with topology.

Question 555

A carrier root-cause review considers: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure. What underlying mechanism explains this?

  1. Multicast forwarding uses Reverse Path Forwarding checks to avoid loops by selecting a valid path toward the source.
  2. Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins.
  3. PIM designated-router election affects which router performs certain source and join responsibilities on a shared LAN.
  4. VPN routing can preserve stale more-specific or static routes that override newly learned paths.

Explanation

Correct Answer

A:

Multicast forwarding uses Reverse Path Forwarding checks to avoid loops by selecting a valid path toward the source. This explains the investigated issue: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure. The approved corrective response is: Correct multicast reverse-path reachability or the supported explicit RPF override consistent with topology.

Incorrect Answers

B:

Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: Multicast forwarding uses Reverse Path Forwarding checks to avoid loops by selecting a valid path toward the source.

C:

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: Multicast forwarding uses Reverse Path Forwarding checks to avoid loops by selecting a valid path toward the source.

D:

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: Multicast forwarding uses Reverse Path Forwarding checks to avoid loops by selecting a valid path toward the source.

Question 556

After addressing: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure. Which recurring service assurance check is most useful?

  1. Test DR state when changing multicast LAN interfaces.
  2. Alert on multicast RPF mismatches after unicast route policy changes.
  3. Include both IGMP and MLD listener tests on dual-stack access nodes.
  4. Include forward and return path checks in shared-services acceptance.

Explanation

Correct Answer

B:

Alert on multicast RPF mismatches after unicast route policy changes. This helps prevent recurrence of the issue: A PIM multicast route shows an incoming interface inconsistent with the unicast route back to the source, dropping traffic as an RPF failure. Acceptance evidence should be: The source stream arrives over the expected incoming interface and the RPF check passes.

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: Alert on multicast RPF mismatches after unicast route policy changes.

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: Alert on multicast RPF mismatches after unicast route policy changes.

D:

Include forward and return path checks in shared-services acceptance. That is a sensible control for 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. It is less targeted to this issue than: Alert on multicast RPF mismatches after unicast route policy changes.

Question 557

A provider backbone escalation identifies: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. What should the network team implement?

  1. Classify backup traffic into an appropriate weighted queue and limit the priority queue to approved delay-sensitive flows.
  2. Recalculate shaping rate and burst parameters from the service contract and platform queue behavior.
  3. Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit.
  4. Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment.

Explanation

Correct Answer

D:

Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment. This directly addresses the fictional service-provider network case: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. The technical mechanism is: Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings. Verify success by: Customer test packets receive the contracted class, and provider protocol packets retain protected control priority.

Incorrect Answers

A:

Classify backup traffic into an appropriate weighted queue and limit the priority queue to approved delay-sensitive flows. This would respond to a DIFFERENT fictional service-provider network issue: A high-volume backup class is placed in the same strict-priority queue as voice, starving the provider's control and ordinary traffic. It does not directly address the current situation: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class.

B:

Recalculate shaping rate and burst parameters from the service contract and platform queue behavior. This would respond to a DIFFERENT fictional service-provider network issue: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. It does not directly address the current situation: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class.

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 customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class.

Question 558

A service-provider operations test targets: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. Which result is required?

  1. Customer test packets receive the contracted class, and provider protocol packets retain protected control priority.
  2. Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective.
  3. A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy.
  4. An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree.

Explanation

Correct Answer

A:

Customer test packets receive the contracted class, and provider protocol packets retain protected control priority. This confirms the approved response: Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment. It is relevant because: Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings.

Incorrect Answers

B:

Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective. This would validate ANOTHER scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. The specific correction here is: Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment.

C:

A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy. This would validate ANOTHER scenario: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. The specific correction here is: Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment.

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: Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment.

Question 559

A provider troubleshooting note states: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. Which mechanism is central?

  1. QoS benefits depend on consistent classification, marking and queue treatment across the full path.
  2. Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings.
  3. Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission.
  4. IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure.

Explanation

Correct Answer

B:

Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings. This explains the investigated issue: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. The approved corrective response is: Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment.

Incorrect Answers

A:

QoS benefits depend on consistent classification, marking and queue treatment across the full path. That explains a DIFFERENT scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. The mechanism to prioritize for this question is: Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings.

C:

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: Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings.

D:

IEEE 802.1ad allows a provider service tag to carry customer-tagged Ethernet traffic across shared infrastructure. That explains a DIFFERENT scenario: A wholesale Ethernet access provider uses an 802.1ad QinQ handoff but pops both tags before the customer PE, collapsing two independent service instances. The mechanism to prioritize for this question is: Trust boundaries stop customers from impersonating carrier routing and control-plane QoS markings.

Question 560

To prevent recurrence of this provider network issue: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. Which control should be retained?

  1. Audit per-hop QoS markings and queue drops during service activation.
  2. Record shaper configuration and measured burst response for each access product.
  3. Include untrusted DSCP abuse tests at provider access interfaces.
  4. Include both IGMP and MLD listener tests on dual-stack access nodes.

Explanation

Correct Answer

C:

Include untrusted DSCP abuse tests at provider access interfaces. This helps prevent recurrence of the issue: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. Acceptance evidence should be: Customer test packets receive the contracted class, and provider protocol packets retain protected control priority.

Incorrect Answers

A:

Audit per-hop QoS markings and queue drops during service activation. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Include untrusted DSCP abuse tests at provider access interfaces.

B:

Record shaper configuration and measured burst response for each access product. That is a sensible control for ANOTHER scenario: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. It is less targeted to this issue than: Include untrusted DSCP abuse tests at provider access interfaces.

D:

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: Include untrusted DSCP abuse tests at provider access interfaces.