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 28

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.

Question 271

During a Cisco data center readiness review, engineers observe: 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 technical condition most directly accounts for the failure?

  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 centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring.
  4. DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN.

Explanation

Correct Answer

B:

The technical cause is DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. The appropriate response is: Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths. Confirm successful repair: Unauthorized DHCP offers are dropped while valid clients receive leases from the approved server.

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 trust is applied to an untrusted edge port and allows unauthorized DHCP server replies.

C:

“Correct the authorized TACACS command or role mapping without granting full switch administrator permissions” responds to this separate finding: the centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. This question instead needs “Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths”, so the alternative does not meet the stated condition.

D:

DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. “Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings” applies to that separate problem. The observed case is a rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping; choosing this alternative would address the wrong failure mode.

Question 272

A data center implementation team investigates the following fault: A virtual machine migrates to a different ESXi host but its ACI EPG policy does not follow because the virtualization integration is incomplete. Which root cause best explains this behavior?

  1. The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events.
  2. The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups.
  3. The leaf has not completed the supported ACI fabric discovery and node-registration workflow.
  4. The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.

Explanation

Correct Answer

B:

The technical cause is The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. The appropriate response is: Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment. Confirm successful repair: After VM migration the endpoint belongs to the right EPG and retains its intended connectivity and contracts.

Incorrect Answers

A:

The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. “Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics” would address that alternative cause, not the condition in this question: the ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups.

C:

“Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC” responds to this separate finding: the leaf has not completed the supported ACI fabric discovery and node-registration workflow. This question instead needs “Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment”, so the alternative does not meet the stated condition.

D:

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 virtual machine migrates to a different ESXi host but its ACI EPG policy does not follow because the virtualization integration is incomplete; choosing this alternative would address the wrong failure mode.

Question 273

A data center implementation team investigates the following fault: A Nexus maintenance plan upgrades only the system image while a documented line-card hardware programming device update is required for the target release. Which verification result most directly demonstrates successful repair?

  1. Hardware and software component versions match the approved release prerequisites after controlled maintenance.
  2. The leaf receives the intended EVPN routes and remote workloads become reachable over VXLAN.
  3. A staged test establishes the actual traffic impact and the upgrade follows the approved compatibility plan.
  4. The device returns to the known-good configuration with traffic restored after rollback is exercised.

Explanation

Correct Answer

A:

This observation validates nexus epld upgrade safety: The planned software transition omits the EPLD compatibility and operational impact assessment. The corresponding corrective action is: Review supported EPLD package requirements and schedule the component update using the prescribed procedure. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

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” would address that alternative cause, not the condition in this question: the planned software transition omits the EPLD compatibility and operational impact assessment.

C:

“Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path” responds to this separate finding: the upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. This question instead needs “Review supported EPLD package requirements and schedule the component update using the prescribed procedure”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a Nexus maintenance plan upgrades only the system image while a documented line-card hardware programming device update is required for the target release; choosing this alternative would address the wrong failure mode.

Question 274

During a Cisco data center readiness review, engineers observe: A Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script. Which implementation action should the engineer take first?

  1. Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow.
  2. Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests.
  3. Use stable approved resource IDs and validate organization scope before assigning Intersight policies.
  4. Send the supported NX-API request in the correct JSON or XML representation with matching headers.

Explanation

Correct Answer

B:

The root problem is that The automation credential is stored insecurely and grants broader privileges than the script requires. The selected change addresses it directly: Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests. Verify the outcome: The job retrieves the required device data without exposing secrets in the repository or task logs.

Incorrect Answers

A:

This action concerns nexus dashboard intent orchestration consistency, where Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. The reported failure instead stems from The automation credential is stored insecurely and grants broader privileges than the script requires.

C:

This action concerns intersight api server policy automation, where The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. The corrective response here is “Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests”; this alternative does not provide that response.

D:

This action concerns nx api json content encoding, where The NX-API request body and declared content format are inconsistent for the selected endpoint. The stem reports a Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script; this control addresses a different failure condition.

Question 275

A Nexus, UCS or MDS operations team encounters this issue: A Nexus switch loses its remote AAA connection during maintenance and administrators have no approved emergency login route because all local recovery credentials were disabled. Which verification result most directly demonstrates successful repair?

  1. An authorized emergency operator can enter through the recovery path while normal remote AAA remains primary.
  2. The analyst inspects FCNS and port health but cannot activate or change production zonesets.
  3. The approved HBA logs in while a test unapproved WWPN is rejected by the protected fabric port.
  4. The operator executes the designated monitoring commands while sensitive configuration changes remain denied.

Explanation

Correct Answer

A:

This observation validates nx os local emergency account control: The management access policy lacks a tested protected local recovery identity for remote AAA outages. The corresponding corrective action is: Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. “Replace the overly broad MDS role with an approved read-only or scoped monitoring role” would address that alternative cause, not the condition in this question: the management access policy lacks a tested protected local recovery identity for remote AAA outages.

C:

“Configure supported MDS port-security bindings for the intended server initiator and affected VSAN” responds to this separate finding: fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. This question instead needs “Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions”, so the alternative does not meet the stated condition.

D:

The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. “Correct the authorized TACACS command or role mapping without granting full switch administrator permissions” applies to that separate problem. The observed case is a Nexus switch loses its remote AAA connection during maintenance and administrators have no approved emergency login route because all local recovery credentials were disabled; choosing this alternative would address the wrong failure mode.

Question 276

