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 31

Question 300

A newly commissioned network, compute or storage service reports: An NX-OS switch loses a critical BGP peer, but an automated EEM diagnostic applet never runs because it listens for a different syslog message pattern. Which implementation action should the engineer take first?

  1. Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event.
  2. Send the supported NX-API request in the correct JSON or XML representation with matching headers.
  3. Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures.
  4. Deploy the script in the approved supported shell environment with required dependencies and bounded permissions.

Explanation

Correct Answer

A:

The root problem is that The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. The selected change addresses it directly: Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event. Verify the outcome: The applet runs only on the targeted peer-down event and preserves the expected diagnostic information.

Incorrect Answers

B:

This action concerns nx api json content encoding, where The NX-API request body and declared content format are inconsistent for the selected endpoint. The reported failure instead stems from The embedded event manager event detector does not match the actual authorized BGP neighbor-down message.

C:

This action concerns rest api authorization status handling, where The REST client does not distinguish insufficient authorization from retryable transport or server errors. The corrective response here is “Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event”; this alternative does not provide that response.

D:

This action concerns nexus bash shell and guest shell isolation, where The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The stem reports an NX-OS switch loses a critical BGP peer, but an automated EEM diagnostic applet never runs because it listens for a different syslog message pattern; this control addresses a different failure condition.

Question 301

A data center implementation team investigates the following fault: A UCS domain loses management when its primary fabric interconnect is rebooted even though the secondary interconnect is operational. Which root cause best explains this behavior?

  1. The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior.
  2. The server pool qualification policy does not limit placement to servers with the required hardware capabilities.
  3. The configured boot-device order does not select the intended SAN boot path before local storage.
  4. The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured.

Explanation

Correct Answer

A:

The technical cause is The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior. The appropriate response is: Repair the UCS fabric-interconnect cluster and management redundancy configuration and validate supported failover. Confirm successful repair: The secondary fabric interconnect takes over management duties without losing the approved domain configuration.

Incorrect Answers

B:

The server pool qualification policy does not limit placement to servers with the required hardware capabilities. “Create the supported UCS server pool qualification and associate the workload profile with eligible members” would address that alternative cause, not the condition in this question: the clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior.

C:

“Restore the supported boot policy and required SAN adapter path in the correct boot-device order” responds to this separate finding: the configured boot-device order does not select the intended SAN boot path before local storage. This question instead needs “Repair the UCS fabric-interconnect cluster and management redundancy configuration and validate supported failover”, so the alternative does not meet the stated condition.

D:

The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. “Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis” applies to that separate problem. The observed case is a UCS domain loses management when its primary fabric interconnect is rebooted even though the secondary interconnect is operational; choosing this alternative would address the wrong failure mode.

Question 302

While checking a production data center change, the team finds: An HBA completes fabric login but the intended target WWPN cannot be discovered because the target never registers with the Fibre Channel name server. Which operational guardrail would prevent a similar outage?

  1. Use capture scope and SAN data sensitivity review before activating port mirroring.
  2. Include FCNS database and target registration checks before troubleshooting zoning alone.
  3. Verify pending and committed device alias state whenever server HBA identities change.
  4. Check active zoneset state and distribution after all SAN access change approvals.

Explanation

Correct Answer

B:

This safeguard addresses fibre channel name server registration: The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. The appropriate prevention is: Include FCNS database and target registration checks before troubleshooting zoning alone. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The Fibre Channel SPAN session source does not identify the failing interface or service path. “Use capture scope and SAN data sensitivity review before activating port mirroring” would address that alternative cause, not the condition in this question: the target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded.

C:

“Verify pending and committed device alias state whenever server HBA identities change” responds to this separate finding: device alias changes have not been committed and distributed through the supported fabric database workflow. This question instead needs “Include FCNS database and target registration checks before troubleshooting zoning alone”, so the alternative does not meet the stated condition.

D:

An inactive zoning database edit does not change the effective active zoneset on the SAN fabric. “Check active zoneset state and distribution after all SAN access change approvals” applies to that separate problem. The observed case is an HBA completes fabric login but the intended target WWPN cannot be discovered because the target never registers with the Fibre Channel name server; choosing this alternative would address the wrong failure mode.

Question 303

A Nexus, UCS or MDS operations team encounters this issue: A Cisco Nexus switch locally observes abnormal traffic, but the monitoring platform receives no NetFlow records after the exporter destination was moved. Which root cause best explains this behavior?

  1. The SPAN session source and dedicated monitor destination roles were assigned incorrectly.
  2. Flow-export destination reachability or the configured source and monitoring VRF are incorrect.
  3. The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events.
  4. The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.

Explanation

Correct Answer

B:

The technical cause is Flow-export destination reachability or the configured source and monitoring VRF are incorrect. The appropriate response is: Repair the approved flow exporter source, destination and transport route, and verify collector acceptance. Confirm successful repair: The collector receives valid sampled flow records with the expected device identity and timestamps.

Incorrect Answers

A:

The SPAN session source and dedicated monitor destination roles were assigned incorrectly. “Configure the authorized SPAN source and monitor-only destination and confirm the capture appliance connection” would address that alternative cause, not the condition in this question: flow-export destination reachability or the configured source and monitoring VRF are incorrect.

C:

“Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics” responds to this separate finding: the monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. This question instead needs “Repair the approved flow exporter source, destination and transport route, and verify collector acceptance”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a Cisco Nexus switch locally observes abnormal traffic, but the monitoring platform receives no NetFlow records after the exporter destination was moved; choosing this alternative would address the wrong failure mode.

Question 304

A newly commissioned network, compute or storage service reports: A two-member uplink from a server-facing switch carries traffic on only one physical member because one end was configured for a static bundle. What technical condition most directly accounts for the failure?

  1. The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.
  2. The failure design does not account for orphan-port behavior and the chosen peer recovery semantics.
  3. The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members.
  4. The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.

Explanation

Correct Answer

C:

The technical cause is The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. The appropriate response is: Configure a matching supported LACP mode and port-channel membership across the two endpoints. Confirm successful repair: Both intended interfaces are bundled and load-balanced without individual or suspended member state.

Incorrect Answers

A:

The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. “Correct the supported ACI interface policy selector and physical domain association for the host-facing port” would address that alternative cause, not the condition in this question: the port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members.

B:

“Review supported orphan-port handling and move or protect the workload on the planned resilient attachment” responds to this separate finding: the failure design does not account for orphan-port behavior and the chosen peer recovery semantics. This question instead needs “Configure a matching supported LACP mode and port-channel membership across the two endpoints”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a two-member uplink from a server-facing switch carries traffic on only one physical member because one end was configured for a static bundle; choosing this alternative would address the wrong failure mode.

Question 305

A newly commissioned network, compute or storage service reports: Voice-processing virtual machines on UCS blades traverse a shared adapter, but their traffic is treated as best effort because the UCS class settings do not match the approved policy. What technical condition most directly accounts for the failure?

  1. The server pool qualification policy does not limit placement to servers with the required hardware capabilities.
  2. The configuration process bypasses the intended reusable UCS service profile template inheritance model.
  3. UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements.
  4. The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths.

Explanation

Correct Answer

C:

The technical cause is UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements. The appropriate response is: Correct the supported UCS class-of-service and network QoS policy for the intended application traffic. Confirm successful repair: Authorized real-time flows receive the designated priority treatment and bulk traffic retains its separate class.

Incorrect Answers

A:

The server pool qualification policy does not limit placement to servers with the required hardware capabilities. “Create the supported UCS server pool qualification and associate the workload profile with eligible members” would address that alternative cause, not the condition in this question: uCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements.

B:

“Use an approved updating service profile template and apply governed changes to its associated server profiles” responds to this separate finding: the configuration process bypasses the intended reusable UCS service profile template inheritance model. This question instead needs “Correct the supported UCS class-of-service and network QoS policy for the intended application traffic”, so the alternative does not meet the stated condition.

D:

The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. “Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior” applies to that separate problem. The observed case is voice-processing virtual machines on UCS blades traverse a shared adapter, but their traffic is treated as best effort because the UCS class settings do not match the approved policy; choosing this alternative would address the wrong failure mode.

Question 306

During a Cisco data center readiness review, engineers observe: A running production blade is reassigned to a different UCS service profile without understanding reboot or identity-change consequences, interrupting applications. What observation best confirms the configuration now behaves correctly?

  1. All attached eligible blades receive consistent policy changes with documented exceptions and maintenance impact.
  2. Intersight records the hardware fault and resolution, while workload stability returns after repair.
  3. The server recognizes the protected boot volume and tolerates the documented single-disk test condition.
  4. The blade receives the intended policy identity after the controlled operation and applications recover as planned.

Explanation

Correct Answer

D:

This observation validates ucs service profile association maintenance: The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings. The corresponding corrective action is: Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The configuration process bypasses the intended reusable UCS service profile template inheritance model. “Use an approved updating service profile template and apply governed changes to its associated server profiles” would address that alternative cause, not the condition in this question: the service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings.

