cert
cert-1
cert-2

Pass Cisco 350-601 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
350-601 Exam - Verified By Experts
350-601 Premium Bundle
$29.98

350-601 Premium Bundle

$79.99
$109.97
  • Premium File 613 Questions & Answers. Last update: Nov 10, 2026
  • Training Course 143 Video Lectures
  • Study Guide 1923 Pages
 
$109.97
$79.99
accept 46 downloads in last 7 days
block-screenshots
Purchase Cisco 350-601 Exam Training Products Individually
Cisco 350-601 Premium File
Premium File 613 Q&A
$76.99$69.99
Cisco 350-601 Video Training Course
Training Course 143 Lectures
$21.99 $19.99
Cisco 350-601 PDF Study Guide
Study Guide 1923 Pages
$21.99 $19.99
Cisco 350-601 Practice Test 14

Question 130

Dual-attached servers lose connectivity after the inter-peer trunk is misconfigured and vPC consistency state changes. The observed failure is: a failed peer link can trigger protective suspension or topology-specific disruption. Which remediation most directly restores the intended behavior?

  1. The controlled remediation is to disable all peer-link monitoring to conceal loss of the link.
  2. The controlled remediation is to repair peer-link capacity and configuration, then confirm vPC consistency and server redundancy.
  3. The controlled remediation is to treat the separate peer-keepalive network as a full data-carrying substitute.
  4. The controlled remediation is to make both peers use unrelated vPC domain identifiers.

Explanation

Correct Answer

B:

Validate against vPC peer-link operational state, consistency checks, role state, and downstream member suspension logs. The vPC peer link carries necessary control and selected data traffic between the cooperating switches.

Incorrect Answers

A:

Disable all peer-link monitoring to conceal loss of the link. This would not reliably restore service after the stated fault. A failed peer link can trigger protective suspension or topology-specific disruption. The controlled recovery is to repair peer-link capacity and configuration, then confirm vPC consistency and server redundancy.

C:

Treat the separate peer-keepalive network as a full data-carrying substitute. This would not reliably restore service after the stated fault. A failed peer link can trigger protective suspension or topology-specific disruption. The controlled recovery is to repair peer-link capacity and configuration, then confirm vPC consistency and server redundancy.

D:

Make both peers use unrelated vPC domain identifiers. This would not reliably restore service after the stated fault. A failed peer link can trigger protective suspension or topology-specific disruption. The controlled recovery is to repair peer-link capacity and configuration, then confirm vPC consistency and server redundancy.

Question 131

Two Nexus peers report missing vPC peer keepalive even while the peer-link trunk is operational. Which configuration decision MOST directly resolves the issue?

  1. Route peer keepalives only over the peer link as a normal design.
  2. Remove the keepalive destination from both peers.
  3. Restore reliable peer-keepalive connectivity through the approved independent path or VRF.
  4. Change the VLAN ID of unrelated storage traffic to fix management reachability.

Explanation

Correct Answer

C:

This directly addresses vPC keepalive reachability because vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. Confirm the change against vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

Incorrect Answers

A:

A missing liveness channel reduces the peers' ability to distinguish failures safely. The relevant correction is to restore reliable peer-keepalive connectivity through the approved independent path or VRF.

B:

Relevant evidence is vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters. The proposed change targets the wrong mechanism or lacks essential validation. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.

D:

A missing liveness channel reduces the peers' ability to distinguish failures safely. The appropriate action remains to restore reliable peer-keepalive connectivity through the approved independent path or VRF.

Question 132

Two Nexus peers report missing vPC peer keepalive even while the peer-link trunk is operational. What should the engineer inspect to confirm the actual state?

  1. A healthy optical light without checking protocol neighbors or forwarding entries.
  2. One successful ping to an unrelated management address.
  3. A pre-change network diagram with no live control-plane state.
  4. vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

Explanation

Correct Answer

D:

These observations test the actual vPC keepalive reachability mechanism rather than a superficial management status. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. They should be checked after restore reliable peer-keepalive connectivity through the approved independent path or VRF.

Incorrect Answers

A:

A healthy optical light without checking protocol neighbors or forwarding entries. This information cannot independently verify vPC keepalive reachability. The decisive records instead include vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.

B:

One successful ping to an unrelated management address. This information cannot independently verify vPC keepalive reachability. The decisive records instead include vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.

C:

A pre-change network diagram with no live control-plane state. This information cannot independently verify vPC keepalive reachability. The decisive records instead include vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.

Question 133

Two Nexus peers report missing vPC peer keepalive even while the peer-link trunk is operational. What technical behavior underlies the correct decision?

  1. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.
  2. Configuration differences between peer switches cannot affect network traffic.
  3. A working management-plane ping proves every tenant and application path is healthy.
  4. All control-plane protocols exchange state automatically after a cable is inserted.

