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 26

Question 250

A data center implementation team investigates the following fault: Two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list. Which test outcome proves the intended service was restored?

  1. The analyzer receives copied packets from the target flow without becoming part of normal switching paths.
  2. Both intended interfaces are bundled and load-balanced without individual or suspended member state.
  3. The host VLAN remains reachable through either peer after a simulated downstream member failure.
  4. The designated aggregation switch is the root and the expected alternate links remain loop-free.

Explanation

Correct Answer

C:

This observation validates vpc peer link consistency: The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The corresponding corrective action is: Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms. Evidence about a different component does not establish the requested service outcome.

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: the vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.

B:

“Configure a matching supported LACP mode and port-channel membership across the two endpoints” responds to this separate finding: the port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. This question instead needs “Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms”, so the alternative does not meet the stated condition.

D:

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 two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list; choosing this alternative would address the wrong failure mode.

Question 251

While checking a production data center change, the team finds: A multi-site fabric policy is changed separately on individual Nexus devices while Nexus Dashboard's centrally managed intent remains unchanged and later overwrites the manual edits. What observation best confirms the configuration now behaves correctly?

  1. The intended policy persists after controller synchronization and devices report consistent compliance.
  2. The job retrieves the required device data without exposing secrets in the repository or task logs.
  3. The applet runs only on the targeted peer-down event and preserves the expected diagnostic information.
  4. The target server profile references the expected boot and connectivity policies with no cross-tenant linkage.

Explanation

Correct Answer

A:

This observation validates nexus dashboard intent orchestration consistency: Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. The corresponding corrective action is: Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The automation credential is stored insecurely and grants broader privileges than the script requires. “Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests” would address that alternative cause, not the condition in this question: device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model.

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 “Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow”, 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 multi-site fabric policy is changed separately on individual Nexus devices while Nexus Dashboard's centrally managed intent remains unchanged and later overwrites the manual edits; choosing this alternative would address the wrong failure mode.

Question 252

While checking a production data center change, the team finds: Two Cisco MDS Fibre Channel switches are merged into one fabric, but an ISL becomes segmented because both switches use the same configured domain ID. What technical condition most directly accounts for the failure?

  1. The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites.
  2. The initiator has not completed successful fabric login and thus has no authorized FCID assignment.
  3. The FC port channel and prospective member disagree on required operational attributes for bundling.
  4. The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization.

Explanation

Correct Answer

D:

The technical cause is The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. The appropriate response is: Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process. Confirm successful repair: Both switches participate in one stable fabric with unique domain IDs and expected FSPF reachability.

Incorrect Answers

A:

The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. “Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method” would address that alternative cause, not the condition in this question: the Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization.

B:

“Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator” responds to this separate finding: the initiator has not completed successful fabric login and thus has no authorized FCID assignment. This question instead needs “Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process”, so the alternative does not meet the stated condition.

C:

The FC port channel and prospective member disagree on required operational attributes for bundling. “Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member” applies to that separate problem. The observed case is two Cisco MDS Fibre Channel switches are merged into one fabric, but an ISL becomes segmented because both switches use the same configured domain ID; choosing this alternative would address the wrong failure mode.

Question 253

A data center implementation team investigates the following fault: A new VXLAN segment experiences unnecessary broadcast amplification when unknown unicast and multicast frames are flooded broadly without validating overlay replication. Which verification result most directly demonstrates successful repair?

  1. The two routers establish an OSPFv3 Full adjacency and learn the expected IPv6 prefixes.
  2. APIC shows the assigned leaf as an active fabric member with the expected spine adjacency.
  3. After VM migration the endpoint belongs to the right EPG and retains its intended connectivity and contracts.
  4. Unicast learning and authorized broadcast discovery work without traffic being replicated to unrelated VTEPs.

Explanation

Correct Answer

D:

This observation validates broadcast unknown unicast multicast replication: BUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model. The corresponding corrective action is: Inspect the bridge-domain BUM replication method and configure only approved VTEP replication membership. 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: bUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model.

B:

“Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC” responds to this separate finding: the leaf has not completed the supported ACI fabric discovery and node-registration workflow. This question instead needs “Inspect the bridge-domain BUM replication method and configure only approved VTEP replication membership”, so the alternative does not meet the stated condition.

C:

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 new VXLAN segment experiences unnecessary broadcast amplification when unknown unicast and multicast frames are flooded broadly without validating overlay replication; choosing this alternative would address the wrong failure mode.

Question 254