B:

“Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend” responds to this separate finding: the monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. This question instead needs “Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a running production blade is reassigned to a different UCS service profile without understanding reboot or identity-change consequences, interrupting applications; choosing this alternative would address the wrong failure mode.

Question 307

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

  1. Intersight records the hardware fault and resolution, while workload stability returns after repair.
  2. The chassis and compute nodes are managed through the expected Intersight policy and profile model.
  3. The server appears as a manageable authorized target in the correct Intersight organization.
  4. The profile deploys without unresolved policy references and the server boots with intended connections.

Explanation

Correct Answer

B:

This observation validates ucs x series intersight managed mode: The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. The corresponding corrective action is: Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. “Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend” would address that alternative cause, not the condition in this question: the platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture.

C:

“Reconcile the claim code and target ownership through supported Intersight claiming and access procedures” responds to this separate finding: the Intersight device claim and account authorization do not match the approved administrative organization. This question instead needs “Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies”, 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. “Complete the required Intersight policies and deploy the server profile with validated resource assignments” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 308

A Nexus, UCS or MDS operations team encounters this issue: A remote tenant workload is connected to a leaf, yet peer VTEPs never learn the workload MAC address from the EVPN control plane. What preventive control would best avoid repeating this fault?

  1. Require a NIST model classification review during cloud migration architecture approvals.
  2. Monitor endpoint advertisement and withdrawal during workload migration and policy updates.
  3. Review tenant L3VNI and route-target controls when adding external routed service networks.
  4. Test VTEP source reachability as a prerequisite for every fabric underlay policy change.

Explanation

Correct Answer

B:

This safeguard addresses evpn mac reachability type two routes: The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. The appropriate prevention is: Monitor endpoint advertisement and withdrawal during workload migration and policy updates. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. “Require a NIST model classification review during cloud migration architecture approvals” would address that alternative cause, not the condition in this question: the Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy.

C:

“Review tenant L3VNI and route-target controls when adding external routed service networks” 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 “Monitor endpoint advertisement and withdrawal during workload migration and policy updates”, 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. “Test VTEP source reachability as a prerequisite for every fabric underlay policy change” applies to that separate problem. The observed case is a remote tenant workload is connected to a leaf, yet peer VTEPs never learn the workload MAC address from the EVPN control plane; choosing this alternative would address the wrong failure mode.

Question 309

During a Cisco data center readiness review, engineers observe: An unauthorized Fibre Channel switch is connected to a production MDS ISL and attempts to join the fabric without meeting the planned trusted-switch membership. What technical condition most directly accounts for the failure?

  1. The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring.
  2. Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.
  3. The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs.
  4. Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL.

Explanation

Correct Answer

D:

The technical cause is Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. The appropriate response is: Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs. Confirm successful repair: The approved peer switch joins the SAN while a nonapproved test switch is denied fabric access.

Incorrect Answers

A:

The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. “Correct the authorized TACACS command or role mapping without granting full switch administrator permissions” would address that alternative cause, not the condition in this question: fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL.

B:

“Configure supported MDS port-security bindings for the intended server initiator and affected VSAN” responds to this separate finding: fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. This question instead needs “Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs”, so the alternative does not meet the stated condition.

C:

The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. “Replace the overly broad MDS role with an approved read-only or scoped monitoring role” applies to that separate problem. The observed case is an unauthorized Fibre Channel switch is connected to a production MDS ISL and attempts to join the fabric without meeting the planned trusted-switch membership; choosing this alternative would address the wrong failure mode.

Question 310

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. Which approved technology action addresses this incident most directly?

  1. Review supported EPLD package requirements and schedule the component update using the prescribed procedure.
  2. Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies.
  3. Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves.
  4. Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF.

Explanation

Correct Answer

C:

The root problem is that The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The selected change addresses it directly: Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves. Verify the outcome: Hosts in the authorized segment communicate across leaves while unrelated tenant segments remain separate.

Incorrect Answers

A:

This action concerns nexus epld upgrade safety, where The planned software transition omits the EPLD compatibility and operational impact assessment. The reported failure instead stems from The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs.

B:

This action concerns vxlan vtep loopback reachability, where The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. The corrective response here is “Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves”; this alternative does not provide that response.

D:

This action concerns evpn ip prefix type five advertisement, where The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. The stem reports two VXLAN leaf switches serve the same tenant bridge domain but forward frames to different VXLAN network identifiers due to mismatched local mappings; this control addresses a different failure condition.