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 6

Question 50

A newly commissioned network, compute or storage service reports: A rack server must boot from an approved SAN LUN but repeatedly starts the local disk after a BIOS update changes its boot device priority. Which approved technology action addresses this incident most directly?

  1. Restore the supported boot policy and required SAN adapter path in the correct boot-device order.
  2. Use an approved updating service profile template and apply governed changes to its associated server profiles.
  3. Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis.
  4. Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network.

Explanation

Correct Answer

A:

The root problem is that The configured boot-device order does not select the intended SAN boot path before local storage. The selected change addresses it directly: Restore the supported boot policy and required SAN adapter path in the correct boot-device order. Verify the outcome: A controlled reboot starts the server from the authorized SAN boot target and reaches the expected OS.

Incorrect Answers

B:

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 configured boot-device order does not select the intended SAN boot path before local storage.

C:

This action concerns ucs blade chassis fabric discovery, where The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. The corrective response here is “Restore the supported boot policy and required SAN adapter path in the correct boot-device order”; this alternative does not provide that response.

D:

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 stem reports a rack server must boot from an approved SAN LUN but repeatedly starts the local disk after a BIOS update changes its boot device priority; this control addresses a different failure condition.

Question 51

A data center administrator identifies the following risk: A replacement UCS fabric interconnect has been installed, but operators have no recent recoverable configuration backup for the domain's identity pools and policies. What preventive control would best avoid repeating this fault?

  1. Check platform and adapter compatibility matrices before changing UCS host firmware policies.
  2. Pilot the firmware sequence and test fabric redundancy before simultaneous domain-wide activation.
  3. Schedule encrypted UCS configuration backups and perform periodic isolated restore tests.
  4. Run Intersight profile validation and dependency checks before assigning profiles to production servers.

Explanation

Correct Answer

C:

This safeguard addresses ucs configuration backup and restore: The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. The appropriate prevention is: Schedule encrypted UCS configuration backups and perform periodic isolated restore tests. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. “Check platform and adapter compatibility matrices before changing UCS host firmware policies” would address that alternative cause, not the condition in this question: the UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow.

B:

“Pilot the firmware sequence and test fabric redundancy before simultaneous domain-wide activation” responds to this separate finding: the upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. This question instead needs “Schedule encrypted UCS configuration backups and perform periodic isolated restore tests”, so the alternative does not meet the stated condition.

D:

The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies. “Run Intersight profile validation and dependency checks before assigning profiles to production servers” applies to that separate problem. The observed case is a replacement UCS fabric interconnect has been installed, but operators have no recent recoverable configuration backup for the domain's identity pools and policies; choosing this alternative would address the wrong failure mode.

Question 52

During a Cisco data center readiness review, engineers observe: Two Cisco MDS Fibre Channel switches are merged into one fabric, but an ISL becomes segmented because both switches use the same configured domain ID. Which deployment safeguard most directly reduces this failure risk?

  1. Validate domain IDs and fabric merge compatibility before joining independently built SAN fabrics.
  2. Track port role, link state and FLOGI database entries in server storage connection validation.
  3. Include FC port-channel member parameter checks in redundant SAN link commissioning.
  4. Audit VSAN allow-lists and operational trunk membership when adding Fibre Channel ISLs.

Explanation

Correct Answer

A:

This safeguard addresses fibre channel domain id collision: The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. The appropriate prevention is: Validate domain IDs and fabric merge compatibility before joining independently built SAN fabrics. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The initiator has not completed successful fabric login and thus has no authorized FCID assignment. “Track port role, link state and FLOGI database entries in server storage connection validation” would address that alternative cause, not the condition in this question: the Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization.

C:

“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 “Validate domain IDs and fabric merge compatibility before joining independently built SAN fabrics”, so the alternative does not meet the stated condition.

D:

The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. “Audit VSAN allow-lists and operational trunk membership when adding Fibre Channel ISLs” applies to that separate problem. The observed case is two Cisco MDS Fibre Channel switches are merged into one fabric, but an ISL becomes segmented because both switches use the same configured domain ID; choosing this alternative would address the wrong failure mode.

Question 53

A data center administrator identifies the following risk: A new stateless UCS blade service profile has its boot policy set to a retired target WWPN, so the host never discovers the correct boot LUN. Which design or configuration error caused the described issue?

  1. The vHBA WWPN allocation violates uniqueness requirements across server storage initiators.
  2. The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path.
  3. The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end.
  4. The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target.

