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 9

Question 80

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

  1. Maintain service-specific CFM endpoint inventories and alarm tests.
  2. Validate VLAN rewrite rules bidirectionally with representative tags.
  3. Confirm product connectivity type against the customer's topology before activating the EVC.
  4. Track provider tree membership and packet replication under subscriber growth.

Explanation

Correct Answer

C:

Confirm product connectivity type against the customer's topology before activating the EVC. This helps prevent recurrence of the 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. Acceptance evidence should be: Three permitted UNI sites exchange expected Ethernet frames without a full mesh of unrelated dedicated circuits.

Incorrect Answers

A:

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: Confirm product connectivity type against the customer's topology before activating the EVC.

B:

Validate VLAN rewrite rules bidirectionally with representative tags. That is a sensible control for ANOTHER scenario: A provider bridges a customer pseudowire into a service where the incoming access VLAN must be rewritten, but the PE maps the customer tag to an unrelated EVC. It is less targeted to this issue than: Confirm product connectivity type against the customer's topology before activating the EVC.

D:

Track provider tree membership and packet replication under subscriber growth. That is a sensible control for 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. It is less targeted to this issue than: Confirm product connectivity type against the customer's topology before activating the EVC.

Question 81

At a managed VPN service carrier, an engineering review finds: 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. Which change most directly corrects the service problem?

  1. Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service.
  2. Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.
  3. Enable supported IPv6 VRF address family and VPNv6 route exchange with matching route targets.
  4. Restore reachability to the authorized RP and verify PIM sparse-mode control-plane associations.

Explanation

Correct Answer

A:

Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service. This directly addresses the fictional service-provider network case: 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 technical mechanism is: MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes. Verify success by: Each tenant can reach its own 10.10.0.0/16 destinations without reaching the other tenant's overlapping addresses.

Incorrect Answers

B:

Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

C:

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

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

Question 82

For a managed VPN service carrier, operators addressed: 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. What is the strongest acceptance evidence?

  1. A remote VRF installs the approved CE prefix and unrelated customer VRFs show no route change.
  2. Each tenant can reach its own 10.10.0.0/16 destinations without reaching the other tenant's overlapping addresses.
  3. An approved Internet test flow completes both directions without exposing other tenants' internal networks.
  4. Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding.

Explanation

Correct Answer

B:

Each tenant can reach its own 10.10.0.0/16 destinations without reaching the other tenant's overlapping addresses. This confirms the approved response: Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service. It is relevant because: MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes.

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: Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service.

C:

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: Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service.

D:

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 per-customer VRFs and correct route-target import/export for the intended L3VPN service.

Question 83

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

  1. Shared Internet or extranet services require symmetric routing or supported translation for the return path.
  2. VPN routing can preserve stale more-specific or static routes that override newly learned paths.
  3. MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes.
  4. Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.

Explanation

Correct Answer

C:

MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes. This explains the investigated 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. The approved corrective response is: Restore per-customer VRFs and correct route-target import/export for the intended L3VPN service.

Incorrect Answers

A:

Shared Internet or extranet services require symmetric routing or supported translation for the return path. That explains a DIFFERENT 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 mechanism to prioritize for this question is: MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes.

B:

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: MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes.

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: MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes.

Question 84

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

  1. Verify RD and RT roles separately in provisioning templates.
  2. Inspect per-VRF service-label mapping after platform or route-policy changes.
  3. Test DR state when changing multicast LAN interfaces.
  4. Require overlapping-address negative tests before new VPN attachments.

Explanation

Correct Answer

D:

Require overlapping-address negative tests before new VPN attachments. This helps prevent recurrence of the 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. Acceptance evidence should be: Each tenant can reach its own 10.10.0.0/16 destinations without reaching the other tenant's overlapping addresses.

Incorrect Answers

A:

Verify RD and RT roles separately in provisioning templates. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Require overlapping-address negative tests before new VPN attachments.

B:

Inspect per-VRF service-label mapping after platform or route-policy changes. That is a sensible control for 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. It is less targeted to this issue than: Require overlapping-address negative tests before new VPN attachments.

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: Require overlapping-address negative tests before new VPN attachments.

Question 85

A carrier service activation check discovers: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. Which action best restores the intended behavior?

  1. Inspect and configure MLD listener state for IPv6 independently from IPv4 IGMP.
  2. Use IGMPv3 source-specific membership where required and align PIM-SSM source/group forwarding.
  3. Align PIM-BIDIR group range and designated-forwarder/RP behavior for the supported multicast domain.
  4. Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs.

Explanation

Correct Answer

B:

Use IGMPv3 source-specific membership where required and align PIM-SSM source/group forwarding. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins. Verify success by: Receiver state records the intended source and group and the video test stream flows only from that source.

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 multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream.