Explanation

Correct Answer

A:

Validation depends on vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters. This explains why the most appropriate response is to restore reliable peer-keepalive connectivity through the approved independent path or VRF.

Incorrect Answers

B:

Configuration differences between peer switches cannot affect network traffic. This is an incorrect generalization for vPC keepalive reachability. The applicable technical behavior is that vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. The operator should verify vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

C:

A working management-plane ping proves every tenant and application path is healthy. This is an incorrect generalization for vPC keepalive reachability. The applicable technical behavior is that vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. The operator should verify vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

D:

All control-plane protocols exchange state automatically after a cable is inserted. This is an incorrect generalization for vPC keepalive reachability. The applicable technical behavior is that vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. The operator should verify vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

Question 134

Two Nexus peers report missing vPC peer keepalive even while the peer-link trunk is operational. Assume an engineer instead chooses to route peer keepalives only over the peer link as a normal design. Which resulting risk or fault should the reviewer identify?

  1. Investigating the forwarding table is the reason a broken route cannot converge.
  2. A missing liveness channel reduces the peers' ability to distinguish failures safely.
  3. The only consequence of the wrong change is a different device description.
  4. Verifying topology after maintenance automatically creates a switching loop.

Explanation

Correct Answer

B:

That is the direct consequence of choosing the misleading shortcut. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. The proper corrective action is to restore reliable peer-keepalive connectivity through the approved independent path or VRF.

Incorrect Answers

A:

This does not explain the actual vPC keepalive reachability defect after the shortcut. The meaningful failure is that a missing liveness channel reduces the peers' ability to distinguish failures safely.

C:

This does not explain the actual vPC keepalive reachability defect after the shortcut. The relevant evidence is vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

D:

This does not explain the actual vPC keepalive reachability defect after the shortcut. Verifying topology after maintenance automatically creates a switching loop.

Question 135

Two Nexus peers report missing vPC peer keepalive even while the peer-link trunk is operational. The observed failure is: a missing liveness channel reduces the peers' ability to distinguish failures safely. Which remediation most directly restores the intended behavior?

  1. Remove the keepalive destination from both peers.
  2. Change the VLAN ID of unrelated storage traffic to fix management reachability.
  3. Correct the management or dedicated keepalive route and verify periodic liveness messages.
  4. Route peer keepalives only over the peer link as a normal design.

Explanation

Correct Answer

C:

This addresses the observable fault while preserving a check of the expected result. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. Validate against vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

Incorrect Answers

A:

Remove the keepalive destination from both peers. This would not reliably restore service after the stated fault. A missing liveness channel reduces the peers' ability to distinguish failures safely. The controlled recovery is to correct the management or dedicated keepalive route and verify periodic liveness messages.

B:

Change the VLAN ID of unrelated storage traffic to fix management reachability. This would not reliably restore service after the stated fault. A missing liveness channel reduces the peers' ability to distinguish failures safely. The controlled recovery is to correct the management or dedicated keepalive route and verify periodic liveness messages.

D:

Route peer keepalives only over the peer link as a normal design. This would not reliably restore service after the stated fault. A missing liveness channel reduces the peers' ability to distinguish failures safely. The controlled recovery is to correct the management or dedicated keepalive route and verify periodic liveness messages.

Question 136

A management VRF change prevents periodic vPC keepalive packets from traversing the designed independent path. Which operator action best meets this technical requirement?

  1. On this affected device, the engineer should remove the keepalive destination from both peers.
  2. On this affected device, the engineer should change the VLAN ID of unrelated storage traffic to fix management reachability.
  3. On this affected device, the engineer should route peer keepalives only over the peer link as a normal design.
  4. On this affected device, the engineer should restore reliable peer-keepalive connectivity through the approved independent path or VRF.

Explanation

Correct Answer

D:

This directly addresses vPC keepalive reachability because vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. In the given case, a management VRF change prevents periodic vPC keepalive packets from traversing the designed independent path.

Incorrect Answers

A:

Relevant evidence is vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

B:

A missing liveness channel reduces the peers' ability to distinguish failures safely. In the given case, a management VRF change prevents periodic vPC keepalive packets from traversing the designed independent path.

C:

A missing liveness channel reduces the peers' ability to distinguish failures safely. Route peer keepalives only over the peer link as a normal design.

Question 137

