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 18

Question 170

A newly commissioned network, compute or storage service reports: A new WWPN zone has been created in the MDS zoning database but the application host still cannot see its storage array because the zoneset was never activated. Which implementation action should the engineer take first?

  1. Update the approved initiator and target CHAP secret settings using the supported secure workflow.
  2. Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning.
  3. Commit the approved device alias database transaction and verify resolution across the affected switches.
  4. Verify target port FLOGI and FCNS registration and restore the authorized target attachment.

Explanation

Correct Answer

B:

The root problem is that An inactive zoning database edit does not change the effective active zoneset on the SAN fabric. The selected change addresses it directly: Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning. Verify the outcome: The active zoneset includes the desired members and the server discovers only its allowed storage target.

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 An inactive zoning database edit does not change the effective active zoneset on the SAN fabric.

C:

This action concerns cisco mds device alias commit behavior, where Device alias changes have not been committed and distributed through the supported fabric database workflow. The corrective response here is “Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning”; this alternative does not provide that response.

D:

This action concerns fibre channel name server registration, where The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. The stem reports a new WWPN zone has been created in the MDS zoning database but the application host still cannot see its storage array because the zoneset was never activated; this control addresses a different failure condition.

Question 171

A newly commissioned network, compute or storage service reports: Two SAN-connected server profiles are provisioned with overlapping manually assigned virtual HBA worldwide port names, disrupting their distinct storage identities. Which approved technology action addresses this incident most directly?

  1. Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters.
  2. Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration.
  3. Associate the intended service profile and its identity pools with the supported replacement hardware.
  4. Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design.

Explanation

Correct Answer

B:

The root problem is that The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. The selected change addresses it directly: Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration. Verify the outcome: Both servers log in with their own WWPN identities and see only their authorized storage paths.

Incorrect Answers

A:

This action concerns ucs san boot target identifiers, where The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. The reported failure instead stems from The vHBA WWPN allocation violates uniqueness requirements across server storage initiators.

C:

This action concerns ucs service profile server identity, where The server identity has not been abstracted through approved UCS service profile and identity-pool associations. The corrective response here is “Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration”; this alternative does not provide that response.

D:

This action concerns ucs vnic fabric failover connectivity, where The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. The stem reports two SAN-connected server profiles are provisioned with overlapping manually assigned virtual HBA worldwide port names, disrupting their distinct storage identities; this control addresses a different failure condition.

Question 172

A Nexus, UCS or MDS operations team encounters this issue: 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 design or configuration error caused the described issue?

  1. The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association.
  2. Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model.
  3. The parser lacks schema validation and robust handling of absent or differently typed telemetry values.
  4. The automation credential is stored insecurely and grants broader privileges than the script requires.

Explanation

Correct Answer

B:

The technical cause is Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. The appropriate response is: Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow. Confirm successful repair: The intended policy persists after controller synchronization and devices report consistent compliance.

Incorrect Answers

A:

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

“Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics” responds to this separate finding: the parser lacks schema validation and robust handling of absent or differently typed telemetry values. 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 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 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 173

A data center administrator identifies the following risk: A new VXLAN segment experiences unnecessary broadcast amplification when unknown unicast and multicast frames are flooded broadly without validating overlay replication. What preventive control would best avoid repeating this fault?

  1. Apply consistent STP root-guard and bridge-priority review when adding access switches.
  2. Maintain a documented node-ID and cabling approval process for new ACI leaf introductions.
  3. Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes.
  4. Review VNI BUM replication scope and flood lists as part of tenant expansion planning.

Explanation

Correct Answer

D:

This safeguard addresses broadcast unknown unicast multicast replication: BUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model. The appropriate prevention is: Review VNI BUM replication scope and flood lists as part of tenant expansion planning. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

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

“Maintain a documented node-ID and cabling approval process for new ACI leaf introductions” responds to this separate finding: the leaf has not completed the supported ACI fabric discovery and node-registration workflow. This question instead needs “Review VNI BUM replication scope and flood lists as part of tenant expansion planning”, 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. “Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes” 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 174

