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 29

Question 280

For an inter-AS service aggregation carrier, the change record describes: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. What preventive validation should be standard?

  1. Document DS-TE bandwidth constraints and test admission cases before enabling policy.
  2. Verify flow-label behavior during software and hashing-policy upgrades.
  3. Maintain a tested ingress-to-egress marking map for each QoS service class.
  4. Validate peer hop counts before applying TTL-security to multihop sessions.

Explanation

Correct Answer

A:

Document DS-TE bandwidth constraints and test admission cases before enabling policy. This helps prevent recurrence of the issue: A transport planner provisions an RSVP bandwidth pool using MAM assumptions but the network is configured for RDM, causing unexpected class bandwidth borrowing. Acceptance evidence should be: An engineered pair of LSP requests is admitted or rejected in line with the expected class-type bandwidth budget.

Incorrect Answers

B:

Verify flow-label behavior during software and hashing-policy upgrades. That is a sensible control for ANOTHER scenario: An IPv6 multicast-sensitive telemetry application changes the IPv6 flow label every packet and load-sharing routers distribute a single transport stream across many paths. It is less targeted to this issue than: Document DS-TE bandwidth constraints and test admission cases before enabling policy.

C:

Maintain a tested ingress-to-egress marking map for each QoS service class. That is a sensible control for ANOTHER scenario: A provider carries a customer's EF-marked voice traffic across an MPLS core but rewrites both customer DSCP and MPLS EXP indiscriminately, breaking the promised QoS trust boundary. It is less targeted to this issue than: Document DS-TE bandwidth constraints and test admission cases before enabling policy.

D:

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: Document DS-TE bandwidth constraints and test admission cases before enabling policy.

Question 281

For a regional service-provider operations center, the failure is: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. Which authorized correction best addresses it?

  1. Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action.
  2. Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer.
  3. Restrict LDP discovery, sessions and label allocation using peer authentication and supported label filters.
  4. Coordinate optical restoration and IP-layer convergence objectives using a documented routed-optical failure strategy.

Explanation

Correct Answer

C:

Restrict LDP discovery, sessions and label allocation using peer authentication and supported label filters. This directly addresses the fictional service-provider network case: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. The technical mechanism is: LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core. Verify success by: Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session.

Incorrect Answers

A:

Validate FlowSpec origin and permitted match components, then install the narrowly approved mitigation action. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment.

B:

Enable supported BGP Generalized TTL Security Mechanism with an appropriate neighbor distance on the intended peer. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment.

D:

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 accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment.

Question 282

After fixing the following network problem, what should the team verify: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment.

  1. The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.
  2. Control-plane counters show bounded unwanted traffic while BGP and IGP keepalives continue under a test burst.
  3. Synthetic timing and delay tests remain within the RAN interface limits at full traffic load.
  4. Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session.

Explanation

Correct Answer

D:

Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session. This confirms the approved response: Restrict LDP discovery, sessions and label allocation using peer authentication and supported label filters. It is relevant because: LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core.

Incorrect Answers

A:

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: Restrict LDP discovery, sessions and label allocation using peer authentication and supported label filters.

B:

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: Restrict LDP discovery, sessions and label allocation using peer authentication and supported label filters.

C:

Synthetic timing and delay tests remain within the RAN interface limits at full traffic load. This would validate ANOTHER scenario: A 5G fronthaul transport team treats a RAN radio-to-distributed-unit path as an ordinary best-effort internet uplink and sees timing instability during peak load. The specific correction here is: Restrict LDP discovery, sessions and label allocation using peer authentication and supported label filters.

Question 283

A carrier root-cause review considers: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. What underlying mechanism explains this?

  1. LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core.
  2. GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic.
  3. BGP FlowSpec can distribute fine-grained traffic-filtering actions that are dangerous if accepted without authorization and specificity.
  4. Cisco IOS software families have different feature and programmability interfaces despite overlapping CLI conventions.

Explanation

Correct Answer

A:

LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core. This explains the investigated issue: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. The approved corrective response is: Restrict LDP discovery, sessions and label allocation using peer authentication and supported label filters.

Incorrect Answers

B:

GTSM uses an expected near-hop TTL to constrain spoofed BGP control traffic. That explains a DIFFERENT 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 mechanism to prioritize for this question is: LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core.

C:

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: LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core.

D:

Cisco IOS software families have different feature and programmability interfaces despite overlapping CLI conventions. That explains a DIFFERENT scenario: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases. The mechanism to prioritize for this question is: LDP peer trust and label distribution are separate controls that should both be scoped in an MPLS core.

Question 284

After addressing: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. Which recurring service assurance check is most useful?

  1. Require peer and prefix authorization and monitor FlowSpec rule impacts.
  2. Audit LDP adjacencies and label allocation policy against topology inventory.
  3. Monitor class-specific drops and legitimate protocol health after policy updates.
  4. Retest compute placement and performance after NFVI scheduler changes.

Explanation

Correct Answer

B:

Audit LDP adjacencies and label allocation policy against topology inventory. This helps prevent recurrence of the issue: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. Acceptance evidence should be: Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session.

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: Audit LDP adjacencies and label allocation policy against topology inventory.

C:

Monitor class-specific drops and legitimate protocol health after policy updates. That is a sensible control for 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. It is less targeted to this issue than: Audit LDP adjacencies and label allocation policy against topology inventory.

D:

Retest compute placement and performance after NFVI scheduler changes. That is a sensible control for ANOTHER scenario: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. It is less targeted to this issue than: Audit LDP adjacencies and label allocation policy against topology inventory.

Question 285

