McAfee Secure

Cisco 350-501 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 Training 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

    Training Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 25

Question 240

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A PE must tag customer service routes for controlled import at remote sites, but its export policy manipulates an unrelated community. Which continuing control best reduces recurrence of this problem?

  1. Monitor port exhaustion and data retention before scaling subscriber density.
  2. Include link MTU compatibility in OSPF turn-up validation.
  3. Audit RT consistency and route-target filtering on PE changes.
  4. Validate unique system IDs and area plans during provisioning.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A PE must tag customer service routes for controlled import at remote sites, but its export policy manipulates an unrelated community. The most directly supported response is: Set and preserve the documented BGP extended community or route target for the relevant service. Technical basis: BGP extended communities carry service membership and routing-policy metadata. Evidence of success: Remote VPN routes appear only in the importing VRFs authorized by the intended RT. Ongoing protection: Audit RT consistency and route-target filtering on PE changes.

Incorrect Answers

A:

CGNAT multiplexes many private subscribers over limited public IPv4 address space. Maintaining that control would not track the failure described here. The relevant risk is: BGP extended communities carry service membership and routing-policy metadata. Review this instead: Audit RT consistency and route-target filtering on PE changes.

B:

OSPF database description exchange can fail when adjacent interfaces disagree on required parameters. Maintaining that control would not track the failure described here. The relevant risk is: BGP extended communities carry service membership and routing-policy metadata. Review this instead: Audit RT consistency and route-target filtering on PE changes.

D:

The alternative guards against: IS-IS NET addressing encodes area identity used to form Level-1 routing adjacencies. The root condition for this case is: BGP extended communities carry service membership and routing-policy metadata. The focused prevention check is: Audit RT consistency and route-target filtering on PE changes.

Question 241

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A BGP session oscillates between Active and Connect though ping works, and an ACL blocks inbound TCP port 179. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Set an appropriate consistent OSPF reference bandwidth and engineered interface cost values.
  2. Inspect BGP TCP reachability and security policy along the peer path.
  3. Check neighbor level, area identity, authentication, and circuit parameters rather than only ping.
  4. Combine supported tracking, protocol health checks, and route withdrawal behavior appropriate to the service.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A BGP session oscillates between Active and Connect though ping works, and an ACL blocks inbound TCP port 179. The most directly supported response is: Inspect BGP TCP reachability and security policy along the peer path. Technical basis: BGP requires a successful TCP session before exchanging UPDATE messages. Evidence of success: The session reaches Established and updates exchange after the permitted TCP handshake. Ongoing protection: Run TCP session tests whenever peering ACLs are changed.

Incorrect Answers

A:

The proposed option addresses this separate mechanism: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. The stated problem instead depends on: BGP requires a successful TCP session before exchanging UPDATE messages. The required response is: Inspect BGP TCP reachability and security policy along the peer path.

C:

The option fits a control for: Level-1 IS-IS neighbors require compatible area membership, while L2 behavior differs. The present failure is caused by a different mechanism: BGP requires a successful TCP session before exchanging UPDATE messages. The targeted implementation is: Inspect BGP TCP reachability and security policy along the peer path.

D:

The option fits a control for: High availability requires validating application-relevant reachability rather than only local link carrier state. The present failure is caused by a different mechanism: BGP requires a successful TCP session before exchanging UPDATE messages. The targeted implementation is: Inspect BGP TCP reachability and security policy along the peer path.

Question 242

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A BGP session oscillates between Active and Connect though ping works, and an ACL blocks inbound TCP port 179. Which observable result most directly verifies that this network issue was resolved?

  1. The Hello neighbor field becomes reciprocal and the adjacency advances from INIT.
  2. The subscriber's allowed IPv4 address/port set follows the configured algorithmic mapping.
  3. The session reaches Established and updates exchange after the permitted TCP handshake.
  4. The port-channel reaches the intended member count and distributes eligible flows without errors.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A BGP session oscillates between Active and Connect though ping works, and an ACL blocks inbound TCP port 179. The most directly supported response is: Inspect BGP TCP reachability and security policy along the peer path. Technical basis: BGP requires a successful TCP session before exchanging UPDATE messages. Evidence of success: The session reaches Established and updates exchange after the permitted TCP handshake. Ongoing protection: Run TCP session tests whenever peering ACLs are changed.

