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 8

Question 70

A data center administrator identifies the following risk: 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. Which root cause best explains this behavior?

  1. The playbook target inventory and variable precedence do not isolate the intended lab device group.
  2. The parser lacks schema validation and robust handling of absent or differently typed telemetry values.
  3. The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement.
  4. The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards.

Explanation

Correct Answer

B:

The technical cause is The parser lacks schema validation and robust handling of absent or differently typed telemetry values. The appropriate response is: Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics. Confirm successful repair: The collector processes supported payload variants and flags incomplete metrics without terminating the monitoring job.

Incorrect Answers

A:

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 parser lacks schema validation and robust handling of absent or differently typed telemetry values.

C:

“Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity” responds to this separate finding: the POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. This question instead needs “Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics”, 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. “Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 71

During a Cisco data center readiness review, engineers observe: A new UCS server is physically reachable but cannot be managed from the organization's Intersight account because its device claim was associated with a different account. After remediation, which acceptance result is most relevant?

  1. The chassis and compute nodes are managed through the expected Intersight policy and profile model.
  2. The hypervisor passes hardware virtualization checks and starts a test virtual machine successfully.
  3. The profile deploys without unresolved policy references and the server boots with intended connections.
  4. The server appears as a manageable authorized target in the correct Intersight organization.

Explanation

Correct Answer

D:

This observation validates cisco intersight target claim ownership: The Intersight device claim and account authorization do not match the approved administrative organization. The corresponding corrective action is: Reconcile the claim code and target ownership through supported Intersight claiming and access procedures. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. “Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies” would address that alternative cause, not the condition in this question: the Intersight device claim and account authorization do not match the approved administrative organization.

B:

“Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot” responds to this separate finding: the BIOS policy disables required CPU virtualization support expected by the approved hypervisor. This question instead needs “Reconcile the claim code and target ownership through supported Intersight claiming and access procedures”, so the alternative does not meet the stated condition.

C:

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 new UCS server is physically reachable but cannot be managed from the organization's Intersight account because its device claim was associated with a different account; choosing this alternative would address the wrong failure mode.

Question 72

A Nexus, UCS or MDS operations team encounters this issue: A Nexus pair is scheduled for supposedly hitless software maintenance even though the target release does not support nondisruptive upgrade for the active feature combination. What preventive control would best avoid repeating this fault?

  1. Include release-path and feature-support checks before all production Nexus software changes.
  2. Track EPLD, line-card and operating system dependencies in change and rollback plans.
  3. Require a validated checkpoint and restore rehearsal for high-impact Nexus configuration edits.
  4. Apply consistent STP root-guard and bridge-priority review when adding access switches.

Explanation

Correct Answer

A:

This safeguard addresses nx os issu support preflight: The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. The appropriate prevention is: Include release-path and feature-support checks before all production Nexus software changes. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The planned software transition omits the EPLD compatibility and operational impact assessment. “Track EPLD, line-card and operating system dependencies in change and rollback plans” would address that alternative cause, not the condition in this question: the upgrade plan assumes ISSU support without validating the platform release path and active feature constraints.

C:

“Require a validated checkpoint and restore rehearsal for high-impact Nexus configuration edits” responds to this separate finding: the change process omitted a recoverable NX-OS configuration checkpoint and validation plan. This question instead needs “Include release-path and feature-support checks before all production Nexus software changes”, 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. “Apply consistent STP root-guard and bridge-priority review when adding access switches” applies to that separate problem. The observed case is a Nexus pair is scheduled for supposedly hitless software maintenance even though the target release does not support nondisruptive upgrade for the active feature combination; choosing this alternative would address the wrong failure mode.

Question 73

While checking a production data center change, the team finds: A zoning administrator cannot commit an MDS fabric configuration because an abandoned pending change session has left a CFS lock on the fabric. What observation best confirms the configuration now behaves correctly?

  1. The MDS name-server database contains the correct target and initiator identities for the relevant VSAN.
  2. The fabric accepts a new authorized zoning transaction with consistent configuration distribution.
  3. Each host discovers its intended target while unrelated initiator WWPNs are not jointly zoned.
  4. The active zoneset includes the desired members and the server discovers only its allowed storage target.

Explanation

Correct Answer

B:

This observation validates cisco fabric services configuration distribution: A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. The corresponding corrective action is: Identify the legitimate lock owner and safely complete or abort the supported CFS session. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. “Verify target port FLOGI and FCNS registration and restore the authorized target attachment” would address that alternative cause, not the condition in this question: a Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session.

C:

“Create separate approved zones for each host initiator with its authorized storage target ports” responds to this separate finding: the zone combines initiators beyond the least-privilege single-initiator zoning design. This question instead needs “Identify the legitimate lock owner and safely complete or abort the supported CFS session”, 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. “Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning” applies to that separate problem. The observed case is a zoning administrator cannot commit an MDS fabric configuration because an abandoned pending change session has left a CFS lock on the fabric; choosing this alternative would address the wrong failure mode.

Question 74

A data center administrator identifies the following risk: An MDS chassis upgrade plan ignores a line-card EPLD requirement even though Cisco's release prerequisites identify hardware programming compatibility work. Which design or configuration error caused the described issue?

  1. VSAN membership is incorrectly shared between isolation domains with different storage access requirements.
  2. The Fibre Channel SPAN session source does not identify the failing interface or service path.
  3. The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image.
  4. The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites.

Explanation

Correct Answer

C:

The technical cause is The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. The appropriate response is: Review the applicable MDS EPLD package and schedule the correct supported component update. Confirm successful repair: The module and operating system versions satisfy Cisco's documented compatibility requirements after the change.

Incorrect Answers

A:

VSAN membership is incorrectly shared between isolation domains with different storage access requirements. “Move the backup server connection into the approved dedicated VSAN and update authorized zoning” would address that alternative cause, not the condition in this question: the storage switch plan omits an EPLD package compatibility assessment for the target hardware and image.

B:

“Set a supported FC SPAN monitor source for the affected port and the approved capture destination” responds to this separate finding: the Fibre Channel SPAN session source does not identify the failing interface or service path. This question instead needs “Review the applicable MDS EPLD package and schedule the correct supported component update”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an MDS chassis upgrade plan ignores a line-card EPLD requirement even though Cisco's release prerequisites identify hardware programming compatibility work; choosing this alternative would address the wrong failure mode.

Question 75

A Nexus, UCS or MDS operations team encounters this issue: An orchestration script provisions a UCS server through Intersight but associates an unapproved boot policy because it selects objects by an ambiguous display name. What preventive control would best avoid repeating this fault?

  1. Version and authenticate POAP bootstrap artifacts while testing device-to-rack mapping before rollout.
  2. Treat centrally managed fabric intent as authoritative and audit out-of-band changes.
  3. Implement identity and organization-scope validation in Intersight automation before execution.
  4. Rotate integration credentials and inspect PowerShell logging and secret-handling policies regularly.

Explanation

Correct Answer

C:

This safeguard addresses intersight api server policy automation: The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. The appropriate prevention is: Implement identity and organization-scope validation in Intersight automation before execution. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. “Version and authenticate POAP bootstrap artifacts while testing device-to-rack mapping before rollout” 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.

B:

“Treat centrally managed fabric intent as authoritative and audit out-of-band changes” responds to this separate finding: device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. This question instead needs “Implement identity and organization-scope validation in Intersight automation before execution”, so the alternative does not meet the stated condition.

D:

The automation credential is stored insecurely and grants broader privileges than the script requires. “Rotate integration credentials and inspect PowerShell logging and secret-handling policies regularly” 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 76

A Nexus, UCS or MDS operations team encounters this issue: A storage technician adds several unrelated host initiators into a single large FC zone with a common array, creating unnecessary visibility between initiators. Which test outcome proves the intended service was restored?

  1. The active zoneset includes the desired members and the server discovers only its allowed storage target.
  2. All participating MDS switches resolve the alias to the intended replacement WWPN consistently.
  3. Each host discovers its intended target while unrelated initiator WWPNs are not jointly zoned.
  4. The fabric accepts a new authorized zoning transaction with consistent configuration distribution.

Explanation

Correct Answer

C:

This observation validates single initiator target zoning design: The zone combines initiators beyond the least-privilege single-initiator zoning design. The corresponding corrective action is: Create separate approved zones for each host initiator with its authorized storage target ports. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

An inactive zoning database edit does not change the effective active zoneset on the SAN fabric. “Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning” would address that alternative cause, not the condition in this question: the zone combines initiators beyond the least-privilege single-initiator zoning design.

B:

“Commit the approved device alias database transaction and verify resolution across the affected switches” responds to this separate finding: device alias changes have not been committed and distributed through the supported fabric database workflow. This question instead needs “Create separate approved zones for each host initiator with its authorized storage target ports”, so the alternative does not meet the stated condition.

D:

A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. “Identify the legitimate lock owner and safely complete or abort the supported CFS session” applies to that separate problem. The observed case is a storage technician adds several unrelated host initiators into a single large FC zone with a common array, creating unnecessary visibility between initiators; choosing this alternative would address the wrong failure mode.

