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 15

Question 140

A Nexus, UCS or MDS operations team encounters this issue: 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 is the most appropriate remediation for these symptoms?

  1. Coordinate the supported authentication keychain parameters and overlapping key transition periods.
  2. Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths.
  3. Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports.
  4. Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings.

Explanation

Correct Answer

B:

The root problem is that DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. The selected change addresses it directly: Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths. Verify the outcome: Unauthorized DHCP offers are dropped while valid clients receive leases from the approved server.

Incorrect Answers

A:

This action concerns ospf keychain authentication rotation, where The OSPF authentication peers are using mismatched active key IDs or validity intervals. The reported failure instead stems from DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies.

C:

This action concerns ipv6 router advertisement guard, where The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. The corrective response here is “Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths”; this alternative does not provide that response.

D:

This action concerns dynamic arp inspection binding validation, where DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. The stem reports a rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping; this control addresses a different failure condition.

Question 141

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. After remediation, which acceptance result is most relevant?

  1. The two routers establish an OSPFv3 Full adjacency and learn the expected IPv6 prefixes.
  2. The intended receivers join and receive source traffic, and PIM control state shows the proper tree.
  3. The leaf receives the intended EVPN routes and remote workloads become reachable over VXLAN.
  4. Both peers reach Full state and exchange the intended routes without retransmission or MTU errors.

Explanation

Correct Answer

A:

This observation validates ospfv3 ipv6 area consistency: The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. The corresponding corrective action is: Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. “Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups” 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 neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. “Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency” 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 142

During a Cisco data center readiness review, engineers observe: A Nexus maintenance plan upgrades only the system image while a documented line-card hardware programming device update is required for the target release. Which deployment safeguard most directly reduces this failure risk?

  1. Track EPLD, line-card and operating system dependencies in change and rollback plans.
  2. Include release-path and feature-support checks before all production Nexus software changes.
  3. Require a validated checkpoint and restore rehearsal for high-impact Nexus configuration edits.
  4. Test upstream failure, HSRP role transitions, and gateway reachability during each redundancy exercise.

Explanation

Correct Answer

A:

This safeguard addresses nexus epld upgrade safety: The planned software transition omits the EPLD compatibility and operational impact assessment. The appropriate prevention is: Track EPLD, line-card and operating system dependencies in change and rollback plans. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

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 planned software transition omits the EPLD compatibility and operational impact assessment.

C:

“Require a validated checkpoint and restore rehearsal for high-impact Nexus configuration edits” responds to this separate finding: the change process omitted a recoverable NX-OS configuration checkpoint and validation plan. This question instead needs “Track EPLD, line-card and operating system dependencies in change and rollback plans”, 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. “Test upstream failure, HSRP role transitions, and gateway reachability during each redundancy exercise” applies to that separate problem. The observed case is a Nexus maintenance plan upgrades only the system image while a documented line-card hardware programming device update is required for the target release; choosing this alternative would address the wrong failure mode.

Question 143

A newly commissioned network, compute or storage service reports: A scheduled Nexus configuration backup runs continuously instead of once nightly because the job's scheduler interval was entered with the wrong units. Which operational guardrail would prevent a similar outage?

  1. Validate API schema and content-type handling before enabling configuration-changing requests.
  2. Build explicit error classification and bounded retries into every infrastructure API client.
  3. Test rerun behavior and configuration diffs before scheduling on-box Python automation.
  4. Audit scheduler job frequency and execution history after automation changes.

Explanation

Correct Answer

D:

This safeguard addresses nx os scheduler job interval: The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The appropriate prevention is: Audit scheduler job frequency and execution history after automation changes. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The NX-API request body and declared content format are inconsistent for the selected endpoint. “Validate API schema and content-type handling before enabling configuration-changing requests” 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.

B:

“Build explicit error classification and bounded retries into every infrastructure API client” responds to this separate finding: the REST client does not distinguish insufficient authorization from retryable transport or server errors. This question instead needs “Audit scheduler job frequency and execution history after automation changes”, so the alternative does not meet the stated condition.

