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 40

Question 390

A Nexus, UCS or MDS operations team encounters this issue: A UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults. Which corrective change best resolves this problem?

  1. Use an approved updating service profile template and apply governed changes to its associated server profiles.
  2. Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot.
  3. Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend.
  4. Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it.

Explanation

Correct Answer

C:

The root problem is that The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. The selected change addresses it directly: Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend. Verify the outcome: Intersight records the hardware fault and resolution, while workload stability returns after repair.

Incorrect Answers

A:

This action concerns ucs updating service profile templates, where The configuration process bypasses the intended reusable UCS service profile template inheritance model. The reported failure instead stems from The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history.

B:

This action concerns ucs bios virtualization extensions, where The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The corrective response here is “Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend”; this alternative does not provide that response.

D:

This action concerns ucs c series virtual disk raid policy, where The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. The stem reports a UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults; this control addresses a different failure condition.

Question 391

While checking a production data center change, the team finds: An MDS monitoring analyst receives a network-admin role and can edit SAN zoning despite requiring only fabric health visibility. What observation best confirms the configuration now behaves correctly?

  1. The analyst inspects FCNS and port health but cannot activate or change production zonesets.
  2. The approved HBA logs in while a test unapproved WWPN is rejected by the protected fabric port.
  3. Authorized operators authenticate normally through remote AAA and recover access through the documented fallback during an outage.
  4. The approved peer switch joins the SAN while a nonapproved test switch is denied fabric access.

Explanation

Correct Answer

A:

This observation validates cisco mds administrative role authorization: The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. The corresponding corrective action is: Replace the overly broad MDS role with an approved read-only or scoped monitoring role. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. “Configure supported MDS port-security bindings for the intended server initiator and affected VSAN” would address that alternative cause, not the condition in this question: the MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs.

C:

“Correct the supported UCS authentication realm order and emergency access procedure under change control” responds to this separate finding: the UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. This question instead needs “Replace the overly broad MDS role with an approved read-only or scoped monitoring role”, so the alternative does not meet the stated condition.

D:

Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. “Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs” applies to that separate problem. The observed case is an MDS monitoring analyst receives a network-admin role and can edit SAN zoning despite requiring only fabric health visibility; choosing this alternative would address the wrong failure mode.

Question 392

A Nexus, UCS or MDS operations team encounters this issue: A scheduled Nexus configuration backup runs continuously instead of once nightly because the job's scheduler interval was entered with the wrong units. Which verification result most directly demonstrates successful repair?

  1. The intended policy persists after controller synchronization and devices report consistent compliance.
  2. The backup executes at the intended time without repeated unnecessary administrative sessions.
  3. The applet runs only on the targeted peer-down event and preserves the expected diagnostic information.
  4. Repeated execution converges to the same desired configuration without unintended duplicate changes.

Explanation

Correct Answer

B:

This observation validates nx os scheduler job interval: The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The corresponding corrective action is: Set the supported scheduler job schedule to the approved daily interval and verify the associated command. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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 NX-OS scheduler job timing is not aligned with the intended maintenance frequency.

C:

“Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event” responds to this separate finding: the embedded event manager event detector does not match the actual authorized BGP neighbor-down message. 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.

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

A Nexus, UCS or MDS operations team encounters this issue: The zoning administrator changes a device alias name to point to a replacement HBA, but other switches keep resolving the old identity because the alias database was not committed. Which 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. Device alias changes have not been committed and distributed through the supported fabric database workflow.
  3. The zone combines initiators beyond the least-privilege single-initiator zoning design.
  4. The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded.

Explanation

Correct Answer

B:

The technical cause is Device alias changes have not been committed and distributed through the supported fabric database workflow. The appropriate response is: Commit the approved device alias database transaction and verify resolution across the affected switches. Confirm successful repair: All participating MDS switches resolve the alias to the intended replacement WWPN consistently.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: device alias changes have not been committed and distributed through the supported fabric database workflow.

C:

“Create separate approved zones for each host initiator with its authorized storage target ports” responds to this separate finding: the zone combines initiators beyond the least-privilege single-initiator zoning design. This question instead needs “Commit the approved device alias database transaction and verify resolution across the affected switches”, so the alternative does not meet the stated condition.

D:

The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. “Verify target port FLOGI and FCNS registration and restore the authorized target attachment” applies to that separate problem. The observed case is the zoning administrator changes a device alias name to point to a replacement HBA, but other switches keep resolving the old identity because the alias database was not committed; choosing this alternative would address the wrong failure mode.

Question 394