While checking a production data center change, the team finds: A dual-fabric UCS server unexpectedly loses the same application VLAN when one fabric interconnect fails because its vNIC failover behavior is not coordinated. What is the primary technical reason the deployment fails?

  1. The server identity has not been abstracted through approved UCS service profile and identity-pool associations.
  2. The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities.
  3. The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target.
  4. The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path.

Explanation

Correct Answer

D:

The technical cause is The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. The appropriate response is: Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design. Confirm successful repair: A controlled fabric failover retains authorized server network reachability without duplicate MAC or VLAN problems.

Incorrect Answers

A:

The server identity has not been abstracted through approved UCS service profile and identity-pool associations. “Associate the intended service profile and its identity pools with the supported replacement hardware” would address that alternative cause, not the condition in this question: the UCS vNIC fabric placement and failover policy do not provide the intended redundant network path.

B:

“Expand or assign a nonoverlapping approved MAC pool and retry the service profile association” responds to this separate finding: the UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. This question instead needs “Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design”, so the alternative does not meet the stated condition.

C:

The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. “Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters” applies to that separate problem. The observed case is a dual-fabric UCS server unexpectedly loses the same application VLAN when one fabric interconnect fails because its vNIC failover behavior is not coordinated; choosing this alternative would address the wrong failure mode.

Question 277

During a Cisco data center readiness review, engineers observe: A scheduled Nexus configuration backup runs continuously instead of once nightly because the job's scheduler interval was entered with the wrong units. What technical condition most directly accounts for the failure?

  1. The script lacks an idempotent precheck to compare desired and current network device state.
  2. The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.
  3. The NX-API request body and declared content format are inconsistent for the selected endpoint.
  4. The NX-OS scheduler job timing is not aligned with the intended maintenance frequency.

Explanation

Correct Answer

D:

The technical cause is The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The appropriate response is: Set the supported scheduler job schedule to the approved daily interval and verify the associated command. Confirm successful repair: The backup executes at the intended time without repeated unnecessary administrative sessions.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the NX-OS scheduler job timing is not aligned with the intended maintenance frequency.

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 “Set the supported scheduler job schedule to the approved daily interval and verify the associated command”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a scheduled Nexus configuration backup runs continuously instead of once nightly because the job's scheduler interval was entered with the wrong units; choosing this alternative would address the wrong failure mode.

Question 278

While checking a production data center change, the team finds: A replacement UCS fabric interconnect has been installed, but operators have no recent recoverable configuration backup for the domain's identity pools and policies. After remediation, which acceptance result is most relevant?

  1. All required vNICs receive unique authorized MAC addresses without conflicting with existing profiles.
  2. The adapter operates on the supported firmware set and the required host feature becomes available.
  3. The replacement blade identifies the intended LUN and completes a controlled SAN boot.
  4. The recovered management domain contains consistent service profiles, pools and fabric policies after restoration.

Explanation

Correct Answer

D:

This observation validates ucs configuration backup and restore: The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. The corresponding corrective action is: Create or restore an authorized UCS configuration backup and validate the documented recovery procedure. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. “Expand or assign a nonoverlapping approved MAC pool and retry the service profile association” 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.

B:

“Select a compatible validated firmware package and update the affected server policy under change control” responds to this separate finding: the effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. 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.

C:

The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. “Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters” 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 279

During a Cisco data center readiness review, engineers observe: 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 operational guardrail would prevent a similar outage?

  1. Review FCoE VLAN and lossless Ethernet prerequisites separately from ordinary LAN configuration.
  2. Audit VSAN allow-lists and operational trunk membership when adding Fibre Channel ISLs.
  3. Track port role, link state and FLOGI database entries in server storage connection validation.
  4. Include FC port-channel member parameter checks in redundant SAN link commissioning.

Explanation

Correct Answer

B:

This safeguard addresses fibre channel isl trunk vsan allowance: The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. The appropriate prevention is: Audit VSAN allow-lists and operational trunk membership when adding Fibre Channel ISLs. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. “Review FCoE VLAN and lossless Ethernet prerequisites separately from ordinary LAN configuration” would address that alternative cause, not the condition in this question: the FC trunk does not carry the required VSAN membership consistently between the two MDS switches.

C:

“Track port role, link state and FLOGI database entries in server storage connection validation” responds to this separate finding: the initiator has not completed successful fabric login and thus has no authorized FCID assignment. This question instead needs “Audit VSAN allow-lists and operational trunk membership when adding Fibre Channel ISLs”, so the alternative does not meet the stated condition.

D:

The FC port channel and prospective member disagree on required operational attributes for bundling. “Include FC port-channel member parameter checks in redundant SAN link commissioning” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 280

A data center administrator identifies the following risk: A UCS domain authenticates administrators through a remote server, but a misconfigured AAA order locks out all operators during a network outage. 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 identity updates permitted server profiles in its organization and receives denials elsewhere.
  3. The two workloads receive their distinct security policies while permitted shared services remain reachable.
  4. The user can inspect authorized SAN settings but cannot change unrelated server identity and LAN policies.

Explanation

Correct Answer

A:

This observation validates ucs remote aaa fallback authentication: The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. The corresponding corrective action is: Correct the supported UCS authentication realm order and emergency access procedure under change control. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. “Apply the approved organization-scoped Intersight RBAC role for the automation identity” would address that alternative cause, not the condition in this question: the UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path.

C:

“Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads” responds to this separate finding: the intended microsegmentation EPG classification rules do not distinguish the workload identities. This question instead needs “Correct the supported UCS authentication realm order and emergency access procedure under change control”, so the alternative does not meet the stated condition.

D:

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 UCS domain authenticates administrators through a remote server, but a misconfigured AAA order locks out all operators during a network outage; choosing this alternative would address the wrong failure mode.