Question 77

A Nexus, UCS or MDS operations team encounters this issue: The underlay BGP neighbors are established, but a new VXLAN leaf does not exchange EVPN endpoint routes after its overlay session was commissioned. Which design or configuration error caused the described issue?

  1. Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility.
  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

C:

The technical cause is The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. The appropriate response is: Activate the correct EVPN address family for authorized peers and verify route advertisement policy. Confirm successful repair: The leaf receives the intended EVPN routes and remote workloads become reachable over VXLAN.

Incorrect Answers

A:

Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. “Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries” would address that alternative cause, not the condition in this question: the BGP peers lack the required L2VPN EVPN address-family activation and exchange capability.

B:

“Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role” 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 “Activate the correct EVPN address family for authorized peers and verify route advertisement policy”, 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 the underlay BGP neighbors are established, but a new VXLAN leaf does not exchange EVPN endpoint routes after its overlay session was commissioned; choosing this alternative would address the wrong failure mode.

Question 78

During a Cisco data center readiness review, engineers observe: A data center team calls a privately operated dedicated cloud a public cloud merely because users reach it remotely through the Internet. Which approved technology action addresses this incident most directly?

  1. Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries.
  2. Activate the correct EVPN address family for authorized peers and verify route advertisement policy.
  3. Provide a valid IGMP querier through the routed gateway or supported switching configuration.
  4. Inspect the bridge-domain BUM replication method and configure only approved VTEP replication membership.

Explanation

Correct Answer

A:

The root problem is that Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. The selected change addresses it directly: Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries. Verify the outcome: The design describes the private deployment and any genuinely shared public components without conflating connectivity.

Incorrect Answers

B:

This action concerns mp-BGP evpn address family activation, where The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. The reported failure instead stems from Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility.

C:

This action concerns igmp snooping querier requirement, where IGMP snooping membership state is not refreshed because the VLAN lacks a reachable supported multicast querier. The corrective response here is “Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries”; this alternative does not provide that response.

D:

This action concerns broadcast unknown unicast multicast replication, where BUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model. The stem reports a data center team calls a privately operated dedicated cloud a public cloud merely because users reach it remotely through the Internet; this control addresses a different failure condition.

Question 79

A newly commissioned network, compute or storage service reports: 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. Which deployment safeguard most directly reduces this failure risk?

  1. Treat centrally managed fabric intent as authoritative and audit out-of-band changes.
  2. Implement identity and organization-scope validation in Intersight automation before execution.
  3. Rotate integration credentials and inspect PowerShell logging and secret-handling policies regularly.
  4. Review inventory membership and variable precedence before every network automation deployment.

Explanation

Correct Answer

A:

This safeguard addresses nexus dashboard intent orchestration consistency: Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. The appropriate prevention is: Treat centrally managed fabric intent as authoritative and audit out-of-band changes. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. “Implement identity and organization-scope validation in Intersight automation before execution” 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:

“Rotate integration credentials and inspect PowerShell logging and secret-handling policies regularly” responds to this separate finding: the automation credential is stored insecurely and grants broader privileges than the script requires. This question instead needs “Treat centrally managed fabric intent as authoritative and audit out-of-band changes”, so the alternative does not meet the stated condition.

D:

The playbook target inventory and variable precedence do not isolate the intended lab device group. “Review inventory membership and variable precedence before every network automation deployment” 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 80

A data center implementation team investigates the following fault: A Nexus on-box Python remediation applet recreates the same VLAN and interface objects every run, producing repeated configuration changes even when state is already correct. Which corrective change best resolves this problem?

  1. Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event.
  2. Query existing NX-OS state before applying only the necessary authorized configuration differences.
  3. Set the supported scheduler job schedule to the approved daily interval and verify the associated command.
  4. Deploy the script in the approved supported shell environment with required dependencies and bounded permissions.

Explanation

Correct Answer

B:

The root problem is that The script lacks an idempotent precheck to compare desired and current network device state. The selected change addresses it directly: Query existing NX-OS state before applying only the necessary authorized configuration differences. Verify the outcome: Repeated execution converges to the same desired configuration without unintended duplicate changes.

Incorrect Answers

A:

This action concerns nx os eem syslog event trigger, where The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. The reported failure instead stems from The script lacks an idempotent precheck to compare desired and current network device state.

C:

This action concerns nx os scheduler job interval, where The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The corrective response here is “Query existing NX-OS state before applying only the necessary authorized configuration differences”; 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 a Nexus on-box Python remediation applet recreates the same VLAN and interface objects every run, producing repeated configuration changes even when state is already correct; this control addresses a different failure condition.