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 6

Question 50

For a converged broadband aggregation team, operators addressed: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. What is the strongest acceptance evidence?

  1. Adjacency and LSP integrity counters remain stable during repeated authenticated hello exchanges.
  2. A lab adjacency reaches Full and the LSDB counts converge without permitting unrelated sources.
  3. In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target.
  4. A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target.

Explanation

Correct Answer

B:

A lab adjacency reaches Full and the LSDB counts converge without permitting unrelated sources. This confirms the approved response: Permit the required OSPF control traffic between approved peers at the correct interface policy boundary. It is relevant because: Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds.

Incorrect Answers

A:

Adjacency and LSP integrity counters remain stable during repeated authenticated hello exchanges. This would validate ANOTHER scenario: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. The specific correction here is: Permit the required OSPF control traffic between approved peers at the correct interface policy boundary.

C:

In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target. This would validate ANOTHER scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. The specific correction here is: Permit the required OSPF control traffic between approved peers at the correct interface policy boundary.

D:

A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target. This would validate ANOTHER scenario: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. The specific correction here is: Permit the required OSPF control traffic between approved peers at the correct interface policy boundary.

Question 51

Which network protocol or forwarding behavior explains the following issue: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment.

  1. Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization.
  2. A physical adjacency can exist without all configured address families exchanging usable reachability.
  3. Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds.
  4. Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length.

Explanation

Correct Answer

C:

Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds. This explains the investigated issue: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. The approved corrective response is: Permit the required OSPF control traffic between approved peers at the correct interface policy boundary.

Incorrect Answers

A:

Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization. That explains a DIFFERENT scenario: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. The mechanism to prioritize for this question is: Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds.

B:

A physical adjacency can exist without all configured address families exchanging usable reachability. That explains a DIFFERENT scenario: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. The mechanism to prioritize for this question is: Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds.

D:

Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length. That explains a DIFFERENT scenario: A BGP router holds multiple valid paths yet chooses an unanticipated route because one path has a smaller origin code, not because of a mistaken community. The mechanism to prioritize for this question is: Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds.

Question 52

A core network change board wants to avoid: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. Which ongoing safeguard fits best?

  1. Tune BFD to observed transport behavior and test at peak utilization.
  2. Verify IPv4/IPv6 route consistency after partial protocol changes.
  3. Maintain release-specific ISSU qualification and rollback documentation.
  4. Include protocol-specific reachability and adjacency checks after ACL changes.

Explanation

Correct Answer

D:

Include protocol-specific reachability and adjacency checks after ACL changes. This helps prevent recurrence of the issue: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. Acceptance evidence should be: A lab adjacency reaches Full and the LSDB counts converge without permitting unrelated sources.

Incorrect Answers

A:

Tune BFD to observed transport behavior and test at peak utilization. That is a sensible control for ANOTHER scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. It is less targeted to this issue than: Include protocol-specific reachability and adjacency checks after ACL changes.

B:

Verify IPv4/IPv6 route consistency after partial protocol changes. That is a sensible control for ANOTHER scenario: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. It is less targeted to this issue than: Include protocol-specific reachability and adjacency checks after ACL changes.

C:

Maintain release-specific ISSU qualification and rollback documentation. That is a sensible control for ANOTHER scenario: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. It is less targeted to this issue than: Include protocol-specific reachability and adjacency checks after ACL changes.

Question 53

A carrier service activation check discovers: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. Which action best restores the intended behavior?

  1. Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules.
  2. Use an appropriate NAT64/DNS64 service design or approved application gateway for IPv6-to-IPv4 reachability.
  3. Provide supported DNS64 synthesis or an equivalent discovery mechanism consistent with NAT64 deployment.
  4. Align stub-area configuration on the ABR and member routers and verify default advertisement.

Explanation

Correct Answer

B:

Use an appropriate NAT64/DNS64 service design or approved application gateway for IPv6-to-IPv4 reachability. This directly addresses the fictional service-provider network case: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. The technical mechanism is: NAT44 translates IPv4 addresses within one family and cannot by itself connect IPv6-only clients to IPv4-only servers. Verify success by: An IPv6-only test client resolves and reaches the target IPv4-only service through the transition gateway.

Incorrect Answers

A:

Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules. This would respond to a DIFFERENT fictional service-provider network issue: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. It does not directly address the current situation: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families.

C:

Provide supported DNS64 synthesis or an equivalent discovery mechanism consistent with NAT64 deployment. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6-only access service installs NAT64 but does not provide a method to obtain suitable IPv6 destinations for IPv4-only DNS names, so subscribers fail by hostname. It does not directly address the current situation: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families.