A provider backbone escalation identifies: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path. What should the network team implement?

  1. Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation.
  2. Repair AAA server group failover and command-accounting configuration while retaining an approved emergency access procedure.
  3. Reapply the documented VNF connectivity, virtual switching and service-chain attachments on the new NFV infrastructure.
  4. Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress.

Explanation

Correct Answer

D:

Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Source traceback across NAT and provider cores requires cross-device path and translation context. Verify success by: A controlled traffic simulation identifies the correct ingress interface and mapped subscriber session without exposing unrelated customers.

Incorrect Answers

A:

Bind management endpoints to the restricted VRF or access policy and enforce scoped authenticated HTTPS with credential rotation. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path.

B:

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 broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path.

C:

Reapply the documented VNF connectivity, virtual switching and service-chain attachments on the new NFV infrastructure. This would respond to a DIFFERENT fictional service-provider network issue: A service provider moves a virtualized firewall to a new NFV host but neglects to recreate the virtual interfaces and cannot forward subscriber traffic. It does not directly address the current situation: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path.

Question 286

A service-provider operations test targets: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path. Which result is required?

  1. A controlled traffic simulation identifies the correct ingress interface and mapped subscriber session without exposing unrelated customers.
  2. A controlled request succeeds with credentials absent from URLs and audit logs.
  3. A lab administrator change creates an attributable record on the healthy collector during primary-server failure.
  4. A capability check selects a valid interface for each device and rejects models not advertised by the platform.

Explanation

Correct Answer

A:

A controlled traffic simulation identifies the correct ingress interface and mapped subscriber session without exposing unrelated customers. This confirms the approved response: Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress. It is relevant because: Source traceback across NAT and provider cores requires cross-device path and translation context.

Incorrect Answers

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: Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress.

C:

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: Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress.

D:

A capability check selects a valid interface for each device and rejects models not advertised by the platform. This would validate ANOTHER scenario: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases. The specific correction here is: Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress.

Question 287

A provider troubleshooting note states: A broadband DDoS traceback requires identifying the real ingress edge but the SOC correlates only NAT-translated destination addresses, losing the source transit path. Which mechanism is central?

  1. URL query strings can leak reusable secrets through access logs and monitoring systems.
  2. Source traceback across NAT and provider cores requires cross-device path and translation context.
  3. Management-plane access must be isolated from subscriber-facing forwarding paths and protected by authorization.
  4. An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router.

Explanation

Correct Answer

B:

Source traceback across NAT and provider cores requires cross-device path and translation context. This explains the investigated 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. The approved corrective response is: Correlate flow records, interface counters and CGNAT translation logs with synchronized timestamps to locate the ingress.

Incorrect Answers

A:

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: Source traceback across NAT and provider cores requires cross-device path and translation context.

C:

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: Source traceback across NAT and provider cores requires cross-device path and translation context.

D:

An SRv6 segment list is encoded in IPv6 forwarding constructs and cannot be processed as an MPLS label stack by a non-SRv6 router. That explains a DIFFERENT scenario: A core team routes an SRv6 service through legacy MPLS-only nodes without defining an interworking point, so traffic loses its intended segment behavior. The mechanism to prioritize for this question is: Source traceback across NAT and provider cores requires cross-device path and translation context.

Question 288

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

  1. Run secret-scanning checks against network automation and management proxy logs.
  2. Test AAA failure behavior and accounting completeness at scheduled intervals.
  3. Keep flow retention and time synchronization aligned with incident investigation requirements.
  4. Revalidate source-verification mode after subscriber routing changes.

Explanation

Correct Answer

C:

Keep flow retention and time synchronization aligned with incident investigation requirements. This helps prevent recurrence of the 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. Acceptance evidence should be: A controlled traffic simulation identifies the correct ingress interface and mapped subscriber session without exposing unrelated customers.

Incorrect Answers

A:

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: Keep flow retention and time synchronization aligned with incident investigation requirements.

B:

Test AAA failure behavior and accounting completeness at scheduled intervals. That is a sensible control for ANOTHER scenario: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. It is less targeted to this issue than: Keep flow retention and time synchronization aligned with incident investigation requirements.

D:

Revalidate source-verification mode after subscriber routing changes. That is a sensible control for ANOTHER scenario: A PE applies loose uRPF on a single-homed subscriber port but an upstream source-spoofing event still enters through a route that exists via another edge. It is less targeted to this issue than: Keep flow retention and time synchronization aligned with incident investigation requirements.

Question 289

At a multi-region fiber backbone operator, an engineering review finds: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. Which change most directly corrects the service problem?

  1. Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.
  2. Use the provider's documented RTBH community and next-hop policy with tightly constrained victim prefix scope.
  3. Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary.
  4. Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture.

Explanation

Correct Answer

A:

Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints. This directly addresses the fictional service-provider network case: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. The technical mechanism is: MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption. Verify success by: An authorized lab peer establishes an encrypted link and passes the intended L3 adjacency and data traffic.

Incorrect Answers

B:

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: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors.

C:

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: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors.

D:

Engineer the xhaul path using the documented latency, synchronization, capacity and isolation targets for the radio architecture. This would respond to a DIFFERENT fictional service-provider network issue: A 5G fronthaul transport team treats a RAN radio-to-distributed-unit path as an ordinary best-effort internet uplink and sees timing instability during peak load. It does not directly address the current situation: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors.

Question 290

For a multi-region fiber backbone operator, operators addressed: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. What is the strongest acceptance evidence?

  1. A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable.
  2. An authorized lab peer establishes an encrypted link and passes the intended L3 adjacency and data traffic.
  3. Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable.
  4. The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.

Explanation

Correct Answer

B:

An authorized lab peer establishes an encrypted link and passes the intended L3 adjacency and data traffic. This confirms the approved response: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints. It is relevant because: MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption.

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: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.

C:

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: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.

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: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.