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 3

Question 20

A core network change board wants to avoid: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. Which ongoing safeguard fits best?

  1. Require peer and prefix authorization and monitor FlowSpec rule impacts.
  2. Audit LDP adjacencies and label allocation policy against topology inventory.
  3. Run restart and rescheduling persistence drills before production upgrade windows.
  4. Validate peer hop counts before applying TTL-security to multihop sessions.

Explanation

Correct Answer

D:

Validate peer hop counts before applying TTL-security to multihop sessions. This helps prevent recurrence of the issue: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. Acceptance evidence should be: The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.

Incorrect Answers

A:

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: Validate peer hop counts before applying TTL-security to multihop sessions.

B:

Audit LDP adjacencies and label allocation policy against topology inventory. That is a sensible control for ANOTHER scenario: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. It is less targeted to this issue than: Validate peer hop counts before applying TTL-security to multihop sessions.

C:

Run restart and rescheduling persistence drills before production upgrade windows. That is a sensible control for ANOTHER scenario: A provider stores a VNF configuration exclusively on the ephemeral container filesystem and loses subscriber policy after an orchestrator restarts the instance. It is less targeted to this issue than: Validate peer hop counts before applying TTL-security to multihop sessions.

Question 21

A carrier service activation check discovers: 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. Which action best restores the intended behavior?

  1. Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress.
  2. Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation.
  3. Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure.
  4. Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.

Explanation

Correct Answer

B:

Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization. Verify success by: External negative tests fail while approved management hosts can read operational data with their assigned roles.

Incorrect Answers

A:

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

C:

Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure. This would respond to a DIFFERENT fictional service-provider network issue: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. It does not directly address the current situation: 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.

D:

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

Question 22

Following a supported configuration correction, the original issue was: 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. Which observation verifies success?

  1. A lab administrator change creates an attributable record on the healthy collector during primary-server failure.
  2. A controlled request succeeds with credentials absent from URLs and audit logs.
  3. External negative tests fail while approved management hosts can read operational data with their assigned roles.
  4. Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst.

Explanation

Correct Answer

C:

External negative tests fail while approved management hosts can read operational data with their assigned roles. This confirms the approved response: Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation. It is relevant because: Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization.

Incorrect Answers

A:

A lab administrator change creates an attributable record on the healthy collector during primary-server failure. This would validate ANOTHER scenario: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. The specific correction here is: Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation.

B:

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: Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation.

D:

Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst. This would validate ANOTHER scenario: 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 specific correction here is: Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation.

Question 23

At a mobile packet-core transport operator, an engineer examines: 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. Which technical principle is most applicable?

  1. Source traceback across NAT and provider cores requires cross-device path and translation context.
  2. URL query strings can leak reusable secrets through access logs and monitoring systems.
  3. Application hosting support is platform-specific and competing workloads can impact critical control processes.
  4. Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization.

Explanation

Correct Answer

D:

Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization. This explains the investigated issue: 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 approved corrective response is: Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation.

Incorrect Answers

A:

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: Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization.

B:

URL query strings can leak reusable secrets through access logs and monitoring systems. That explains a DIFFERENT scenario: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. The mechanism to prioritize for this question is: Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization.

C:

Application hosting support is platform-specific and competing workloads can impact critical control processes. That explains a DIFFERENT scenario: An operations team deploys an application container directly onto a router control processor without checking vendor-supported hosting resources or isolation limits. The mechanism to prioritize for this question is: Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization.

Question 24

For a mobile packet-core transport operator, the change record describes: 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. What preventive validation should be standard?

  1. Inventory exposed management listeners after each platform upgrade.
  2. Run secret-scanning checks against network automation and management proxy logs.
  3. Keep flow retention and time synchronization aligned with incident investigation requirements.
  4. Require postboot image attestation and rollback readiness in change acceptance.

Explanation

Correct Answer

A:

Inventory exposed management listeners after each platform upgrade. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: External negative tests fail while approved management hosts can read operational data with their assigned roles.

Incorrect Answers

B:

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: Inventory exposed management listeners after each platform upgrade.

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: Inventory exposed management listeners after each platform upgrade.

D:

Require postboot image attestation and rollback readiness in change acceptance. That is a sensible control for ANOTHER scenario: After an IOS XE image update, the route processor boots but a router retains an old package set because the team updated the boot variable without verifying install mode. It is less targeted to this issue than: Inventory exposed management listeners after each platform upgrade.

Question 25

For a managed VPN service carrier, the failure is: 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. Which authorized correction best addresses it?

  1. Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope.
  2. Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary.
  3. Choose strict or feasible-path uRPF as appropriate to the actual subscriber multihoming and reverse-route design.
  4. Use only the supported application-hosting environment with explicit CPU, memory, interface and lifecycle controls.

Explanation

Correct Answer

C:

Choose strict or feasible-path uRPF as appropriate to the actual subscriber multihoming and reverse-route design. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths. Verify success by: Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable.

Incorrect Answers

A:

Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: 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.

B:

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

D:

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

Question 26

After fixing the following network problem, what should the team verify: 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.

  1. A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable.
  2. Benign IPv6 reachability and ND continue while the prohibited probe traffic is blocked.
  3. In a benign test, only the intended attack tuple is filtered and legitimate same-prefix traffic continues.
  4. Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable.

Explanation

Correct Answer

D:

Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable. This confirms the approved response: Choose strict or feasible-path uRPF as appropriate to the actual subscriber multihoming and reverse-route design. It is relevant because: Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths.

Incorrect Answers

A:

A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable. This would validate 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. The specific correction here is: Choose strict or feasible-path uRPF as appropriate to the actual subscriber multihoming and reverse-route design.

B:

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: Choose strict or feasible-path uRPF as appropriate to the actual subscriber multihoming and reverse-route design.

C:

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: Choose strict or feasible-path uRPF as appropriate to the actual subscriber multihoming and reverse-route design.

Question 27

A carrier root-cause review considers: 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. What underlying mechanism explains this?

  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. MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption.
  4. Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation.

Explanation

Correct Answer

A:

Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths. This explains the investigated issue: 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 approved corrective response is: Choose strict or feasible-path uRPF as appropriate to the actual subscriber multihoming and reverse-route design.

Incorrect Answers

B:

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

C:

MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption. That explains a DIFFERENT scenario: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. The mechanism to prioritize for this question is: Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths.

D:

Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation. That explains a DIFFERENT scenario: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. The mechanism to prioritize for this question is: Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths.

Question 28

After addressing: 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. Which recurring service assurance check is most useful?

  1. Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.
  2. Revalidate source-verification mode after subscriber routing changes.
  3. Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance.
  4. Validate UNI and EVC service attributes against an end-to-end circuit acceptance matrix.

Explanation

Correct Answer

B:

Revalidate source-verification mode after subscriber routing changes. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable.

Incorrect Answers

A:

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: Revalidate source-verification mode after subscriber routing changes.

C:

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: Revalidate source-verification mode after subscriber routing changes.

D:

Validate UNI and EVC service attributes against an end-to-end circuit acceptance matrix. That is a sensible control for 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. It is less targeted to this issue than: Revalidate source-verification mode after subscriber routing changes.

Question 29

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

  1. Align both ends to a common supported IS-IS adjacency level with consistent interface settings.
  2. Reconcile the L1 area addresses or adjust the level participation according to the planned hierarchy.
  3. Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family.
  4. Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.

Explanation

Correct Answer

D:

Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design. This directly addresses the fictional service-provider network case: 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 technical mechanism is: IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability. Verify success by: A test prefix from the remote area appears in the intended routing table without unintended leaking of unrelated routes.

Incorrect Answers

A:

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

B:

Reconcile the L1 area addresses or adjust the level participation according to the planned hierarchy. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

C:

Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI. It does not directly address the current situation: 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.

Question 30

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

  1. A test prefix from the remote area appears in the intended routing table without unintended leaking of unrelated routes.
  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. During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load.

Explanation

Correct Answer

A:

A test prefix from the remote area appears in the intended routing table without unintended leaking of unrelated routes. This confirms the approved response: Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design. It is relevant because: IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability.

Incorrect Answers

B:

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: Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.

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: Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.

D:

During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load. This would validate ANOTHER scenario: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. The specific correction here is: Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.