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 16

Question 150

Following a supported configuration correction, the original issue was: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. Which observation verifies success?

  1. In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues.
  2. Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session.
  3. Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst.
  4. A simulated restart restores service with the approved subscriber policy intact.

Explanation

Correct Answer

C:

Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst. This confirms the approved response: Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies. It is relevant because: Control-plane policing acts on packets punted to route-processing functions rather than ordinary transit forwarding.

Incorrect Answers

A:

In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues. This would validate ANOTHER scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. The specific correction here is: Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.

B:

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: Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.

D:

A simulated restart restores service with the approved subscriber policy intact. This would validate ANOTHER scenario: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. The specific correction here is: Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.

Question 151

At a carrier automation platform team, an engineer examines: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. Which technical principle is most applicable?

  1. BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity.
  2. LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core.
  3. Maximum Allocation Model and Russian Dolls Model partition reservable bandwidth differently for traffic-engineering classes.
  4. Control-plane policing acts on packets punted to route-processing functions rather than ordinary transit forwarding.

Explanation

Correct Answer

D:

Control-plane policing acts on packets punted to route-processing functions rather than ordinary transit forwarding. This explains the investigated issue: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. The approved corrective response is: Configure supported LPTS or CoPP classifications and policers to protect necessary control traffic without suppressing routing adjacencies.

Incorrect Answers

A:

BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity. That explains a DIFFERENT scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. The mechanism to prioritize for this question is: Control-plane policing acts on packets punted to route-processing functions rather than ordinary transit forwarding.

B:

LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core. That explains a DIFFERENT scenario: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. The mechanism to prioritize for this question is: Control-plane policing acts on packets punted to route-processing functions rather than ordinary transit forwarding.

C:

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: Control-plane policing acts on packets punted to route-processing functions rather than ordinary transit forwarding.

Question 152

For a carrier automation platform team, the change record describes: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. What preventive validation should be standard?

  1. Monitor class-specific drops and legitimate protocol health after policy updates.
  2. Require peer and prefix authorization and monitor FlowSpec rule impacts.
  3. Validate peer hop counts before applying TTL-security to multihop sessions.
  4. Run secret-scanning checks against network automation and management proxy logs.

Explanation

Correct Answer

A:

Monitor class-specific drops and legitimate protocol health after policy updates. This helps prevent recurrence of the issue: A network's IOS XR control processor is overwhelmed by bursts of ICMP and BGP packets after access ACLs are changed, even though the data-plane uplinks are uncongested. Acceptance evidence should be: Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst.

Incorrect Answers

B:

Require peer and prefix authorization and monitor FlowSpec rule impacts. That is a sensible control for ANOTHER scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. It is less targeted to this issue than: Monitor class-specific drops and legitimate protocol health after policy updates.

C:

Validate peer hop counts before applying TTL-security to multihop sessions. That is a sensible control for ANOTHER scenario: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. It is less targeted to this issue than: Monitor class-specific drops and legitimate protocol health after policy updates.

D:

Run secret-scanning checks against network automation and management proxy logs. That is a sensible control for ANOTHER scenario: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. It is less targeted to this issue than: Monitor class-specific drops and legitimate protocol health after policy updates.

Question 153

For a multi-tenant data transport provider, the failure is: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. Which authorized correction best addresses it?

  1. Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials.
  2. Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress.
  3. Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure.
  4. Identify the running IOS XR platform and follow its supported installation and operational command workflow.

Explanation

Correct Answer

C:

Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure. This directly addresses the fictional service-provider network case: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. The technical mechanism is: Authentication, authorization and accounting have different operational roles and redundancy must preserve auditability. Verify success by: A lab administrator change creates an attributable record on the healthy collector during primary-server failure.

Incorrect Answers

A:

Transmit the documented token through protected authorization headers over TLS and revoke any logged credentials. This would respond to a DIFFERENT fictional service-provider network issue: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. It does not directly address the current situation: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs.