Incorrect Answers

A:

OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: BGP requires a successful TCP session before exchanging UPDATE messages. A passing check should show: The session reaches Established and updates exchange after the permitted TCP handshake.

B:

The proposed test would be relevant to: MAP-T supports algorithmic IPv4-to-IPv6 translation and port-set assignment rather than central per-flow NAT state. The reported problem follows from: BGP requires a successful TCP session before exchanging UPDATE messages. Instead, verify: The session reaches Established and updates exchange after the permitted TCP handshake.

D:

The proposed test would be relevant to: Link aggregation combines compatible physical members into one logical forwarding interface. The reported problem follows from: BGP requires a successful TCP session before exchanging UPDATE messages. Instead, verify: The session reaches Established and updates exchange after the permitted TCP handshake.

Question 243

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A BGP session oscillates between Active and Connect though ping works, and an ACL blocks inbound TCP port 179. Which underlying network infrastructure principle best explains the situation?

  1. IS-IS overload and high-cost advertisement can drain transit traffic without tearing down every adjacency.
  2. Cisco route-policy languages differ across operating systems and cannot always be pasted interchangeably.
  3. BGP requires a successful TCP session before exchanging UPDATE messages.
  4. BGP transport session establishment does not automatically enable every address family.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A BGP session oscillates between Active and Connect though ping works, and an ACL blocks inbound TCP port 179. The most directly supported response is: Inspect BGP TCP reachability and security policy along the peer path. Technical basis: BGP requires a successful TCP session before exchanging UPDATE messages. Evidence of success: The session reaches Established and updates exchange after the permitted TCP handshake. Ongoing protection: Run TCP session tests whenever peering ACLs are changed.

Incorrect Answers

A:

The option explains a separate issue: IS-IS overload and high-cost advertisement can drain transit traffic without tearing down every adjacency. The reported condition instead follows from: BGP requires a successful TCP session before exchanging UPDATE messages.

B:

The option explains a separate issue: Cisco route-policy languages differ across operating systems and cannot always be pasted interchangeably. The reported condition instead follows from: BGP requires a successful TCP session before exchanging UPDATE messages.

D:

The option explains a separate issue: BGP transport session establishment does not automatically enable every address family. The reported condition instead follows from: BGP requires a successful TCP session before exchanging UPDATE messages.

Question 244

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A BGP session oscillates between Active and Connect though ping works, and an ACL blocks inbound TCP port 179. Which continuing control best reduces recurrence of this problem?

  1. Monitor unresolved next-hop counters following transport topology changes.
  2. Test stub and NSSA behavior before deploying common area profiles.
  3. Run TCP session tests whenever peering ACLs are changed.
  4. Use route-state and next-hop resolution verification in route-reflector troubleshooting.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A BGP session oscillates between Active and Connect though ping works, and an ACL blocks inbound TCP port 179. The most directly supported response is: Inspect BGP TCP reachability and security policy along the peer path. Technical basis: BGP requires a successful TCP session before exchanging UPDATE messages. Evidence of success: The session reaches Established and updates exchange after the permitted TCP handshake. Ongoing protection: Run TCP session tests whenever peering ACLs are changed.

Incorrect Answers

A:

The alternative guards against: BGP paths require resolvable next-hop reachability before installation and forwarding. The root condition for this case is: BGP requires a successful TCP session before exchanging UPDATE messages. The focused prevention check is: Run TCP session tests whenever peering ACLs are changed.

B:

The alternative guards against: OSPF area types determine which external and summary LSAs may be flooded. The root condition for this case is: BGP requires a successful TCP session before exchanging UPDATE messages. The focused prevention check is: Run TCP session tests whenever peering ACLs are changed.

D:

That recurring practice manages a separate exposure: BGP may retain several path candidates while selecting a subset for best-path and forwarding use. The present case instead depends on: BGP requires a successful TCP session before exchanging UPDATE messages. The suitable ongoing safeguard is: Run TCP session tests whenever peering ACLs are changed.

