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 10

Question 90

While checking a production data center change, the team finds: A dual-fabric UCS server unexpectedly loses the same application VLAN when one fabric interconnect fails because its vNIC failover behavior is not coordinated. Which implementation action should the engineer take first?

  1. Expand or assign a nonoverlapping approved MAC pool and retry the service profile association.
  2. Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration.
  3. Associate the intended service profile and its identity pools with the supported replacement hardware.
  4. Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design.

Explanation

Correct Answer

D:

The root problem is that The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. The selected change addresses it directly: Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design. Verify the outcome: A controlled fabric failover retains authorized server network reachability without duplicate MAC or VLAN problems.

Incorrect Answers

A:

This action concerns ucs mac address pool exhaustion, where The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. The reported failure instead stems from The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path.

B:

This action concerns ucs wwpn pool uniqueness, where The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. The corrective response here is “Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design”; this alternative does not provide that response.

C:

This action concerns ucs service profile server identity, where The server identity has not been abstracted through approved UCS service profile and identity-pool associations. The stem reports a dual-fabric UCS server unexpectedly loses the same application VLAN when one fabric interconnect fails because its vNIC failover behavior is not coordinated; this control addresses a different failure condition.

Question 91

During a Cisco data center readiness review, engineers observe: A Fibre Channel HBA has physical link but never receives a fabric address after a switch port was assigned the wrong interface role. Which implementation action should the engineer take first?

  1. Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator.
  2. Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status.
  3. Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member.
  4. Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process.

Explanation

Correct Answer

A:

The root problem is that The initiator has not completed successful fabric login and thus has no authorized FCID assignment. The selected change addresses it directly: Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator. Verify the outcome: The initiator completes FLOGI and receives a valid FCID in the correct SAN fabric.

Incorrect Answers

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 reported failure instead stems from The initiator has not completed successful fabric login and thus has no authorized FCID assignment.

C:

This action concerns fibre channel port channel member consistency, where The FC port channel and prospective member disagree on required operational attributes for bundling. The corrective response here is “Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator”; this alternative does not provide that response.

D:

This action concerns fibre channel domain id collision, where The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. The stem reports a Fibre Channel HBA has physical link but never receives a fabric address after a switch port was assigned the wrong interface role; this control addresses a different failure condition.

Question 92

A newly commissioned network, compute or storage service reports: A Nexus switch loses its remote AAA connection during maintenance and administrators have no approved emergency login route because all local recovery credentials were disabled. Which deployment safeguard most directly reduces this failure risk?

  1. Review fabric-binding membership with SAN topology changes and device replacement plans.
  2. Test actual AAA command authorization and accounting for each approved Nexus support role.
  3. Exercise break-glass access and credential rotation under controlled audit conditions.
  4. Periodically audit Intersight role scopes and API account privileges for privilege creep.

Explanation

Correct Answer

C:

This safeguard addresses nx os local emergency account control: The management access policy lacks a tested protected local recovery identity for remote AAA outages. The appropriate prevention is: Exercise break-glass access and credential rotation under controlled audit conditions. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the management access policy lacks a tested protected local recovery identity for remote AAA outages.

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 “Exercise break-glass access and credential rotation under controlled audit conditions”, 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. “Periodically audit Intersight role scopes and API account privileges for privilege creep” applies to that separate problem. The observed case is a Nexus switch loses its remote AAA connection during maintenance and administrators have no approved emergency login route because all local recovery credentials were disabled; choosing this alternative would address the wrong failure mode.

Question 93

During a Cisco data center readiness review, engineers observe: An engineer changes a Nexus port-channel policy and several interfaces stop passing traffic, but no approved prechange rollback point exists. Which operational guardrail would prevent a similar outage?

  1. Include release-path and feature-support checks before all production Nexus software changes.
  2. Require a validated checkpoint and restore rehearsal for high-impact Nexus configuration edits.
  3. Track EPLD, line-card and operating system dependencies in change and rollback plans.
  4. Confirm querier presence and snooping tables in every multicast-capable access VLAN.

