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 1

Question 1

During a Cisco data center readiness review, engineers observe: The team activates an I/O module and fabric-interconnect firmware change simultaneously without scheduling expected service impact for dependent blades. Which operational guardrail would prevent a similar outage?

  1. Schedule encrypted UCS configuration backups and perform periodic isolated restore tests.
  2. Maintain service profile templates and identity pools independent of individual server serial numbers.
  3. Check platform and adapter compatibility matrices before changing UCS host firmware policies.
  4. Pilot the firmware sequence and test fabric redundancy before simultaneous domain-wide activation.

Explanation

Correct Answer

D:

This safeguard addresses ucs disruptive firmware activation planning: The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. The appropriate prevention is: Pilot the firmware sequence and test fabric redundancy before simultaneous domain-wide activation. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. “Schedule encrypted UCS configuration backups and perform periodic isolated restore tests” would address that alternative cause, not the condition in this question: the upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints.

B:

“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 “Pilot the firmware sequence and test fabric redundancy before simultaneous domain-wide activation”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is the team activates an I/O module and fabric-interconnect firmware change simultaneously without scheduling expected service impact for dependent blades; choosing this alternative would address the wrong failure mode.

Question 2

A Nexus, UCS or MDS operations team encounters this issue: An AI training fabric uses RoCEv2 GPU collective traffic, but bursts are repeatedly dropped because the Ethernet switches lack the supported priority flow-control and congestion management plan. Which test outcome proves the intended service was restored?

  1. The approved plan makes intended changes and leaves unrelated network resources intact.
  2. A permitted API call succeeds while denied operations report a clear nonretryable authorization error.
  3. Collective workload tests meet the required throughput and latency targets without sustained link oversubscription.
  4. The GPU fabric sustains the benchmark workload with controlled loss and congestion indicators during bursts.

Explanation

Correct Answer

D:

This observation validates ai roce lossless class design: The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. The corresponding corrective action is: Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. “Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources” would address that alternative cause, not the condition in this question: the RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards.

B:

“Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures” responds to this separate finding: the REST client does not distinguish insufficient authorization from retryable transport or server errors. This question instead needs “Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path”, so the alternative does not meet the stated condition.

C:

The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload. “Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology” applies to that separate problem. The observed case is an AI training fabric uses RoCEv2 GPU collective traffic, but bursts are repeatedly dropped because the Ethernet switches lack the supported priority flow-control and congestion management plan; choosing this alternative would address the wrong failure mode.

Question 3

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 observation best confirms the configuration now behaves correctly?

  1. All required vNICs receive unique authorized MAC addresses without conflicting with existing profiles.
  2. The server HBA registers in the correct VSAN and discovers the authorized target storage port.
  3. The replacement blade receives the designated server identity and boots its workload according to policy.
  4. Both servers log in with their own WWPN identities and see only their authorized storage paths.

Explanation

Correct Answer

C:

This observation validates ucs service profile server identity: The server identity has not been abstracted through approved UCS service profile and identity-pool associations. The corresponding corrective action is: Associate the intended service profile and its identity pools with the supported replacement hardware. 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 server identity has not been abstracted through approved UCS service profile and identity-pool associations.

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 “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 vHBA WWPN allocation violates uniqueness requirements across server storage initiators. “Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration” 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 4

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

  1. Test VTEP source reachability as a prerequisite for every fabric underlay policy change.
  2. Review tenant L3VNI and route-target controls when adding external routed service networks.
  3. Monitor endpoint advertisement and withdrawal during workload migration and policy updates.
  4. Maintain a controlled VNI allocation register and validate mappings before extending tenant VLANs.

Explanation

Correct Answer

D:

This safeguard addresses vxlan vlan vni mapping consistency: The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The appropriate prevention is: Maintain a controlled VNI allocation register and validate mappings before extending tenant VLANs. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

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

“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 “Maintain a controlled VNI allocation register and validate mappings before extending tenant VLANs”, so the alternative does not meet the stated condition.

C:

The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. “Monitor endpoint advertisement and withdrawal during workload migration and policy updates” 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 5

While checking a production data center change, the team finds: A regulated east-west inter-switch link must protect Ethernet frames in transit, but an approved MACsec session is absent even though the physical port is up. Which approved technology action addresses this incident most directly?

  1. Configure supported MACsec policy and secure key agreement on both authorized switch endpoints.
  2. Coordinate the supported authentication keychain parameters and overlapping key transition periods.
  3. Apply the approved organization-scoped Intersight RBAC role for the automation identity.
  4. Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports.

Explanation

Correct Answer

A:

The root problem is that Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. The selected change addresses it directly: Configure supported MACsec policy and secure key agreement on both authorized switch endpoints. Verify the outcome: The link shows an operational encrypted MACsec association and permitted traffic continues normally.

Incorrect Answers

B:

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 Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection.

C:

This action concerns intersight organization scoped administrative role, where The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. The corrective response here is “Configure supported MACsec policy and secure key agreement on both authorized switch endpoints”; this alternative does not provide that response.

D:

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 stem reports a regulated east-west inter-switch link must protect Ethernet frames in transit, but an approved MACsec session is absent even though the physical port is up; this control addresses a different failure condition.

Question 6

