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 9

Question 80

A PIM deployment passes multicast joins, but forwarding drops appear after the RPF path changes to a different uplink. The observed failure is: continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. What is the BEST controlled recovery once this failure is recognized?

  1. The controlled remediation is to disable all reverse-path checks globally as the first troubleshooting step.
  2. The controlled remediation is to enable PortFast on every routed multicast transit interface.
  3. The controlled remediation is to replace a valid multicast group address with an IPv4 broadcast.
  4. The controlled remediation is to restore a consistent source route and verify RPF and multicast forwarding entries.

Explanation

Correct Answer

D:

PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. Validate against multicast routing table, RPF interface selection, source route lookup, and drop counters.

Incorrect Answers

A:

Disable all reverse-path checks globally as the first troubleshooting step. This would not reliably restore service after the stated fault. Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. The controlled recovery is to restore a consistent source route and verify RPF and multicast forwarding entries.

B:

Enable PortFast on every routed multicast transit interface. This would not reliably restore service after the stated fault. Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. The controlled recovery is to restore a consistent source route and verify RPF and multicast forwarding entries.

C:

Replace a valid multicast group address with an IPv4 broadcast. This would not reliably restore service after the stated fault. Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. The controlled recovery is to restore a consistent source route and verify RPF and multicast forwarding entries.

Question 81

A sparse-mode multicast application fails to build shared-tree state after the configured RP became unreachable. What is the BEST supported implementation or corrective action?

  1. Restore a reachable, consistently configured rendezvous point for the intended sparse-mode groups.
  2. Disable IGMP on every receiver VLAN and rely on ARP.
  3. Change a Fibre Channel zone name to restore PIM joins.
  4. Assume any OSPF adjacency automatically supplies the correct PIM RP.

Explanation

Correct Answer

A:

This directly addresses PIM rendezvous point reachability because PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. Confirm the change against rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

Incorrect Answers

B:

An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. The relevant correction is to restore a reachable, consistently configured rendezvous point for the intended sparse-mode groups.

C:

Change a Fibre Channel zone name to restore PIM joins. The proposed change targets the wrong mechanism or lacks essential validation. PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. Relevant evidence is rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

D:

An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. The appropriate action remains to restore a reachable, consistently configured rendezvous point for the intended sparse-mode groups.

Question 82

A sparse-mode multicast application fails to build shared-tree state after the configured RP became unreachable. Which evidence BEST verifies the intended technical behavior?

  1. A healthy optical light without checking protocol neighbors or forwarding entries.
  2. RP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.
  3. One successful ping to an unrelated management address.
  4. A pre-change network diagram with no live control-plane state.

Explanation

Correct Answer

B:

These observations test the actual PIM rendezvous point reachability mechanism rather than a superficial management status. PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior.

Incorrect Answers

A:

This information cannot independently verify PIM rendezvous point reachability. The decisive records instead include rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

C:

This information cannot independently verify PIM rendezvous point reachability. PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior.

D:

This information cannot independently verify PIM rendezvous point reachability. In the given case, a sparse-mode multicast application fails to build shared-tree state after the configured RP became unreachable.

Question 83

A sparse-mode multicast application fails to build shared-tree state after the configured RP became unreachable. Which principle BEST explains why the recommended solution is appropriate?

  1. Configuration differences between peer switches cannot affect network traffic.
  2. A working management-plane ping proves every tenant and application path is healthy.
  3. PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior.
  4. All control-plane protocols exchange state automatically after a cable is inserted.

Explanation

Correct Answer

C:

Validation depends on rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state. This explains why the most appropriate response is to restore a reachable, consistently configured rendezvous point for the intended sparse-mode groups.

Incorrect Answers

A:

Configuration differences between peer switches cannot affect network traffic. This is an incorrect generalization for PIM rendezvous point reachability. The applicable technical behavior is that PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. The operator should verify rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

B:

A working management-plane ping proves every tenant and application path is healthy. This is an incorrect generalization for PIM rendezvous point reachability. The applicable technical behavior is that PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. The operator should verify rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

