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 12

Question 110

During a Cisco data center readiness review, engineers observe: A storage administrator is given a full UCS administrator role even though the job requires only SAN and vHBA policy visibility. Which approved technology action addresses this incident most directly?

  1. Correct the supported UCS authentication realm order and emergency access procedure under change control.
  2. Assign a supported restricted UCS role and scope matching the storage administration tasks.
  3. Configure supported MDS port-security bindings for the intended server initiator and affected VSAN.
  4. Apply the approved organization-scoped Intersight RBAC role for the automation identity.

Explanation

Correct Answer

B:

The root problem is that The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. The selected change addresses it directly: Assign a supported restricted UCS role and scope matching the storage administration tasks. Verify the outcome: The user can inspect authorized SAN settings but cannot change unrelated server identity and LAN policies.

Incorrect Answers

A:

This action concerns ucs remote aaa fallback authentication, where The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. The reported failure instead stems from The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities.

C:

This action concerns mds fibre channel port security binding, where Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. The corrective response here is “Assign a supported restricted UCS role and scope matching the storage administration tasks”; this alternative does not provide that response.

D:

This action concerns intersight organization scoped administrative role, where The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. The stem reports a storage administrator is given a full UCS administrator role even though the job requires only SAN and vHBA policy visibility; this control addresses a different failure condition.

Question 111

A Nexus, UCS or MDS operations team encounters this issue: The zoning administrator changes a device alias name to point to a replacement HBA, but other switches keep resolving the old identity because the alias database was not committed. What preventive control would best avoid repeating this fault?

  1. Include FCNS database and target registration checks before troubleshooting zoning alone.
  2. Verify pending and committed device alias state whenever server HBA identities change.
  3. Check active zoneset state and distribution after all SAN access change approvals.
  4. Require CFS lock review and transaction closeout after SAN zoning maintenance.

Explanation

Correct Answer

B:

This safeguard addresses cisco mds device alias commit behavior: Device alias changes have not been committed and distributed through the supported fabric database workflow. The appropriate prevention is: Verify pending and committed device alias state whenever server HBA identities change. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. “Include FCNS database and target registration checks before troubleshooting zoning alone” would address that alternative cause, not the condition in this question: device alias changes have not been committed and distributed through the supported fabric database workflow.

C:

“Check active zoneset state and distribution after all SAN access change approvals” responds to this separate finding: an inactive zoning database edit does not change the effective active zoneset on the SAN fabric. This question instead needs “Verify pending and committed device alias state whenever server HBA identities change”, so the alternative does not meet the stated condition.

D:

A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. “Require CFS lock review and transaction closeout after SAN zoning maintenance” applies to that separate problem. The observed case is the zoning administrator changes a device alias name to point to a replacement HBA, but other switches keep resolving the old identity because the alias database was not committed; choosing this alternative would address the wrong failure mode.

Question 112

A Nexus, UCS or MDS operations team encounters this issue: An engineer changes a Nexus port-channel policy and several interfaces stop passing traffic, but no approved prechange rollback point exists. What is the most appropriate remediation for these symptoms?

  1. Review supported EPLD package requirements and schedule the component update using the prescribed procedure.
  2. Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves.
  3. Create and use a supported configuration checkpoint or approved rollback before editing the production policy.
  4. Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path.

Explanation

Correct Answer

C:

The root problem is that The change process omitted a recoverable NX-OS configuration checkpoint and validation plan. The selected change addresses it directly: Create and use a supported configuration checkpoint or approved rollback before editing the production policy. Verify the outcome: The device returns to the known-good configuration with traffic restored after rollback is exercised.

Incorrect Answers

A:

This action concerns nexus epld upgrade safety, where The planned software transition omits the EPLD compatibility and operational impact assessment. The reported failure instead stems from The change process omitted a recoverable NX-OS configuration checkpoint and validation plan.

B:

This action concerns vxlan vlan vni mapping consistency, where The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The corrective response here is “Create and use a supported configuration checkpoint or approved rollback before editing the production policy”; this alternative does not provide that response.

D:

This action concerns nx os issu support preflight, where The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. The stem reports an engineer changes a Nexus port-channel policy and several interfaces stop passing traffic, but no approved prechange rollback point exists; this control addresses a different failure condition.

Question 113

A data center administrator identifies the following risk: A new Fibre Channel port-channel member on MDS remains suspended after a technician applies the wrong VSAN trunk attributes to that physical interface. Which corrective change best resolves this problem?

  1. Identify the legitimate lock owner and safely complete or abort the supported CFS session.
  2. Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status.
  3. Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member.
  4. Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process.

Explanation

Correct Answer

C:

The root problem is that The FC port channel and prospective member disagree on required operational attributes for bundling. The selected change addresses it directly: Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member. Verify the outcome: Both members become operational in the port channel and load distribution remains stable.

Incorrect Answers

A:

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 reported failure instead stems from The FC port channel and prospective member disagree on required operational attributes for bundling.

B:

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 corrective response here is “Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member”; this alternative does not provide that response.

D:

This action concerns fibre channel domain id collision, where The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. The stem reports a new Fibre Channel port-channel member on MDS remains suspended after a technician applies the wrong VSAN trunk attributes to that physical interface; this control addresses a different failure condition.

Question 114

A data center administrator identifies the following risk: Intermittent Fibre Channel congestion causes storage latency spikes, yet operators rely only on link-up indicators and miss buffer-credit or port-error trends. Which verification result most directly demonstrates successful repair?

  1. The module and operating system versions satisfy Cisco's documented compatibility requirements after the change.
  2. A lab or pilot establishes the expected outage characteristics and the approved upgrade completes safely.
  3. A time-aligned report identifies the affected SAN ports and correlates counters with storage latency.
  4. The SAN analyzer receives the relevant FC exchanges needed to isolate the transport fault.

Explanation

Correct Answer

C:

This observation validates nexus dashboard san performance assurance: The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. The corresponding corrective action is: Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. “Review the applicable MDS EPLD package and schedule the correct supported component update” would address that alternative cause, not the condition in this question: the SAN observability baseline does not collect relevant port performance metrics and historical assurance trends.

B:

“Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method” responds to this separate finding: the selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. This question instead needs “Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis”, so the alternative does not meet the stated condition.

D:

The Fibre Channel SPAN session source does not identify the failing interface or service path. “Set a supported FC SPAN monitor source for the affected port and the approved capture destination” applies to that separate problem. The observed case is intermittent Fibre Channel congestion causes storage latency spikes, yet operators rely only on link-up indicators and miss buffer-credit or port-error trends; choosing this alternative would address the wrong failure mode.

Question 115

A Nexus, UCS or MDS operations team encounters this issue: Distributed model training runs across GPU pods but experiences network bottlenecks because oversubscribed links carry synchronized east-west collective operations without capacity planning. Which design or configuration error caused the described issue?

  1. The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload.
  2. The parser lacks schema validation and robust handling of absent or differently typed telemetry values.
  3. The REST client does not distinguish insufficient authorization from retryable transport or server errors.
  4. The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards.

Explanation

Correct Answer

A:

The technical cause is The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload. The appropriate response is: Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology. Confirm successful repair: Collective workload tests meet the required throughput and latency targets without sustained link oversubscription.

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 data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload.

C:

“Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures” responds to this separate finding: the REST client does not distinguish insufficient authorization from retryable transport or server errors. This question instead needs “Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology”, so the alternative does not meet the stated condition.

D:

The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. “Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path” applies to that separate problem. The observed case is distributed model training runs across GPU pods but experiences network bottlenecks because oversubscribed links carry synchronized east-west collective operations without capacity planning; choosing this alternative would address the wrong failure mode.

Question 116

A data center implementation team investigates the following fault: An MDS inter-switch link is online but initiators in VSAN 30 cannot reach targets on the far switch after a new trunk was introduced. Which corrective change best resolves this problem?

  1. Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status.
  2. Commit the approved device alias database transaction and verify resolution across the affected switches.
  3. Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member.
  4. Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator.

Explanation

Correct Answer

A:

The root problem is that The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. The selected change addresses it directly: Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status. Verify the outcome: The target and initiator register and exchange traffic inside VSAN 30 without affecting other VSANs.

Incorrect Answers

B:

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 reported failure instead stems from The FC trunk does not carry the required VSAN membership consistently between the two MDS switches.

C:

This action concerns fibre channel port channel member consistency, where The FC port channel and prospective member disagree on required operational attributes for bundling. The corrective response here is “Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status”; this alternative does not provide that response.

D:

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 stem reports an MDS inter-switch link is online but initiators in VSAN 30 cannot reach targets on the far switch after a new trunk was introduced; this control addresses a different failure condition.

Question 117

A data center administrator identifies the following risk: A replacement UCS fabric interconnect has been installed, but operators have no recent recoverable configuration backup for the domain's identity pools and policies. Which design or configuration error caused the described issue?

  1. The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints.
  2. The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow.
  3. The server identity has not been abstracted through approved UCS service profile and identity-pool associations.
  4. The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites.

Explanation

Correct Answer

B:

The technical cause is The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. The appropriate response is: Create or restore an authorized UCS configuration backup and validate the documented recovery procedure. Confirm successful repair: The recovered management domain contains consistent service profiles, pools and fabric policies after restoration.

Incorrect Answers

A:

The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. “Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria” would address that alternative cause, not the condition in this question: the UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow.

C:

“Associate the intended service profile and its identity pools with the supported replacement hardware” responds to this separate finding: the server identity has not been abstracted through approved UCS service profile and identity-pool associations. This question instead needs “Create or restore an authorized UCS configuration backup and validate the documented recovery procedure”, so the alternative does not meet the stated condition.

D:

The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. “Select a compatible validated firmware package and update the affected server policy under change control” applies to that separate problem. The observed case is a replacement UCS fabric interconnect has been installed, but operators have no recent recoverable configuration backup for the domain's identity pools and policies; choosing this alternative would address the wrong failure mode.

Question 118

A newly commissioned network, compute or storage service reports: An external service subnet must be reached through an EVPN VXLAN fabric, but peer leaves learn endpoint MACs without the expected IP prefix route. Which implementation action should the engineer take first?

  1. Provide a valid IGMP querier through the routed gateway or supported switching configuration.
  2. Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF.
  3. Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies.
  4. Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves.

Explanation

Correct Answer

B:

The root problem is that The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. The selected change addresses it directly: Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF. Verify the outcome: Remote VTEPs learn the required IP prefix in the correct VRF and forward traffic toward its reachable next hop.

Incorrect Answers

A:

This action concerns igmp snooping querier requirement, where IGMP snooping membership state is not refreshed because the VLAN lacks a reachable supported multicast querier. The reported failure instead stems from The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route.

C:

This action concerns vxlan vtep loopback reachability, where The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. The corrective response here is “Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF”; this alternative does not provide that response.

D:

This action concerns vxlan vlan vni mapping consistency, where The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The stem reports an external service subnet must be reached through an EVPN VXLAN fabric, but peer leaves learn endpoint MACs without the expected IP prefix route; this control addresses a different failure condition.

Question 119

A newly commissioned network, compute or storage service reports: An NFS mount command fails from a new virtualization host even though the storage array responds to ping, and the export permits only the retired host subnet. What technical condition most directly accounts for the failure?

  1. The NFS export access rules do not authorize the requesting client address or security identity.
  2. The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials.
  3. The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation.
  4. NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch.

Explanation

Correct Answer

A:

The technical cause is The NFS export access rules do not authorize the requesting client address or security identity. The appropriate response is: Update the scoped NFS export policy to include only the approved new hypervisor client addresses. Confirm successful repair: The new host mounts the intended export while an unauthorized client remains denied.

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 NFS export access rules do not authorize the requesting client address or security identity.

C:

“Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk” responds to this separate finding: the application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. This question instead needs “Update the scoped NFS export policy to include only the approved new hypervisor client addresses”, so the alternative does not meet the stated condition.

D:

NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. “Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design” applies to that separate problem. The observed case is an NFS mount command fails from a new virtualization host even though the storage array responds to ping, and the export permits only the retired host subnet; choosing this alternative would address the wrong failure mode.

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.