B:

Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress. This would respond to a DIFFERENT fictional service-provider network issue: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path. It does not directly address the current situation: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs.

D:

Identify the running IOS XR platform and follow its supported installation and operational command workflow. This would respond to a DIFFERENT fictional service-provider network issue: A technician deploys IOS XE package commands to an IOS XR route processor, then misinterprets the command rejection as a missing license. It does not directly address the current situation: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs.

Question 154

After fixing the following network problem, what should the team verify: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs.

  1. A controlled request succeeds with credentials absent from URLs and audit logs.
  2. External negative tests fail while approved management hosts can read operational data with their assigned roles.
  3. A lab trace shows the correct encapsulation before and after the gateway with the customer prefix still reachable.
  4. A lab administrator change creates an attributable record on the healthy collector during primary-server failure.

Explanation

Correct Answer

D:

A lab administrator change creates an attributable record on the healthy collector during primary-server failure. This confirms the approved response: Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure. It is relevant because: Authentication, authorization and accounting have different operational roles and redundancy must preserve auditability.

Incorrect Answers

A:

A controlled request succeeds with credentials absent from URLs and audit logs. This would validate ANOTHER scenario: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. The specific correction here is: Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure.

B:

External negative tests fail while approved management hosts can read operational data with their assigned roles. This would validate ANOTHER scenario: A provider's router management API is reachable from the public internet using a broad admin token, even though the operations team uses a dedicated management VRF. The specific correction here is: Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure.

C:

A lab trace shows the correct encapsulation before and after the gateway with the customer prefix still reachable. This would validate 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. The specific correction here is: Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure.

Question 155

A carrier root-cause review considers: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. What underlying mechanism explains this?

  1. Authentication, authorization and accounting have different operational roles and redundancy must preserve auditability.
  2. Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization.
  3. Source traceback across NAT and provider cores requires cross-device path and translation context.
  4. DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state.

Explanation

Correct Answer

A:

Authentication, authorization and accounting have different operational roles and redundancy must preserve auditability. This explains the investigated issue: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. The approved corrective response is: Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure.

Incorrect Answers

B:

Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization. That explains a DIFFERENT scenario: A provider's router management API is reachable from the public internet using a broad admin token, even though the operations team uses a dedicated management VRF. The mechanism to prioritize for this question is: Authentication, authorization and accounting have different operational roles and redundancy must preserve auditability.

C:

Source traceback across NAT and provider cores requires cross-device path and translation context. That explains a DIFFERENT scenario: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path. The mechanism to prioritize for this question is: Authentication, authorization and accounting have different operational roles and redundancy must preserve auditability.

D:

DiffServ groups traffic into forwarding classes whereas IntServ-style reservation can entail per-flow state. That explains a DIFFERENT scenario: A designer replaces all DiffServ core queues with per-flow IntServ reservations for millions of broadband sessions, exhausting router control resources. The mechanism to prioritize for this question is: Authentication, authorization and accounting have different operational roles and redundancy must preserve auditability.

Question 156

After addressing: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. Which recurring service assurance check is most useful?

  1. Inventory exposed management listeners after each platform upgrade.
  2. Test AAA failure behavior and accounting completeness at scheduled intervals.
  3. Keep flow retention and time synchronization aligned with incident investigation requirements.
  4. Maintain an inventory of per-hop encapsulation support and interworking validation tests.

Explanation

Correct Answer

B:

Test AAA failure behavior and accounting completeness at scheduled intervals. This helps prevent recurrence of the issue: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. Acceptance evidence should be: A lab administrator change creates an attributable record on the healthy collector during primary-server failure.

Incorrect Answers

A:

Inventory exposed management listeners after each platform upgrade. That is a sensible control for ANOTHER scenario: A provider's router management API is reachable from the public internet using a broad admin token, even though the operations team uses a dedicated management VRF. It is less targeted to this issue than: Test AAA failure behavior and accounting completeness at scheduled intervals.