D:

All control-plane protocols exchange state automatically after a cable is inserted. This is an incorrect generalization for PIM rendezvous point reachability. The applicable technical behavior is that PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. The operator should verify rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

Question 84

A sparse-mode multicast application fails to build shared-tree state after the configured RP became unreachable. Assume an engineer instead chooses to disable IGMP on every receiver VLAN and rely on ARP. What is the MOST significant failure introduced by that shortcut?

  1. Investigating the forwarding table is the reason a broken route cannot converge.
  2. The only consequence of the wrong change is a different device description.
  3. Verifying topology after maintenance automatically creates a switching loop.
  4. An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins.

Explanation

Correct Answer

D:

PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. That is the direct consequence of choosing the misleading shortcut.

Incorrect Answers

A:

This does not explain the actual PIM rendezvous point reachability defect after the shortcut. The meaningful failure is that an incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins.

B:

This does not explain the actual PIM rendezvous point reachability defect after the shortcut. The relevant evidence is rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

C:

This does not explain the actual PIM rendezvous point reachability defect after the shortcut. Verifying topology after maintenance automatically creates a switching loop.

Question 85

A sparse-mode multicast application fails to build shared-tree state after the configured RP became unreachable. The observed failure is: an incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. What is the BEST controlled recovery once this failure is recognized?

  1. Correct RP reachability and mappings and verify group-specific multicast state.
  2. Change a Fibre Channel zone name to restore PIM joins.
  3. Assume any OSPF adjacency automatically supplies the correct PIM RP.
  4. Disable IGMP on every receiver VLAN and rely on ARP.

Explanation

Correct Answer

A:

PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. This addresses the observable fault while preserving a check of the expected result.

Incorrect Answers

B:

Change a Fibre Channel zone name to restore PIM joins. This would not reliably restore service after the stated fault. An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. The controlled recovery is to correct RP reachability and mappings and verify group-specific multicast state.

C:

Assume any OSPF adjacency automatically supplies the correct PIM RP. This would not reliably restore service after the stated fault. An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. The controlled recovery is to correct RP reachability and mappings and verify group-specific multicast state.

D:

Disable IGMP on every receiver VLAN and rely on ARP. This would not reliably restore service after the stated fault. An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. The controlled recovery is to correct RP reachability and mappings and verify group-specific multicast state.

Question 86

New receivers cannot join a PIM sparse-mode group although local IGMP reports work after an RP change. Which configuration decision MOST directly resolves the issue?

  1. On this affected device, the engineer should change a Fibre Channel zone name to restore PIM joins.
  2. On this affected device, the engineer should restore a reachable, consistently configured rendezvous point for the intended sparse-mode groups.
  3. On this affected device, the engineer should assume any OSPF adjacency automatically supplies the correct PIM RP.
  4. On this affected device, the engineer should disable IGMP on every receiver VLAN and rely on ARP.

Explanation

Correct Answer

B:

This directly addresses PIM rendezvous point reachability because PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. In the given case, new receivers cannot join a PIM sparse-mode group although local IGMP reports work after an RP change.

Incorrect Answers

A:

Change a Fibre Channel zone name to restore PIM joins. The proposed change targets the wrong mechanism or lacks essential validation. PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. Relevant evidence is rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

C:

An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. In the given case, new receivers cannot join a PIM sparse-mode group although local IGMP reports work after an RP change.

D:

An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. Disable IGMP on every receiver VLAN and rely on ARP.

Question 87

New receivers cannot join a PIM sparse-mode group although local IGMP reports work after an RP change. What should the engineer inspect to confirm the actual state?

  1. For this deployment, examine an interface description without the effective peer or VXLAN policy.
  2. For this deployment, examine a healthy optical light without checking protocol neighbors or forwarding entries.
  3. For this deployment, examine rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.
  4. For this deployment, examine one successful ping to an unrelated management address.

Explanation

Correct Answer

C:

These observations test the actual PIM rendezvous point reachability mechanism rather than a superficial management status. They should be checked after restore a reachable, consistently configured rendezvous point for the intended sparse-mode groups.

Incorrect Answers

A:

This information cannot independently verify PIM rendezvous point reachability. An interface description without the effective peer or VXLAN policy.

B:

This information cannot independently verify PIM rendezvous point reachability. A healthy optical light without checking protocol neighbors or forwarding entries.

D:

This information cannot independently verify PIM rendezvous point reachability. In the given case, new receivers cannot join a PIM sparse-mode group although local IGMP reports work after an RP change.

Question 88

New receivers cannot join a PIM sparse-mode group although local IGMP reports work after an RP change. What technical behavior underlies the correct decision?

  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 configuration differences between peer switches cannot affect network traffic.
  3. For this condition, the applicable principle is that a device description always determines actual forwarding policy regardless of running configuration.
  4. For this condition, the applicable principle is that PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior.

Explanation

Correct Answer

D:

Validation depends on rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

Incorrect Answers

A:

All control-plane protocols exchange state automatically after a cable is inserted. This is an incorrect generalization for PIM rendezvous point reachability. The applicable technical behavior is that PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. The operator should verify rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

B:

Configuration differences between peer switches cannot affect network traffic. This is an incorrect generalization for PIM rendezvous point reachability. The applicable technical behavior is that PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. The operator should verify rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

C:

A device description always determines actual forwarding policy regardless of running configuration. This is an incorrect generalization for PIM rendezvous point reachability. The applicable technical behavior is that PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. The operator should verify rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

Question 89

New receivers cannot join a PIM sparse-mode group although local IGMP reports work after an RP change. Assume an engineer instead chooses to disable IGMP on every receiver VLAN and rely on ARP. Which resulting risk or fault should the reviewer identify?

  1. The resulting defect is that an incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins.
  2. The resulting defect is that verifying topology after maintenance automatically creates a switching loop.
  3. The resulting defect is that the defect exists solely because the engineer documented the change.
  4. The resulting defect is that the only consequence of the wrong change is a different device description.

Explanation

Correct Answer

A:

PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. The proper corrective action is to restore a reachable, consistently configured rendezvous point for the intended sparse-mode groups.

Incorrect Answers

B:

This does not explain the actual PIM rendezvous point reachability defect after the shortcut. In the given case, new receivers cannot join a PIM sparse-mode group although local IGMP reports work after an RP change.

C:

This does not explain the actual PIM rendezvous point reachability defect after the shortcut. The defect exists solely because the engineer documented the change.

D:

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

Question 90

New receivers cannot join a PIM sparse-mode group although local IGMP reports work after an RP change. The observed failure is: an incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. Which remediation most directly restores the intended behavior?

  1. The controlled remediation is to assume any OSPF adjacency automatically supplies the correct PIM RP.
  2. The controlled remediation is to correct RP reachability and mappings and verify group-specific multicast state.
  3. The controlled remediation is to disable IGMP on every receiver VLAN and rely on ARP.
  4. The controlled remediation is to change a Fibre Channel zone name to restore PIM joins.

Explanation

Correct Answer

B:

PIM sparse mode relies on the configured RP for relevant shared-tree discovery and forwarding behavior. Validate against rP mapping, unicast reachability to the RP, PIM neighbors, and multicast join state.

Incorrect Answers

A:

Assume any OSPF adjacency automatically supplies the correct PIM RP. This would not reliably restore service after the stated fault. An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. The controlled recovery is to correct RP reachability and mappings and verify group-specific multicast state.

C:

Disable IGMP on every receiver VLAN and rely on ARP. This would not reliably restore service after the stated fault. An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. The controlled recovery is to correct RP reachability and mappings and verify group-specific multicast state.

D:

Change a Fibre Channel zone name to restore PIM joins. This would not reliably restore service after the stated fault. An incorrect or unreachable RP prevents intended sparse-mode group registration and receiver joins. The controlled recovery is to correct RP reachability and mappings and verify group-specific multicast state.

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