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 24

Question 230

While checking a production data center change, the team finds: 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 observation best confirms the configuration now behaves correctly?

  1. The time-series reports expose the loss interval and correlate it with the affected interfaces and fabric paths.
  2. Remote VTEPs learn the required IP prefix in the correct VRF and forward traffic toward its reachable next hop.
  3. Remote VTEP loopbacks resolve correctly and workload frames traverse the VXLAN overlay.
  4. Hosts in the authorized segment communicate across leaves while unrelated tenant segments remain separate.

Explanation

Correct Answer

B:

This observation validates 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 corresponding corrective action is: Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF. Evidence about a different component does not establish the requested service outcome.

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 routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route.

C:

“Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies” responds to this separate finding: the NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. This question instead needs “Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF”, so the alternative does not meet the stated condition.

D:

The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. “Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves” 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 231

While checking a production data center change, the team finds: A data center hypervisor installation fails hardware virtualization preflight on otherwise compatible UCS blades after a generic BIOS profile disabled virtualization features. Which approved technology action addresses this incident most directly?

  1. Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network.
  2. Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot.
  3. Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it.
  4. Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend.

Explanation

Correct Answer

B:

The root problem is that The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The selected change addresses it directly: Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot. Verify the outcome: The hypervisor passes hardware virtualization checks and starts a test virtual machine successfully.

Incorrect Answers

A:

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

C:

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 corrective response here is “Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot”; this alternative does not provide that response.

D:

This action concerns intersight hardware telemetry alarm review, where The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. The stem reports a data center hypervisor installation fails hardware virtualization preflight on otherwise compatible UCS blades after a generic BIOS profile disabled virtualization features; this control addresses a different failure condition.

Question 232

While checking a production data center change, the team finds: A storage administrator is given a full UCS administrator role even though the job requires only SAN and vHBA policy visibility. Which deployment safeguard most directly reduces this failure risk?

  1. Exercise break-glass access and credential rotation under controlled audit conditions.
  2. Recertify UCS role assignments after team or responsibility changes.
  3. Periodically audit Intersight role scopes and API account privileges for privilege creep.
  4. Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes.

Explanation

Correct Answer

B:

This safeguard addresses ucs manager role based access: The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. The appropriate prevention is: Recertify UCS role assignments after team or responsibility changes. 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: the UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities.

C:

“Periodically audit Intersight role scopes and API account privileges for privilege creep” responds to this separate finding: the Intersight role assignment is not scoped to the authorized organization and permitted resource actions. This question instead needs “Recertify UCS role assignments after team or responsibility changes”, so the alternative does not meet the stated condition.

D:

DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. “Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes” applies to that separate problem. The observed case is a storage administrator is given a full UCS administrator role even though the job requires only SAN and vHBA policy visibility; choosing this alternative would address the wrong failure mode.

Question 233

A data center administrator identifies the following risk: 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. What preventive control would best avoid repeating this fault?

  1. Verify pending and committed device alias state whenever server HBA identities change.
  2. Validate iSCSI authentication lifecycle and secret rotation with connectivity testing.
  3. Document file versus block protocols as separate design decisions in storage onboarding.
  4. Reconcile NFS export client authorization when hypervisor subnets or hosts change.

Explanation

Correct Answer

B:

This safeguard addresses iscsi chap target authentication: The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. The appropriate prevention is: Validate iSCSI authentication lifecycle and secret rotation with connectivity testing. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

Device alias changes have not been committed and distributed through the supported fabric database workflow. “Verify pending and committed device alias state whenever server HBA identities change” would address that alternative cause, not the condition in this question: the iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials.

C:

“Document file versus block protocols as separate design decisions in storage onboarding” responds to this separate finding: the application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. This question instead needs “Validate iSCSI authentication lifecycle and secret rotation with connectivity testing”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 234

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

  1. Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups.
  2. Configure a matching supported LACP mode and port-channel membership across the two endpoints.
  3. Review supported orphan-port handling and move or protect the workload on the planned resilient attachment.
  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 The failure design does not account for orphan-port behavior and the chosen peer recovery semantics. The selected change addresses it directly: Review supported orphan-port handling and move or protect the workload on the planned resilient attachment. Verify the outcome: The server remains reachable during documented peer and peer-link failure tests without unsafe duplicate forwarding.

Incorrect Answers

A:

This action concerns pim multicast rendezvous point reachability, where The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. The reported failure instead stems from The failure design does not account for orphan-port behavior and the chosen peer recovery semantics.

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 “Review supported orphan-port handling and move or protect the workload on the planned resilient attachment”; 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 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; this control addresses a different failure condition.

Question 235

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 deployment safeguard most directly reduces this failure risk?

  1. Reconcile NFS export client authorization when hypervisor subnets or hosts change.
  2. Include FC port-channel member parameter checks in redundant SAN link commissioning.
  3. Validate domain IDs and fabric merge compatibility before joining independently built SAN fabrics.
  4. Track port role, link state and FLOGI database entries in server storage connection validation.

Explanation

Correct Answer

D:

This safeguard addresses flogi registration and fcid assignment: The initiator has not completed successful fabric login and thus has no authorized FCID assignment. The appropriate prevention is: Track port role, link state and FLOGI database entries in server storage connection validation. 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 initiator has not completed successful fabric login and thus has no authorized FCID assignment.

B:

“Include FC port-channel member parameter checks in redundant SAN link commissioning” responds to this separate finding: the FC port channel and prospective member disagree on required operational attributes for bundling. This question instead needs “Track port role, link state and FLOGI database entries in server storage connection validation”, so the alternative does not meet the stated condition.

C:

The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. “Validate domain IDs and fabric merge compatibility before joining independently built SAN fabrics” 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 236

During a Cisco data center readiness review, engineers observe: A rack server intended for local mirrored boot disks reports an absent boot volume after the storage controller was left with unconfigured physical drives. Which implementation action should the engineer take first?

  1. Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it.
  2. Expand or assign a nonoverlapping approved MAC pool and retry the service profile association.
  3. Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks.
  4. Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot.

Explanation

Correct Answer

A:

The root problem is that The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. The selected change addresses it directly: Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it. Verify the outcome: The server recognizes the protected boot volume and tolerates the documented single-disk test condition.

Incorrect Answers

B:

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 server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy.

C:

This action concerns ucs service profile association maintenance, where The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings. The corrective response here is “Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it”; this alternative does not provide that response.

D:

This action concerns ucs bios virtualization extensions, where The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The stem reports a rack server intended for local mirrored boot disks reports an absent boot volume after the storage controller was left with unconfigured physical drives; this control addresses a different failure condition.

Question 237

A newly commissioned network, compute or storage service reports: Two SAN-connected server profiles are provisioned with overlapping manually assigned virtual HBA worldwide port names, disrupting their distinct storage identities. What technical condition most directly accounts for the failure?

  1. UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements.
  2. The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end.
  3. The vHBA WWPN allocation violates uniqueness requirements across server storage initiators.
  4. The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities.

Explanation

Correct Answer

C:

The technical cause is The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. The appropriate response is: Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration. Confirm successful repair: Both servers log in with their own WWPN identities and see only their authorized storage paths.

Incorrect Answers

A:

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 vHBA WWPN allocation violates uniqueness requirements across server storage initiators.

B:

“Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN” 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 “Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration”, so the alternative does not meet the stated condition.

D:

The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. “Expand or assign a nonoverlapping approved MAC pool and retry the service profile association” applies to that separate problem. The observed case is two SAN-connected server profiles are provisioned with overlapping manually assigned virtual HBA worldwide port names, disrupting their distinct storage identities; choosing this alternative would address the wrong failure mode.

Question 238

While checking a production data center change, the team finds: Two VXLAN leaf switches serve the same tenant bridge domain but forward frames to different VXLAN network identifiers due to mismatched local mappings. What is the primary technical reason the deployment fails?

  1. The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.
  2. The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route.
  3. The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs.
  4. The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain.

Explanation

Correct Answer

C:

The technical cause is The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The appropriate response is: Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves. Confirm successful repair: Hosts in the authorized segment communicate across leaves while unrelated tenant segments remain separate.

Incorrect Answers

A:

The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. “Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms” would address that alternative cause, not the condition in this question: the tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs.

B:

“Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF” responds to this separate finding: the routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. This question instead needs “Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is two VXLAN leaf switches serve the same tenant bridge domain but forward frames to different VXLAN network identifiers due to mismatched local mappings; choosing this alternative would address the wrong failure mode.

Question 239

A newly commissioned network, compute or storage service reports: An NFS mount command fails from a new virtualization host even though the storage array responds to ping, and the export permits only the retired host subnet. What observation best confirms the configuration now behaves correctly?

  1. The new host mounts the intended export while an unauthorized client remains denied.
  2. The module and operating system versions satisfy Cisco's documented compatibility requirements after the change.
  3. The iSCSI login authenticates successfully and the host discovers its authorized block LUN.
  4. The host discovers an iSCSI target LUN and presents the expected block device to the hypervisor.

Explanation

Correct Answer

A:

This observation validates nfs export client authorization: The NFS export access rules do not authorize the requesting client address or security identity. The corresponding corrective action is: Update the scoped NFS export policy to include only the approved new hypervisor client addresses. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. “Review the applicable MDS EPLD package and schedule the correct supported component update” would address that alternative cause, not the condition in this question: the NFS export access rules do not authorize the requesting client address or security identity.

C:

“Update the approved initiator and target CHAP secret settings using the supported secure workflow” responds to this separate finding: the iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. This question instead needs “Update the scoped NFS export policy to include only the approved new hypervisor client addresses”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an NFS mount command fails from a new virtualization host even though the storage array responds to ping, and the export permits only the retired host subnet; choosing this alternative would address the wrong failure mode.

Question 240

A data center administrator identifies the following risk: An installed UCS blade becomes unreachable when the only mapped I/O module path is disabled although a second IOM is physically available. Which verification result most directly demonstrates successful repair?

  1. The replacement blade identifies the intended LUN and completes a controlled SAN boot.
  2. The guest and external hosts exchange traffic over the authorized VLAN on both supported fabric paths.
  3. The blade retains expected connectivity under an individual fabric path outage within the approved design.
  4. Authorized real-time flows receive the designated priority treatment and bulk traffic retains its separate class.

Explanation

Correct Answer

C:

This observation validates ucs chassis iom fabric path redundancy: The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. The corresponding corrective action is: Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. “Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters” would address that alternative cause, not the condition in this question: the chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths.

B:

“Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access” responds to this separate finding: the VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. This question instead needs “Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an installed UCS blade becomes unreachable when the only mapped I/O module path is disabled although a second IOM is physically available; choosing this alternative would address the wrong failure mode.