C:

Keep flow retention and time synchronization aligned with incident investigation requirements. That is a sensible control for ANOTHER scenario: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path. It is less targeted to this issue than: Test AAA failure behavior and accounting completeness at scheduled intervals.

D:

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: Test AAA failure behavior and accounting completeness at scheduled intervals.

Question 157

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

  1. Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary.
  2. Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.
  3. Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy.
  4. Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope.

Explanation

Correct Answer

D:

Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope. This directly addresses the fictional service-provider network case: 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. The technical mechanism is: Remotely Triggered Black Hole routing relies on agreed route policy and communities to steer selected traffic to a null destination. Verify success by: A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable.

Incorrect Answers

A:

Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary. This would respond to a DIFFERENT fictional service-provider network issue: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. It does not directly address the current situation: 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.

B:

Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints. This would respond to a DIFFERENT fictional service-provider network issue: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. It does not directly address the current situation: 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.

C:

Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy. This would respond to a DIFFERENT fictional service-provider network issue: A provider builds an optical routed backbone but still treats every DWDM wavelength change as independent from IP restoration, creating contradictory failover policies. It does not directly address the current situation: 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.

Question 158

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

  1. A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable.
  2. Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable.
  3. Benign IPv6 reachability and ND continue while the prohibited probe traffic is blocked.
  4. The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.

Explanation

Correct Answer

A:

A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable. This confirms the approved response: Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope. It is relevant because: Remotely Triggered Black Hole routing relies on agreed route policy and communities to steer selected traffic to a null destination.

Incorrect Answers

B:

Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable. This would validate 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. The specific correction here is: Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope.

C:

Benign IPv6 reachability and ND continue while the prohibited probe traffic is blocked. This would validate ANOTHER scenario: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. The specific correction here is: Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope.

D:

The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected. This would validate ANOTHER scenario: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. The specific correction here is: Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope.

Question 159

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

  1. Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths.
  2. Remotely Triggered Black Hole routing relies on agreed route policy and communities to steer selected traffic to a null destination.
  3. IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic.
  4. DOCSIS and xPON are different access technologies with different physical and control-plane termination systems.

Explanation

Correct Answer

B:

Remotely Triggered Black Hole routing relies on agreed route policy and communities to steer selected traffic to a null destination. This explains the investigated issue: 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. The approved corrective response is: Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope.

Incorrect Answers

A:

Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: Remotely Triggered Black Hole routing relies on agreed route policy and communities to steer selected traffic to a null destination.

C:

IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic. That explains a DIFFERENT scenario: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. The mechanism to prioritize for this question is: Remotely Triggered Black Hole routing relies on agreed route policy and communities to steer selected traffic to a null destination.

D:

DOCSIS and xPON are different access technologies with different physical and control-plane termination systems. That explains a DIFFERENT scenario: A wholesale provider expects DOCSIS cable access equipment to terminate xPON optical network units and finds that provisioning never completes. The mechanism to prioritize for this question is: Remotely Triggered Black Hole routing relies on agreed route policy and communities to steer selected traffic to a null destination.

Question 160

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

  1. Verify MACsec secure-channel state after optics and link-aggregation changes.
  2. Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance.
  3. Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.
  4. Require peer and prefix authorization and monitor FlowSpec rule impacts.

Explanation

Correct Answer

C:

Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable.

Incorrect Answers

A:

Verify MACsec secure-channel state after optics and link-aggregation changes. That is a sensible control for ANOTHER scenario: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. It is less targeted to this issue than: Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.

B:

Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance. That is a sensible control for ANOTHER scenario: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. It is less targeted to this issue than: Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.

D:

Require peer and prefix authorization and monitor FlowSpec rule impacts. That is a sensible control for ANOTHER scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. It is less targeted to this issue than: Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.