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 35

Question 340

During a Cisco data center readiness review, engineers observe: A dual-fabric UCS server unexpectedly loses the same application VLAN when one fabric interconnect fails because its vNIC failover behavior is not coordinated. Which operational guardrail would prevent a similar outage?

  1. Validate failover semantics against the host operating system teaming configuration before production use.
  2. Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment.
  3. Monitor pool utilization and reserve addresses before deploying large numbers of server profiles.
  4. Maintain service profile templates and identity pools independent of individual server serial numbers.

Explanation

Correct Answer

A:

This safeguard addresses ucs vnic fabric failover connectivity: The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. The appropriate prevention is: Validate failover semantics against the host operating system teaming configuration before production use. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. “Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment” 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.

C:

“Monitor pool utilization and reserve addresses before deploying large numbers of server profiles” responds to this separate finding: the UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. This question instead needs “Validate failover semantics against the host operating system teaming configuration before production use”, so the alternative does not meet the stated condition.

D:

The server identity has not been abstracted through approved UCS service profile and identity-pool associations. “Maintain service profile templates and identity pools independent of individual server serial numbers” 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 341

A Nexus, UCS or MDS operations team encounters this issue: A critical database server uses a single-homed orphan port on one vPC peer and loses service during peer-link failure despite other paths remaining up. Which root cause best explains this behavior?

  1. The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain.
  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. Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root.

Explanation

Correct Answer

B:

The technical cause is The failure design does not account for orphan-port behavior and the chosen peer recovery semantics. The appropriate response is: Review supported orphan-port handling and move or protect the workload on the planned resilient attachment. Confirm successful repair: The server remains reachable during documented peer and peer-link failure tests without unsafe duplicate forwarding.

Incorrect Answers

A:

The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. “Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies” would address that alternative cause, not the condition in this question: the failure design does not account for orphan-port behavior and the chosen peer recovery semantics.

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 “Review supported orphan-port handling and move or protect the workload on the planned resilient attachment”, so the alternative does not meet the stated condition.

D:

Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. “Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology” applies to that separate problem. The observed case is a critical database server uses a single-homed orphan port on one vPC peer and loses service during peer-link failure despite other paths remaining up; choosing this alternative would address the wrong failure mode.

Question 342

A newly commissioned network, compute or storage service reports: A data center server finds its iSCSI target portal but cannot establish a usable storage session because its initiator CHAP secret differs from the target configuration. Which implementation action should the engineer take first?

  1. Create separate approved zones for each host initiator with its authorized storage target ports.
  2. Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status.
  3. Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk.
  4. Update the approved initiator and target CHAP secret settings using the supported secure workflow.

Explanation

Correct Answer

D:

The root problem is that The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. The selected change addresses it directly: Update the approved initiator and target CHAP secret settings using the supported secure workflow. Verify the outcome: The iSCSI login authenticates successfully and the host discovers its authorized block LUN.

Incorrect Answers

A:

This action concerns single initiator target zoning design, where The zone combines initiators beyond the least-privilege single-initiator zoning design. The reported failure instead stems from The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials.

B:

This action concerns fibre channel isl trunk vsan allowance, where The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. The corrective response here is “Update the approved initiator and target CHAP secret settings using the supported secure workflow”; this alternative does not provide that response.

C:

This action concerns nfs file storage versus iscsi block storage, where The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. The stem reports a data center server finds its iSCSI target portal but cannot establish a usable storage session because its initiator CHAP secret differs from the target configuration; this control addresses a different failure condition.

Question 343

A newly commissioned network, compute or storage service reports: Multicast receivers connected to a routed leaf cannot join a source in another segment after a PIM sparse-mode domain is extended to a new pod. After remediation, which acceptance result is most relevant?

  1. The intended receivers join and receive source traffic, and PIM control state shows the proper tree.
  2. The remote leaf learns the intended endpoint MAC through a valid EVPN route and forwards frames correctly.
  3. Both peers reach Full state and exchange the intended routes without retransmission or MTU errors.
  4. The two routers establish an OSPFv3 Full adjacency and learn the expected IPv6 prefixes.

Explanation

Correct Answer

A:

This observation validates pim multicast rendezvous point reachability: The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. The corresponding corrective action is: Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. “Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI” would address that alternative cause, not the condition in this question: the routers do not agree on or reach the required rendezvous-point mapping for the multicast group range.

C:

“Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency” responds to this separate finding: the neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. This question instead needs “Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups”, so the alternative does not meet the stated condition.

D:

The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. “Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation” applies to that separate problem. The observed case is multicast receivers connected to a routed leaf cannot join a source in another segment after a PIM sparse-mode domain is extended to a new pod; choosing this alternative would address the wrong failure mode.

Question 344

A Nexus, UCS or MDS operations team encounters this issue: A UCS-adjacent SAN access switch configured for NPV cannot perform independent fabric services, but engineers expect it to act as the fabric principal switch. Which root cause best explains this behavior?

  1. NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch.
  2. Device alias changes have not been committed and distributed through the supported fabric database workflow.
  3. VSAN membership is incorrectly shared between isolation domains with different storage access requirements.
  4. The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service.

Explanation

Correct Answer

A:

The technical cause is NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. The appropriate response is: Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design. Confirm successful repair: The upstream switch sees proxied initiator logins and the access device no longer relies on principal-switch services.

Incorrect Answers

B:

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: nPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch.

C:

“Move the backup server connection into the approved dedicated VSAN and update authorized zoning” responds to this separate finding: vSAN membership is incorrectly shared between isolation domains with different storage access requirements. This question instead needs “Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design”, so the alternative does not meet the stated condition.

