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 30

Question 290

While checking a production data center change, the team finds: A fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes. Which implementation action should the engineer take first?

  1. Configure the authorized SPAN source and monitor-only destination and confirm the capture appliance connection.
  2. Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics.
  3. Repair the approved flow exporter source, destination and transport route, and verify collector acceptance.
  4. Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms.

Explanation

Correct Answer

B:

The root problem is that The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. The selected change addresses it directly: Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics. Verify the outcome: The time-series reports expose the loss interval and correlate it with the affected interfaces and fabric paths.

Incorrect Answers

A:

This action concerns span source and destination isolation, where The SPAN session source and dedicated monitor destination roles were assigned incorrectly. The reported failure instead stems from The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events.

C:

This action concerns netflow exporter reachability, where Flow-export destination reachability or the configured source and monitoring VRF are incorrect. The corrective response here is “Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics”; this alternative does not provide that response.

D:

This action concerns vpc peer link consistency, where The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The stem reports a fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes; this control addresses a different failure condition.

Question 291

A data center implementation team investigates the following fault: A server NIC connects to an ACI leaf port, but the configured EPG never becomes operational on that port after the tenant was deployed. Which verification result most directly demonstrates successful repair?

  1. APIC reports the expected interface and EPG deployment, and authorized server traffic is forwarded.
  2. The collector receives valid sampled flow records with the expected device identity and timestamps.
  3. Unicast learning and authorized broadcast discovery work without traffic being replicated to unrelated VTEPs.
  4. After VM migration the endpoint belongs to the right EPG and retains its intended connectivity and contracts.

Explanation

Correct Answer

A:

This observation validates aci access policy interface selector binding: The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. The corresponding corrective action is: Correct the supported ACI interface policy selector and physical domain association for the host-facing port. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

Flow-export destination reachability or the configured source and monitoring VRF are incorrect. “Repair the approved flow exporter source, destination and transport route, and verify collector acceptance” would address that alternative cause, not the condition in this question: the interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.

C:

“Inspect the bridge-domain BUM replication method and configure only approved VTEP replication membership” responds to this separate finding: bUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model. This question instead needs “Correct the supported ACI interface policy selector and physical domain association for the host-facing port”, so the alternative does not meet the stated condition.

D:

The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. “Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment” applies to that separate problem. The observed case is a server NIC connects to an ACI leaf port, but the configured EPG never becomes operational on that port after the tenant was deployed; choosing this alternative would address the wrong failure mode.

Question 292

A Nexus, UCS or MDS operations team encounters this issue: An Intersight-managed UCS X blade receives a server profile but fails its deployment because mandatory network and storage policy references are missing. Which design or configuration error caused the described issue?

  1. The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints.
  2. The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture.
  3. The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies.
  4. The Intersight device claim and account authorization do not match the approved administrative organization.

Explanation

Correct Answer

C:

The technical cause is The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies. The appropriate response is: Complete the required Intersight policies and deploy the server profile with validated resource assignments. Confirm successful repair: The profile deploys without unresolved policy references and the server boots with intended connections.

Incorrect Answers

A:

The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. “Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria” would address that alternative cause, not the condition in this question: the Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies.

B:

“Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies” responds to this separate finding: the platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. This question instead needs “Complete the required Intersight policies and deploy the server profile with validated resource assignments”, so the alternative does not meet the stated condition.

D:

The Intersight device claim and account authorization do not match the approved administrative organization. “Reconcile the claim code and target ownership through supported Intersight claiming and access procedures” applies to that separate problem. The observed case is an Intersight-managed UCS X blade receives a server profile but fails its deployment because mandatory network and storage policy references are missing; choosing this alternative would address the wrong failure mode.

Question 293

A Nexus, UCS or MDS operations team encounters this issue: A UCS service profile contains the correct vNIC VLAN, but the upstream fabric interconnect uplink does not carry the server's new application VLAN. What is the most appropriate remediation for these symptoms?

  1. Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend.
  2. Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior.
  3. Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access.
  4. Use an approved updating service profile template and apply governed changes to its associated server profiles.

