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 13

Question 120

A data center implementation team investigates the following fault: A data center hypervisor installation fails hardware virtualization preflight on otherwise compatible UCS blades after a generic BIOS profile disabled virtualization features. What preventive control would best avoid repeating this fault?

  1. Review association change previews, reboot implications and backout steps before production reassignment.
  2. Check local RAID configuration, disk health and boot target during UCS C-Series acceptance.
  3. Include hardware sensors and fault trend alerts in the standard UCS server health baseline.
  4. Tie UCS BIOS templates to documented operating system and hypervisor compatibility requirements.

Explanation

Correct Answer

D:

This safeguard addresses ucs bios virtualization extensions: The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The appropriate prevention is: Tie UCS BIOS templates to documented operating system and hypervisor compatibility requirements. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings. “Review association change previews, reboot implications and backout steps before production reassignment” would address that alternative cause, not the condition in this question: the BIOS policy disables required CPU virtualization support expected by the approved hypervisor.

B:

“Check local RAID configuration, disk health and boot target during UCS C-Series acceptance” responds to this separate finding: the server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. This question instead needs “Tie UCS BIOS templates to documented operating system and hypervisor compatibility requirements”, so the alternative does not meet the stated condition.

C:

The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. “Include hardware sensors and fault trend alerts in the standard UCS server health baseline” applies to that separate problem. The observed case is a data center hypervisor installation fails hardware virtualization preflight on otherwise compatible UCS blades after a generic BIOS profile disabled virtualization features; choosing this alternative would address the wrong failure mode.

Question 121

A newly commissioned network, compute or storage service reports: An installed UCS blade becomes unreachable when the only mapped I/O module path is disabled although a second IOM is physically available. Which implementation action should the engineer take first?

  1. Create the supported UCS server pool qualification and associate the workload profile with eligible members.
  2. Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access.
  3. Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior.
  4. Use an approved updating service profile template and apply governed changes to its associated server profiles.

Explanation

Correct Answer

C:

The root problem is that The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. The selected change addresses it directly: Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior. Verify the outcome: The blade retains expected connectivity under an individual fabric path outage within the approved design.

Incorrect Answers

A:

This action concerns ucs server pool qualification matching, where The server pool qualification policy does not limit placement to servers with the required hardware capabilities. The reported failure instead stems from The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths.

B:

This action concerns ucs vlan uplink permitted configuration, where The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. The corrective response here is “Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior”; this alternative does not provide that response.

D:

This action concerns ucs updating service profile templates, where The configuration process bypasses the intended reusable UCS service profile template inheritance model. The stem reports an installed UCS blade becomes unreachable when the only mapped I/O module path is disabled although a second IOM is physically available; this control addresses a different failure condition.

Question 122

While checking a production data center change, the team finds: An HBA completes fabric login but the intended target WWPN cannot be discovered because the target never registers with the Fibre Channel name server. After remediation, which acceptance result is most relevant?

  1. The MDS name-server database contains the correct target and initiator identities for the relevant VSAN.
  2. The iSCSI login authenticates successfully and the host discovers its authorized block LUN.
  3. The fabric accepts a new authorized zoning transaction with consistent configuration distribution.
  4. Each host discovers its intended target while unrelated initiator WWPNs are not jointly zoned.

Explanation

Correct Answer

A:

This observation validates fibre channel name server registration: The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. The corresponding corrective action is: Verify target port FLOGI and FCNS registration and restore the authorized target attachment. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. “Update the approved initiator and target CHAP secret settings using the supported secure workflow” would address that alternative cause, not the condition in this question: the target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded.

C:

“Identify the legitimate lock owner and safely complete or abort the supported CFS session” responds to this separate finding: a Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. This question instead needs “Verify target port FLOGI and FCNS registration and restore the authorized target attachment”, so the alternative does not meet the stated condition.

D:

The zone combines initiators beyond the least-privilege single-initiator zoning design. “Create separate approved zones for each host initiator with its authorized storage target ports” applies to that separate problem. The observed case is an HBA completes fabric login but the intended target WWPN cannot be discovered because the target never registers with the Fibre Channel name server; choosing this alternative would address the wrong failure mode.

Question 123