C:

The script lacks an idempotent precheck to compare desired and current network device state. “Test rerun behavior and configuration diffs before scheduling on-box Python automation” 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 144

A data center administrator identifies the following risk: 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. Which test outcome proves the intended service was restored?

  1. All required vNICs receive unique authorized MAC addresses without conflicting with existing profiles.
  2. A controlled fabric failover retains authorized server network reachability without duplicate MAC or VLAN problems.
  3. The server HBA registers in the correct VSAN and discovers the authorized target storage port.
  4. The replacement blade receives the designated server identity and boots its workload according to policy.

Explanation

Correct Answer

C:

This observation validates ucs vhba vsan assignment consistency: The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. The corresponding corrective action is: Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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

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 “Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN”, so the alternative does not meet the stated condition.

D:

The server identity has not been abstracted through approved UCS service profile and identity-pool associations. “Associate the intended service profile and its identity pools with the supported replacement hardware” 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 145

While checking a production data center change, the team finds: A host sends FCoE storage traffic on an ordinary IP VLAN with no supported Fibre Channel Forwarder or proper FCoE VLAN configuration. Which operational guardrail would prevent a similar outage?

  1. Audit VSAN allow-lists and operational trunk membership when adding Fibre Channel ISLs.
  2. Review FCoE VLAN and lossless Ethernet prerequisites separately from ordinary LAN configuration.
  3. Document NPV versus NPIV responsibilities before configuring UCS and MDS fabric attachment.
  4. Review VSAN boundaries independently of physical switch and trunk connectivity.

Explanation

Correct Answer

B:

This safeguard addresses fibre channel over ethernet storage vlan mapping: The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. The appropriate prevention is: Review FCoE VLAN and lossless Ethernet prerequisites separately from ordinary LAN configuration. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

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

C:

“Document NPV versus NPIV responsibilities before configuring UCS and MDS fabric attachment” responds to this separate finding: nPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. This question instead needs “Review FCoE VLAN and lossless Ethernet prerequisites separately from ordinary LAN configuration”, so the alternative does not meet the stated condition.

D:

VSAN membership is incorrectly shared between isolation domains with different storage access requirements. “Review VSAN boundaries independently of physical switch and trunk connectivity” 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 146

A newly commissioned network, compute or storage service reports: A Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script. What observation best confirms the configuration now behaves correctly?

  1. The job retrieves the required device data without exposing secrets in the repository or task logs.
  2. The switch downloads its own authorized initial configuration and registers in the intended management inventory.
  3. The intended policy persists after controller synchronization and devices report consistent compliance.
  4. The target server profile references the expected boot and connectivity policies with no cross-tenant linkage.

Explanation

Correct Answer

A:

This observation validates powershell rest secure credentials: The automation credential is stored insecurely and grants broader privileges than the script requires. The corresponding corrective action is: Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. “Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity” would address that alternative cause, not the condition in this question: the automation credential is stored insecurely and grants broader privileges than the script requires.

C:

“Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow” responds to this separate finding: device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. This question instead needs “Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests”, so the alternative does not meet the stated condition.

D:

The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. “Use stable approved resource IDs and validate organization scope before assigning Intersight policies” applies to that separate problem. The observed case is a Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script; choosing this alternative would address the wrong failure mode.

Question 147

While checking a production data center change, the team finds: A blade replacement is delayed because the team assumes MAC addresses and server identities must remain bound to the failed physical blade. What technical condition most directly accounts for the failure?

  1. The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end.
  2. The vHBA WWPN allocation violates uniqueness requirements across server storage initiators.
  3. The server identity has not been abstracted through approved UCS service profile and identity-pool associations.
  4. The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target.

Explanation

Correct Answer

C:

The technical cause is The server identity has not been abstracted through approved UCS service profile and identity-pool associations. The appropriate response is: Associate the intended service profile and its identity pools with the supported replacement hardware. Confirm successful repair: The replacement blade receives the designated server identity and boots its workload according to policy.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the server identity has not been abstracted through approved UCS service profile and identity-pool associations.

