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 17

Question 160

A data center implementation team investigates the following fault: A new UCS server is physically reachable but cannot be managed from the organization's Intersight account because its device claim was associated with a different account. Which corrective change best resolves this problem?

  1. Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies.
  2. Reconcile the claim code and target ownership through supported Intersight claiming and access procedures.
  3. Complete the required Intersight policies and deploy the server profile with validated resource assignments.
  4. Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria.

Explanation

Correct Answer

B:

The root problem is that The Intersight device claim and account authorization do not match the approved administrative organization. The selected change addresses it directly: Reconcile the claim code and target ownership through supported Intersight claiming and access procedures. Verify the outcome: The server appears as a manageable authorized target in the correct Intersight organization.

Incorrect Answers

A:

This action concerns ucs x series intersight managed mode, where The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. The reported failure instead stems from The Intersight device claim and account authorization do not match the approved administrative organization.

C:

This action concerns intersight server profile deployment consistency, where The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies. The corrective response here is “Reconcile the claim code and target ownership through supported Intersight claiming and access procedures”; this alternative does not provide that response.

D:

This action concerns ucs disruptive firmware activation planning, where The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. The stem reports a new UCS server is physically reachable but cannot be managed from the organization's Intersight account because its device claim was associated with a different account; this control addresses a different failure condition.

Question 161

During a Cisco data center readiness review, engineers observe: A data center team modifies a static service profile on every blade individually, causing configuration drift when a shared SAN policy changes. Which operational guardrail would prevent a similar outage?

  1. Reconcile UCS VLAN definitions with upstream trunk allow-lists during every server network expansion.
  2. Test UCS QoS policies with the upstream switching trust boundary after adapter-policy changes.
  3. Review template association and change propagation before broad UCS configuration updates.
  4. Inspect chassis IOM inventory and dual-fabric paths during blade server deployment.

Explanation

Correct Answer

C:

This safeguard addresses ucs updating service profile templates: The configuration process bypasses the intended reusable UCS service profile template inheritance model. The appropriate prevention is: Review template association and change propagation before broad UCS configuration updates. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. “Reconcile UCS VLAN definitions with upstream trunk allow-lists during every server network expansion” would address that alternative cause, not the condition in this question: the configuration process bypasses the intended reusable UCS service profile template inheritance model.

B:

“Test UCS QoS policies with the upstream switching trust boundary after adapter-policy changes” responds to this separate finding: uCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements. This question instead needs “Review template association and change propagation before broad UCS configuration updates”, so the alternative does not meet the stated condition.

D:

The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. “Inspect chassis IOM inventory and dual-fabric paths during blade server deployment” applies to that separate problem. The observed case is a data center team modifies a static service profile on every blade individually, causing configuration drift when a shared SAN policy changes; choosing this alternative would address the wrong failure mode.

Question 162

A data center administrator identifies the following risk: Two ACI endpoint groups should communicate over a narrowly permitted database port, but the contract is attached in the wrong provider-consumer direction. Which design or configuration error caused the described issue?

  1. The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs.
  2. The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter.
  3. The intended microsegmentation EPG classification rules do not distinguish the workload identities.
  4. The Intersight role assignment is not scoped to the authorized organization and permitted resource actions.

Explanation

Correct Answer

B:

The technical cause is The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. The appropriate response is: Correct the ACI contract consumer-provider bindings and permit only the required application port. Confirm successful repair: Application sessions traverse the authorized EPG path and prohibited traffic remains blocked.

Incorrect Answers

A:

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 contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter.

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 ACI contract consumer-provider bindings and permit only the required application port”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is two ACI endpoint groups should communicate over a narrowly permitted database port, but the contract is attached in the wrong provider-consumer direction; choosing this alternative would address the wrong failure mode.

Question 163

A data center implementation team investigates the following fault: A UCS service profile requires a newer adapter firmware feature, but the applied host firmware package omits the compatible adapter release. 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 effective UCS host firmware package is inconsistent with the server adapter feature prerequisites.
  3. The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow.
  4. The configuration process bypasses the intended reusable UCS service profile template inheritance model.

Explanation

Correct Answer

B:

The technical cause is The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. The appropriate response is: Select a compatible validated firmware package and update the affected server policy under change control. Confirm successful repair: The adapter operates on the supported firmware set and the required host feature becomes available.

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 effective UCS host firmware package is inconsistent with the server adapter feature prerequisites.

C:

“Create or restore an authorized UCS configuration backup and validate the documented recovery procedure” responds to this separate finding: the UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. This question instead needs “Select a compatible validated firmware package and update the affected server policy under change control”, so the alternative does not meet the stated condition.