During a Cisco data center readiness review, engineers observe: A service profile template should deploy only to blades with a required adapter model, but a broad server pool includes incompatible hardware. Which deployment safeguard most directly reduces this failure risk?

  1. Reconcile UCS VLAN definitions with upstream trunk allow-lists during every server network expansion.
  2. Update UCS server pool qualifications as new hardware revisions enter the chassis.
  3. Inspect chassis IOM inventory and dual-fabric paths during blade server deployment.
  4. Test UCS QoS policies with the upstream switching trust boundary after adapter-policy changes.

Explanation

Correct Answer

B:

This safeguard addresses ucs server pool qualification matching: The server pool qualification policy does not limit placement to servers with the required hardware capabilities. The appropriate prevention is: Update UCS server pool qualifications as new hardware revisions enter the chassis. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. “Reconcile UCS VLAN definitions with upstream trunk allow-lists during every server network expansion” would address that alternative cause, not the condition in this question: the server pool qualification policy does not limit placement to servers with the required hardware capabilities.

C:

“Inspect chassis IOM inventory and dual-fabric paths during blade server deployment” responds to this separate finding: the chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. This question instead needs “Update UCS server pool qualifications as new hardware revisions enter the chassis”, 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. “Test UCS QoS policies with the upstream switching trust boundary after adapter-policy changes” applies to that separate problem. The observed case is a service profile template should deploy only to blades with a required adapter model, but a broad server pool includes incompatible hardware; choosing this alternative would address the wrong failure mode.

Question 7

A data center implementation team investigates the following fault: An Ansible playbook meant for lab Nexus switches changes production switch banners because its inventory group variables include production hosts inadvertently. Which design or configuration error caused the described issue?

  1. The playbook target inventory and variable precedence do not isolate the intended lab device group.
  2. The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards.
  3. The embedded event manager event detector does not match the actual authorized BGP neighbor-down message.
  4. The parser lacks schema validation and robust handling of absent or differently typed telemetry values.

Explanation

Correct Answer

A:

The technical cause is The playbook target inventory and variable precedence do not isolate the intended lab device group. The appropriate response is: Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution. Confirm successful repair: Only the designated lab devices receive changes and production targets remain unchanged.

Incorrect Answers

B:

The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. “Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path” would address that alternative cause, not the condition in this question: the playbook target inventory and variable precedence do not isolate the intended lab device group.

C:

“Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event” responds to this separate finding: the embedded event manager event detector does not match the actual authorized BGP neighbor-down message. This question instead needs “Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution”, so the alternative does not meet the stated condition.

D:

The parser lacks schema validation and robust handling of absent or differently typed telemetry values. “Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics” applies to that separate problem. The observed case is an Ansible playbook meant for lab Nexus switches changes production switch banners because its inventory group variables include production hosts inadvertently; choosing this alternative would address the wrong failure mode.

Question 8

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

  1. The server remains reachable during documented peer and peer-link failure tests without unsafe duplicate forwarding.
  2. The host VLAN remains reachable through either peer after a simulated downstream member failure.
  3. The designated aggregation switch is the root and the expected alternate links remain loop-free.
  4. Both intended interfaces are bundled and load-balanced without individual or suspended member state.

Explanation

Correct Answer

D:

This observation validates lacp port channel negotiation: The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. The corresponding corrective action is: Configure a matching supported LACP mode and port-channel membership across the two endpoints. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The failure design does not account for orphan-port behavior and the chosen peer recovery semantics. “Review supported orphan-port handling and move or protect the workload on the planned resilient attachment” 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:

“Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms” responds to this separate finding: the vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. 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.

C:

Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. “Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology” 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 9

A Nexus, UCS or MDS operations team encounters this issue: Two distribution switches provide HSRP default gateways, but the active switch continues answering for the virtual gateway after losing its only upstream path. Which root cause best explains this behavior?

  1. The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts.
  2. The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link.
  3. The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability.
  4. The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably.

Explanation

Correct Answer

B:

The technical cause is The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. The appropriate response is: Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role. Confirm successful repair: After an uplink failure, the standby switch becomes active and application traffic uses its available upstream path.

Incorrect Answers

A:

The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. “Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation” would address that alternative cause, not the condition in this question: the first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link.

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 supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role”, 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 two distribution switches provide HSRP default gateways, but the active switch continues answering for the virtual gateway after losing its only upstream path; choosing this alternative would address the wrong failure mode.

Question 10

A newly commissioned network, compute or storage service reports: A fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes. What technical condition most directly accounts for the failure?

  1. The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events.
  2. The SPAN session source and dedicated monitor destination roles were assigned incorrectly.
  3. Flow-export destination reachability or the configured source and monitoring VRF are incorrect.
  4. The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs.

Explanation

Correct Answer

A:

The technical cause is The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. The appropriate response is: Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics. Confirm successful repair: The time-series reports expose the loss interval and correlate it with the affected interfaces and fabric paths.

Incorrect Answers

B:

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: the monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events.

C:

“Repair the approved flow exporter source, destination and transport route, and verify collector acceptance” responds to this separate finding: flow-export destination reachability or the configured source and monitoring VRF are incorrect. This question instead needs “Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics”, 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 a fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes; choosing this alternative would address the wrong failure mode.