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 61

Question 600

For a carrier automation platform team, the change record describes: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. What preventive validation should be standard?

  1. Verify data-plane steering separately from RSVP session state.
  2. Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.
  3. Record reoptimization stability and path-change rate in monitoring.
  4. Include crossregion label-stack tracing in service acceptance.

Explanation

Correct Answer

A:

Verify data-plane steering separately from RSVP session state. This helps prevent recurrence of the issue: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. Acceptance evidence should be: FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path.

Incorrect Answers

B:

Inspect protection flags and test actual repair behavior instead of assuming FRR is armed. That is a sensible control for ANOTHER scenario: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. It is less targeted to this issue than: Verify data-plane steering separately from RSVP session state.

C:

Record reoptimization stability and path-change rate in monitoring. That is a sensible control for ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. It is less targeted to this issue than: Verify data-plane steering separately from RSVP session state.

D:

Include crossregion label-stack tracing in service acceptance. That is a sensible control for ANOTHER scenario: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. It is less targeted to this issue than: Verify data-plane steering separately from RSVP session state.

Question 601

For a multi-tenant data transport provider, the failure is: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. Which authorized correction best addresses it?

  1. Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility.
  2. Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination.
  3. Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.
  4. Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.

Explanation

Correct Answer

C:

Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths. This directly addresses the fictional service-provider network case: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. The technical mechanism is: SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone. Verify success by: Flex-Algo route and SID tables show a consistent constraint topology across the intended service path.

Incorrect Answers

A:

Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve.

B:

Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination. This would respond to a DIFFERENT fictional service-provider network issue: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology. It does not directly address the current situation: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve.

D:

Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link. This would respond to a DIFFERENT fictional service-provider network issue: An MPLS TE bypass tunnel is administratively configured but the protected service shows no local protection because node protection was requested and only link protection is available. It does not directly address the current situation: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve.

Question 602

After fixing the following network problem, what should the team verify: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve.

  1. FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF.
  2. A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state.
  3. Link-failure injection switches the intended LSP onto its pre-signaled detour within the acceptance target.
  4. Flex-Algo route and SID tables show a consistent constraint topology across the intended service path.

Explanation

Correct Answer

D:

Flex-Algo route and SID tables show a consistent constraint topology across the intended service path. This confirms the approved response: Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths. It is relevant because: SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone.

Incorrect Answers

A:

FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF. This would validate ANOTHER scenario: A Segment Routing policy is installed but no customer route is steered to its binding SID, so measured traffic still follows ordinary IGP shortest paths. The specific correction here is: Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.

B:

A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state. This would validate ANOTHER scenario: A provider enables SR-MPLS forwarding but assumes each SR-TE path requires RSVP-TE state on every transit router, blocking deployment when RSVP is disabled. The specific correction here is: Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.

C:

Link-failure injection switches the intended LSP onto its pre-signaled detour within the acceptance target. This would validate ANOTHER scenario: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. The specific correction here is: Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.

Question 603

A carrier root-cause review considers: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. What underlying mechanism explains this?

  1. SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone.
  2. An SR policy defines an engineered path but requires steering to affect user traffic.
  3. Segment Routing policy feasibility is constrained by how many segment labels the headend or transit hardware can impose.
  4. Local protection for a link and local protection for a full node require different bypass topology constraints.

Explanation

Correct Answer

A:

SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone. This explains the investigated issue: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. The approved corrective response is: Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.

Incorrect Answers

B:

An SR policy defines an engineered path but requires steering to affect user traffic. That explains a DIFFERENT scenario: A Segment Routing policy is installed but no customer route is steered to its binding SID, so measured traffic still follows ordinary IGP shortest paths. The mechanism to prioritize for this question is: SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone.

C:

Segment Routing policy feasibility is constrained by how many segment labels the headend or transit hardware can impose. That explains a DIFFERENT scenario: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. The mechanism to prioritize for this question is: SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone.

D:

Local protection for a link and local protection for a full node require different bypass topology constraints. That explains a DIFFERENT scenario: An MPLS TE bypass tunnel is administratively configured but the protected service shows no local protection because node protection was requested and only link protection is available. The mechanism to prioritize for this question is: SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone.

Question 604

After addressing: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. Which recurring service assurance check is most useful?

  1. Maintain validated micro-segment encoding templates per software release.
  2. Validate algorithm definition consistency before changing service steering.
  3. Audit protected-prefix coverage before deploying TI-LFA claims.
  4. Test route and label binding presence separately for every new backbone link.

Explanation

Correct Answer

B:

Validate algorithm definition consistency before changing service steering. This helps prevent recurrence of the issue: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. Acceptance evidence should be: Flex-Algo route and SID tables show a consistent constraint topology across the intended service path.

Incorrect Answers

A:

Maintain validated micro-segment encoding templates per software release. That is a sensible control for ANOTHER scenario: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. It is less targeted to this issue than: Validate algorithm definition consistency before changing service steering.

C:

Audit protected-prefix coverage before deploying TI-LFA claims. That is a sensible control for ANOTHER scenario: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology. It is less targeted to this issue than: Validate algorithm definition consistency before changing service steering.

D:

Test route and label binding presence separately for every new backbone link. That is a sensible control for ANOTHER scenario: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. It is less targeted to this issue than: Validate algorithm definition consistency before changing service steering.