Explanation

Correct Answer

D:

The technical cause is The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. The appropriate response is: Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters. Confirm successful repair: The replacement blade identifies the intended LUN and completes a controlled SAN boot.

Incorrect Answers

A:

The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. “Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration” would address that alternative cause, not the condition in this question: the SAN boot policy refers to an unavailable storage target identity rather than the authorized active target.

B:

“Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design” responds to this separate finding: the UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. This question instead needs “Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters”, so the alternative does not meet the stated condition.

C:

The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. “Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN” applies to that separate problem. The observed case is a new stateless UCS blade service profile has its boot policy set to a retired target WWPN, so the host never discovers the correct boot LUN; choosing this alternative would address the wrong failure mode.

Question 54

A data center implementation team investigates the following fault: A rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping. What preventive control would best avoid repeating this fault?

  1. Test UCS AAA dependency failure without weakening audit and least-privilege controls.
  2. Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes.
  3. Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added.
  4. Test IPv6 first-hop security along with DHCP and ARP controls during access-switch turnup.

Explanation

Correct Answer

B:

This safeguard addresses dhcp snooping trusted server interface: DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. The appropriate prevention is: Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: dHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies.

C:

“Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added” responds to this separate finding: dHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. This question instead needs “Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes”, so the alternative does not meet the stated condition.

D:

The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. “Test IPv6 first-hop security along with DHCP and ARP controls during access-switch turnup” applies to that separate problem. The observed case is a rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping; choosing this alternative would address the wrong failure mode.

Question 55

A newly commissioned network, compute or storage service reports: A virtualization platform needs a block device for a raw LUN but the proposed integration offers only an NFS file-system export as though it were an iSCSI target. Which approved technology action addresses this incident most directly?

  1. Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk.
  2. Update the approved initiator and target CHAP secret settings using the supported secure workflow.
  3. Update the scoped NFS export policy to include only the approved new hypervisor client addresses.
  4. Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status.

Explanation

Correct Answer

A:

The root problem is that The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. The selected change addresses it directly: Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk. Verify the outcome: The host discovers an iSCSI target LUN and presents the expected block device to the hypervisor.

Incorrect Answers

B:

This action concerns iscsi chap target authentication, where The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. The reported failure instead stems from The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation.

C:

This action concerns nfs export client authorization, where The NFS export access rules do not authorize the requesting client address or security identity. The corrective response here is “Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk”; this alternative does not provide that response.

D:

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 stem reports a virtualization platform needs a block device for a raw LUN but the proposed integration offers only an NFS file-system export as though it were an iSCSI target; this control addresses a different failure condition.

Question 56

A data center administrator identifies the following risk: A host sends FCoE storage traffic on an ordinary IP VLAN with no supported Fibre Channel Forwarder or proper FCoE VLAN configuration. Which design or configuration error caused the described issue?

  1. NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch.
  2. The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset.
  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

D:

The technical cause is The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. The appropriate response is: Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path. Confirm successful repair: The converged adapter completes supported FCoE fabric login and discovers the permitted storage target.

Incorrect Answers

A:

NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. “Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design” would address that alternative cause, not the condition in this question: the converged network design does not map the FCoE traffic to the required supported FCF and VSAN service.

B:

“Assign the target port to the approved VSAN and verify its effective FCNS and zone membership” responds to this separate finding: the target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. This question instead needs “Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path”, so the alternative does not meet the stated condition.

C:

VSAN membership is incorrectly shared between isolation domains with different storage access requirements. “Move the backup server connection into the approved dedicated VSAN and update authorized zoning” applies to that separate problem. The observed case is a host sends FCoE storage traffic on an ordinary IP VLAN with no supported Fibre Channel Forwarder or proper FCoE VLAN configuration; choosing this alternative would address the wrong failure mode.

Question 57

A newly commissioned network, compute or storage service reports: An IPv6-only data center link has working layer-three connectivity but an OSPFv3 neighbor never forms because opposite ends use different area assignments. What is the primary technical reason the deployment fails?

  1. The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts.
  2. The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints.
  3. The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability.
  4. The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link.

Explanation

Correct Answer

A:

The technical cause is The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. The appropriate response is: Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation. Confirm successful repair: The two routers establish an OSPFv3 Full adjacency and learn the expected IPv6 prefixes.