B:

“Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration” responds to this separate finding: the vHBA WWPN allocation violates uniqueness requirements across server storage initiators. This question instead needs “Associate the intended service profile and its identity pools with the supported replacement hardware”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a blade replacement is delayed because the team assumes MAC addresses and server identities must remain bound to the failed physical blade; choosing this alternative would address the wrong failure mode.

Question 148

During a Cisco data center readiness review, engineers observe: A UCS X-Series chassis is onboarded with a legacy UCS Manager policy workflow that does not provide the supported Intersight-managed server configuration model. Which approved technology action addresses this incident most directly?

  1. Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies.
  2. Select a compatible validated firmware package and update the affected server policy under change control.
  3. Reconcile the claim code and target ownership through supported Intersight claiming and access procedures.
  4. Complete the required Intersight policies and deploy the server profile with validated resource assignments.

Explanation

Correct Answer

A:

The root problem is that The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. The selected change addresses it directly: Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies. Verify the outcome: The chassis and compute nodes are managed through the expected Intersight policy and profile model.

Incorrect Answers

B:

This action concerns ucs firmware policy package compatibility, where The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. The reported failure instead stems from The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture.

C:

This action concerns cisco intersight target claim ownership, where The Intersight device claim and account authorization do not match the approved administrative organization. The corrective response here is “Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies”; this alternative does not provide that response.

D:

This action concerns intersight server profile deployment consistency, where The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies. The stem reports a UCS X-Series chassis is onboarded with a legacy UCS Manager policy workflow that does not provide the supported Intersight-managed server configuration model; this control addresses a different failure condition.

Question 149

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. Which verification result most directly demonstrates successful repair?

  1. The iSCSI login authenticates successfully and the host discovers its authorized block LUN.
  2. The new host mounts the intended export while an unauthorized client remains denied.
  3. The host discovers an iSCSI target LUN and presents the expected block device to the hypervisor.
  4. The authorized target and host appear in the same intended VSAN and storage access succeeds.

Explanation

Correct Answer

A:

This observation validates iscsi chap target authentication: The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. The corresponding corrective action is: Update the approved initiator and target CHAP secret settings using the supported secure workflow. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The NFS export access rules do not authorize the requesting client address or security identity. “Update the scoped NFS export policy to include only the approved new hypervisor client addresses” 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:

“Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk” responds to this separate finding: the application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. This question instead needs “Update the approved initiator and target CHAP secret settings using the supported secure workflow”, so the alternative does not meet the stated condition.

D:

The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. “Assign the target port to the approved VSAN and verify its effective FCNS and zone membership” 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 150

During a Cisco data center readiness review, engineers observe: A data center team calls a privately operated dedicated cloud a public cloud merely because users reach it remotely through the Internet. Which operational guardrail would prevent a similar outage?

  1. Validate rendezvous-point redundancy and group mapping whenever multicast domains expand.
  2. Require a NIST model classification review during cloud migration architecture approvals.
  3. Confirm querier presence and snooping tables in every multicast-capable access VLAN.
  4. Document SPAN source and destination interface restrictions for troubleshooting changes.

Explanation

Correct Answer

B:

This safeguard addresses nist public private hybrid cloud models: Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. The appropriate prevention is: Require a NIST model classification review during cloud migration architecture approvals. 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: cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility.

C:

“Confirm querier presence and snooping tables in every multicast-capable access VLAN” responds to this separate finding: the VLAN lacks a reachable supported multicast querier. This question instead needs “Require a NIST model classification review during cloud migration architecture approvals”, so the alternative does not meet the stated condition.

D:

The SPAN session source and dedicated monitor destination roles were assigned incorrectly. “Document SPAN source and destination interface restrictions for troubleshooting changes” applies to that separate problem. The observed case is a data center team calls a privately operated dedicated cloud a public cloud merely because users reach it remotely through the Internet; choosing this alternative would address the wrong failure mode.