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 63

Question 620

After addressing: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. Which recurring service assurance check is most useful?

  1. Include both IGMP and MLD listener tests on dual-stack access nodes.
  2. Test DR state when changing multicast LAN interfaces.
  3. Validate host and router IGMPv3 compatibility before deploying SSM services.
  4. Inspect header encapsulation at both service demarcations after provider bridge changes.

Explanation

Correct Answer

B:

Test DR state when changing multicast LAN interfaces. This helps prevent recurrence of the issue: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. Acceptance evidence should be: One intended DR is elected and the shared LAN emits the expected controlled PIM behavior.

Incorrect Answers

A:

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: Test DR state when changing multicast LAN interfaces.

C:

Validate host and router IGMPv3 compatibility before deploying SSM services. That is a sensible control for ANOTHER scenario: A multicast source sends video to an SSM group, but an access router uses IGMPv2 joins without source specification and receivers see no stream. It is less targeted to this issue than: Test DR state when changing multicast LAN interfaces.

D:

Inspect header encapsulation at both service demarcations after provider bridge changes. That is a sensible control for ANOTHER scenario: A carrier backbone applies provider bridging with 802.1ah MAC-in-MAC but its edge fails to strip the outer backbone header, so customer switches receive unknown backbone addresses. It is less targeted to this issue than: Test DR state when changing multicast LAN interfaces.

Question 621

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

  1. Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment.
  2. Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class.
  3. Align the configured Inter-AS VPN option and VPN route-label signaling at the authorized provider border nodes.
  4. Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification.

Explanation

Correct Answer

D:

Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks. Verify success by: During deliberate congestion, both sites show the intended class distribution and measurable queuing behavior.

Incorrect Answers

A:

Re-mark untrusted customer CS6 traffic according to the provider ingress trust policy while preserving genuine internal control traffic treatment. This would respond to a DIFFERENT fictional service-provider network issue: A customer sends traffic marked CS6 from its access port and expects unlimited priority throughout the provider despite not purchasing a network-control service class. It does not directly address the current situation: 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.

B:

Preserve the contracted classification through each applicable policy stage and map EF to the intended low-latency forwarding class. This would respond to a DIFFERENT fictional service-provider network issue: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. It does not directly address the current situation: 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.

C:

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

Question 622

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

  1. During deliberate congestion, both sites show the intended class distribution and measurable queuing behavior.
  2. A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy.
  3. Customer test packets receive the contracted class, and provider protocol packets retain protected control priority.
  4. Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss.

Explanation

Correct Answer

A:

During deliberate congestion, both sites show the intended class distribution and measurable queuing behavior. This confirms the approved response: Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification. It is relevant because: Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.

Incorrect Answers

B:

A rate-controlled test reaches the agreed throughput while excess traffic is buffered or scheduled within policy. This would validate ANOTHER scenario: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. The specific correction here is: Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification.

C:

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: Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification.

D:

Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss. This would validate ANOTHER 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 specific correction here is: Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification.

Question 623

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

  1. Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission.
  2. Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.
  3. Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters.
  4. Multicast forwarding uses Reverse Path Forwarding checks to avoid loops by selecting a valid path toward the source.

Explanation

Correct Answer

B:

Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks. This explains the investigated 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. The approved corrective response is: Attach the required egress scheduler and queue policy at each congestible link while retaining correct ingress classification.

Incorrect Answers

A:

Policing typically drops or remarks traffic above a threshold, whereas shaping queues traffic to smooth transmission. That explains a DIFFERENT scenario: An access policy applies a strict policer to interactive traffic and expects it to smooth bursts like a shaper, resulting in avoidable packet discards. The mechanism to prioritize for this question is: Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.

C:

Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters. That explains a DIFFERENT scenario: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. The mechanism to prioritize for this question is: Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.

D:

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: Classification and marking label traffic, but congestion handling depends on actual queue and scheduling policies at bottlenecks.

Question 624

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

  1. Record shaper configuration and measured burst response for each access product.
  2. Audit per-hop QoS markings and queue drops during service activation.
  3. Verify deployed service policies on every physical and logical egress bottleneck.
  4. Document the selected inter-AS option and verify service labels at each boundary.

Explanation

Correct Answer

C:

Verify deployed service policies on every physical and logical egress bottleneck. This helps prevent recurrence of the 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. Acceptance evidence should be: During deliberate congestion, both sites show the intended class distribution and measurable queuing behavior.

Incorrect Answers

A:

Record shaper configuration and measured burst response for each access product. That is a sensible control for ANOTHER scenario: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. It is less targeted to this issue than: Verify deployed service policies on every physical and logical egress bottleneck.

B:

Audit per-hop QoS markings and queue drops during service activation. That is a sensible control for ANOTHER scenario: A provider classifies customer voice using DSCP EF at ingress but a later output policy remarks it to best effort, causing jitter under congestion. It is less targeted to this issue than: Verify deployed service policies on every physical and logical egress bottleneck.

D:

Document the selected inter-AS option and verify service labels at each boundary. That is a sensible control for 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. It is less targeted to this issue than: Verify deployed service policies on every physical and logical egress bottleneck.

Question 625

At a multi-region fiber backbone operator, an engineering review finds: 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. Which change most directly corrects the service problem?

  1. Hold the overload condition until the router is ready to carry transit traffic and validate adjacency and route-table convergence.
  2. Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route.
  3. Align both ends to a common supported IS-IS adjacency level with consistent interface settings.
  4. Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.