A management VRF change prevents periodic vPC keepalive packets from traversing the designed independent path. Which collection of observations most directly tests the suspected cause?

  1. For this deployment, examine vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.
  2. For this deployment, examine an interface description without the effective peer or VXLAN policy.
  3. For this deployment, examine a healthy optical light without checking protocol neighbors or forwarding entries.
  4. For this deployment, examine one successful ping to an unrelated management address.

Explanation

Correct Answer

A:

These observations test the actual vPC keepalive reachability mechanism rather than a superficial management status. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.

Incorrect Answers

B:

An interface description without the effective peer or VXLAN policy. This information cannot independently verify vPC keepalive reachability. The decisive records instead include vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.

C:

A healthy optical light without checking protocol neighbors or forwarding entries. This information cannot independently verify vPC keepalive reachability. The decisive records instead include vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.

D:

One successful ping to an unrelated management address. This information cannot independently verify vPC keepalive reachability. The decisive records instead include vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.

Question 138

A management VRF change prevents periodic vPC keepalive packets from traversing the designed independent path. Which statement most accurately explains this scenario?

  1. For this condition, the applicable principle is that all control-plane protocols exchange state automatically after a cable is inserted.
  2. For this condition, the applicable principle is that vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.
  3. For this condition, the applicable principle is that configuration differences between peer switches cannot affect network traffic.
  4. For this condition, the applicable principle is that a device description always determines actual forwarding policy regardless of running configuration.

Explanation

Correct Answer

B:

Validation depends on vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

Incorrect Answers

A:

All control-plane protocols exchange state automatically after a cable is inserted. This is an incorrect generalization for vPC keepalive reachability. The applicable technical behavior is that vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. The operator should verify vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

C:

Configuration differences between peer switches cannot affect network traffic. This is an incorrect generalization for vPC keepalive reachability. The applicable technical behavior is that vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. The operator should verify vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

D:

A device description always determines actual forwarding policy regardless of running configuration. This is an incorrect generalization for vPC keepalive reachability. The applicable technical behavior is that vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. The operator should verify vPC peer-keepalive destination and source, reachability tests, VRF routing, and role counters.

Question 139

A management VRF change prevents periodic vPC keepalive packets from traversing the designed independent path. Assume an engineer instead chooses to route peer keepalives only over the peer link as a normal design. What is the principal technical consequence of the mistaken choice?

  1. The resulting defect is that verifying topology after maintenance automatically creates a switching loop.
  2. The resulting defect is that the defect exists solely because the engineer documented the change.
  3. The resulting defect is that a missing liveness channel reduces the peers' ability to distinguish failures safely.
  4. The resulting defect is that the only consequence of the wrong change is a different device description.

Explanation

Correct Answer

C:

That is the direct consequence of choosing the misleading shortcut. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link. In the given case, a management VRF change prevents periodic vPC keepalive packets from traversing the designed independent path.

Incorrect Answers

A:

This does not explain the actual vPC keepalive reachability defect after the shortcut. In the given case, a management VRF change prevents periodic vPC keepalive packets from traversing the designed independent path.

B:

This does not explain the actual vPC keepalive reachability defect after the shortcut. The defect exists solely because the engineer documented the change.

D:

This does not explain the actual vPC keepalive reachability defect after the shortcut. The only consequence of the wrong change is a different device description.

Question 140

A management VRF change prevents periodic vPC keepalive packets from traversing the designed independent path. The observed failure is: a missing liveness channel reduces the peers' ability to distinguish failures safely. What should the engineer do to recover and validate the service?

  1. The controlled remediation is to change the VLAN ID of unrelated storage traffic to fix management reachability.
  2. The controlled remediation is to route peer keepalives only over the peer link as a normal design.
  3. The controlled remediation is to remove the keepalive destination from both peers.
  4. The controlled remediation is to correct the management or dedicated keepalive route and verify periodic liveness messages.

Explanation

Correct Answer

D:

This addresses the observable fault while preserving a check of the expected result. vPC peer keepalive is an independent liveness signal and should not be conflated with the peer link.

Incorrect Answers

A:

Change the VLAN ID of unrelated storage traffic to fix management reachability. This would not reliably restore service after the stated fault. A missing liveness channel reduces the peers' ability to distinguish failures safely. The controlled recovery is to correct the management or dedicated keepalive route and verify periodic liveness messages.

B:

Route peer keepalives only over the peer link as a normal design. This would not reliably restore service after the stated fault. A missing liveness channel reduces the peers' ability to distinguish failures safely. The controlled recovery is to correct the management or dedicated keepalive route and verify periodic liveness messages.

C:

Remove the keepalive destination from both peers. This would not reliably restore service after the stated fault. A missing liveness channel reduces the peers' ability to distinguish failures safely. The controlled recovery is to correct the management or dedicated keepalive route and verify periodic liveness messages.

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests