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 27

Question 260

A Nexus, UCS or MDS operations team encounters this issue: A monitoring Python script assumes a nested JSON metric is always a number and crashes when NX-OS telemetry omits the optional field on one hardware platform. What is the most appropriate remediation for these symptoms?

  1. Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path.
  2. Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics.
  3. Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution.
  4. Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources.

Explanation

Correct Answer

B:

The root problem is that The parser lacks schema validation and robust handling of absent or differently typed telemetry values. The selected change addresses it directly: Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics. Verify the outcome: The collector processes supported payload variants and flags incomplete metrics without terminating the monitoring job.

Incorrect Answers

A:

This action concerns ai roce lossless class design, where The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. The reported failure instead stems from The parser lacks schema validation and robust handling of absent or differently typed telemetry values.

C:

This action concerns ansible inventory variable scoping, where The playbook target inventory and variable precedence do not isolate the intended lab device group. The corrective response here is “Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics”; this alternative does not provide that response.

D:

This action concerns terraform plan infrastructure drift, where The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. The stem reports a monitoring Python script assumes a nested JSON metric is always a number and crashes when NX-OS telemetry omits the optional field on one hardware platform; this control addresses a different failure condition.

Question 261

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. Which test outcome proves the intended service was restored?

  1. All participating MDS switches resolve the alias to the intended replacement WWPN consistently.
  2. The active zoneset includes the desired members and the server discovers only its allowed storage target.
  3. The MDS name-server database contains the correct target and initiator identities for the relevant VSAN.
  4. The fabric accepts a new authorized zoning transaction with consistent configuration distribution.

Explanation

Correct Answer

A:

This observation validates cisco mds device alias commit behavior: Device alias changes have not been committed and distributed through the supported fabric database workflow. The corresponding corrective action is: Commit the approved device alias database transaction and verify resolution across the affected switches. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

An inactive zoning database edit does not change the effective active zoneset on the SAN fabric. “Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning” 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:

“Verify target port FLOGI and FCNS registration and restore the authorized target attachment” responds to this separate finding: the target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. This question instead needs “Commit the approved device alias database transaction and verify resolution across the affected switches”, 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. “Identify the legitimate lock owner and safely complete or abort the supported CFS session” 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 262

A data center implementation team investigates the following fault: A newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management. Which corrective change best resolves this problem?

  1. Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC.
  2. Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves.
  3. Correct the supported ACI interface policy selector and physical domain association for the host-facing port.
  4. Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment.

Explanation

Correct Answer

A:

The root problem is that The leaf has not completed the supported ACI fabric discovery and node-registration workflow. The selected change addresses it directly: Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC. Verify the outcome: APIC shows the assigned leaf as an active fabric member with the expected spine adjacency.

Incorrect Answers

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 reported failure instead stems from The leaf has not completed the supported ACI fabric discovery and node-registration workflow.

C:

This action concerns aci access policy interface selector binding, where The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. The corrective response here is “Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC”; this alternative does not provide that response.

D:

This action concerns aci vmm domain dynamic endpoint learning, where The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. The stem reports a newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management; this control addresses a different failure condition.

Question 263

A data center implementation team investigates the following fault: An engineer runs a Linux shell script inside the Nexus host environment and assumes it has the same dependencies and resource isolation as a supported Guest Shell container. What ongoing validation should operations establish for this service?

  1. Review EEM triggers and action privilege requirements whenever NX-OS log formats or releases change.
  2. Document shell boundaries and supported packages before on-box automation deployment.
  3. Build explicit error classification and bounded retries into every infrastructure API client.
  4. Audit scheduler job frequency and execution history after automation changes.

Explanation

Correct Answer

B:

This safeguard addresses nexus bash shell and guest shell isolation: The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The appropriate prevention is: Document shell boundaries and supported packages before on-box automation deployment. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. “Review EEM triggers and action privilege requirements whenever NX-OS log formats or releases change” would address that alternative cause, not the condition in this question: the deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.

C:

“Build explicit error classification and bounded retries into every infrastructure API client” responds to this separate finding: the REST client does not distinguish insufficient authorization from retryable transport or server errors. This question instead needs “Document shell boundaries and supported packages before on-box automation deployment”, so the alternative does not meet the stated condition.

D:

The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. “Audit scheduler job frequency and execution history after automation changes” applies to that separate problem. The observed case is an engineer runs a Linux shell script inside the Nexus host environment and assumes it has the same dependencies and resource isolation as a supported Guest Shell container; choosing this alternative would address the wrong failure mode.

Question 264

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. What preventive control would best avoid repeating this fault?

  1. Include FCNS database and target registration checks before troubleshooting zoning alone.
  2. Use standardized single-initiator zoning patterns in the SAN access request process.
  3. Require CFS lock review and transaction closeout after SAN zoning maintenance.
  4. Verify pending and committed device alias state whenever server HBA identities change.

Explanation

Correct Answer

C:

This safeguard addresses cisco fabric services configuration distribution: A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. The appropriate prevention is: Require CFS lock review and transaction closeout after SAN zoning maintenance. 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: a Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session.

B:

“Use standardized single-initiator zoning patterns in the SAN access request process” responds to this separate finding: the zone combines initiators beyond the least-privilege single-initiator zoning design. This question instead needs “Require CFS lock review and transaction closeout after SAN zoning maintenance”, so the alternative does not meet the stated condition.

D:

Device alias changes have not been committed and distributed through the supported fabric database workflow. “Verify pending and committed device alias state whenever server HBA identities change” applies to that separate problem. The observed case is a zoning administrator cannot commit an MDS fabric configuration because an abandoned pending change session has left a CFS lock on the fabric; choosing this alternative would address the wrong failure mode.

Question 265

A data center administrator identifies the following risk: A new WWPN zone has been created in the MDS zoning database but the application host still cannot see its storage array because the zoneset was never activated. Which root cause best explains this behavior?

  1. An inactive zoning database edit does not change the effective active zoneset on the SAN fabric.
  2. The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation.
  3. Device alias changes have not been committed and distributed through the supported fabric database workflow.
  4. The zone combines initiators beyond the least-privilege single-initiator zoning design.

Explanation

Correct Answer

A:

The technical cause is An inactive zoning database edit does not change the effective active zoneset on the SAN fabric. The appropriate response is: Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning. Confirm successful repair: The active zoneset includes the desired members and the server discovers only its allowed storage target.

Incorrect Answers

B:

The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. “Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk” would address that alternative cause, not the condition in this question: an inactive zoning database edit does not change the effective active zoneset on the SAN fabric.

C:

“Commit the approved device alias database transaction and verify resolution across the affected switches” responds to this separate finding: device alias changes have not been committed and distributed through the supported fabric database workflow. This question instead needs “Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning”, 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 a new WWPN zone has been created in the MDS zoning database but the application host still cannot see its storage array because the zoneset was never activated; choosing this alternative would address the wrong failure mode.

Question 266

A data center implementation team investigates the following fault: A newly installed blade chassis has power but its I/O modules and blades never appear under fabric-interconnect inventory after uplink cabling was changed. What ongoing validation should operations establish for this service?

  1. Review Intersight target claims and account lifecycle as part of server ownership transfers.
  2. Exercise cluster failover and management reachability during controlled platform maintenance.
  3. Verify CIMC routing, management segmentation and administrator access at rack-server acceptance.
  4. Test FI-to-IOM connectivity and chassis discovery after moving server-facing cables.

Explanation

Correct Answer

D:

This safeguard addresses ucs blade chassis fabric discovery: The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. The appropriate prevention is: Test FI-to-IOM connectivity and chassis discovery after moving server-facing cables. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The Intersight device claim and account authorization do not match the approved administrative organization. “Review Intersight target claims and account lifecycle as part of server ownership transfers” would address that alternative cause, not the condition in this question: the chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured.

B:

“Exercise cluster failover and management reachability during controlled platform maintenance” responds to this separate finding: the clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior. This question instead needs “Test FI-to-IOM connectivity and chassis discovery after moving server-facing cables”, so the alternative does not meet the stated condition.

C:

The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. “Verify CIMC routing, management segmentation and administrator access at rack-server acceptance” applies to that separate problem. The observed case is a newly installed blade chassis has power but its I/O modules and blades never appear under fabric-interconnect inventory after uplink cabling was changed; choosing this alternative would address the wrong failure mode.

Question 267

During a Cisco data center readiness review, engineers observe: A storage technician adds several unrelated host initiators into a single large FC zone with a common array, creating unnecessary visibility between initiators. Which deployment safeguard most directly reduces this failure risk?

  1. Use standardized single-initiator zoning patterns in the SAN access request process.
  2. Reconcile NFS export client authorization when hypervisor subnets or hosts change.
  3. Verify pending and committed device alias state whenever server HBA identities change.
  4. Include FCNS database and target registration checks before troubleshooting zoning alone.

Explanation

Correct Answer

A:

This safeguard addresses single initiator target zoning design: The zone combines initiators beyond the least-privilege single-initiator zoning design. The appropriate prevention is: Use standardized single-initiator zoning patterns in the SAN access request process. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The NFS export access rules do not authorize the requesting client address or security identity. “Reconcile NFS export client authorization when hypervisor subnets or hosts change” would address that alternative cause, not the condition in this question: the zone combines initiators beyond the least-privilege single-initiator zoning design.

C:

“Verify pending and committed device alias state whenever server HBA identities change” responds to this separate finding: device alias changes have not been committed and distributed through the supported fabric database workflow. This question instead needs “Use standardized single-initiator zoning patterns in the SAN access request process”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a storage technician adds several unrelated host initiators into a single large FC zone with a common array, creating unnecessary visibility between initiators; choosing this alternative would address the wrong failure mode.

Question 268

A data center administrator identifies the following risk: The team activates an I/O module and fabric-interconnect firmware change simultaneously without scheduling expected service impact for dependent blades. Which test outcome proves the intended service was restored?

  1. The recovered management domain contains consistent service profiles, pools and fabric policies after restoration.
  2. The server recognizes the protected boot volume and tolerates the documented single-disk test condition.
  3. The intended firmware versions activate while the measured service interruption remains within the planned window.
  4. The adapter operates on the supported firmware set and the required host feature becomes available.

Explanation

Correct Answer

C:

This observation validates ucs disruptive firmware activation planning: The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. The corresponding corrective action is: Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. “Create or restore an authorized UCS configuration backup and validate the documented recovery procedure” would address that alternative cause, not the condition in this question: the upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints.

B:

“Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it” 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 “Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria”, 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 the team activates an I/O module and fabric-interconnect firmware change simultaneously without scheduling expected service impact for dependent blades; choosing this alternative would address the wrong failure mode.

Question 269

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. What is the most appropriate remediation for these symptoms?

  1. Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports.
  2. Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings.
  3. Assign a supported restricted UCS role and scope matching the storage administration tasks.
  4. Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths.

Explanation

Correct Answer

B:

The root problem is that DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. The selected change addresses it directly: Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings. Verify the outcome: Spoofed ARP replies are discarded while authorized clients retain normal gateway connectivity.

Incorrect Answers

A:

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 reported failure instead stems from DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN.

C:

This action concerns ucs manager role based access, where The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. The corrective response here is “Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings”; this alternative does not provide that response.

D:

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 stem reports 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; this control addresses a different failure condition.

Question 270

During a Cisco data center readiness review, engineers observe: An MDS maintenance team attempts a nondisruptive SAN switch upgrade while a required redundancy check and supported release-path validation are incomplete. Which operational guardrail would prevent a similar outage?

  1. Require SAN path redundancy and release-matrix signoff before MDS firmware activation.
  2. Validate iSCSI authentication lifecycle and secret rotation with connectivity testing.
  3. Review SAN health telemetry and alert thresholds after changes in storage workload patterns.
  4. Include EPLD impact and recovery planning when scheduling MDS component software updates.

Explanation

Correct Answer

A:

This safeguard addresses cisco mds nondisruptive upgrade prechecks: The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. The appropriate prevention is: Require SAN path redundancy and release-matrix signoff before MDS firmware activation. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. “Validate iSCSI authentication lifecycle and secret rotation with connectivity testing” would address that alternative cause, not the condition in this question: the selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites.

C:

“Review SAN health telemetry and alert thresholds after changes in storage workload patterns” responds to this separate finding: the SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. This question instead needs “Require SAN path redundancy and release-matrix signoff before MDS firmware activation”, so the alternative does not meet the stated condition.

D:

The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. “Include EPLD impact and recovery planning when scheduling MDS component software updates” applies to that separate problem. The observed case is an MDS maintenance team attempts a nondisruptive SAN switch upgrade while a required redundancy check and supported release-path validation are incomplete; choosing this alternative would address the wrong failure mode.