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 50

Question 490

After fixing the following network problem, what should the team verify: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies.

  1. A test frame sent between the two UNI endpoints retains the required service VLAN attributes and does not reach any unapproved site.
  2. Synthetic timing and delay tests remain within the RAN interface limits at full traffic load.
  3. A capability check selects a valid interface for each device and rejects models not advertised by the platform.
  4. Link-down and lightpath-loss tests select the intended restoration layer without persistent forwarding loops.

Explanation

Correct Answer

D:

Link-down and lightpath-loss tests select the intended restoration layer without persistent forwarding loops. This confirms the approved response: Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy. It is relevant because: Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence.

Incorrect Answers

A:

A test frame sent between the two UNI endpoints retains the required service VLAN attributes and does not reach any unapproved site. This would validate ANOTHER scenario: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage. The specific correction here is: Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy.

B:

Synthetic timing and delay tests remain within the RAN interface limits at full traffic load. This would validate ANOTHER scenario: A 5G fronthaul transport team treats a RAN radio-to-distributed-unit path as an ordinary best-effort internet uplink and sees timing instability during peak load. The specific correction here is: Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy.

C:

A capability check selects a valid interface for each device and rejects models not advertised by the platform. This would validate ANOTHER scenario: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases. The specific correction here is: Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy.

Question 491

A carrier root-cause review considers: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. What underlying mechanism explains this?

  1. Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence.
  2. An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router.
  3. An E-Line is a point-to-point Ethernet service whose service boundary must be explicit even when the underlying provider backbone uses routed transport.
  4. Modular network operating systems may isolate process failures from overall forwarding and supervisor availability.

Explanation

Correct Answer

A:

Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence. This explains the investigated issue: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. The approved corrective response is: Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy.

Incorrect Answers

B:

An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router. That explains a DIFFERENT scenario: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. The mechanism to prioritize for this question is: Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence.

C:

An E-Line is a point-to-point Ethernet service whose service boundary must be explicit even when the underlying provider backbone uses routed transport. That explains a DIFFERENT scenario: A metro aggregation design places a latency-sensitive enterprise E-Line directly across an IP core with no documented Ethernet service handoff, leading to mismatched expectations for transparent VLAN carriage. The mechanism to prioritize for this question is: Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence.

D:

Modular network operating systems may isolate process failures from overall forwarding and supervisor availability. That explains a DIFFERENT scenario: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. The mechanism to prioritize for this question is: Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence.

Question 492

After addressing: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. Which recurring service assurance check is most useful?

  1. Check subscriber access-media type before selecting aggregation hardware and automation profiles.
  2. Review optical and routing timer interaction in multilayer failure drills.
  3. Maintain an inventory of per-hop encapsulation support and interworking validation tests.
  4. Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.

Explanation

Correct Answer

B:

Review optical and routing timer interaction in multilayer failure drills. This helps prevent recurrence of the issue: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. Acceptance evidence should be: Link-down and lightpath-loss tests select the intended restoration layer without persistent forwarding loops.

Incorrect Answers

A:

Check subscriber access-media type before selecting aggregation hardware and automation profiles. That is a sensible control for ANOTHER scenario: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. It is less targeted to this issue than: Review optical and routing timer interaction in multilayer failure drills.

C:

Maintain an inventory of per-hop encapsulation support and interworking validation tests. That is a sensible control for ANOTHER scenario: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. It is less targeted to this issue than: Review optical and routing timer interaction in multilayer failure drills.

D:

Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks. That is a sensible control for ANOTHER scenario: A provider triggers RTBH by announcing a route with an incorrect blackhole community, and legitimate subscriber traffic to the target continues to traverse the core. It is less targeted to this issue than: Review optical and routing timer interaction in multilayer failure drills.

Question 493

A provider backbone escalation identifies: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. What should the network team implement?

  1. Align the DS-TE class type bandwidth model and router reservations with the intended MAM or RDM admission policy.
  2. Classify or remark traffic at the customer-provider handoff according to the contracted class-of-service policy.
  3. Use only the supported application-hosting environment with explicit CPU, memory, interface and lifecycle controls.
  4. Apply scalable differentiated class treatment in the backbone and reserve per-flow signaling for limited domains where it is feasible.

Explanation

Correct Answer

D:

Apply scalable differentiated class treatment in the backbone and reserve per-flow signaling for limited domains where it is feasible. This directly addresses the fictional service-provider network case: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. The technical mechanism is: DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state. Verify success by: At scale, traffic classes meet their service objectives without requiring one signaling state entry for every subscriber flow.

Incorrect Answers

A:

Align the DS-TE class type bandwidth model and router reservations with the intended MAM or RDM admission policy. This would respond to a DIFFERENT fictional service-provider network issue: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. It does not directly address the current situation: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources.

B:

Classify or remark traffic at the customer-provider handoff according to the contracted class-of-service policy. This would respond to a DIFFERENT fictional service-provider network issue: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. It does not directly address the current situation: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources.

C:

Use only the supported application-hosting environment with explicit CPU, memory, interface and lifecycle controls. This would respond to a DIFFERENT fictional service-provider network issue: An operations team deploys an application container directly onto a router control processor without checking vendor-supported hosting resources or isolation limits. It does not directly address the current situation: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources.

Question 494

A service-provider operations test targets: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. Which result is required?

  1. At scale, traffic classes meet their service objectives without requiring one signaling state entry for every subscriber flow.
  2. An engineered pair of LSP requests is admitted or rejected in line with the expected class-type bandwidth budget.
  3. A packet capture shows one flow retains a consistent label and path selection stabilizes.
  4. Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session.

Explanation

Correct Answer

A:

At scale, traffic classes meet their service objectives without requiring one signaling state entry for every subscriber flow. This confirms the approved response: Apply scalable differentiated class treatment in the backbone and reserve per-flow signaling for limited domains where it is feasible. It is relevant because: DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state.

Incorrect Answers

B:

An engineered pair of LSP requests is admitted or rejected in line with the expected class-type bandwidth budget. This would validate ANOTHER scenario: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. The specific correction here is: Apply scalable differentiated class treatment in the backbone and reserve per-flow signaling for limited domains where it is feasible.

C:

A packet capture shows one flow retains a consistent label and path selection stabilizes. This would validate ANOTHER scenario: An IPv6 multicast-sensitive telemetry application changes the IPv6 flow label every packet and load-sharing routers distribute a single transport stream across many paths. The specific correction here is: Apply scalable differentiated class treatment in the backbone and reserve per-flow signaling for limited domains where it is feasible.

D:

Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session. This would validate ANOTHER scenario: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. The specific correction here is: Apply scalable differentiated class treatment in the backbone and reserve per-flow signaling for limited domains where it is feasible.

Question 495

A provider troubleshooting note states: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. Which mechanism is central?

  1. Maximum Allocation Model and Russian Dolls Model partition reservable bandwidth differently for traffic-engineering classes.
  2. DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state.
  3. The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing.
  4. Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence.

Explanation

Correct Answer

B:

DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state. This explains the investigated issue: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. The approved corrective response is: Apply scalable differentiated class treatment in the backbone and reserve per-flow signaling for limited domains where it is feasible.

Incorrect Answers

A:

Maximum Allocation Model and Russian Dolls Model partition reservable bandwidth differently for traffic-engineering classes. That explains a DIFFERENT scenario: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. The mechanism to prioritize for this question is: DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state.

C:

The IPv6 flow label can help identify related packets for consistent treatment when network devices use it in hashing. That explains a DIFFERENT scenario: An IPv6 multicast-sensitive telemetry application changes the IPv6 flow label every packet and load-sharing routers distribute a single transport stream across many paths. The mechanism to prioritize for this question is: DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state.

D:

Optical and packet layers can both repair failures, and uncoordinated timers may cause oscillation or unnecessarily prolonged reconvergence. That explains a DIFFERENT scenario: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. The mechanism to prioritize for this question is: DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state.

Question 496

To prevent recurrence of this provider network issue: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. Which control should be retained?

  1. Include negative marking tests at each new customer UNI.
  2. Verify flow-label behavior during software and hashing-policy upgrades.
  3. Capacity-test classifier, policer and scheduler state before service rollout.
  4. Revalidate source-verification mode after subscriber routing changes.

Explanation

Correct Answer

C:

Capacity-test classifier, policer and scheduler state before service rollout. This helps prevent recurrence of the issue: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. Acceptance evidence should be: At scale, traffic classes meet their service objectives without requiring one signaling state entry for every subscriber flow.

Incorrect Answers

A:

Include negative marking tests at each new customer UNI. That is a sensible control for ANOTHER scenario: A customer sends traffic already marked high priority and an access PE trusts every DSCP value, letting uncontracted backups crowd out voice queues. It is less targeted to this issue than: Capacity-test classifier, policer and scheduler state before service rollout.

B:

Verify flow-label behavior during software and hashing-policy upgrades. That is a sensible control for ANOTHER scenario: An IPv6 multicast-sensitive telemetry application changes the IPv6 flow label every packet and load-sharing routers distribute a single transport stream across many paths. It is less targeted to this issue than: Capacity-test classifier, policer and scheduler state before service rollout.

D:

Revalidate source-verification mode after subscriber routing changes. That is a sensible control for ANOTHER scenario: A PE applies loose uRPF on a single-homed subscriber port but an upstream source-spoofing event still enters through a route that exists via another edge. It is less targeted to this issue than: Capacity-test classifier, policer and scheduler state before service rollout.

Question 497

At a converged broadband aggregation team, an engineering review finds: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. Which change most directly corrects the service problem?

  1. Align both ends to a common supported IS-IS adjacency level with consistent interface settings.
  2. Correct the interlevel advertisement and summary scope after checking reachability to the component routes.
  3. Set the intended IS-IS wide metric on the optical link based on approved transport cost.
  4. Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI.