During a Cisco data center readiness review, engineers observe: A factory-default Nexus switch runs PowerOn Auto Provisioning but fetches a bootstrap configuration intended for a different rack due to an incorrect DHCP-supplied file path. Which operational guardrail would prevent a similar outage?

  1. Version and authenticate POAP bootstrap artifacts while testing device-to-rack mapping before rollout.
  2. Measure AI job communication patterns and model network growth before adding GPU clusters.
  3. Require drift detection and reviewed plan artifacts in Terraform change-control procedures.
  4. Treat centrally managed fabric intent as authoritative and audit out-of-band changes.

Explanation

Correct Answer

A:

This safeguard addresses poap initial provisioning ownership: The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. The appropriate prevention is: Version and authenticate POAP bootstrap artifacts while testing device-to-rack mapping before rollout. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload. “Measure AI job communication patterns and model network growth before adding GPU clusters” would address that alternative cause, not the condition in this question: the POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement.

C:

“Require drift detection and reviewed plan artifacts in Terraform change-control procedures” responds to this separate finding: the infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. This question instead needs “Version and authenticate POAP bootstrap artifacts while testing device-to-rack mapping before rollout”, so the alternative does not meet the stated condition.

D:

Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. “Treat centrally managed fabric intent as authoritative and audit out-of-band changes” applies to that separate problem. The observed case is a factory-default Nexus switch runs PowerOn Auto Provisioning but fetches a bootstrap configuration intended for a different rack due to an incorrect DHCP-supplied file path; choosing this alternative would address the wrong failure mode.

Question 175

While checking a production data center change, the team finds: An MDS chassis upgrade plan ignores a line-card EPLD requirement even though Cisco's release prerequisites identify hardware programming compatibility work. After remediation, which acceptance result is most relevant?

  1. The new host mounts the intended export while an unauthorized client remains denied.
  2. The module and operating system versions satisfy Cisco's documented compatibility requirements after the change.
  3. The SAN analyzer receives the relevant FC exchanges needed to isolate the transport fault.
  4. A lab or pilot establishes the expected outage characteristics and the approved upgrade completes safely.

Explanation

Correct Answer

B:

This observation validates cisco mds epld hardware dependency: The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. The corresponding corrective action is: Review the applicable MDS EPLD package and schedule the correct supported component update. Evidence about a different component does not establish the requested service outcome.

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 storage switch plan omits an EPLD package compatibility assessment for the target hardware and image.

C:

“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 176

A Nexus, UCS or MDS operations team encounters this issue: Multicast video receivers remain connected at layer two, but group membership ages out because there is no active IGMP querier in their VLAN. What is the most appropriate remediation for these symptoms?

  1. Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries.
  2. Provide a valid IGMP querier through the routed gateway or supported switching configuration.
  3. Activate the correct EVPN address family for authorized peers and verify route advertisement policy.
  4. Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves.

Explanation

Correct Answer

B:

The root problem is that IGMP snooping membership state is not refreshed because the VLAN lacks a reachable supported multicast querier. The selected change addresses it directly: Provide a valid IGMP querier through the routed gateway or supported switching configuration. Verify the outcome: Interested ports retain multicast group membership and nonmembers do not receive unwanted replicated streams.

Incorrect Answers

A:

This action concerns nist public private hybrid cloud models, where Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. The reported failure instead stems from IGMP snooping membership state is not refreshed because the VLAN lacks a reachable supported multicast querier.

C:

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 corrective response here is “Provide a valid IGMP querier through the routed gateway or supported switching configuration”; this alternative does not provide that response.

D:

This action concerns vxlan vlan vni mapping consistency, where The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The stem reports multicast video receivers remain connected at layer two, but group membership ages out because there is no active IGMP querier in their VLAN; this control addresses a different failure condition.

Question 177

A data center administrator identifies the following risk: A new backup server is placed into the production database VSAN, exposing it to unintended storage fabric control and zoning scope. Which corrective change best resolves this problem?

  1. Assign the target port to the approved VSAN and verify its effective FCNS and zone membership.
  2. Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design.
  3. Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path.
  4. Move the backup server connection into the approved dedicated VSAN and update authorized zoning.