While checking a production data center change, the team finds: An AI training fabric uses RoCEv2 GPU collective traffic, but bursts are repeatedly dropped because the Ethernet switches lack the supported priority flow-control and congestion management plan. Which approved technology action addresses this incident most directly?

  1. Deploy the script in the approved supported shell environment with required dependencies and bounded permissions.
  2. Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures.
  3. Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path.
  4. Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology.

Explanation

Correct Answer

C:

The root problem is that The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. The selected change addresses it directly: Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path. Verify the outcome: The GPU fabric sustains the benchmark workload with controlled loss and congestion indicators during bursts.

Incorrect Answers

A:

This action concerns nexus bash shell and guest shell isolation, where The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The reported failure instead stems from The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards.

B:

This action concerns rest api authorization status handling, where The REST client does not distinguish insufficient authorization from retryable transport or server errors. The corrective response here is “Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path”; this alternative does not provide that response.

D:

This action concerns ai workload high bandwidth east west paths, where The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload. The stem reports an AI training fabric uses RoCEv2 GPU collective traffic, but bursts are repeatedly dropped because the Ethernet switches lack the supported priority flow-control and congestion management plan; this control addresses a different failure condition.

Question 124

A Nexus, UCS or MDS operations team encounters this issue: A Nexus on-box Python remediation applet recreates the same VLAN and interface objects every run, producing repeated configuration changes even when state is already correct. Which root cause best explains this behavior?

  1. The NX-API request body and declared content format are inconsistent for the selected endpoint.
  2. The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.
  3. The script lacks an idempotent precheck to compare desired and current network device state.
  4. The embedded event manager event detector does not match the actual authorized BGP neighbor-down message.

Explanation

Correct Answer

C:

The technical cause is The script lacks an idempotent precheck to compare desired and current network device state. The appropriate response is: Query existing NX-OS state before applying only the necessary authorized configuration differences. Confirm successful repair: Repeated execution converges to the same desired configuration without unintended duplicate changes.

Incorrect Answers

A:

The NX-API request body and declared content format are inconsistent for the selected endpoint. “Send the supported NX-API request in the correct JSON or XML representation with matching headers” would address that alternative cause, not the condition in this question: the script lacks an idempotent precheck to compare desired and current network device state.

B:

“Deploy the script in the approved supported shell environment with required dependencies and bounded permissions” responds to this separate finding: the deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. This question instead needs “Query existing NX-OS state before applying only the necessary authorized configuration differences”, so the alternative does not meet the stated condition.

D:

The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. “Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event” applies to that separate problem. The observed case is a Nexus on-box Python remediation applet recreates the same VLAN and interface objects every run, producing repeated configuration changes even when state is already correct; choosing this alternative would address the wrong failure mode.

Question 125

While checking a production data center change, the team finds: Multicast receivers connected to a routed leaf cannot join a source in another segment after a PIM sparse-mode domain is extended to a new pod. What technical condition most directly accounts for the failure?

  1. The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts.
  2. The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link.
  3. The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range.
  4. The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability.

Explanation

Correct Answer

C:

The technical cause is The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. The appropriate response is: Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups. Confirm successful repair: The intended receivers join and receive source traffic, and PIM control state shows the proper tree.

Incorrect Answers

A:

The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. “Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation” would address that alternative cause, not the condition in this question: the routers do not agree on or reach the required rendezvous-point mapping for the multicast group range.

B:

“Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role” responds to this separate finding: the first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. This question instead needs “Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups”, so the alternative does not meet the stated condition.

D:

The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. “Activate the correct EVPN address family for authorized peers and verify route advertisement policy” applies to that separate problem. The observed case is multicast receivers connected to a routed leaf cannot join a source in another segment after a PIM sparse-mode domain is extended to a new pod; choosing this alternative would address the wrong failure mode.

Question 126

While checking a production data center change, the team finds: Two Cisco MDS Fibre Channel switches are merged into one fabric, but an ISL becomes segmented because both switches use the same configured domain ID. Which approved technology action addresses this incident most directly?

  1. Set a supported FC SPAN monitor source for the affected port and the approved capture destination.
  2. Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator.
  3. Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status.
  4. Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process.

Explanation

Correct Answer

D:

The root problem is that The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. The selected change addresses it directly: Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process. Verify the outcome: Both switches participate in one stable fabric with unique domain IDs and expected FSPF reachability.

Incorrect Answers

A:

This action concerns cisco mds span fibre channel troubleshooting, where The Fibre Channel SPAN session source does not identify the failing interface or service path. The reported failure instead stems from The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization.

B:

This action concerns flogi registration and fcid assignment, where The initiator has not completed successful fabric login and thus has no authorized FCID assignment. The corrective response here is “Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process”; this alternative does not provide that response.

C:

This action concerns fibre channel isl trunk vsan allowance, where The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. The stem reports two Cisco MDS Fibre Channel switches are merged into one fabric, but an ISL becomes segmented because both switches use the same configured domain ID; this control addresses a different failure condition.

Question 127

While checking a production data center change, the team finds: An unauthorized workstation sends IPv6 router advertisements on a Nexus access VLAN, causing nearby hosts to adopt an attacker-controlled default router. Which approved technology action addresses this incident most directly?

  1. Configure supported MACsec policy and secure key agreement on both authorized switch endpoints.
  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

C:

The root problem is that The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. The selected change addresses it directly: Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports. Verify the outcome: Hosts ignore the unauthorized router advertisement and retain the approved IPv6 default gateway.

Incorrect Answers

A:

This action concerns macsec encrypted inter switch links, where Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. The reported failure instead stems from The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements.

B:

This action concerns dhcp snooping trusted server interface, where DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. The corrective response here is “Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports”; 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 an unauthorized workstation sends IPv6 router advertisements on a Nexus access VLAN, causing nearby hosts to adopt an attacker-controlled default router; this control addresses a different failure condition.

Question 128

During a Cisco data center readiness review, engineers observe: A Cisco Nexus switch locally observes abnormal traffic, but the monitoring platform receives no NetFlow records after the exporter destination was moved. Which deployment safeguard most directly reduces this failure risk?

  1. Document SPAN source and destination interface restrictions for troubleshooting changes.
  2. Review telemetry subscriptions and alert coverage after changes to device software or fabric topology.
  3. Monitor flow exporter reachability and collector acceptance after telemetry network changes.
  4. Require a NIST model classification review during cloud migration architecture approvals.

Explanation

Correct Answer

C:

This safeguard addresses netflow exporter reachability: Flow-export destination reachability or the configured source and monitoring VRF are incorrect. The appropriate prevention is: Monitor flow exporter reachability and collector acceptance after telemetry network changes. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The SPAN session source and dedicated monitor destination roles were assigned incorrectly. “Document SPAN source and destination interface restrictions for troubleshooting changes” would address that alternative cause, not the condition in this question: flow-export destination reachability or the configured source and monitoring VRF are incorrect.

B:

“Review telemetry subscriptions and alert coverage after changes to device software or fabric topology” responds to this separate finding: the monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. This question instead needs “Monitor flow exporter reachability and collector acceptance after telemetry network changes”, so the alternative does not meet the stated condition.

D:

Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. “Require a NIST model classification review during cloud migration architecture approvals” applies to that separate problem. The observed case is a Cisco Nexus switch locally observes abnormal traffic, but the monitoring platform receives no NetFlow records after the exporter destination was moved; choosing this alternative would address the wrong failure mode.

Question 129

A data center implementation team investigates the following fault: A replacement HBA connects to an open MDS F-port and can enter the SAN even though the port should accept only preauthorized initiator identities. What is the most appropriate remediation for these symptoms?

  1. Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs.
  2. Configure supported MDS port-security bindings for the intended server initiator and affected VSAN.
  3. Correct the ACI contract consumer-provider bindings and permit only the required application port.
  4. Replace the overly broad MDS role with an approved read-only or scoped monitoring role.

Explanation

Correct Answer

B:

The root problem is that Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. The selected change addresses it directly: Configure supported MDS port-security bindings for the intended server initiator and affected VSAN. Verify the outcome: The approved HBA logs in while a test unapproved WWPN is rejected by the protected fabric port.

Incorrect Answers

A:

This action concerns mds fibre channel fabric binding, where Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. The reported failure instead stems from Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.

C:

This action concerns aci contract consumer provider policy, where The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. The corrective response here is “Configure supported MDS port-security bindings for the intended server initiator and affected VSAN”; this alternative does not provide that response.

D:

This action concerns cisco mds administrative role authorization, where The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. The stem reports a replacement HBA connects to an open MDS F-port and can enter the SAN even though the port should accept only preauthorized initiator identities; this control addresses a different failure condition.

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.