Explanation

Correct Answer

A:

Align both ends to a common supported IS-IS adjacency level with consistent interface settings. This directly addresses the fictional service-provider network case: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. The technical mechanism is: Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information. Verify success by: A lab peering test establishes a stable adjacency and exchanges the intended LSPs.

Incorrect Answers

B:

Correct the interlevel advertisement and summary scope after checking reachability to the component routes. This would respond to a DIFFERENT fictional service-provider network issue: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. It does not directly address the current situation: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only.

C:

Set the intended IS-IS wide metric on the optical link based on approved transport cost. This would respond to a DIFFERENT fictional service-provider network issue: An IS-IS L2 router forms adjacency but traffic chooses a high-latency optical link because the interface metric was left at a low default. It does not directly address the current situation: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only.

D:

Separate service VRF import/export route targets from public internet BGP policy and validate permitted NLRI. This would respond to a DIFFERENT fictional service-provider network issue: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. It does not directly address the current situation: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only.

Question 498

For a converged broadband aggregation team, operators addressed: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. What is the strongest acceptance evidence?

  1. Both routers report the intended adjacency level and the local area route becomes reachable.
  2. A lab peering test establishes a stable adjacency and exchanges the intended LSPs.
  3. During restart testing, other routers avoid the node for transit until its forwarding state is ready.
  4. A known IPv4-only test name yields a reachable synthesized AAAA result and end-to-end connectivity.

Explanation

Correct Answer

B:

A lab peering test establishes a stable adjacency and exchanges the intended LSPs. This confirms the approved response: Align both ends to a common supported IS-IS adjacency level with consistent interface settings. It is relevant because: Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information.

Incorrect Answers

A:

Both routers report the intended adjacency level and the local area route becomes reachable. This would validate ANOTHER scenario: A core interface comes up but its IS-IS hellos never result in adjacency because peer system IDs use incompatible area addressing on L1-only neighbors. The specific correction here is: Align both ends to a common supported IS-IS adjacency level with consistent interface settings.

C:

During restart testing, other routers avoid the node for transit until its forwarding state is ready. This would validate ANOTHER scenario: A provider enables IS-IS overload on a recovering core node then removes the flag before the full route database is synchronized, leading to transient transit blackholes. The specific correction here is: Align both ends to a common supported IS-IS adjacency level with consistent interface settings.

D:

A known IPv4-only test name yields a reachable synthesized AAAA result and end-to-end connectivity. This would validate ANOTHER scenario: An IPv6-only access service installs NAT64 but does not provide a method to obtain suitable IPv6 destinations for IPv4-only DNS names, so subscribers fail by hostname. The specific correction here is: Align both ends to a common supported IS-IS adjacency level with consistent interface settings.

Question 499

Which network protocol or forwarding behavior explains the following issue: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only.

  1. IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default.
  2. Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled.
  3. Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information.
  4. Route targets control VPN route distribution and should not be treated as ordinary public BGP communities.

Explanation

Correct Answer

C:

Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information. This explains the investigated issue: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. The approved corrective response is: Align both ends to a common supported IS-IS adjacency level with consistent interface settings.

Incorrect Answers

A:

IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default. That explains a DIFFERENT scenario: An IS-IS L2 router forms adjacency but traffic chooses a high-latency optical link because the interface metric was left at a low default. The mechanism to prioritize for this question is: Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information.

B:

Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled. That explains a DIFFERENT scenario: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. The mechanism to prioritize for this question is: Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information.

D:

Route targets control VPN route distribution and should not be treated as ordinary public BGP communities. That explains a DIFFERENT scenario: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. The mechanism to prioritize for this question is: Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information.

Question 500

A core network change board wants to avoid: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. Which ongoing safeguard fits best?

  1. Validate NET configuration and IS-IS levels during provisioning.
  2. Document each node's IS-IS level and area role before topology extensions.
  3. Use a peer inventory to preflight local and remote AS values.
  4. Add a common-level check to link commissioning scripts.

Explanation

Correct Answer

D:

Add a common-level check to link commissioning scripts. This helps prevent recurrence of the issue: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. Acceptance evidence should be: A lab peering test establishes a stable adjacency and exchanges the intended LSPs.

Incorrect Answers

A:

Validate NET configuration and IS-IS levels during provisioning. That is a sensible control for ANOTHER scenario: A core interface comes up but its IS-IS hellos never result in adjacency because peer system IDs use incompatible area addressing on L1-only neighbors. It is less targeted to this issue than: Add a common-level check to link commissioning scripts.

B:

Document each node's IS-IS level and area role before topology extensions. That is a sensible control for ANOTHER scenario: Two provider core routers form an IS-IS L1 adjacency but do not exchange a prefix from another area because the engineer assumes L1 routers have universal interarea visibility. It is less targeted to this issue than: Add a common-level check to link commissioning scripts.

C:

Use a peer inventory to preflight local and remote AS values. That is a sensible control for ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. It is less targeted to this issue than: Add a common-level check to link commissioning scripts.