Explanation

Correct Answer

D:

The root problem is that VSAN membership is incorrectly shared between isolation domains with different storage access requirements. The selected change addresses it directly: Move the backup server connection into the approved dedicated VSAN and update authorized zoning. Verify the outcome: The backup initiator registers only in its permitted VSAN and cannot discover unrelated production zones.

Incorrect Answers

A:

This action concerns san vsan interface assignment at attachment, where The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. The reported failure instead stems from VSAN membership is incorrectly shared between isolation domains with different storage access requirements.

B:

This action concerns npv and npiv switch roles, where NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. The corrective response here is “Move the backup server connection into the approved dedicated VSAN and update authorized zoning”; this alternative does not provide that response.

C:

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 stem reports a new backup server is placed into the production database VSAN, exposing it to unintended storage fabric control and zoning scope; this control addresses a different failure condition.

Question 178

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

  1. Review telemetry subscriptions and alert coverage after changes to device software or fabric topology.
  2. Document SPAN source and destination interface restrictions for troubleshooting changes.
  3. Monitor flow exporter reachability and collector acceptance after telemetry network changes.
  4. Monitor endpoint advertisement and withdrawal during workload migration and policy updates.

Explanation

Correct Answer

A:

This safeguard addresses nexus dashboard assurance and streaming telemetry: The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. The appropriate prevention is: Review telemetry subscriptions and alert coverage after changes to device software or fabric topology. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The SPAN session source and dedicated monitor destination roles were assigned incorrectly. “Document SPAN source and destination interface restrictions for troubleshooting changes” 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:

“Monitor flow exporter reachability and collector acceptance after telemetry network changes” responds to this separate finding: flow-export destination reachability or the configured source and monitoring VRF are incorrect. This question instead needs “Review telemetry subscriptions and alert coverage after changes to device software or fabric topology”, so the alternative does not meet the stated condition.

D:

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

Question 179

While checking a production data center change, the team finds: A new Nexus leaf has its VXLAN NVE interface configured but cannot encapsulate traffic to remote VTEPs after the underlay route filters changed. Which implementation action should the engineer take first?

  1. Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment.
  2. Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF.
  3. Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies.
  4. Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves.

Explanation

Correct Answer

C:

The root problem is that The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. The selected change addresses it directly: Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies. Verify the outcome: Remote VTEP loopbacks resolve correctly and workload frames traverse the VXLAN overlay.

Incorrect Answers

A:

This action concerns aci vmm domain dynamic endpoint learning, where The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. The reported failure instead stems from The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain.

B:

This action concerns evpn ip prefix type five advertisement, where The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. The corrective response here is “Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies”; this alternative does not provide that response.

D:

This action concerns vxlan vlan vni mapping consistency, where The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The stem reports a new Nexus leaf has its VXLAN NVE interface configured but cannot encapsulate traffic to remote VTEPs after the underlay route filters changed; this control addresses a different failure condition.

Question 180

A data center administrator identifies the following risk: A newly installed blade chassis has power but its I/O modules and blades never appear under fabric-interconnect inventory after uplink cabling was changed. Which corrective change best resolves this problem?

  1. Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria.
  2. Repair the UCS fabric-interconnect cluster and management redundancy configuration and validate supported failover.
  3. Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis.
  4. Restore the supported boot policy and required SAN adapter path in the correct boot-device order.

Explanation

Correct Answer

C:

The root problem is that The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. The selected change addresses it directly: Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis. Verify the outcome: Both intended fabric paths enumerate the chassis and associated blades under UCS management.

Incorrect Answers

A:

This action concerns ucs disruptive firmware activation planning, where The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. The reported failure instead stems from The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured.

B:

This action concerns ucs fabric interconnect management failover, where The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior. The corrective response here is “Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis”; this alternative does not provide that response.

D:

This action concerns ucs c series boot policy device order, where The configured boot-device order does not select the intended SAN boot path before local storage. The stem reports a newly installed blade chassis has power but its I/O modules and blades never appear under fabric-interconnect inventory after uplink cabling was changed; this control addresses a different failure condition.