Explanation

Correct Answer

A:

Hold the overload condition until the router is ready to carry transit traffic and validate adjacency and route-table convergence. This directly addresses the fictional service-provider network case: 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 technical mechanism is: The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance. Verify success by: During restart testing, other routers avoid the node for transit until its forwarding state is ready.

Incorrect Answers

B:

Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. It does not directly address the current situation: 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.

C:

Align both ends to a common supported IS-IS adjacency level with consistent interface settings. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: 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.

D:

Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology. This would respond to a DIFFERENT fictional service-provider network issue: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. It does not directly address the current situation: 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.

Question 626

For a multi-region fiber backbone operator, operators addressed: 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. What is the strongest acceptance evidence?

  1. Both routers report the intended adjacency level and the local area route becomes reachable.
  2. During restart testing, other routers avoid the node for transit until its forwarding state is ready.
  3. Route calculation shifts the test prefix to the expected lower-cost path without interrupting control adjacencies.
  4. The prefix becomes usable with a resolved next hop while the IGP remains stable.

Explanation

Correct Answer

B:

During restart testing, other routers avoid the node for transit until its forwarding state is ready. This confirms the approved response: Hold the overload condition until the router is ready to carry transit traffic and validate adjacency and route-table convergence. It is relevant because: The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance.

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: Hold the overload condition until the router is ready to carry transit traffic and validate adjacency and route-table convergence.

C:

Route calculation shifts the test prefix to the expected lower-cost path without interrupting control adjacencies. This would validate ANOTHER 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 specific correction here is: Hold the overload condition until the router is ready to carry transit traffic and validate adjacency and route-table convergence.

D:

The prefix becomes usable with a resolved next hop while the IGP remains stable. This would validate ANOTHER scenario: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. The specific correction here is: Hold the overload condition until the router is ready to carry transit traffic and validate adjacency and route-table convergence.

Question 627

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

  1. IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability.
  2. IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default.
  3. The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance.
  4. MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.

Explanation

Correct Answer

C:

The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance. This explains the investigated issue: 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 approved corrective response is: Hold the overload condition until the router is ready to carry transit traffic and validate adjacency and route-table convergence.

Incorrect Answers

A:

IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance.

B:

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: The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance.

D:

MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation. That explains a DIFFERENT scenario: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. The mechanism to prioritize for this question is: The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance.

Question 628

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

  1. Perform IPv6 topology capability verification for every new core node.
  2. Maintain dual-stack adjacency and LSDB checks after MT feature changes.
  3. Test deterministic mapping and log lookup as part of CGNAT capacity exercises.
  4. Automate overload clearance only after readiness gates pass.

Explanation

Correct Answer

D:

Automate overload clearance only after readiness gates pass. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: During restart testing, other routers avoid the node for transit until its forwarding state is ready.

Incorrect Answers

A:

Perform IPv6 topology capability verification for every new core node. That is a sensible control for ANOTHER scenario: A new IPv6-only service is added to an IS-IS core, but routers run a single topology configuration where the IPv6 reachability bits are not negotiated consistently. It is less targeted to this issue than: Automate overload clearance only after readiness gates pass.

B:

Maintain dual-stack adjacency and LSDB checks after MT feature changes. That is a sensible control for ANOTHER scenario: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. It is less targeted to this issue than: Automate overload clearance only after readiness gates pass.

C:

Test deterministic mapping and log lookup as part of CGNAT capacity exercises. That is a sensible control for ANOTHER scenario: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. It is less targeted to this issue than: Automate overload clearance only after readiness gates pass.

Question 629

A carrier service activation check discovers: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. Which action best restores the intended behavior?

  1. Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan.
  2. Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.
  3. Verify the DR/BDR design and inspect Full adjacencies with the designated router rather than forcing every DROTHER to Full.
  4. Set the intended IS-IS wide metric on the optical link based on approved transport cost.

Explanation

Correct Answer

B:

Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context. This directly addresses the fictional service-provider network case: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. The technical mechanism is: IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally. Verify success by: Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address.

Incorrect Answers

A:

Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan. This would respond to a DIFFERENT fictional service-provider network issue: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links. It does not directly address the current situation: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management.

C:

Verify the DR/BDR design and inspect Full adjacencies with the designated router rather than forcing every DROTHER to Full. This would respond to a DIFFERENT fictional service-provider network issue: A multiaccess OSPF network forms neighbor relationships but routes stay stuck at 2-Way between two DROTHER peers, and the operator repeatedly resets them. It does not directly address the current situation: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management.

D:

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: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management.

Question 630

Following a supported configuration correction, the original issue was: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. Which observation verifies success?

  1. Valid component destinations work and an unassigned prefix does not loop indefinitely.
  2. OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability.
  3. Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address.
  4. The eBGP FSM reaches Established and the peer's AS is recorded correctly.

Explanation

Correct Answer

C:

Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address. This confirms the approved response: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context. It is relevant because: IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally.

Incorrect Answers

A:

Valid component destinations work and an unassigned prefix does not loop indefinitely. This would validate ANOTHER scenario: An ABR summarizes branch routes into one large prefix that points into an area missing part of the address space, leading to a forwarding loop for unallocated addresses. The specific correction here is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.

B:

OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability. This would validate ANOTHER scenario: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. The specific correction here is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.

D:

The eBGP FSM reaches Established and the peer's AS is recorded correctly. This would validate ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. The specific correction here is: Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.