Question 245

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: Two OSPF peers see each other but have different hello and dead intervals and never reach FULL. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Align OSPF neighbor timer and authentication parameters on both ends.
  2. Enable and verify supported BGP graceful restart behavior and independent next-hop recovery constraints.
  3. Evaluate supported additional-path advertisement and BGP PIC designs consistent with platform capabilities.
  4. Set documented OSPF priorities and stable router IDs for designated-router candidates.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: Two OSPF peers see each other but have different hello and dead intervals and never reach FULL. The most directly supported response is: Align OSPF neighbor timer and authentication parameters on both ends. Technical basis: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. Evidence of success: The adjacency stabilizes and LSDB synchronization completes. Ongoing protection: Compare both peers' timer settings during maintenance.

Incorrect Answers

B:

The option fits a control for: Graceful restart can preserve routing information temporarily while a control plane reconverges. The present failure is caused by a different mechanism: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. The targeted implementation is: Align OSPF neighbor timer and authentication parameters on both ends.

C:

BGP Add-Paths and PIC address different multipath signaling and precomputed backup forwarding aspects. That principle governs the alternative intervention. The issue described here is different: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. The case-matched corrective action is: Align OSPF neighbor timer and authentication parameters on both ends.

D:

OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. That principle governs the alternative intervention. The issue described here is different: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. The case-matched corrective action is: Align OSPF neighbor timer and authentication parameters on both ends.

Question 246

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: Two OSPF peers see each other but have different hello and dead intervals and never reach FULL. Which observable result most directly verifies that this network issue was resolved?

  1. Service reachability failure triggers the intended route withdrawal instead of persistent blackholing.
  2. The subscriber's allowed IPv4 address/port set follows the configured algorithmic mapping.
  3. The peer receives public approved customer aggregates and no private addressing.
  4. The adjacency stabilizes and LSDB synchronization completes.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: Two OSPF peers see each other but have different hello and dead intervals and never reach FULL. The most directly supported response is: Align OSPF neighbor timer and authentication parameters on both ends. Technical basis: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. Evidence of success: The adjacency stabilizes and LSDB synchronization completes. Ongoing protection: Compare both peers' timer settings during maintenance.

Incorrect Answers

A:

The proposed test would be relevant to: High availability requires validating application-relevant reachability rather than only local link carrier state. The reported problem follows from: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. Instead, verify: The adjacency stabilizes and LSDB synchronization completes.

B:

That observation tests a different mechanism: MAP-T supports algorithmic IPv4-to-IPv6 translation and port-set assignment rather than central per-flow NAT state. It cannot establish this case, whose mechanism is: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. The needed verification is: The adjacency stabilizes and LSDB synchronization completes.

C:

That observation tests a different mechanism: BGP export policy is the boundary controlling which NLRI leaves an autonomous system. It cannot establish this case, whose mechanism is: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. The needed verification is: The adjacency stabilizes and LSDB synchronization completes.

Question 247

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: Two OSPF peers see each other but have different hello and dead intervals and never reach FULL. Which underlying network infrastructure principle best explains the situation?

  1. BGP transport session establishment does not automatically enable every address family.
  2. Cisco route-policy languages differ across operating systems and cannot always be pasted interchangeably.
  3. OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability.
  4. IS-IS multitopology can maintain separate route calculations for distinct supported protocol topologies.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: Two OSPF peers see each other but have different hello and dead intervals and never reach FULL. The most directly supported response is: Align OSPF neighbor timer and authentication parameters on both ends. Technical basis: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. Evidence of success: The adjacency stabilizes and LSDB synchronization completes. Ongoing protection: Compare both peers' timer settings during maintenance.

Incorrect Answers

A:

The alternative principle describes: BGP transport session establishment does not automatically enable every address family. In this question, the decisive mechanism is: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. These are distinct technical causes, even when they share a platform.

B:

The alternative principle describes: Cisco route-policy languages differ across operating systems and cannot always be pasted interchangeably. In this question, the decisive mechanism is: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. These are distinct technical causes, even when they share a platform.

D:

The alternative principle describes: IS-IS multitopology can maintain separate route calculations for distinct supported protocol topologies. In this question, the decisive mechanism is: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. These are distinct technical causes, even when they share a platform.

