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 36

Question 350

While checking a production data center change, the team finds: Distributed model training runs across GPU pods but experiences network bottlenecks because oversubscribed links carry synchronized east-west collective operations without capacity planning. Which implementation action should the engineer take first?

  1. Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path.
  2. Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology.
  3. Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity.
  4. Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution.

Explanation

Correct Answer

B:

The root problem is that The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload. The selected change addresses it directly: Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology. Verify the outcome: Collective workload tests meet the required throughput and latency targets without sustained link oversubscription.

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

C:

This action concerns poap initial provisioning ownership, where The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. The corrective response here is “Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology”; this alternative does not provide that response.

D:

This action concerns ansible inventory variable scoping, where The playbook target inventory and variable precedence do not isolate the intended lab device group. The stem reports distributed model training runs across GPU pods but experiences network bottlenecks because oversubscribed links carry synchronized east-west collective operations without capacity planning; this control addresses a different failure condition.

Question 351

While checking a production data center change, the team finds: Multicast video receivers remain connected at layer two, but group membership ages out because there is no active IGMP querier in their VLAN. What technical condition most directly accounts for the failure?

  1. The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events.
  2. Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility.
  3. The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link.
  4. IGMP snooping membership state is not refreshed because the VLAN lacks a reachable supported multicast querier.

Explanation

Correct Answer

D:

The technical cause is IGMP snooping membership state is not refreshed because the VLAN lacks a reachable supported multicast querier. The appropriate response is: Provide a valid IGMP querier through the routed gateway or supported switching configuration. Confirm successful repair: Interested ports retain multicast group membership and nonmembers do not receive unwanted replicated streams.

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 VLAN lacks a reachable supported multicast querier.

B:

“Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries” responds to this separate finding: cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. This question instead needs “Provide a valid IGMP querier through the routed gateway or supported switching configuration”, so the alternative does not meet the stated condition.

C:

The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. “Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role” applies to that separate problem. The observed case is multicast video receivers remain connected at layer two, but group membership ages out because there is no active IGMP querier in their VLAN; choosing this alternative would address the wrong failure mode.

Question 352

A Nexus, UCS or MDS operations team encounters this issue: An Intersight-managed UCS X blade receives a server profile but fails its deployment because mandatory network and storage policy references are missing. What ongoing validation should operations establish for this service?

  1. Review Intersight target claims and account lifecycle as part of server ownership transfers.
  2. Verify the supported UCS generation and management mode before migrating service policies.
  3. Run Intersight profile validation and dependency checks before assigning profiles to production servers.
  4. Schedule encrypted UCS configuration backups and perform periodic isolated restore tests.

Explanation

Correct Answer

C:

This safeguard addresses intersight server profile deployment consistency: The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies. The appropriate prevention is: Run Intersight profile validation and dependency checks before assigning profiles to production servers. 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 Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies.

B:

“Verify the supported UCS generation and management mode before migrating service policies” responds to this separate finding: the platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. This question instead needs “Run Intersight profile validation and dependency checks before assigning profiles to production servers”, so the alternative does not meet the stated condition.

D:

The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. “Schedule encrypted UCS configuration backups and perform periodic isolated restore tests” applies to that separate problem. The observed case is an Intersight-managed UCS X blade receives a server profile but fails its deployment because mandatory network and storage policy references are missing; choosing this alternative would address the wrong failure mode.

Question 353

A Nexus, UCS or MDS operations team encounters this issue: A replacement HBA connects to an open MDS F-port and can enter the SAN even though the port should accept only preauthorized initiator identities. What ongoing validation should operations establish for this service?

  1. Exercise break-glass access and credential rotation under controlled audit conditions.
  2. Monitor MACsec security associations and key rotation without assuming link-up equals encryption.
  3. Review fabric-binding membership with SAN topology changes and device replacement plans.
  4. Maintain approved HBA identity records and update port security during controlled hardware replacement.

Explanation

Correct Answer

D:

This safeguard addresses mds fibre channel port security binding: Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. The appropriate prevention is: Maintain approved HBA identity records and update port security during controlled hardware replacement. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The management access policy lacks a tested protected local recovery identity for remote AAA outages. “Exercise break-glass access and credential rotation under controlled audit conditions” would address that alternative cause, not the condition in this question: fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.

B:

“Monitor MACsec security associations and key rotation without assuming link-up equals encryption” responds to this separate finding: link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. This question instead needs “Maintain approved HBA identity records and update port security during controlled hardware replacement”, so the alternative does not meet the stated condition.

C:

Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. “Review fabric-binding membership with SAN topology changes and device replacement plans” applies to that separate problem. The observed case is a replacement HBA connects to an open MDS F-port and can enter the SAN even though the port should accept only preauthorized initiator identities; choosing this alternative would address the wrong failure mode.

Question 354

A Nexus, UCS or MDS operations team encounters this issue: A new Cisco UCS C-Series rack server boots its operating system, yet the remote administrators cannot access CIMC because the out-of-band address is on an unreachable subnet. Which corrective change best resolves this problem?

  1. Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot.
  2. Restore the supported boot policy and required SAN adapter path in the correct boot-device order.
  3. Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network.
  4. Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis.

Explanation

Correct Answer

C:

The root problem is that The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. The selected change addresses it directly: Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network. Verify the outcome: Authorized operators can open CIMC over the management path without exposing it on the application data plane.

Incorrect Answers

A:

This action concerns ucs bios virtualization extensions, where The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The reported failure instead stems from The CIMC management interface has incorrect IP addressing or missing management default gateway reachability.

B:

This action concerns ucs c series boot policy device order, where The configured boot-device order does not select the intended SAN boot path before local storage. The corrective response here is “Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network”; this alternative does not provide that response.

D:

This action concerns ucs blade chassis fabric discovery, where The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. The stem reports a new Cisco UCS C-Series rack server boots its operating system, yet the remote administrators cannot access CIMC because the out-of-band address is on an unreachable subnet; this control addresses a different failure condition.

Question 355

A data center administrator identifies the following risk: Two Cisco MDS Fibre Channel switches are merged into one fabric, but an ISL becomes segmented because both switches use the same configured domain ID. Which verification result most directly demonstrates successful repair?

  1. Each host discovers its intended target while unrelated initiator WWPNs are not jointly zoned.
  2. The initiator completes FLOGI and receives a valid FCID in the correct SAN fabric.
  3. The target and initiator register and exchange traffic inside VSAN 30 without affecting other VSANs.
  4. Both switches participate in one stable fabric with unique domain IDs and expected FSPF reachability.

Explanation

Correct Answer

D:

This observation validates fibre channel domain id collision: The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. The corresponding corrective action is: Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization.

B:

“Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator” responds to this separate finding: the initiator has not completed successful fabric login and thus has no authorized FCID assignment. This question instead needs “Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process”, so the alternative does not meet the stated condition.

C:

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 two Cisco MDS Fibre Channel switches are merged into one fabric, but an ISL becomes segmented because both switches use the same configured domain ID; choosing this alternative would address the wrong failure mode.

Question 356

A data center implementation team investigates the following fault: A UCS blade can reach its Ethernet network but cannot discover a SAN boot target because the vHBA has been assigned to a different VSAN from its storage uplink. Which design or configuration error caused the described issue?

  1. The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history.
  2. The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target.
  3. The server identity has not been abstracted through approved UCS service profile and identity-pool associations.
  4. The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end.

Explanation

Correct Answer

D:

The technical cause is The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. The appropriate response is: Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN. Confirm successful repair: The server HBA registers in the correct VSAN and discovers the authorized target storage port.

Incorrect Answers

A:

The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. “Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend” would address that alternative cause, not the condition in this question: the virtual HBA path is not participating in the intended Fibre Channel VSAN end to end.

B:

“Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters” responds to this separate finding: the SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. This question instead needs “Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a UCS blade can reach its Ethernet network but cannot discover a SAN boot target because the vHBA has been assigned to a different VSAN from its storage uplink; choosing this alternative would address the wrong failure mode.