Explanation

Correct Answer

C:

The root problem is that The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. The selected change addresses it directly: Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access. Verify the outcome: The guest and external hosts exchange traffic over the authorized VLAN on both supported fabric paths.

Incorrect Answers

A:

This action concerns intersight hardware telemetry alarm review, where The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. The reported failure instead stems from The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy.

B:

This action concerns ucs chassis iom fabric path redundancy, where The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. The corrective response here is “Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access”; this alternative does not provide that response.

D:

This action concerns ucs updating service profile templates, where The configuration process bypasses the intended reusable UCS service profile template inheritance model. The stem reports a UCS service profile contains the correct vNIC VLAN, but the upstream fabric interconnect uplink does not carry the server's new application VLAN; this control addresses a different failure condition.

Question 294

A newly commissioned network, compute or storage service reports: A UCS domain loses management when its primary fabric interconnect is rebooted even though the secondary interconnect is operational. What observation best confirms the configuration now behaves correctly?

  1. The replacement blade receives the designated server identity and boots its workload according to policy.
  2. Authorized operators can open CIMC over the management path without exposing it on the application data plane.
  3. The secondary fabric interconnect takes over management duties without losing the approved domain configuration.
  4. Both intended fabric paths enumerate the chassis and associated blades under UCS management.

Explanation

Correct Answer

C:

This observation validates ucs fabric interconnect management failover: The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior. The corresponding corrective action is: Repair the UCS fabric-interconnect cluster and management redundancy configuration and validate supported failover. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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

B:

“Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network” responds to this separate finding: the CIMC management interface has incorrect IP addressing or missing management default gateway reachability. 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 295

During a Cisco data center readiness review, engineers observe: A new access switch unexpectedly becomes the spanning-tree root and traffic now follows a slow backup inter-switch link across the data center. What observation best confirms the configuration now behaves correctly?

  1. The two routers establish an OSPFv3 Full adjacency and learn the expected IPv6 prefixes.
  2. The server remains reachable during documented peer and peer-link failure tests without unsafe duplicate forwarding.
  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

C:

This observation validates rstp root bridge placement: Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. The corresponding corrective action is: Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology. Evidence about a different component does not establish the requested service outcome.

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: bridge priority design does not select the intended distribution switches as the RSTP root and secondary root.

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 “Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology”, so the alternative does not meet the stated condition.

D:

The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. “Configure a matching supported LACP mode and port-channel membership across the two endpoints” applies to that separate problem. The observed case is a new access switch unexpectedly becomes the spanning-tree root and traffic now follows a slow backup inter-switch link across the data center; choosing this alternative would address the wrong failure mode.

Question 296

A newly commissioned network, compute or storage service reports: A storage performance incident cannot be diagnosed because a copied FC traffic capture is configured to mirror an unrelated VSAN port instead of the affected ISL. What is the primary technical reason the deployment fails?

  1. Device alias changes have not been committed and distributed through the supported fabric database workflow.
  2. The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image.
  3. The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends.
  4. The Fibre Channel SPAN session source does not identify the failing interface or service path.

Explanation

Correct Answer

D:

The technical cause is The Fibre Channel SPAN session source does not identify the failing interface or service path. The appropriate response is: Set a supported FC SPAN monitor source for the affected port and the approved capture destination. Confirm successful repair: The SAN analyzer receives the relevant FC exchanges needed to isolate the transport fault.

Incorrect Answers

A:

Device alias changes have not been committed and distributed through the supported fabric database workflow. “Commit the approved device alias database transaction and verify resolution across the affected switches” would address that alternative cause, not the condition in this question: the Fibre Channel SPAN session source does not identify the failing interface or service path.

B:

“Review the applicable MDS EPLD package and schedule the correct supported component update” responds to this separate finding: the storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. This question instead needs “Set a supported FC SPAN monitor source for the affected port and the approved capture destination”, so the alternative does not meet the stated condition.