Question 248

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: Two OSPF peers see each other but have different hello and dead intervals and never reach FULL. Which continuing control best reduces recurrence of this problem?

  1. Review best-path debug evidence before tuning otherwise irrelevant attributes.
  2. Test stale-route timer expiry and unsupported-peer behavior before relying on graceful restart.
  3. Audit RT consistency and route-target filtering on PE changes.
  4. Compare both peers' timer settings during maintenance.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: Two OSPF peers see each other but have different hello and dead intervals and never reach FULL. The most directly supported response is: Align OSPF neighbor timer and authentication parameters on both ends. Technical basis: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. Evidence of success: The adjacency stabilizes and LSDB synchronization completes. Ongoing protection: Compare both peers' timer settings during maintenance.

Incorrect Answers

A:

That recurring practice manages a separate exposure: BGP origin is one of several ordered best-path criteria, not a universal primary selector. The present case instead depends on: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. The suitable ongoing safeguard is: Compare both peers' timer settings during maintenance.

B:

That recurring practice manages a separate exposure: Graceful restart can preserve routing information temporarily while a control plane reconverges. The present case instead depends on: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. The suitable ongoing safeguard is: Compare both peers' timer settings during maintenance.

C:

That recurring practice manages a separate exposure: BGP extended communities carry service membership and routing-policy metadata. The present case instead depends on: OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. The suitable ongoing safeguard is: Compare both peers' timer settings during maintenance.

Question 249

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IS-IS link shows Level-2 Up while remote IPv6 prefixes are absent because address-family participation differs. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Check IS-IS IPv6 topology advertisements, supported AF configuration, and next-hop calculation.
  2. Configure a unique 32-bit OSPFv3 router ID and valid IPv6 interface advertisements.
  3. Update the explicitly configured IS-IS wide metrics according to engineered path costs.
  4. Inspect weight, local preference, and then AS-path among applicable BGP decision criteria.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An IS-IS link shows Level-2 Up while remote IPv6 prefixes are absent because address-family participation differs. The most directly supported response is: Check IS-IS IPv6 topology advertisements, supported AF configuration, and next-hop calculation. Technical basis: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. Evidence of success: IPv6 prefixes appear in the intended database and routing table after AF correction. Ongoing protection: Track adjacency and per-family prefix counters separately.

Incorrect Answers

B:

OSPFv3 retains a 32-bit router identifier even though it exchanges IPv6 reachability. That principle governs the alternative intervention. The issue described here is different: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. The case-matched corrective action is: Check IS-IS IPv6 topology advertisements, supported AF configuration, and next-hop calculation.

C:

The proposed option addresses this separate mechanism: IS-IS shortest-path selection uses advertised metrics rather than inferring every physical speed change. The stated problem instead depends on: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. The required response is: Check IS-IS IPv6 topology advertisements, supported AF configuration, and next-hop calculation.

D:

The proposed option addresses this separate mechanism: BGP evaluates ordered criteria, so later comparisons apply only when earlier attributes are tied. The stated problem instead depends on: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. The required response is: Check IS-IS IPv6 topology advertisements, supported AF configuration, and next-hop calculation.

Question 250

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An IS-IS link shows Level-2 Up while remote IPv6 prefixes are absent because address-family participation differs. Which observable result most directly verifies that this network issue was resolved?

  1. IPv6 prefixes appear in the intended database and routing table after AF correction.
  2. The IPv6-only client reaches the IPv4 service through a measured translation state.
  3. The Hello neighbor field becomes reciprocal and the adjacency advances from INIT.
  4. A simulated link failure triggers routing repair within the measured target without false positives.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An IS-IS link shows Level-2 Up while remote IPv6 prefixes are absent because address-family participation differs. The most directly supported response is: Check IS-IS IPv6 topology advertisements, supported AF configuration, and next-hop calculation. Technical basis: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. Evidence of success: IPv6 prefixes appear in the intended database and routing table after AF correction. Ongoing protection: Track adjacency and per-family prefix counters separately.

Incorrect Answers

B:

NAT64 bridges IPv6 endpoints to IPv4 destinations with state and addressing considerations. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. A passing check should show: IPv6 prefixes appear in the intended database and routing table after AF correction.

C:

OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. A passing check should show: IPv6 prefixes appear in the intended database and routing table after AF correction.

D:

BFD supplies fast bidirectional failure detection independently of slower protocol hello timers. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: A live IS-IS adjacency does not guarantee all address-family reachability is exchanged. A passing check should show: IPv6 prefixes appear in the intended database and routing table after AF correction.