Question 357

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. What is the primary technical reason the deployment fails?

  1. An inactive zoning database edit does not change the effective active zoneset on the SAN fabric.
  2. The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded.
  3. A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session.
  4. The zone combines initiators beyond the least-privilege single-initiator zoning design.

Explanation

Correct Answer

D:

The technical cause is The zone combines initiators beyond the least-privilege single-initiator zoning design. The appropriate response is: Create separate approved zones for each host initiator with its authorized storage target ports. Confirm successful repair: Each host discovers its intended target while unrelated initiator WWPNs are not jointly zoned.

Incorrect Answers

A:

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: the zone combines initiators beyond the least-privilege single-initiator zoning design.

B:

“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 “Create separate approved zones for each host initiator with its authorized storage target ports”, so the alternative does not meet the stated condition.

C:

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 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 358

A data center implementation team investigates the following fault: A zoning administrator cannot commit an MDS fabric configuration because an abandoned pending change session has left a CFS lock on the fabric. Which design or configuration error caused the described issue?

  1. A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session.
  2. The zone combines initiators beyond the least-privilege single-initiator zoning design.
  3. Device alias changes have not been committed and distributed through the supported fabric database workflow.
  4. An inactive zoning database edit does not change the effective active zoneset on the SAN fabric.

Explanation

Correct Answer

A:

The technical cause is A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. The appropriate response is: Identify the legitimate lock owner and safely complete or abort the supported CFS session. Confirm successful repair: The fabric accepts a new authorized zoning transaction with consistent configuration distribution.

Incorrect Answers

B:

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” 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.

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 “Identify the legitimate lock owner and safely complete or abort the supported CFS session”, so the alternative does not meet the stated condition.

D:

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” 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 359

While checking a production data center change, the team finds: A regulated east-west inter-switch link must protect Ethernet frames in transit, but an approved MACsec session is absent even though the physical port is up. Which deployment safeguard most directly reduces this failure risk?

  1. Stage keychain changes and check device time synchronization before routing-authentication rotation.
  2. Test actual AAA command authorization and accounting for each approved Nexus support role.
  3. Review MDS command authorization and SAN change permissions separately from ordinary read access.
  4. Monitor MACsec security associations and key rotation without assuming link-up equals encryption.

Explanation

Correct Answer

D:

This safeguard addresses macsec encrypted inter switch links: Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. The appropriate prevention is: Monitor MACsec security associations and key rotation without assuming link-up equals encryption. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The OSPF authentication peers are using mismatched active key IDs or validity intervals. “Stage keychain changes and check device time synchronization before routing-authentication rotation” would address that alternative cause, not the condition in this question: link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection.

B:

“Test actual AAA command authorization and accounting for each approved Nexus support role” 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 “Monitor MACsec security associations and key rotation without assuming link-up equals encryption”, so the alternative does not meet the stated condition.

C:

The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. “Review MDS command authorization and SAN change permissions separately from ordinary read access” applies to that separate problem. The observed case is a regulated east-west inter-switch link must protect Ethernet frames in transit, but an approved MACsec session is absent even though the physical port is up; choosing this alternative would address the wrong failure mode.

Question 360

While checking a production data center change, the team finds: A Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script. What is the primary technical reason the deployment fails?

  1. The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation.
  2. The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association.
  3. The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.
  4. The automation credential is stored insecurely and grants broader privileges than the script requires.

Explanation

Correct Answer

D:

The technical cause is The automation credential is stored insecurely and grants broader privileges than the script requires. The appropriate response is: Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests. Confirm successful repair: The job retrieves the required device data without exposing secrets in the repository or task logs.

Incorrect Answers

A:

The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. “Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources” would address that alternative cause, not the condition in this question: the automation credential is stored insecurely and grants broader privileges than the script requires.

B:

“Use stable approved resource IDs and validate organization scope before assigning Intersight policies” responds to this separate finding: the API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. This question instead needs “Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script; choosing this alternative would address the wrong failure mode.