Explanation

Correct Answer

B:

This safeguard addresses nexus configuration checkpoint recovery: The change process omitted a recoverable NX-OS configuration checkpoint and validation plan. The appropriate prevention is: Require a validated checkpoint and restore rehearsal for high-impact Nexus configuration edits. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. “Include release-path and feature-support checks before all production Nexus software changes” would address that alternative cause, not the condition in this question: the change process omitted a recoverable NX-OS configuration checkpoint and validation plan.

C:

“Track EPLD, line-card and operating system dependencies in change and rollback plans” responds to this separate finding: the planned software transition omits the EPLD compatibility and operational impact assessment. This question instead needs “Require a validated checkpoint and restore rehearsal for high-impact Nexus configuration edits”, so the alternative does not meet the stated condition.

D:

The VLAN lacks a reachable supported multicast querier. “Confirm querier presence and snooping tables in every multicast-capable access VLAN” applies to that separate problem. The observed case is an engineer changes a Nexus port-channel policy and several interfaces stop passing traffic, but no approved prechange rollback point exists; choosing this alternative would address the wrong failure mode.

Question 94

During a Cisco data center readiness review, engineers observe: 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. Which implementation action should the engineer take first?

  1. Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method.
  2. Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis.
  3. Review the applicable MDS EPLD package and schedule the correct supported component update.
  4. Set a supported FC SPAN monitor source for the affected port and the approved capture destination.

Explanation

Correct Answer

D:

The root problem is that The Fibre Channel SPAN session source does not identify the failing interface or service path. The selected change addresses it directly: Set a supported FC SPAN monitor source for the affected port and the approved capture destination. Verify the outcome: The SAN analyzer receives the relevant FC exchanges needed to isolate the transport fault.

Incorrect Answers

A:

This action concerns cisco mds nondisruptive upgrade prechecks, where The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. The reported failure instead stems from The Fibre Channel SPAN session source does not identify the failing interface or service path.

B:

This action concerns nexus dashboard san performance assurance, where The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. The corrective response here is “Set a supported FC SPAN monitor source for the affected port and the approved capture destination”; this alternative does not provide that response.

C:

This action concerns cisco mds epld hardware dependency, where The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. The stem reports 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; this control addresses a different failure condition.

Question 95

A data center implementation team investigates the following fault: An external service subnet must be reached through an EVPN VXLAN fabric, but peer leaves learn endpoint MACs without the expected IP prefix route. What ongoing validation should operations establish for this service?

  1. Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes.
  2. Monitor endpoint advertisement and withdrawal during workload migration and policy updates.
  3. Test VTEP source reachability as a prerequisite for every fabric underlay policy change.
  4. Review tenant L3VNI and route-target controls when adding external routed service networks.

Explanation

Correct Answer

D:

This safeguard addresses evpn ip prefix type five advertisement: The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. The appropriate prevention is: Review tenant L3VNI and route-target controls when adding external routed service networks. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. “Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes” would address that alternative cause, not the condition in this question: the routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route.

B:

“Monitor endpoint advertisement and withdrawal during workload migration and policy updates” responds to this separate finding: the Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. This question instead needs “Review tenant L3VNI and route-target controls when adding external routed service networks”, so the alternative does not meet the stated condition.

C:

The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. “Test VTEP source reachability as a prerequisite for every fabric underlay policy change” applies to that separate problem. The observed case is an external service subnet must be reached through an EVPN VXLAN fabric, but peer leaves learn endpoint MACs without the expected IP prefix route; choosing this alternative would address the wrong failure mode.

Question 96

A data center administrator identifies the following risk: An MDS inter-switch link is online but initiators in VSAN 30 cannot reach targets on the far switch after a new trunk was introduced. Which root cause best explains this behavior?

  1. The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded.
  2. The initiator has not completed successful fabric login and thus has no authorized FCID assignment.
  3. The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization.
  4. The FC trunk does not carry the required VSAN membership consistently between the two MDS switches.