A newly commissioned network, compute or storage service reports: A newly introduced access VLAN sees ARP spoofing attempts despite DHCP snooping being enabled because no dynamic ARP inspection policy is active for the VLAN. Which operational guardrail would prevent a similar outage?

  1. Maintain approved HBA identity records and update port security during controlled hardware replacement.
  2. Test IPv6 first-hop security along with DHCP and ARP controls during access-switch turnup.
  3. Test UCS AAA dependency failure without weakening audit and least-privilege controls.
  4. Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added.

Explanation

Correct Answer

D:

This safeguard addresses dynamic arp inspection binding validation: DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. The appropriate prevention is: Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. “Maintain approved HBA identity records and update port security during controlled hardware replacement” would address that alternative cause, not the condition in this question: dHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN.

B:

“Test IPv6 first-hop security along with DHCP and ARP controls during access-switch turnup” responds to this separate finding: the access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. This question instead needs “Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added”, so the alternative does not meet the stated condition.

C:

The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. “Test UCS AAA dependency failure without weakening audit and least-privilege controls” applies to that separate problem. The observed case is a newly introduced access VLAN sees ARP spoofing attempts despite DHCP snooping being enabled because no dynamic ARP inspection policy is active for the VLAN; choosing this alternative would address the wrong failure mode.

Question 395

A data center implementation team investigates the following fault: A newly attached service profile cannot create its virtual network adapters because every address in its assigned MAC pool is already allocated. What preventive control would best avoid repeating this fault?

  1. Validate failover semantics against the host operating system teaming configuration before production use.
  2. Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot.
  3. Revalidate target WWPN and LUN mappings after storage-controller failover or replacement.
  4. Monitor pool utilization and reserve addresses before deploying large numbers of server profiles.

Explanation

Correct Answer

D:

This safeguard addresses ucs mac address pool exhaustion: The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. The appropriate prevention is: Monitor pool utilization and reserve addresses before deploying large numbers of server profiles. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. “Validate failover semantics against the host operating system teaming configuration before production use” would address that alternative cause, not the condition in this question: the UCS MAC identity pool has insufficient available addresses for the requested vNIC identities.

B:

“Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot” responds to this separate finding: the virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. This question instead needs “Monitor pool utilization and reserve addresses before deploying large numbers of server profiles”, 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. “Revalidate target WWPN and LUN mappings after storage-controller failover or replacement” applies to that separate problem. The observed case is a newly attached service profile cannot create its virtual network adapters because every address in its assigned MAC pool is already allocated; choosing this alternative would address the wrong failure mode.

Question 396

A Nexus, UCS or MDS operations team encounters this issue: Two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list. What preventive control would best avoid repeating this fault?

  1. Monitor flow exporter reachability and collector acceptance after telemetry network changes.
  2. Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover.
  3. Document orphan workloads and test their failure conditions independently of dual-homed vPC hosts.
  4. Check channel mode, speed, VLAN and allowed-interface consistency before bringing up bundled links.

Explanation

Correct Answer

B:

This safeguard addresses vpc peer link consistency: The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The appropriate prevention is: Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

Flow-export destination reachability or the configured source and monitoring VRF are incorrect. “Monitor flow exporter reachability and collector acceptance after telemetry network changes” would address that alternative cause, not the condition in this question: the vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.

C:

“Document orphan workloads and test their failure conditions independently of dual-homed vPC hosts” 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 “Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover”, so the alternative does not meet the stated condition.

D:

The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. “Check channel mode, speed, VLAN and allowed-interface consistency before bringing up bundled links” applies to that separate problem. The observed case is two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list; choosing this alternative would address the wrong failure mode.

Question 397

A data center administrator identifies the following risk: A new MDS F-port physically connects to a storage target but remains in the default VSAN while its allowed initiator is in a separate production VSAN. What ongoing validation should operations establish for this service?

  1. Check each SAN port VSAN assignment before activating new production zones.
  2. Include EPLD impact and recovery planning when scheduling MDS component software updates.
  3. Review VSAN boundaries independently of physical switch and trunk connectivity.
  4. Document NPV versus NPIV responsibilities before configuring UCS and MDS fabric attachment.

Explanation

Correct Answer

A:

This safeguard addresses san vsan interface assignment at attachment: The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. The appropriate prevention is: Check each SAN port VSAN assignment before activating new production zones. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

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” would address that alternative cause, not the condition in this question: the target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset.

C:

“Review VSAN boundaries independently of physical switch and trunk connectivity” responds to this separate finding: vSAN membership is incorrectly shared between isolation domains with different storage access requirements. This question instead needs “Check each SAN port VSAN assignment before activating new production zones”, so the alternative does not meet the stated condition.