D:

Align stub-area configuration on the ABR and member routers and verify default advertisement. This would respond to a DIFFERENT fictional service-provider network issue: An OSPF stub area loses its expected default route when an engineer configures stub mode on the access router but not consistently on the area border router. It does not directly address the current situation: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families.

Question 54

Following a supported configuration correction, the original issue was: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. Which observation verifies success?

  1. A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload.
  2. Parallel test sessions resolve to unique external tuples and return to the correct subscriber.
  3. An IPv6-only test client resolves and reaches the target IPv4-only service through the transition gateway.
  4. A lab peering test establishes a stable adjacency and exchanges the intended LSPs.

Explanation

Correct Answer

C:

An IPv6-only test client resolves and reaches the target IPv4-only service through the transition gateway. This confirms the approved response: Use an appropriate NAT64/DNS64 service design or approved application gateway for IPv6-to-IPv4 reachability. It is relevant because: NAT44 translates IPv4 addresses within one family and cannot by itself connect IPv6-only clients to IPv4-only servers.

Incorrect Answers

A:

A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload. This would validate ANOTHER scenario: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. The specific correction here is: Use an appropriate NAT64/DNS64 service design or approved application gateway for IPv6-to-IPv4 reachability.

B:

Parallel test sessions resolve to unique external tuples and return to the correct subscriber. This would validate ANOTHER scenario: An ISP assigns customer IPv4 address blocks through CGNAT but configures identical port-set mappings on two subscribers behind the same public address, causing connection collisions. The specific correction here is: Use an appropriate NAT64/DNS64 service design or approved application gateway for IPv6-to-IPv4 reachability.

D:

A lab peering test establishes a stable adjacency and exchanges the intended LSPs. This would validate ANOTHER scenario: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. The specific correction here is: Use an appropriate NAT64/DNS64 service design or approved application gateway for IPv6-to-IPv4 reachability.

Question 55

At an inter-AS service aggregation carrier, an engineer examines: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. Which technical principle is most applicable?

  1. NAT64 forwarding requires an IPv6 destination representation of the IPv4 server, frequently supplied by DNS64.
  2. MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.
  3. OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them.
  4. NAT44 translates IPv4 addresses within one family and cannot by itself connect IPv6-only clients to IPv4-only servers.

Explanation

Correct Answer

D:

NAT44 translates IPv4 addresses within one family and cannot by itself connect IPv6-only clients to IPv4-only servers. This explains the investigated issue: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. The approved corrective response is: Use an appropriate NAT64/DNS64 service design or approved application gateway for IPv6-to-IPv4 reachability.

Incorrect Answers

A:

NAT64 forwarding requires an IPv6 destination representation of the IPv4 server, frequently supplied by DNS64. That explains a DIFFERENT scenario: An IPv6-only access service installs NAT64 but does not provide a method to obtain suitable IPv6 destinations for IPv4-only DNS names, so subscribers fail by hostname. The mechanism to prioritize for this question is: NAT44 translates IPv4 addresses within one family and cannot by itself connect IPv6-only clients to IPv4-only servers.

B:

MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation. That explains a DIFFERENT scenario: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. The mechanism to prioritize for this question is: NAT44 translates IPv4 addresses within one family and cannot by itself connect IPv6-only clients to IPv4-only servers.

C:

OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them. That explains a DIFFERENT scenario: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. The mechanism to prioritize for this question is: NAT44 translates IPv4 addresses within one family and cannot by itself connect IPv6-only clients to IPv4-only servers.

Question 56

For an inter-AS service aggregation carrier, the change record describes: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. What preventive validation should be standard?

  1. Validate dual-family translation behavior before onboarding IPv6-only customers.
  2. Audit port-block assignments and exhausted mapping pools.
  3. Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles.
  4. Record upstream acceptance of traffic-engineering communities and MED policy.

Explanation

Correct Answer

A:

Validate dual-family translation behavior before onboarding IPv6-only customers. This helps prevent recurrence of the issue: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. Acceptance evidence should be: An IPv6-only test client resolves and reaches the target IPv4-only service through the transition gateway.

Incorrect Answers

B:

Audit port-block assignments and exhausted mapping pools. That is a sensible control for ANOTHER scenario: An ISP assigns customer IPv4 address blocks through CGNAT but configures identical port-set mappings on two subscribers behind the same public address, causing connection collisions. It is less targeted to this issue than: Validate dual-family translation behavior before onboarding IPv6-only customers.

C:

Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles. That is a sensible control for ANOTHER scenario: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. It is less targeted to this issue than: Validate dual-family translation behavior before onboarding IPv6-only customers.

D:

Record upstream acceptance of traffic-engineering communities and MED policy. That is a sensible control for ANOTHER scenario: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. It is less targeted to this issue than: Validate dual-family translation behavior before onboarding IPv6-only customers.

Question 57

For a regional service-provider operations center, the failure is: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. Which authorized correction best addresses it?

  1. Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.
  2. Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing.
  3. Validate compatible NSF/graceful-restart capability and forwarding-state retention behavior on the platform.
  4. Enable the intended OSPFv3 address-family participation in the correct routing context.

Explanation

Correct Answer

C:

Validate compatible NSF/graceful-restart capability and forwarding-state retention behavior on the platform. This directly addresses the fictional service-provider network case: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. The technical mechanism is: Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts. Verify success by: During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget.

Incorrect Answers

A:

Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology. This would respond to a DIFFERENT fictional service-provider network issue: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. It does not directly address the current situation: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements.

B:

Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing. This would respond to a DIFFERENT fictional service-provider network issue: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. It does not directly address the current situation: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements.

D:

Enable the intended OSPFv3 address-family participation in the correct routing context. This would respond to a DIFFERENT fictional service-provider network issue: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. It does not directly address the current situation: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements.

Question 58

After fixing the following network problem, what should the team verify: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements.

  1. A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state.
  2. A failure drill on one shelf leaves at least one approved end-to-end route available.
  3. BGP route state transitions to valid forwarding with the expected next-hop recursion resolved.
  4. During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget.

Explanation

Correct Answer

D:

During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget. This confirms the approved response: Validate compatible NSF/graceful-restart capability and forwarding-state retention behavior on the platform. It is relevant because: Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts.

Incorrect Answers

A:

A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state. This would validate ANOTHER scenario: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. The specific correction here is: Validate compatible NSF/graceful-restart capability and forwarding-state retention behavior on the platform.

B:

A failure drill on one shelf leaves at least one approved end-to-end route available. This would validate ANOTHER scenario: An operator assumes two physically diverse core paths are independent, yet both circuits terminate in the same optical amplifier shelf and fail together during power loss. The specific correction here is: Validate compatible NSF/graceful-restart capability and forwarding-state retention behavior on the platform.

C:

BGP route state transitions to valid forwarding with the expected next-hop recursion resolved. This would validate ANOTHER scenario: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. The specific correction here is: Validate compatible NSF/graceful-restart capability and forwarding-state retention behavior on the platform.

Question 59

A carrier root-cause review considers: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. What underlying mechanism explains this?

  1. Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts.
  2. BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures.
  3. Logical ECMP diversity does not ensure physical failure independence when transport infrastructure shares common risk.
  4. OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them.

Explanation

Correct Answer

A:

Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts. This explains the investigated issue: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. The approved corrective response is: Validate compatible NSF/graceful-restart capability and forwarding-state retention behavior on the platform.

Incorrect Answers

B:

BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures. That explains a DIFFERENT scenario: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. The mechanism to prioritize for this question is: Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts.

C:

Logical ECMP diversity does not ensure physical failure independence when transport infrastructure shares common risk. That explains a DIFFERENT scenario: An operator assumes two physically diverse core paths are independent, yet both circuits terminate in the same optical amplifier shelf and fail together during power loss. The mechanism to prioritize for this question is: Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts.

D:

OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them. That explains a DIFFERENT scenario: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. The mechanism to prioritize for this question is: Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts.

Question 60

After addressing: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. Which recurring service assurance check is most useful?

  1. Baseline BFD jitter and loss before setting aggressive detection timers.
  2. Exercise planned supervisor failovers with forwarding and GR timer telemetry.
  3. Maintain release-specific ISSU qualification and rollback documentation.
  4. Test component-prefix ownership before exporting aggregates.

Explanation

Correct Answer

B:

Exercise planned supervisor failovers with forwarding and GR timer telemetry. This helps prevent recurrence of the issue: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. Acceptance evidence should be: During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget.

Incorrect Answers

A:

Baseline BFD jitter and loss before setting aggressive detection timers. That is a sensible control for ANOTHER scenario: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. It is less targeted to this issue than: Exercise planned supervisor failovers with forwarding and GR timer telemetry.

C:

Maintain release-specific ISSU qualification and rollback documentation. That is a sensible control for ANOTHER scenario: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. It is less targeted to this issue than: Exercise planned supervisor failovers with forwarding and GR timer telemetry.

D:

Test component-prefix ownership before exporting aggregates. That is a sensible control for ANOTHER scenario: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. It is less targeted to this issue than: Exercise planned supervisor failovers with forwarding and GR timer telemetry.