mcAfee Secure Website
23

Cisco 350-601 Bundle

Exam Code: 350-601

Exam Name Implementing and Operating Cisco Data Center Core Technologies (DCCOR)

Certification Provider: Cisco

Corresponding Certifications: CCIE Data Center , CCNP Data Center

350-601 Training Materials $25.00

Reliable & Actual Study Materials for 350-601 Exam Success

The Latest 350-601 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    350-601 Questions & Answers

    630 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    350-601 Video Course

    350-601 Training Course

    143 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

exam =32

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

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Cisco Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $164.98
Bundle Price: $139.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    630 Questions

    $124.99
    exam =35
  • exam =37
    350-601 Video Course

    Training Course

    143 Video Lectures

    $39.99

Cisco 350-601 Practice Test 14

Question 130

A newly commissioned network, compute or storage service reports: Two Nexus switches share an OSPFv2 segment, but their neighbors remain stuck in ExStart immediately after one uplink was changed to a larger MTU. Which implementation action should the engineer take first?

  1. Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role.
  2. Activate the correct EVPN address family for authorized peers and verify route advertisement policy.
  3. Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency.
  4. Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation.

Explanation

Correct Answer

C:

The root problem is that The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. The selected change addresses it directly: Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency. Verify the outcome: Both peers reach Full state and exchange the intended routes without retransmission or MTU errors.

Incorrect Answers

A:

This action concerns hsrp uplink tracking failover, where The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. The reported failure instead stems from The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably.

B:

This action concerns mp-BGP evpn address family activation, where The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. The corrective response here is “Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency”; this alternative does not provide that response.

D:

This action concerns ospfv3 ipv6 area consistency, where The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. The stem reports two Nexus switches share an OSPFv2 segment, but their neighbors remain stuck in ExStart immediately after one uplink was changed to a larger MTU; this control addresses a different failure condition.

Question 131

A data center implementation team investigates the following fault: A newly introduced access VLAN sees ARP spoofing attempts despite DHCP snooping being enabled because no dynamic ARP inspection policy is active for the VLAN. Which root cause best explains this behavior?

  1. The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements.
  2. DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies.
  3. The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities.
  4. DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN.

Explanation

Correct Answer

D:

The technical cause is DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. The appropriate response is: Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings. Confirm successful repair: Spoofed ARP replies are discarded while authorized clients retain normal gateway connectivity.

Incorrect Answers

A:

The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. “Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports” would address that alternative cause, not the condition in this question: dHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN.

B:

“Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths” responds to this separate finding: dHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. This question instead needs “Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings”, so the alternative does not meet the stated condition.

C:

The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. “Assign a supported restricted UCS role and scope matching the storage administration tasks” applies to that separate problem. The observed case is a newly introduced access VLAN sees ARP spoofing attempts despite DHCP snooping being enabled because no dynamic ARP inspection policy is active for the VLAN; choosing this alternative would address the wrong failure mode.

Question 132

A Nexus, UCS or MDS operations team encounters this issue: A zoning administrator cannot commit an MDS fabric configuration because an abandoned pending change session has left a CFS lock on the fabric. Which corrective change best resolves this problem?

  1. Verify target port FLOGI and FCNS registration and restore the authorized target attachment.
  2. Identify the legitimate lock owner and safely complete or abort the supported CFS session.
  3. Commit the approved device alias database transaction and verify resolution across the affected switches.
  4. Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning.

Explanation

Correct Answer

B:

The root problem is that A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. The selected change addresses it directly: Identify the legitimate lock owner and safely complete or abort the supported CFS session. Verify the outcome: The fabric accepts a new authorized zoning transaction with consistent configuration distribution.

Incorrect Answers

A:

This action concerns fibre channel name server registration, where The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. The reported failure instead stems from A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session.

C:

This action concerns cisco mds device alias commit behavior, where Device alias changes have not been committed and distributed through the supported fabric database workflow. The corrective response here is “Identify the legitimate lock owner and safely complete or abort the supported CFS session”; this alternative does not provide that response.

D:

This action concerns active fibre channel zoneset validation, where An inactive zoning database edit does not change the effective active zoneset on the SAN fabric. The stem reports a zoning administrator cannot commit an MDS fabric configuration because an abandoned pending change session has left a CFS lock on the fabric; this control addresses a different failure condition.

Question 133

A data center implementation team investigates the following fault: Two VXLAN leaf switches serve the same tenant bridge domain but forward frames to different VXLAN network identifiers due to mismatched local mappings. Which test outcome proves the intended service was restored?

  1. Remote VTEPs learn the required IP prefix in the correct VRF and forward traffic toward its reachable next hop.
  2. Hosts in the authorized segment communicate across leaves while unrelated tenant segments remain separate.
  3. Remote VTEP loopbacks resolve correctly and workload frames traverse the VXLAN overlay.
  4. The remote leaf learns the intended endpoint MAC through a valid EVPN route and forwards frames correctly.

Explanation

Correct Answer

B:

This observation validates vxlan vlan vni mapping consistency: The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The corresponding corrective action is: Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. “Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF” would address that alternative cause, not the condition in this question: the tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs.

C:

“Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies” responds to this separate finding: the NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. This question instead needs “Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves”, so the alternative does not meet the stated condition.

D:

The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. “Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI” applies to that separate problem. The observed case is two VXLAN leaf switches serve the same tenant bridge domain but forward frames to different VXLAN network identifiers due to mismatched local mappings; choosing this alternative would address the wrong failure mode.

Question 134

A data center implementation team investigates the following fault: A regulated east-west inter-switch link must protect Ethernet frames in transit, but an approved MACsec session is absent even though the physical port is up. Which verification result most directly demonstrates successful repair?

  1. Authorized operators authenticate normally through remote AAA and recover access through the documented fallback during an outage.
  2. The approved peer switch joins the SAN while a nonapproved test switch is denied fabric access.
  3. The intended OSPF adjacency remains authenticated across the key-rotation window with old keys retired safely.
  4. The link shows an operational encrypted MACsec association and permitted traffic continues normally.

Explanation

Correct Answer

D:

This observation validates macsec encrypted inter switch links: Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. The corresponding corrective action is: Configure supported MACsec policy and secure key agreement on both authorized switch endpoints. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. “Correct the supported UCS authentication realm order and emergency access procedure under change control” would address that alternative cause, not the condition in this question: link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection.

B:

“Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs” responds to this separate finding: fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. This question instead needs “Configure supported MACsec policy and secure key agreement on both authorized switch endpoints”, so the alternative does not meet the stated condition.

C:

The OSPF authentication peers are using mismatched active key IDs or validity intervals. “Coordinate the supported authentication keychain parameters and overlapping key transition periods” applies to that separate problem. The observed case is a regulated east-west inter-switch link must protect Ethernet frames in transit, but an approved MACsec session is absent even though the physical port is up; choosing this alternative would address the wrong failure mode.

Question 135

A Nexus, UCS or MDS operations team encounters this issue: An Ansible playbook meant for lab Nexus switches changes production switch banners because its inventory group variables include production hosts inadvertently. Which test outcome proves the intended service was restored?

  1. Only the designated lab devices receive changes and production targets remain unchanged.
  2. The collector processes supported payload variants and flags incomplete metrics without terminating the monitoring job.
  3. The target server profile references the expected boot and connectivity policies with no cross-tenant linkage.
  4. Repeated execution converges to the same desired configuration without unintended duplicate changes.

Explanation

Correct Answer

A:

This observation validates ansible inventory variable scoping: The playbook target inventory and variable precedence do not isolate the intended lab device group. The corresponding corrective action is: Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The parser lacks schema validation and robust handling of absent or differently typed telemetry values. “Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics” would address that alternative cause, not the condition in this question: the playbook target inventory and variable precedence do not isolate the intended lab device group.

C:

“Use stable approved resource IDs and validate organization scope before assigning Intersight policies” responds to this separate finding: the API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. This question instead needs “Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution”, so the alternative does not meet the stated condition.

D:

The script lacks an idempotent precheck to compare desired and current network device state. “Query existing NX-OS state before applying only the necessary authorized configuration differences” applies to that separate problem. The observed case is an Ansible playbook meant for lab Nexus switches changes production switch banners because its inventory group variables include production hosts inadvertently; choosing this alternative would address the wrong failure mode.

Question 136

A Nexus, UCS or MDS operations team encounters this issue: A storage technician adds several unrelated host initiators into a single large FC zone with a common array, creating unnecessary visibility between initiators. What is the most appropriate remediation for these symptoms?

  1. Verify target port FLOGI and FCNS registration and restore the authorized target attachment.
  2. Identify the legitimate lock owner and safely complete or abort the supported CFS session.
  3. Create separate approved zones for each host initiator with its authorized storage target ports.
  4. Commit the approved device alias database transaction and verify resolution across the affected switches.

Explanation

Correct Answer

C:

The root problem is that The zone combines initiators beyond the least-privilege single-initiator zoning design. The selected change addresses it directly: Create separate approved zones for each host initiator with its authorized storage target ports. Verify the outcome: Each host discovers its intended target while unrelated initiator WWPNs are not jointly zoned.

Incorrect Answers

A:

This action concerns fibre channel name server registration, where The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. The reported failure instead stems from The zone combines initiators beyond the least-privilege single-initiator zoning design.

B:

This action concerns cisco fabric services configuration distribution, where A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. The corrective response here is “Create separate approved zones for each host initiator with its authorized storage target ports”; this alternative does not provide that response.

D:

This action concerns cisco mds device alias commit behavior, where Device alias changes have not been committed and distributed through the supported fabric database workflow. The stem reports a storage technician adds several unrelated host initiators into a single large FC zone with a common array, creating unnecessary visibility between initiators; this control addresses a different failure condition.

Question 137

During a Cisco data center readiness review, engineers observe: A Nexus pair is scheduled for supposedly hitless software maintenance even though the target release does not support nondisruptive upgrade for the active feature combination. What technical condition most directly accounts for the failure?

  1. The change process omitted a recoverable NX-OS configuration checkpoint and validation plan.
  2. The planned software transition omits the EPLD compatibility and operational impact assessment.
  3. The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range.
  4. The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints.

Explanation

Correct Answer

D:

The technical cause is The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. The appropriate response is: Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path. Confirm successful repair: A staged test establishes the actual traffic impact and the upgrade follows the approved compatibility plan.

Incorrect Answers

A:

The change process omitted a recoverable NX-OS configuration checkpoint and validation plan. “Create and use a supported configuration checkpoint or approved rollback before editing the production policy” would address that alternative cause, not the condition in this question: the upgrade plan assumes ISSU support without validating the platform release path and active feature constraints.

B:

“Review supported EPLD package requirements and schedule the component update using the prescribed procedure” responds to this separate finding: the planned software transition omits the EPLD compatibility and operational impact assessment. This question instead needs “Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path”, so the alternative does not meet the stated condition.

C:

The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. “Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups” applies to that separate problem. The observed case is a Nexus pair is scheduled for supposedly hitless software maintenance even though the target release does not support nondisruptive upgrade for the active feature combination; choosing this alternative would address the wrong failure mode.

Question 138

A Nexus, UCS or MDS operations team encounters this issue: A newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management. Which verification result most directly demonstrates successful repair?

  1. Remote VTEPs learn the required IP prefix in the correct VRF and forward traffic toward its reachable next hop.
  2. After VM migration the endpoint belongs to the right EPG and retains its intended connectivity and contracts.
  3. APIC reports the expected interface and EPG deployment, and authorized server traffic is forwarded.
  4. APIC shows the assigned leaf as an active fabric member with the expected spine adjacency.

Explanation

Correct Answer

D:

This observation validates aci leaf onboarding discovery: The leaf has not completed the supported ACI fabric discovery and node-registration workflow. The corresponding corrective action is: Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. “Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF” would address that alternative cause, not the condition in this question: the leaf has not completed the supported ACI fabric discovery and node-registration workflow.

B:

“Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment” responds to this separate finding: the ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. This question instead needs “Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC”, so the alternative does not meet the stated condition.

C:

The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. “Correct the supported ACI interface policy selector and physical domain association for the host-facing port” applies to that separate problem. The observed case is a newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management; choosing this alternative would address the wrong failure mode.

Question 139

During a Cisco data center readiness review, engineers observe: A remote tenant workload is connected to a leaf, yet peer VTEPs never learn the workload MAC address from the EVPN control plane. After remediation, which acceptance result is most relevant?

  1. The remote leaf learns the intended endpoint MAC through a valid EVPN route and forwards frames correctly.
  2. Interested ports retain multicast group membership and nonmembers do not receive unwanted replicated streams.
  3. Remote VTEP loopbacks resolve correctly and workload frames traverse the VXLAN overlay.
  4. Hosts in the authorized segment communicate across leaves while unrelated tenant segments remain separate.

Explanation

Correct Answer

A:

This observation validates evpn mac reachability type two routes: The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. The corresponding corrective action is: Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The VLAN lacks a reachable supported multicast querier. “Provide a valid IGMP querier through the routed gateway or supported switching configuration” would address that alternative cause, not the condition in this question: the Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy.

C:

“Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies” responds to this separate finding: the NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. This question instead needs “Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI”, so the alternative does not meet the stated condition.

D:

The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. “Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves” applies to that separate problem. The observed case is a remote tenant workload is connected to a leaf, yet peer VTEPs never learn the workload MAC address from the EVPN control plane; choosing this alternative would address the wrong failure mode.

Question 140

A Nexus, UCS or MDS operations team encounters this issue: A rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping. What is the most appropriate remediation for these symptoms?

  1. Coordinate the supported authentication keychain parameters and overlapping key transition periods.
  2. Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths.
  3. Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports.
  4. Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings.

Explanation

Correct Answer

B:

The root problem is that DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. The selected change addresses it directly: Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths. Verify the outcome: Unauthorized DHCP offers are dropped while valid clients receive leases from the approved server.

Incorrect Answers

A:

This action concerns ospf keychain authentication rotation, where The OSPF authentication peers are using mismatched active key IDs or validity intervals. The reported failure instead stems from DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies.

C:

This action concerns ipv6 router advertisement guard, where The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. The corrective response here is “Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths”; this alternative does not provide that response.

D:

This action concerns dynamic arp inspection binding validation, where DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. The stem reports a rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping; this control addresses a different failure condition.