D:

The configuration process bypasses the intended reusable UCS service profile template inheritance model. “Use an approved updating service profile template and apply governed changes to its associated server profiles” applies to that separate problem. The observed case is a UCS service profile requires a newer adapter firmware feature, but the applied host firmware package omits the compatible adapter release; choosing this alternative would address the wrong failure mode.

Question 164

A Nexus, UCS or MDS operations team encounters this issue: A Fibre Channel HBA has physical link but never receives a fabric address after a switch port was assigned the wrong interface role. Which design or configuration error caused the described issue?

  1. Device alias changes have not been committed and distributed through the supported fabric database workflow.
  2. The FC port channel and prospective member disagree on required operational attributes for bundling.
  3. The initiator has not completed successful fabric login and thus has no authorized FCID assignment.
  4. The FC trunk does not carry the required VSAN membership consistently between the two MDS switches.

Explanation

Correct Answer

C:

The technical cause is The initiator has not completed successful fabric login and thus has no authorized FCID assignment. The appropriate response is: Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator. Confirm successful repair: The initiator completes FLOGI and receives a valid FCID in the correct SAN fabric.

Incorrect Answers

A:

Device alias changes have not been committed and distributed through the supported fabric database workflow. “Commit the approved device alias database transaction and verify resolution across the affected switches” would address that alternative cause, not the condition in this question: the initiator has not completed successful fabric login and thus has no authorized FCID assignment.

B:

“Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member” responds to this separate finding: the FC port channel and prospective member disagree on required operational attributes for bundling. This question instead needs “Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator”, so the alternative does not meet the stated condition.

D:

The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. “Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status” applies to that separate problem. The observed case is a Fibre Channel HBA has physical link but never receives a fabric address after a switch port was assigned the wrong interface role; choosing this alternative would address the wrong failure mode.

Question 165

While checking a production data center change, the team finds: Voice-processing virtual machines on UCS blades traverse a shared adapter, but their traffic is treated as best effort because the UCS class settings do not match the approved policy. What observation best confirms the configuration now behaves correctly?

  1. Authorized real-time flows receive the designated priority treatment and bulk traffic retains its separate class.
  2. The profile associates only with hardware satisfying its documented adapter and compute requirements.
  3. The blade retains expected connectivity under an individual fabric path outage within the approved design.
  4. The guest and external hosts exchange traffic over the authorized VLAN on both supported fabric paths.

Explanation

Correct Answer

A:

This observation validates ucs lan qos class mapping: UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements. The corresponding corrective action is: Correct the supported UCS class-of-service and network QoS policy for the intended application traffic. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The server pool qualification policy does not limit placement to servers with the required hardware capabilities. “Create the supported UCS server pool qualification and associate the workload profile with eligible members” would address that alternative cause, not the condition in this question: uCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements.

C:

“Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior” responds to this separate finding: the chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. This question instead needs “Correct the supported UCS class-of-service and network QoS policy for the intended application traffic”, so the alternative does not meet the stated condition.

D:

The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. “Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access” applies to that separate problem. The observed case is voice-processing virtual machines on UCS blades traverse a shared adapter, but their traffic is treated as best effort because the UCS class settings do not match the approved policy; choosing this alternative would address the wrong failure mode.

Question 166

While checking a production data center change, the team finds: An orchestration script provisions a UCS server through Intersight but associates an unapproved boot policy because it selects objects by an ambiguous display name. What is the primary technical reason the deployment fails?

  1. The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association.
  2. The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.
  3. The automation credential is stored insecurely and grants broader privileges than the script requires.
  4. Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model.

Explanation

Correct Answer

A:

The technical cause is The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. The appropriate response is: Use stable approved resource IDs and validate organization scope before assigning Intersight policies. Confirm successful repair: The target server profile references the expected boot and connectivity policies with no cross-tenant linkage.

Incorrect Answers

B:

The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. “Deploy the script in the approved supported shell environment with required dependencies and bounded permissions” would address that alternative cause, not the condition in this question: the API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association.

C:

“Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests” responds to this separate finding: the automation credential is stored insecurely and grants broader privileges than the script requires. This question instead needs “Use stable approved resource IDs and validate organization scope before assigning Intersight policies”, so the alternative does not meet the stated condition.

D:

Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. “Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow” applies to that separate problem. The observed case is an orchestration script provisions a UCS server through Intersight but associates an unapproved boot policy because it selects objects by an ambiguous display name; choosing this alternative would address the wrong failure mode.

Question 167