Question 605

A provider backbone escalation identifies: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. What should the network team implement?

  1. Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.
  2. Use the supported Carrier Supporting Carrier VPN transport design and preserve customer route isolation across the wholesale boundary.
  3. Restore the intended ERP blocking and ring protection state with verified RPL ownership.
  4. Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs.

Explanation

Correct Answer

D:

Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs. This directly addresses the fictional service-provider network case: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. The technical mechanism is: EVPN all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic. Verify success by: A link-loss test forwards traffic through the surviving PE without duplicates or a transient broadcast loop.

Incorrect Answers

A:

Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes. This would respond to a DIFFERENT fictional service-provider network issue: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. It does not directly address the current situation: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree.

B:

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: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree.

C:

Restore the intended ERP blocking and ring protection state with verified RPL ownership. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree.

Question 606

A service-provider operations test targets: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. Which result is required?

  1. A link-loss test forwards traffic through the surviving PE without duplicates or a transient broadcast loop.
  2. A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.
  3. A remote MAC route resolves to the correct border and service encapsulation and transmits a unicast frame.
  4. An IPv6 test host produces the expected MLDv2 source/group membership and receives the authorized stream.

Explanation

Correct Answer

A:

A link-loss test forwards traffic through the surviving PE without duplicates or a transient broadcast loop. This confirms the approved response: Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs. It is relevant because: EVPN all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic.

Incorrect Answers

B:

A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes. This would validate ANOTHER scenario: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. The specific correction here is: Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs.

C:

A remote MAC route resolves to the correct border and service encapsulation and transmits a unicast frame. This would validate 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. The specific correction here is: Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs.

D:

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: Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs.

Question 607

A provider troubleshooting note states: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. Which mechanism is central?

  1. EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability.
  2. EVPN all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic.
  3. Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.
  4. PE-CE routing and provider MP-BGP VPN distribution are distinct control-plane stages in an L3VPN service.

Explanation

Correct Answer

B:

EVPN all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic. This explains the investigated issue: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. The approved corrective response is: Align Ethernet Segment Identifier, DF election and split-horizon signaling on the multihomed PEs.

Incorrect Answers

A:

EVPN uses BGP route targets and service identifiers to control which tenant tables import distributed Ethernet reachability. That explains a DIFFERENT scenario: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. The mechanism to prioritize for this question is: EVPN all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic.

C:

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 all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic.

D:

PE-CE routing and provider MP-BGP VPN distribution are distinct control-plane stages in an L3VPN service. That explains a DIFFERENT 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 mechanism to prioritize for this question is: EVPN all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic.

Question 608

To prevent recurrence of this provider network issue: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. Which control should be retained?

  1. Run controlled host-movement tests after EVPN control-plane upgrades.
  2. Track provider tree membership and packet replication under subscriber growth.
  3. Include DF state and failover packet captures in access certification.
  4. Include both IGMP and MLD listener tests on dual-stack access nodes.

Explanation

Correct Answer

C:

Include DF state and failover packet captures in access certification. This helps prevent recurrence of the issue: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. Acceptance evidence should be: A link-loss test forwards traffic through the surviving PE without duplicates or a transient broadcast loop.

Incorrect Answers

A:

Run controlled host-movement tests after EVPN control-plane upgrades. That is a sensible control for ANOTHER scenario: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. It is less targeted to this issue than: Include DF state and failover packet captures in access certification.

B:

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: Include DF state and failover packet captures in access certification.

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 DF state and failover packet captures in access certification.

Question 609

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

  1. Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit.
  2. Correct the CFM maintenance domain, association and MEP identifiers for the intended service.
  3. Restore the intended ERP blocking and ring protection state with verified RPL ownership.
  4. Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF.

Explanation

Correct Answer

A:

Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit. This directly addresses the fictional service-provider network case: 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 technical mechanism is: VLAN tag manipulation at the PE defines the customer-to-provider service mapping and can change tenant isolation. Verify success by: Tagged frame tests map each subscriber VLAN to the intended service and restore the expected egress tag.

Incorrect Answers

B:

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

C:

Restore the intended ERP blocking and ring protection state with verified RPL ownership. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

D:

Bind IP prefix route import to the authorized EVPN L3 service route targets and VRF. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: 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.

Question 610

For a converged broadband aggregation team, operators addressed: 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. What is the strongest acceptance evidence?

  1. A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format.
  2. Tagged frame tests map each subscriber VLAN to the intended service and restore the expected egress tag.
  3. Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked.
  4. A test burst within authorized limits traverses with predictable delay and without unnecessary drops.

Explanation

Correct Answer

B:

Tagged frame tests map each subscriber VLAN to the intended service and restore the expected egress tag. This confirms the approved response: Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit. It is relevant because: VLAN tag manipulation at the PE defines the customer-to-provider service mapping and can change tenant isolation.

Incorrect Answers

A:

A lab traffic test passes with consistent pseudowire labels and expected Ethernet frame format. This would validate 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. The specific correction here is: Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit.

C:

Root-to-leaf tests pass and direct leaf-to-leaf attempts are blocked. This would validate 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. The specific correction here is: Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit.

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: Apply the approved ingress and egress VLAN translation and encapsulation rewrite on the correct attachment circuit.