C:

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 multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream.

D:

Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs. This would respond to a DIFFERENT fictional service-provider network issue: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. It does not directly address the current situation: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream.

Question 86

Following a supported configuration correction, the original issue was: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. Which observation verifies success?

  1. An IPv6 test host produces the expected MLDv2 source/group membership and receives the authorized stream.
  2. Controlled traffic from multiple sources reaches receivers without duplicated registration-path forwarding.
  3. Receiver state records the intended source and group and the video test stream flows only from that source.
  4. A test burst within authorized limits traverses with predictable delay and without unnecessary drops.

Explanation

Correct Answer

C:

Receiver state records the intended source and group and the video test stream flows only from that source. This confirms the approved response: Use IGMPv3 source-specific membership where required and align PIM-SSM source/group forwarding. It is relevant because: Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins.

Incorrect Answers

A:

An IPv6 test host produces the expected MLDv2 source/group membership and receives the authorized stream. This would validate ANOTHER scenario: An IPv6 multicast receiver joins an MLDv2 group, but the adjacent router polls only IGMP state and reports no listeners. The specific correction here is: Use IGMPv3 source-specific membership where required and align PIM-SSM source/group forwarding.

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: Use IGMPv3 source-specific membership where required and align PIM-SSM source/group forwarding.

D:

A test burst within authorized limits traverses with predictable delay and without unnecessary drops. This would validate ANOTHER 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 specific correction here is: Use IGMPv3 source-specific membership where required and align PIM-SSM source/group forwarding.

Question 87

At a regional peering-exchange operator, an engineer examines: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. Which technical principle is most applicable?

  1. Multicast forwarding uses Reverse Path Forwarding checks to avoid loops by selecting a valid path toward the source.
  2. Bidirectional PIM uses a shared bidirectional tree and forwarding responsibilities different from ordinary PIM-SM source registration.
  3. L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.
  4. Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins.

Explanation

Correct Answer

D:

Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins. This explains the investigated issue: 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 approved corrective response is: Use IGMPv3 source-specific membership where required and align PIM-SSM source/group forwarding.

Incorrect Answers

A:

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

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: Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins.

C:

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: Source-Specific Multicast relies on explicit source/group membership signaling rather than any-source group joins.

Question 88

For a regional peering-exchange operator, the change record describes: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. What preventive validation should be standard?

  1. Validate host and router IGMPv3 compatibility before deploying SSM services.
  2. Test DR state when changing multicast LAN interfaces.
  3. Alert on multicast RPF mismatches after unicast route policy changes.
  4. Audit bidirectional prefix scope and service ACLs on extranet changes.

Explanation

Correct Answer

A:

Validate host and router IGMPv3 compatibility before deploying SSM services. This helps prevent recurrence of the issue: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. Acceptance evidence should be: Receiver state records the intended source and group and the video test stream flows only from that source.

Incorrect Answers

B:

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: Validate host and router IGMPv3 compatibility before deploying SSM services.

C:

Alert on multicast RPF mismatches after unicast route policy changes. That is a sensible control for 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. It is less targeted to this issue than: Validate host and router IGMPv3 compatibility before deploying SSM services.

D:

Audit bidirectional prefix scope and service ACLs on extranet changes. That is a sensible control for ANOTHER scenario: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. It is less targeted to this issue than: Validate host and router IGMPv3 compatibility before deploying SSM services.

Question 89

For an optical transport engineering team, the failure is: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. Which authorized correction best addresses it?

  1. Classify backup traffic into an appropriate weighted queue and limit the priority queue to approved delay-sensitive flows.
  2. Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification.
  3. Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.
  4. Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit.

Explanation

Correct Answer

C:

Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class. This directly addresses the fictional service-provider network case: 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 technical mechanism is: QoS benefits depend on consistent classification, marking and queue treatment across the full path. Verify success by: Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective.

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 provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion.

B:

Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion.

D:

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 provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion.

Question 90

After fixing the following network problem, what should the team verify: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion.

  1. A test burst within authorized limits traverses with predictable delay and without unnecessary drops.
  2. Customer test packets receive the contracted class, and provider protocol packets retain protected control priority.
  3. A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes.
  4. Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective.

Explanation

Correct Answer

D:

Peak-load packet captures retain the expected markings and voice delay and loss remain inside the service objective. This confirms the approved response: Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class. It is relevant because: QoS benefits depend on consistent classification, marking and queue treatment across the full path.

Incorrect Answers

A:

A test burst within authorized limits traverses with predictable delay and without unnecessary drops. This would validate ANOTHER 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 specific correction here is: Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.

B:

Customer test packets receive the contracted class, and provider protocol packets retain protected control priority. This would validate ANOTHER 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 specific correction here is: Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.

C:

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: Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.