A newly commissioned network, compute or storage service 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. What observation best confirms the configuration now behaves correctly?

  1. The collector processes supported payload variants and flags incomplete metrics without terminating the monitoring job.
  2. The intended policy persists after controller synchronization and devices report consistent compliance.
  3. Only the designated lab devices receive changes and production targets remain unchanged.
  4. Repeated execution converges to the same desired configuration without unintended duplicate changes.

Explanation

Correct Answer

A:

This observation validates python structured telemetry parsing: The parser lacks schema validation and robust handling of absent or differently typed telemetry values. The corresponding corrective action is: Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. “Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow” would address that alternative cause, not the condition in this question: the parser lacks schema validation and robust handling of absent or differently typed telemetry values.

C:

“Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution” responds to this separate finding: the playbook target inventory and variable precedence do not isolate the intended lab device group. This question instead needs “Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics”, so the alternative does not meet the stated condition.

D:

The script lacks an idempotent precheck to compare desired and current network device state. “Query existing NX-OS state before applying only the necessary authorized configuration differences” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 168

A data center implementation team investigates the following fault: A new access switch unexpectedly becomes the spanning-tree root and traffic now follows a slow backup inter-switch link across the data center. Which design or configuration error caused the described issue?

  1. Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root.
  2. The failure design does not account for orphan-port behavior and the chosen peer recovery semantics.
  3. The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members.
  4. The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.

Explanation

Correct Answer

A:

The technical cause is Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. The appropriate response is: Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology. Confirm successful repair: The designated aggregation switch is the root and the expected alternate links remain loop-free.

Incorrect Answers

B:

The failure design does not account for orphan-port behavior and the chosen peer recovery semantics. “Review supported orphan-port handling and move or protect the workload on the planned resilient attachment” would address that alternative cause, not the condition in this question: bridge priority design does not select the intended distribution switches as the RSTP root and secondary root.

C:

“Configure a matching supported LACP mode and port-channel membership across the two endpoints” responds to this separate finding: the port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. This question instead needs “Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology”, so the alternative does not meet the stated condition.

D:

The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. “Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms” applies to that separate problem. The observed case is a new access switch unexpectedly becomes the spanning-tree root and traffic now follows a slow backup inter-switch link across the data center; choosing this alternative would address the wrong failure mode.

Question 169

A data center implementation team investigates the following fault: A UCS domain loses management when its primary fabric interconnect is rebooted even though the secondary interconnect is operational. What preventive control would best avoid repeating this fault?

  1. Monitor pool utilization and reserve addresses before deploying large numbers of server profiles.
  2. Record boot order and recovery expectations alongside BIOS and SAN maintenance procedures.
  3. Exercise cluster failover and management reachability during controlled platform maintenance.
  4. Test FI-to-IOM connectivity and chassis discovery after moving server-facing cables.

Explanation

Correct Answer

C:

This safeguard addresses ucs fabric interconnect management failover: The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior. The appropriate prevention is: Exercise cluster failover and management reachability during controlled platform maintenance. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. “Monitor pool utilization and reserve addresses before deploying large numbers of server profiles” would address that alternative cause, not the condition in this question: the clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior.

B:

“Record boot order and recovery expectations alongside BIOS and SAN maintenance procedures” responds to this separate finding: the configured boot-device order does not select the intended SAN boot path before local storage. This question instead needs “Exercise cluster failover and management reachability during controlled platform maintenance”, so the alternative does not meet the stated condition.

D:

The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. “Test FI-to-IOM connectivity and chassis discovery after moving server-facing cables” applies to that separate problem. The observed case is a UCS domain loses management when its primary fabric interconnect is rebooted even though the secondary interconnect is operational; choosing this alternative would address the wrong failure mode.

Question 170

A newly commissioned network, compute or storage service reports: 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 implementation action should the engineer take first?

  1. Update the approved initiator and target CHAP secret settings using the supported secure workflow.
  2. Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning.
  3. Commit the approved device alias database transaction and verify resolution across the affected switches.
  4. Verify target port FLOGI and FCNS registration and restore the authorized target attachment.

Explanation

Correct Answer

B:

The root problem is that An inactive zoning database edit does not change the effective active zoneset on the SAN fabric. The selected change addresses it directly: Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning. Verify the outcome: The active zoneset includes the desired members and the server discovers only its allowed storage target.

Incorrect Answers

A:

This action concerns iscsi chap target authentication, where The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. The reported failure instead stems from An inactive zoning database edit does not change the effective active zoneset on the SAN fabric.

C:

This action concerns cisco mds device alias commit behavior, where Device alias changes have not been committed and distributed through the supported fabric database workflow. The corrective response here is “Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning”; this alternative does not provide that response.

D:

This action concerns fibre channel name server registration, where The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. The stem reports 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; this control addresses a different failure condition.