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 34

Question 330

After fixing the following network problem, what should the team verify: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut.

  1. The replacement LSP becomes usable before the previous one is torn down in an acceptance test.
  2. The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route.
  3. Policy state selects the highest eligible preference candidate and traffic follows its listed segments.
  4. Link-failure injection switches the intended LSP onto its pre-signaled detour within the acceptance target.

Explanation

Correct Answer

D:

Link-failure injection switches the intended LSP onto its pre-signaled detour within the acceptance target. This confirms the approved response: Configure and verify compatible facility or one-to-one local repair for the critical protected link. It is relevant because: MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected.

Incorrect Answers

A:

The replacement LSP becomes usable before the previous one is torn down in an acceptance test. This would validate ANOTHER scenario: A provisioning system attempts to reoptimize an RSVP LSP using a new path but drops the existing path before the replacement is established, causing service interruption. The specific correction here is: Configure and verify compatible facility or one-to-one local repair for the critical protected link.

B:

The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route. This would validate ANOTHER scenario: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. The specific correction here is: Configure and verify compatible facility or one-to-one local repair for the critical protected link.

C:

Policy state selects the highest eligible preference candidate and traffic follows its listed segments. This would validate ANOTHER scenario: A carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it. The specific correction here is: Configure and verify compatible facility or one-to-one local repair for the critical protected link.

Question 331

A carrier root-cause review considers: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. What underlying mechanism explains this?

  1. MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected.
  2. Local protection for a link and local protection for a full node require different bypass topology constraints.
  3. Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale.
  4. MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress.

Explanation

Correct Answer

A:

MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected. This explains the investigated issue: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. The approved corrective response is: Configure and verify compatible facility or one-to-one local repair for the critical protected link.

Incorrect Answers

B:

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: MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected.

C:

Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale. That explains a DIFFERENT scenario: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale. The mechanism to prioritize for this question is: MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected.

D:

MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress. That explains a DIFFERENT scenario: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition. The mechanism to prioritize for this question is: MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected.

Question 332

After addressing: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. Which recurring service assurance check is most useful?

  1. Test the exact failure class named in each protection service objective.
  2. Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.
  3. Verify data-plane steering separately from RSVP session state.
  4. Include MSD capability checks in every SR policy computation.

Explanation

Correct Answer

B:

Inspect protection flags and test actual repair behavior instead of assuming FRR is armed. This helps prevent recurrence of the issue: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. Acceptance evidence should be: Link-failure injection switches the intended LSP onto its pre-signaled detour within the acceptance target.

Incorrect Answers

A:

Test the exact failure class named in each protection service objective. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.

C:

Verify data-plane steering separately from RSVP session state. That is a sensible control for ANOTHER scenario: 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. It is less targeted to this issue than: Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.

D:

Include MSD capability checks in every SR policy computation. That is a sensible control for ANOTHER scenario: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. It is less targeted to this issue than: Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.

Question 333

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

  1. Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.
  2. Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.
  3. Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route.
  4. Configure an explicit color/endpoint or route-policy steering association that maps the service flow to the intended SR policy.

Explanation

Correct Answer

D:

Configure an explicit color/endpoint or route-policy steering association that maps the service flow to the intended SR policy. This directly addresses the fictional service-provider network case: 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 technical mechanism is: An SR policy defines an engineered path but requires steering to affect user traffic. Verify success by: FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF.

Incorrect Answers

A:

Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly. This would respond to a DIFFERENT fictional service-provider network issue: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. It does not directly address the current situation: 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.

B:

Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics. This would respond to a DIFFERENT fictional service-provider network issue: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. It does not directly address the current situation: 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.

C:

Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route. This would respond to a DIFFERENT fictional service-provider network issue: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale. It does not directly address the current situation: 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.

Question 334

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

  1. FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF.
  2. The PCC installs only approved delegated candidates and reports their active state back to the PCE.
  3. Policy state selects the highest eligible preference candidate and traffic follows its listed segments.
  4. RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.

Explanation

Correct Answer

A:

FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF. This confirms the approved response: Configure an explicit color/endpoint or route-policy steering association that maps the service flow to the intended SR policy. It is relevant because: An SR policy defines an engineered path but requires steering to affect user traffic.

Incorrect Answers

B:

The PCC installs only approved delegated candidates and reports their active state back to the PCE. This would validate ANOTHER scenario: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. The specific correction here is: Configure an explicit color/endpoint or route-policy steering association that maps the service flow to the intended SR policy.

C:

Policy state selects the highest eligible preference candidate and traffic follows its listed segments. This would validate ANOTHER scenario: A carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it. The specific correction here is: Configure an explicit color/endpoint or route-policy steering association that maps the service flow to the intended SR policy.

D:

RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic. This would validate ANOTHER scenario: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. The specific correction here is: Configure an explicit color/endpoint or route-policy steering association that maps the service flow to the intended SR policy.

Question 335

A provider troubleshooting note states: 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. Which mechanism is central?

  1. SR policy candidate selection can prioritize administrative preference over metric optimization.
  2. An SR policy defines an engineered path but requires steering to affect user traffic.
  3. Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments.
  4. Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes.

Explanation

Correct Answer

B:

An SR policy defines an engineered path but requires steering to affect user traffic. This explains the investigated issue: 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 approved corrective response is: Configure an explicit color/endpoint or route-policy steering association that maps the service flow to the intended SR policy.