D:

The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. “Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path” applies to that separate problem. The observed case is a UCS-adjacent SAN access switch configured for NPV cannot perform independent fabric services, but engineers expect it to act as the fabric principal switch; choosing this alternative would address the wrong failure mode.

Question 345

While checking a production data center change, the team finds: A Fibre Channel HBA has physical link but never receives a fabric address after a switch port was assigned the wrong interface role. After remediation, which acceptance result is most relevant?

  1. The host discovers an iSCSI target LUN and presents the expected block device to the hypervisor.
  2. Both members become operational in the port channel and load distribution remains stable.
  3. The target and initiator register and exchange traffic inside VSAN 30 without affecting other VSANs.
  4. The initiator completes FLOGI and receives a valid FCID in the correct SAN fabric.

Explanation

Correct Answer

D:

This observation validates flogi registration and fcid assignment: The initiator has not completed successful fabric login and thus has no authorized FCID assignment. The corresponding corrective action is: Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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

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

A data center administrator identifies the following risk: A data center hypervisor installation fails hardware virtualization preflight on otherwise compatible UCS blades after a generic BIOS profile disabled virtualization features. Which design or configuration error caused the described issue?

  1. The BIOS policy disables required CPU virtualization support expected by the approved hypervisor.
  2. UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements.
  3. The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings.
  4. The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy.

Explanation

Correct Answer

A:

The technical cause is The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The appropriate response is: Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot. Confirm successful repair: The hypervisor passes hardware virtualization checks and starts a test virtual machine successfully.

Incorrect Answers

B:

UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements. “Correct the supported UCS class-of-service and network QoS policy for the intended application traffic” would address that alternative cause, not the condition in this question: the BIOS policy disables required CPU virtualization support expected by the approved hypervisor.

C:

“Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks” responds to this separate finding: the service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings. This question instead needs “Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot”, so the alternative does not meet the stated condition.

D:

The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. “Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it” applies to that separate problem. The observed case is a data center hypervisor installation fails hardware virtualization preflight on otherwise compatible UCS blades after a generic BIOS profile disabled virtualization features; choosing this alternative would address the wrong failure mode.

Question 347

While checking a production data center change, the team finds: A multi-site fabric policy is changed separately on individual Nexus devices while Nexus Dashboard's centrally managed intent remains unchanged and later overwrites the manual edits. Which implementation action should the engineer take first?

  1. Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests.
  2. Use stable approved resource IDs and validate organization scope before assigning Intersight policies.
  3. Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow.
  4. Deploy the script in the approved supported shell environment with required dependencies and bounded permissions.

Explanation

Correct Answer

C:

The root problem is that Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. The selected change addresses it directly: Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow. Verify the outcome: The intended policy persists after controller synchronization and devices report consistent compliance.

Incorrect Answers

A:

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

B:

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 “Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow”; this alternative does not provide that response.

D:

This action concerns nexus bash shell and guest shell isolation, where The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The stem reports a multi-site fabric policy is changed separately on individual Nexus devices while Nexus Dashboard's centrally managed intent remains unchanged and later overwrites the manual edits; this control addresses a different failure condition.

Question 348

A data center administrator identifies the following risk: Intermittent Fibre Channel congestion causes storage latency spikes, yet operators rely only on link-up indicators and miss buffer-credit or port-error trends. Which design or configuration error caused the described issue?

  1. The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset.
  2. The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends.
  3. The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image.
  4. The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites.

Explanation

Correct Answer

B:

The technical cause is The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. The appropriate response is: Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis. Confirm successful repair: A time-aligned report identifies the affected SAN ports and correlates counters with storage latency.

Incorrect Answers

A:

The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. “Assign the target port to the approved VSAN and verify its effective FCNS and zone membership” would address that alternative cause, not the condition in this question: the SAN observability baseline does not collect relevant port performance metrics and historical assurance trends.

C:

“Review the applicable MDS EPLD package and schedule the correct supported component update” responds to this separate finding: the storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. This question instead needs “Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis”, so the alternative does not meet the stated condition.

D:

The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. “Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method” applies to that separate problem. The observed case is intermittent Fibre Channel congestion causes storage latency spikes, yet operators rely only on link-up indicators and miss buffer-credit or port-error trends; choosing this alternative would address the wrong failure mode.

Question 349

A Nexus, UCS or MDS operations team encounters this issue: A data center team calls a privately operated dedicated cloud a public cloud merely because users reach it remotely through the Internet. Which design or configuration error caused the described issue?

  1. The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably.
  2. The failure design does not account for orphan-port behavior and the chosen peer recovery semantics.
  3. IGMP snooping membership state is not refreshed because the VLAN lacks a reachable supported multicast querier.
  4. Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility.

Explanation

Correct Answer

D:

The technical cause is Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. The appropriate response is: Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries. Confirm successful repair: The design describes the private deployment and any genuinely shared public components without conflating connectivity.

Incorrect Answers

A:

The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. “Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency” would address that alternative cause, not the condition in this question: cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility.

B:

“Review supported orphan-port handling and move or protect the workload on the planned resilient attachment” responds to this separate finding: the failure design does not account for orphan-port behavior and the chosen peer recovery semantics. This question instead needs “Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries”, so the alternative does not meet the stated condition.

C:

The VLAN lacks a reachable supported multicast querier. “Provide a valid IGMP querier through the routed gateway or supported switching configuration” applies to that separate problem. The observed case is a data center team calls a privately operated dedicated cloud a public cloud merely because users reach it remotely through the Internet; choosing this alternative would address the wrong failure mode.

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.