D:

NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. “Document NPV versus NPIV responsibilities before configuring UCS and MDS fabric attachment” applies to that separate problem. The observed case is a new MDS F-port physically connects to a storage target but remains in the default VSAN while its allowed initiator is in a separate production VSAN; choosing this alternative would address the wrong failure mode.

Question 398

A data center administrator identifies the following risk: A data center team modifies a static service profile on every blade individually, causing configuration drift when a shared SAN policy changes. Which verification result most directly demonstrates successful repair?

  1. The blade retains expected connectivity under an individual fabric path outage within the approved design.
  2. All attached eligible blades receive consistent policy changes with documented exceptions and maintenance impact.
  3. Authorized real-time flows receive the designated priority treatment and bulk traffic retains its separate class.
  4. The guest and external hosts exchange traffic over the authorized VLAN on both supported fabric paths.

Explanation

Correct Answer

B:

This observation validates ucs updating service profile templates: The configuration process bypasses the intended reusable UCS service profile template inheritance model. The corresponding corrective action is: Use an approved updating service profile template and apply governed changes to its associated server profiles. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. “Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior” would address that alternative cause, not the condition in this question: the configuration process bypasses the intended reusable UCS service profile template inheritance model.

C:

“Correct the supported UCS class-of-service and network QoS policy for the intended application traffic” 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 “Use an approved updating service profile template and apply governed changes to its associated server profiles”, 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 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 399

A data center implementation team investigates the following fault: A storage performance incident cannot be diagnosed because a copied FC traffic capture is configured to mirror an unrelated VSAN port instead of the affected ISL. What ongoing validation should operations establish for this service?

  1. Reconcile NFS export client authorization when hypervisor subnets or hosts change.
  2. Use capture scope and SAN data sensitivity review before activating port mirroring.
  3. Require SAN path redundancy and release-matrix signoff before MDS firmware activation.
  4. Include EPLD impact and recovery planning when scheduling MDS component software updates.

Explanation

Correct Answer

B:

This safeguard addresses cisco mds span fibre channel troubleshooting: The Fibre Channel SPAN session source does not identify the failing interface or service path. The appropriate prevention is: Use capture scope and SAN data sensitivity review before activating port mirroring. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The NFS export access rules do not authorize the requesting client address or security identity. “Reconcile NFS export client authorization when hypervisor subnets or hosts change” would address that alternative cause, not the condition in this question: the Fibre Channel SPAN session source does not identify the failing interface or service path.

C:

“Require SAN path redundancy and release-matrix signoff before MDS firmware activation” responds to this separate finding: the selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. This question instead needs “Use capture scope and SAN data sensitivity review before activating port mirroring”, 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 a storage performance incident cannot be diagnosed because a copied FC traffic capture is configured to mirror an unrelated VSAN port instead of the affected ISL; choosing this alternative would address the wrong failure mode.

Question 400

A data center administrator identifies the following risk: A packet-capture appliance shows no useful frames after a SPAN session was configured with the destination set to an ordinary forwarding interface. What preventive control would best avoid repeating this fault?

  1. Validate rendezvous-point redundancy and group mapping whenever multicast domains expand.
  2. Monitor flow exporter reachability and collector acceptance after telemetry network changes.
  3. Document SPAN source and destination interface restrictions for troubleshooting changes.
  4. Review telemetry subscriptions and alert coverage after changes to device software or fabric topology.

Explanation

Correct Answer

C:

This safeguard addresses span source and destination isolation: The SPAN session source and dedicated monitor destination roles were assigned incorrectly. The appropriate prevention is: Document SPAN source and destination interface restrictions for troubleshooting changes. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. “Validate rendezvous-point redundancy and group mapping whenever multicast domains expand” would address that alternative cause, not the condition in this question: the SPAN session source and dedicated monitor destination roles were assigned incorrectly.

B:

“Monitor flow exporter reachability and collector acceptance after telemetry network changes” responds to this separate finding: flow-export destination reachability or the configured source and monitoring VRF are incorrect. This question instead needs “Document SPAN source and destination interface restrictions for troubleshooting changes”, so the alternative does not meet the stated condition.

D:

The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. “Review telemetry subscriptions and alert coverage after changes to device software or fabric topology” applies to that separate problem. The observed case is a packet-capture appliance shows no useful frames after a SPAN session was configured with the destination set to an ordinary forwarding interface; choosing this alternative would address the wrong failure mode.