Incorrect Answers

B:

The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. “Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path” would address that alternative cause, not the condition in this question: the OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts.

C:

“Activate the correct EVPN address family for authorized peers and verify route advertisement policy” responds to this separate finding: the BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. This question instead needs “Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation”, so the alternative does not meet the stated condition.

D:

The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. “Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role” applies to that separate problem. The observed case is an IPv6-only data center link has working layer-three connectivity but an OSPFv3 neighbor never forms because opposite ends use different area assignments; choosing this alternative would address the wrong failure mode.

Question 58

A Nexus, UCS or MDS operations team encounters this issue: A UCS blade can reach its Ethernet network but cannot discover a SAN boot target because the vHBA has been assigned to a different VSAN from its storage uplink. What preventive control would best avoid repeating this fault?

  1. Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot.
  2. Monitor pool utilization and reserve addresses before deploying large numbers of server profiles.
  3. Maintain service profile templates and identity pools independent of individual server serial numbers.
  4. Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment.

Explanation

Correct Answer

A:

This safeguard addresses ucs vhba vsan assignment consistency: The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. The appropriate prevention is: Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. “Monitor pool utilization and reserve addresses before deploying large numbers of server profiles” would address that alternative cause, not the condition in this question: the virtual HBA path is not participating in the intended Fibre Channel VSAN end to end.

C:

“Maintain service profile templates and identity pools independent of individual server serial numbers” responds to this separate finding: the server identity has not been abstracted through approved UCS service profile and identity-pool associations. This question instead needs “Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot”, so the alternative does not meet the stated condition.

D:

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

Question 59

A data center administrator identifies the following risk: 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 corrective change best resolves this problem?

  1. Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning.
  2. Create separate approved zones for each host initiator with its authorized storage target ports.
  3. Identify the legitimate lock owner and safely complete or abort the supported CFS session.
  4. Commit the approved device alias database transaction and verify resolution across the affected switches.

Explanation

Correct Answer

D:

The root problem is that Device alias changes have not been committed and distributed through the supported fabric database workflow. The selected change addresses it directly: Commit the approved device alias database transaction and verify resolution across the affected switches. Verify the outcome: All participating MDS switches resolve the alias to the intended replacement WWPN consistently.

Incorrect Answers

A:

This action concerns active fibre channel zoneset validation, where An inactive zoning database edit does not change the effective active zoneset on the SAN fabric. The reported failure instead stems from Device alias changes have not been committed and distributed through the supported fabric database workflow.

B:

This action concerns single initiator target zoning design, where The zone combines initiators beyond the least-privilege single-initiator zoning design. The corrective response here is “Commit the approved device alias database transaction and verify resolution across the affected switches”; this alternative does not provide that response.

C:

This action concerns cisco fabric services configuration distribution, where A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. The stem reports 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; this control addresses a different failure condition.

Question 60

While checking a production data center change, the team finds: An automation client retries an administrative NX-API request repeatedly after receiving HTTP 403, misclassifying authorization denial as a transient device failure. Which deployment safeguard most directly reduces this failure risk?

  1. Document shell boundaries and supported packages before on-box automation deployment.
  2. Test rerun behavior and configuration diffs before scheduling on-box Python automation.
  3. Audit scheduler job frequency and execution history after automation changes.
  4. Build explicit error classification and bounded retries into every infrastructure API client.

Explanation

Correct Answer

D:

This safeguard addresses rest api authorization status handling: The REST client does not distinguish insufficient authorization from retryable transport or server errors. The appropriate prevention is: Build explicit error classification and bounded retries into every infrastructure API client. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. “Document shell boundaries and supported packages before on-box automation deployment” would address that alternative cause, not the condition in this question: the REST client does not distinguish insufficient authorization from retryable transport or server errors.

B:

“Test rerun behavior and configuration diffs before scheduling on-box Python automation” responds to this separate finding: the script lacks an idempotent precheck to compare desired and current network device state. This question instead needs “Build explicit error classification and bounded retries into every infrastructure API client”, so the alternative does not meet the stated condition.

C:

The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. “Audit scheduler job frequency and execution history after automation changes” applies to that separate problem. The observed case is an automation client retries an administrative NX-API request repeatedly after receiving HTTP 403, misclassifying authorization denial as a transient device failure; choosing this alternative would address the wrong failure mode.