Explanation

Correct Answer

D:

The technical cause is The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. The appropriate response is: Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status. Confirm successful repair: The target and initiator register and exchange traffic inside VSAN 30 without affecting other VSANs.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the FC trunk does not carry the required VSAN membership consistently between the two MDS switches.

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 “Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status”, so the alternative does not meet the stated condition.

C:

The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. “Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process” applies to that separate problem. The observed case is an MDS inter-switch link is online but initiators in VSAN 30 cannot reach targets on the far switch after a new trunk was introduced; choosing this alternative would address the wrong failure mode.

Question 97

A Nexus, UCS or MDS operations team encounters this issue: Distributed model training runs across GPU pods but experiences network bottlenecks because oversubscribed links carry synchronized east-west collective operations without capacity planning. Which verification result most directly demonstrates successful repair?

  1. Collective workload tests meet the required throughput and latency targets without sustained link oversubscription.
  2. The intended policy persists after controller synchronization and devices report consistent compliance.
  3. A permitted API call succeeds while denied operations report a clear nonretryable authorization error.
  4. The GPU fabric sustains the benchmark workload with controlled loss and congestion indicators during bursts.

Explanation

Correct Answer

A:

This observation validates ai workload high bandwidth east west paths: The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload. The corresponding corrective action is: Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology. 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 data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload.

C:

“Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures” responds to this separate finding: the REST client does not distinguish insufficient authorization from retryable transport or server errors. This question instead needs “Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology”, so the alternative does not meet the stated condition.

D:

The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. “Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path” applies to that separate problem. The observed case is distributed model training runs across GPU pods but experiences network bottlenecks because oversubscribed links carry synchronized east-west collective operations without capacity planning; choosing this alternative would address the wrong failure mode.

Question 98

A data center administrator identifies the following risk: A UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults. Which root cause best explains this behavior?

  1. The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy.
  2. The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history.
  3. The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings.
  4. The BIOS policy disables required CPU virtualization support expected by the approved hypervisor.

Explanation

Correct Answer

B:

The technical cause is The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. The appropriate response is: Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend. Confirm successful repair: Intersight records the hardware fault and resolution, while workload stability returns after repair.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history.

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 supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend”, so the alternative does not meet the stated condition.

D:

The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. “Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot” applies to that separate problem. The observed case is a UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults; choosing this alternative would address the wrong failure mode.

Question 99

While checking a production data center change, the team finds: 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 implementation action should the engineer take first?

  1. Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path.
  2. Configure a matching supported LACP mode and port-channel membership across the two endpoints.
  3. Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology.
  4. Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms.

Explanation

Correct Answer

C:

The root problem is that Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. The selected change addresses it directly: Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology. Verify the outcome: The designated aggregation switch is the root and the expected alternate links remain loop-free.

Incorrect Answers

A:

This action concerns nx os issu support preflight, where The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. The reported failure instead stems from Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root.

B:

This action concerns lacp port channel negotiation, where The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. The corrective response here is “Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology”; this alternative does not provide that response.

D:

This action concerns vpc peer link consistency, where The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The stem reports a new access switch unexpectedly becomes the spanning-tree root and traffic now follows a slow backup inter-switch link across the data center; this control addresses a different failure condition.

Question 100

A data center implementation team investigates the following fault: An MDS monitoring analyst receives a network-admin role and can edit SAN zoning despite requiring only fabric health visibility. Which design or configuration error caused the described issue?

  1. The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs.
  2. Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL.
  3. The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter.
  4. Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.

Explanation

Correct Answer

A:

The technical cause is The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. The appropriate response is: Replace the overly broad MDS role with an approved read-only or scoped monitoring role. Confirm successful repair: The analyst inspects FCNS and port health but cannot activate or change production zonesets.

Incorrect Answers

B:

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” 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 ACI contract consumer-provider bindings and permit only the required application port” responds to this separate finding: the contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. 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:

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