Incorrect Answers

A:

SR policy candidate selection can prioritize administrative preference over metric optimization. That explains a DIFFERENT scenario: A carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it. The mechanism to prioritize for this question is: An SR policy defines an engineered path but requires steering to affect user traffic.

C:

Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments. That explains a DIFFERENT scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. The mechanism to prioritize for this question is: An SR policy defines an engineered path but requires steering to affect user traffic.

D:

Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes. That explains a DIFFERENT scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. The mechanism to prioritize for this question is: An SR policy defines an engineered path but requires steering to affect user traffic.

Question 336

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

  1. Validate SID index and SRGB advertisements during node onboarding.
  2. Verify local SID behaviors and VRF bindings during VPN service provisioning.
  3. Check SR policy candidate selection and actual prefix steering in acceptance.
  4. Test preemption conditions and impact warnings before new tunnel activation.

Explanation

Correct Answer

C:

Check SR policy candidate selection and actual prefix steering in acceptance. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF.

Incorrect Answers

A:

Validate SID index and SRGB advertisements during node onboarding. That is a sensible control for ANOTHER scenario: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. It is less targeted to this issue than: Check SR policy candidate selection and actual prefix steering in acceptance.

B:

Verify local SID behaviors and VRF bindings during VPN service provisioning. That is a sensible control for ANOTHER scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. It is less targeted to this issue than: Check SR policy candidate selection and actual prefix steering in acceptance.

D:

Test preemption conditions and impact warnings before new tunnel activation. That is a sensible control for ANOTHER scenario: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. It is less targeted to this issue than: Check SR policy candidate selection and actual prefix steering in acceptance.

Question 337

At a regional service-provider operations center, an engineering review finds: 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. Which change most directly corrects the service problem?

  1. Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.
  2. Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport.
  3. Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale.
  4. Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points.

Explanation

Correct Answer

A:

Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border. Verify success by: A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.

Incorrect Answers

B:

Keep tenant multicast routing contexts and mVPN signaling separate across the provider transport. This would respond to a DIFFERENT fictional service-provider network issue: A multicast VPN customer uses overlapping group addresses with another tenant, and the service provider combines the flows into one global multicast state. It does not directly address the current situation: 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.

C:

Select the supported Rosen or next-generation mVPN transport model and appropriate provider multicast tree design for the scale. This would respond to a DIFFERENT fictional service-provider network issue: A provider deploys mVPN for an IPTV customer but replicates each source stream individually to every access PE even when a shared provider multicast tree is available. It does not directly address the current situation: 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.

D:

Apply the service's root-leaf forwarding restrictions at the correct bridge-domain and UNI attachment points. This would respond to a DIFFERENT fictional service-provider network issue: A carrier sells an E-Tree service with root and leaf sites but accidentally permits leaf-to-leaf bridging, exposing isolated branch traffic. It does not directly address the current situation: 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.

Question 338

For a regional service-provider operations center, operators addressed: 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. What is the strongest acceptance evidence?

  1. Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context.
  2. A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.
  3. A host migration test updates the remote PE forwarding location without persistent duplicate MAC forwarding.
  4. Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated.

Explanation

Correct Answer

B:

A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes. This confirms the approved response: Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes. It is relevant because: Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.

Incorrect Answers

A:

Route readback shows the prefix only in the intended tenant VRF and the correct L3 VNI or service context. This would validate ANOTHER scenario: A provider imports an EVPN Type-5 IP prefix into the wrong VRF because a route-target policy matches a customer label instead of the service's approved tenant RT. The specific correction here is: Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.

C:

A host migration test updates the remote PE forwarding location without persistent duplicate MAC forwarding. This would validate ANOTHER scenario: Two PEs establish BGP EVPN but remote MAC mobility updates are ignored because a device keeps an older sequence number as authoritative. The specific correction here is: Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.

D:

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: Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.

Question 339

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

  1. EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy.
  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. MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes.

Explanation

Correct Answer

C:

Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border. This explains the investigated 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. The approved corrective response is: Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.

Incorrect Answers

A:

EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy. That explains a DIFFERENT scenario: A provider imports an EVPN Type-5 IP prefix into the wrong VRF because a route-target policy matches a customer label instead of the service's approved tenant RT. The mechanism to prioritize for this question is: Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.

B:

EVPN all-active multihoming relies on consistent Ethernet segment membership and designated forwarder behavior for BUM traffic. That explains a DIFFERENT scenario: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. The mechanism to prioritize for this question is: Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.

D:

MPLS L3VPN separates customer routing information using VRFs and VPN route distribution attributes. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Inter-AS VPN models differ in whether VRFs, labeled IPv4 or VPNv4 NLRI are exchanged at the border.

Question 340

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

  1. Contract-test route-target separation before onboarding a new tenant EVI.
  2. Track provider tree membership and packet replication under subscriber growth.
  3. Include both IGMP and MLD listener tests on dual-stack access nodes.
  4. Document the selected inter-AS option and verify service labels at each boundary.

Explanation

Correct Answer

D:

Document the selected inter-AS option and verify service labels at each boundary. This helps prevent recurrence of the 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. Acceptance evidence should be: A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.

Incorrect Answers

A:

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: Document the selected inter-AS option and verify service labels at each boundary.

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: Document the selected inter-AS option and verify service labels at each boundary.

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: Document the selected inter-AS option and verify service labels at each boundary.