C:

The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. “Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis” applies to that separate problem. The observed case is a storage performance incident cannot be diagnosed because a copied FC traffic capture is configured to mirror an unrelated VSAN port instead of the affected ISL; choosing this alternative would address the wrong failure mode.

Question 297

A data center administrator identifies the following risk: An infrastructure automation identity can edit server policies in several unrelated Intersight organizations even though it supports just one business unit. Which root cause best explains this behavior?

  1. Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection.
  2. The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path.
  3. The Intersight role assignment is not scoped to the authorized organization and permitted resource actions.
  4. The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities.

Explanation

Correct Answer

C:

The technical cause is The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. The appropriate response is: Apply the approved organization-scoped Intersight RBAC role for the automation identity. Confirm successful repair: The identity updates permitted server profiles in its organization and receives denials elsewhere.

Incorrect Answers

A:

Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. “Configure supported MACsec policy and secure key agreement on both authorized switch endpoints” would address that alternative cause, not the condition in this question: the Intersight role assignment is not scoped to the authorized organization and permitted resource actions.

B:

“Correct the supported UCS authentication realm order and emergency access procedure under change control” responds to this separate finding: the UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. This question instead needs “Apply the approved organization-scoped Intersight RBAC role for the automation identity”, so the alternative does not meet the stated condition.

D:

The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. “Assign a supported restricted UCS role and scope matching the storage administration tasks” applies to that separate problem. The observed case is an infrastructure automation identity can edit server policies in several unrelated Intersight organizations even though it supports just one business unit; choosing this alternative would address the wrong failure mode.

Question 298

A data center administrator identifies the following risk: A UCS-adjacent SAN access switch configured for NPV cannot perform independent fabric services, but engineers expect it to act as the fabric principal switch. What is the most appropriate remediation for these symptoms?

  1. Update the approved initiator and target CHAP secret settings using the supported secure workflow.
  2. Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path.
  3. Move the backup server connection into the approved dedicated VSAN and update authorized zoning.
  4. Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design.

Explanation

Correct Answer

D:

The root problem is that NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. The selected change addresses it directly: Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design. Verify the outcome: The upstream switch sees proxied initiator logins and the access device no longer relies on principal-switch services.

Incorrect Answers

A:

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 NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch.

B:

This action concerns fibre channel over ethernet storage vlan mapping, where The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. The corrective response here is “Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design”; this alternative does not provide that response.

C:

This action concerns fibre channel vsan traffic isolation, where VSAN membership is incorrectly shared between isolation domains with different storage access requirements. The stem reports a UCS-adjacent SAN access switch configured for NPV cannot perform independent fabric services, but engineers expect it to act as the fabric principal switch; this control addresses a different failure condition.

Question 299

A Nexus, UCS or MDS operations team encounters this issue: A new MDS F-port physically connects to a storage target but remains in the default VSAN while its allowed initiator is in a separate production VSAN. Which root cause best explains this behavior?

  1. The NFS export access rules do not authorize the requesting client address or security identity.
  2. VSAN membership is incorrectly shared between isolation domains with different storage access requirements.
  3. NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch.
  4. The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset.

Explanation

Correct Answer

D:

The technical cause is The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. The appropriate response is: Assign the target port to the approved VSAN and verify its effective FCNS and zone membership. Confirm successful repair: The authorized target and host appear in the same intended VSAN and storage access succeeds.

Incorrect Answers

A:

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 target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset.

B:

“Move the backup server connection into the approved dedicated VSAN and update authorized zoning” responds to this separate finding: vSAN membership is incorrectly shared between isolation domains with different storage access requirements. This question instead needs “Assign the target port to the approved VSAN and verify its effective FCNS and zone membership”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a new MDS F-port physically connects to a storage target but remains in the default VSAN while its allowed initiator is in a separate production VSAN; choosing this alternative would address the wrong failure mode.

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.