A data center implementation team investigates the following fault: 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. Which test outcome proves the intended service was restored?

  1. The approved HBA logs in while a test unapproved WWPN is rejected by the protected fabric port.
  2. The approved peer switch joins the SAN while a nonapproved test switch is denied fabric access.
  3. The link shows an operational encrypted MACsec association and permitted traffic continues normally.
  4. The analyst inspects FCNS and port health but cannot activate or change production zonesets.

Explanation

Correct Answer

B:

This observation validates mds fibre channel fabric binding: Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. The corresponding corrective action is: Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. “Configure supported MDS port-security bindings for the intended server initiator and affected VSAN” 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.

C:

“Configure supported MACsec policy and secure key agreement on both authorized switch endpoints” responds to this separate finding: link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. 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.

D:

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 255

During a Cisco data center readiness review, engineers observe: Multicast receivers connected to a routed leaf cannot join a source in another segment after a PIM sparse-mode domain is extended to a new pod. Which operational guardrail would prevent a similar outage?

  1. Audit IPv6 routing area design and neighbor status during dual-stack network changes.
  2. Validate rendezvous-point redundancy and group mapping whenever multicast domains expand.
  3. Test upstream failure, HSRP role transitions, and gateway reachability during each redundancy exercise.
  4. Include EVPN-family capability and received route checks in fabric peer change validation.

Explanation

Correct Answer

B:

This safeguard addresses pim multicast rendezvous point reachability: The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. The appropriate prevention is: Validate rendezvous-point redundancy and group mapping whenever multicast domains expand. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. “Audit IPv6 routing area design and neighbor status during dual-stack network changes” would address that alternative cause, not the condition in this question: the routers do not agree on or reach the required rendezvous-point mapping for the multicast group range.

C:

“Test upstream failure, HSRP role transitions, and gateway reachability during each redundancy exercise” responds to this separate finding: the first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. This question instead needs “Validate rendezvous-point redundancy and group mapping whenever multicast domains expand”, so the alternative does not meet the stated condition.

D:

The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. “Include EVPN-family capability and received route checks in fabric peer change validation” applies to that separate problem. The observed case is multicast receivers connected to a routed leaf cannot join a source in another segment after a PIM sparse-mode domain is extended to a new pod; choosing this alternative would address the wrong failure mode.

Question 256

While checking a production data center change, the team finds: A UCS service profile requires a newer adapter firmware feature, but the applied host firmware package omits the compatible adapter release. Which approved technology action addresses this incident most directly?

  1. Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot.
  2. Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria.
  3. Create or restore an authorized UCS configuration backup and validate the documented recovery procedure.
  4. Select a compatible validated firmware package and update the affected server policy under change control.

Explanation

Correct Answer

D:

The root problem is that The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. The selected change addresses it directly: Select a compatible validated firmware package and update the affected server policy under change control. Verify the outcome: The adapter operates on the supported firmware set and the required host feature becomes available.

Incorrect Answers

A:

This action concerns ucs bios virtualization extensions, where The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The reported failure instead stems from The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites.

B:

This action concerns ucs disruptive firmware activation planning, where The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. The corrective response here is “Select a compatible validated firmware package and update the affected server policy under change control”; this alternative does not provide that response.

C:

This action concerns ucs configuration backup and restore, where The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. The stem reports a UCS service profile requires a newer adapter firmware feature, but the applied host firmware package omits the compatible adapter release; this control addresses a different failure condition.

Question 257

A data center implementation team investigates the following fault: Distributed model training runs across GPU pods but experiences network bottlenecks because oversubscribed links carry synchronized east-west collective operations without capacity planning. What preventive control would best avoid repeating this fault?

  1. Use representative multi-platform telemetry fixtures in automated parser regression tests.
  2. Audit scheduler job frequency and execution history after automation changes.
  3. Measure AI job communication patterns and model network growth before adding GPU clusters.
  4. Test PFC deadlock risk and congestion behavior before production AI network scale-out.

Explanation

Correct Answer

C:

This safeguard addresses ai workload high bandwidth east west paths: The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload. The appropriate prevention is: Measure AI job communication patterns and model network growth before adding GPU clusters. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The parser lacks schema validation and robust handling of absent or differently typed telemetry values. “Use representative multi-platform telemetry fixtures in automated parser regression tests” would address that alternative cause, not the condition in this question: the data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload.

B:

“Audit scheduler job frequency and execution history after automation changes” responds to this separate finding: the NX-OS scheduler job timing is not aligned with the intended maintenance frequency. This question instead needs “Measure AI job communication patterns and model network growth before adding GPU clusters”, so the alternative does not meet the stated condition.

D:

The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. “Test PFC deadlock risk and congestion behavior before production AI network scale-out” applies to that separate problem. The observed case is distributed model training runs across GPU pods but experiences network bottlenecks because oversubscribed links carry synchronized east-west collective operations without capacity planning; choosing this alternative would address the wrong failure mode.

Question 258

A Nexus, UCS or MDS operations team encounters this issue: A Python script sends a Nexus configuration request to NX-API but receives parsing errors because its payload is XML while the request declares JSON encoding. Which verification result most directly demonstrates successful repair?

  1. The backup executes at the intended time without repeated unnecessary administrative sessions.
  2. The script executes within its intended environment without changing unapproved host system files.
  3. Repeated execution converges to the same desired configuration without unintended duplicate changes.
  4. The device returns a successful structured response and the intended read-only verification completes.

Explanation

Correct Answer

D:

This observation validates nx api json content encoding: The NX-API request body and declared content format are inconsistent for the selected endpoint. The corresponding corrective action is: Send the supported NX-API request in the correct JSON or XML representation with matching headers. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. “Set the supported scheduler job schedule to the approved daily interval and verify the associated command” would address that alternative cause, not the condition in this question: the NX-API request body and declared content format are inconsistent for the selected endpoint.

B:

“Deploy the script in the approved supported shell environment with required dependencies and bounded permissions” responds to this separate finding: the deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. This question instead needs “Send the supported NX-API request in the correct JSON or XML representation with matching headers”, so the alternative does not meet the stated condition.

C:

The script lacks an idempotent precheck to compare desired and current network device state. “Query existing NX-OS state before applying only the necessary authorized configuration differences” applies to that separate problem. The observed case is a Python script sends a Nexus configuration request to NX-API but receives parsing errors because its payload is XML while the request declares JSON encoding; choosing this alternative would address the wrong failure mode.

Question 259

A data center implementation team investigates the following fault: An orchestration script provisions a UCS server through Intersight but associates an unapproved boot policy because it selects objects by an ambiguous display name. Which verification result most directly demonstrates successful repair?

  1. The target server profile references the expected boot and connectivity policies with no cross-tenant linkage.
  2. Only the designated lab devices receive changes and production targets remain unchanged.
  3. The intended policy persists after controller synchronization and devices report consistent compliance.
  4. The job retrieves the required device data without exposing secrets in the repository or task logs.

Explanation

Correct Answer

A:

This observation validates intersight api server policy automation: The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. The corresponding corrective action is: Use stable approved resource IDs and validate organization scope before assigning Intersight policies. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The playbook target inventory and variable precedence do not isolate the intended lab device group. “Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution” would address that alternative cause, not the condition in this question: the API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association.

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 “Use stable approved resource IDs and validate organization scope before assigning Intersight policies”, so the alternative does not meet the stated condition.

D:

The automation credential is stored insecurely and grants broader privileges than the script requires. “Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests” applies to that separate problem. The observed case is an orchestration script provisions a UCS server through Intersight but associates an unapproved boot policy because it selects objects by an ambiguous display name; choosing this alternative would address the wrong failure mode.

Question 260

A Nexus, UCS or MDS operations team encounters this issue: A monitoring Python script assumes a nested JSON metric is always a number and crashes when NX-OS telemetry omits the optional field on one hardware platform. What is the most appropriate remediation for these symptoms?

  1. Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path.
  2. Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics.
  3. Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution.
  4. Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources.

Explanation

Correct Answer

B:

The root problem is that The parser lacks schema validation and robust handling of absent or differently typed telemetry values. The selected change addresses it directly: Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics. Verify the outcome: The collector processes supported payload variants and flags incomplete metrics without terminating the monitoring job.

Incorrect Answers

A:

This action concerns ai roce lossless class design, where The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. The reported failure instead stems from The parser lacks schema validation and robust handling of absent or differently typed telemetry values.

C:

This action concerns ansible inventory variable scoping, where The playbook target inventory and variable precedence do not isolate the intended lab device group. The corrective response here is “Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics”; this alternative does not provide that response.

D:

This action concerns terraform plan infrastructure drift, where The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. The stem reports a monitoring Python script assumes a nested JSON metric is always a number and crashes when NX-OS telemetry omits the optional field on one hardware platform; this control addresses a different failure condition.