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 39

Question 380

A data center implementation team investigates the following fault: A virtualization platform needs a block device for a raw LUN but the proposed integration offers only an NFS file-system export as though it were an iSCSI target. Which root cause best explains this behavior?

  1. The NFS export access rules do not authorize the requesting client address or security identity.
  2. The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials.
  3. The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded.
  4. The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation.

Explanation

Correct Answer

D:

The technical cause is The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. The appropriate response is: Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk. Confirm successful repair: The host discovers an iSCSI target LUN and presents the expected block device to the hypervisor.

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 application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation.

B:

“Update the approved initiator and target CHAP secret settings using the supported secure workflow” responds to this separate finding: the iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. This question instead needs “Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a virtualization platform needs a block device for a raw LUN but the proposed integration offers only an NFS file-system export as though it were an iSCSI target; choosing this alternative would address the wrong failure mode.

Question 381

A newly commissioned network, compute or storage service reports: An unauthorized workstation sends IPv6 router advertisements on a Nexus access VLAN, causing nearby hosts to adopt an attacker-controlled default router. Which deployment safeguard most directly reduces this failure risk?

  1. Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added.
  2. Test IPv6 first-hop security along with DHCP and ARP controls during access-switch turnup.
  3. Recertify UCS role assignments after team or responsibility changes.
  4. Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes.

Explanation

Correct Answer

B:

This safeguard addresses ipv6 router advertisement guard: The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. The appropriate prevention is: Test IPv6 first-hop security along with DHCP and ARP controls during access-switch turnup. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. “Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added” would address that alternative cause, not the condition in this question: the access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements.

C:

“Recertify UCS role assignments after team or responsibility changes” responds to this separate finding: the UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. This question instead needs “Test IPv6 first-hop security along with DHCP and ARP controls during access-switch turnup”, so the alternative does not meet the stated condition.

D:

DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. “Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes” applies to that separate problem. The observed case is an unauthorized workstation sends IPv6 router advertisements on a Nexus access VLAN, causing nearby hosts to adopt an attacker-controlled default router; choosing this alternative would address the wrong failure mode.

Question 382

A newly commissioned network, compute or storage service reports: An engineer runs a Linux shell script inside the Nexus host environment and assumes it has the same dependencies and resource isolation as a supported Guest Shell container. What technical condition most directly accounts for the failure?

  1. The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.
  2. The parser lacks schema validation and robust handling of absent or differently typed telemetry values.
  3. The script lacks an idempotent precheck to compare desired and current network device state.
  4. The NX-API request body and declared content format are inconsistent for the selected endpoint.

Explanation

Correct Answer

A:

The technical cause is The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The appropriate response is: Deploy the script in the approved supported shell environment with required dependencies and bounded permissions. Confirm successful repair: The script executes within its intended environment without changing unapproved host system files.

Incorrect Answers

B:

The parser lacks schema validation and robust handling of absent or differently typed telemetry values. “Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics” would address that alternative cause, not the condition in this question: the deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.

C:

“Query existing NX-OS state before applying only the necessary authorized configuration differences” responds to this separate finding: the script lacks an idempotent precheck to compare desired and current network device state. This question instead needs “Deploy the script in the approved supported shell environment with required dependencies and bounded permissions”, so the alternative does not meet the stated condition.

D:

The NX-API request body and declared content format are inconsistent for the selected endpoint. “Send the supported NX-API request in the correct JSON or XML representation with matching headers” applies to that separate problem. The observed case is an engineer runs a Linux shell script inside the Nexus host environment and assumes it has the same dependencies and resource isolation as a supported Guest Shell container; choosing this alternative would address the wrong failure mode.

Question 383

During a Cisco data center readiness review, engineers observe: 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. Which approved technology action addresses this incident most directly?

  1. Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology.
  2. Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF.
  3. Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path.
  4. Review supported EPLD package requirements and schedule the component update using the prescribed procedure.

Explanation

Correct Answer

C:

The root problem is that The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. The selected change addresses it directly: Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path. Verify the outcome: A staged test establishes the actual traffic impact and the upgrade follows the approved compatibility plan.

Incorrect Answers

A:

This action concerns rstp root bridge placement, where Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. The reported failure instead stems from The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints.

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 “Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path”; this alternative does not provide that response.

D:

This action concerns nexus epld upgrade safety, where The planned software transition omits the EPLD compatibility and operational impact assessment. The stem reports 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; this control addresses a different failure condition.

Question 384

While checking a production data center change, the team finds: A Nexus maintenance plan upgrades only the system image while a documented line-card hardware programming device update is required for the target release. What is the primary technical reason the deployment fails?

  1. The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints.
  2. The planned software transition omits the EPLD compatibility and operational impact assessment.
  3. The change process omitted a recoverable NX-OS configuration checkpoint and validation plan.
  4. Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility.

Explanation

Correct Answer

B:

The technical cause is The planned software transition omits the EPLD compatibility and operational impact assessment. The appropriate response is: Review supported EPLD package requirements and schedule the component update using the prescribed procedure. Confirm successful repair: Hardware and software component versions match the approved release prerequisites after controlled maintenance.

Incorrect Answers

A:

The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. “Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path” would address that alternative cause, not the condition in this question: the planned software transition omits the EPLD compatibility and operational impact assessment.

C:

“Create and use a supported configuration checkpoint or approved rollback before editing the production policy” responds to this separate finding: the change process omitted a recoverable NX-OS configuration checkpoint and validation plan. This question instead needs “Review supported EPLD package requirements and schedule the component update using the prescribed procedure”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a Nexus maintenance plan upgrades only the system image while a documented line-card hardware programming device update is required for the target release; choosing this alternative would address the wrong failure mode.

Question 385

A newly commissioned network, compute or storage service 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. What observation best confirms the configuration now behaves correctly?

  1. Both intended fabric paths enumerate the chassis and associated blades under UCS management.
  2. The profile associates only with hardware satisfying its documented adapter and compute requirements.
  3. A controlled reboot starts the server from the authorized SAN boot target and reaches the expected OS.
  4. The secondary fabric interconnect takes over management duties without losing the approved domain configuration.

Explanation

Correct Answer

A:

This observation validates ucs blade chassis fabric discovery: The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. The corresponding corrective action is: Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The server pool qualification policy does not limit placement to servers with the required hardware capabilities. “Create the supported UCS server pool qualification and associate the workload profile with eligible members” would address that alternative cause, not the condition in this question: the chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured.

C:

“Restore the supported boot policy and required SAN adapter path in the correct boot-device order” responds to this separate finding: the configured boot-device order does not select the intended SAN boot path before local storage. This question instead needs “Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis”, so the alternative does not meet the stated condition.

D:

The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior. “Repair the UCS fabric-interconnect cluster and management redundancy configuration and validate supported failover” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 386

A data center implementation team investigates the following fault: A virtual machine migrates to a different ESXi host but its ACI EPG policy does not follow because the virtualization integration is incomplete. What ongoing validation should operations establish for this service?

  1. Document orphan workloads and test their failure conditions independently of dual-homed vPC hosts.
  2. Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes.
  3. Validate leaf interface selectors, domains and EPG paths together in access-policy reviews.
  4. Review VNI BUM replication scope and flood lists as part of tenant expansion planning.

Explanation

Correct Answer

B:

This safeguard addresses aci vmm domain dynamic endpoint learning: The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. The appropriate prevention is: Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The failure design does not account for orphan-port behavior and the chosen peer recovery semantics. “Document orphan workloads and test their failure conditions independently of dual-homed vPC hosts” would address that alternative cause, not the condition in this question: the ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups.

C:

“Validate leaf interface selectors, domains and EPG paths together in access-policy reviews” responds to this separate finding: the interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. This question instead needs “Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes”, so the alternative does not meet the stated condition.

D:

BUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model. “Review VNI BUM replication scope and flood lists as part of tenant expansion planning” applies to that separate problem. The observed case is a virtual machine migrates to a different ESXi host but its ACI EPG policy does not follow because the virtualization integration is incomplete; choosing this alternative would address the wrong failure mode.

Question 387

During a Cisco data center readiness review, engineers observe: A new Nexus leaf has its VXLAN NVE interface configured but cannot encapsulate traffic to remote VTEPs after the underlay route filters changed. What observation best confirms the configuration now behaves correctly?

  1. APIC shows the assigned leaf as an active fabric member with the expected spine adjacency.
  2. The remote leaf learns the intended endpoint MAC through a valid EVPN route and forwards frames correctly.
  3. Remote VTEP loopbacks resolve correctly and workload frames traverse the VXLAN overlay.
  4. Hosts in the authorized segment communicate across leaves while unrelated tenant segments remain separate.

Explanation

Correct Answer

C:

This observation validates vxlan vtep loopback reachability: The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. The corresponding corrective action is: Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The leaf has not completed the supported ACI fabric discovery and node-registration workflow. “Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC” would address that alternative cause, not the condition in this question: the NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain.

B:

“Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI” responds to this separate finding: the Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. This question instead needs “Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies”, so the alternative does not meet the stated condition.

D:

The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. “Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves” applies to that separate problem. The observed case is a new Nexus leaf has its VXLAN NVE interface configured but cannot encapsulate traffic to remote VTEPs after the underlay route filters changed; choosing this alternative would address the wrong failure mode.

Question 388

A newly commissioned network, compute or storage service reports: An MDS maintenance team attempts a nondisruptive SAN switch upgrade while a required redundancy check and supported release-path validation are incomplete. 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. A time-aligned report identifies the affected SAN ports and correlates counters with storage latency.
  3. A lab or pilot establishes the expected outage characteristics and the approved upgrade completes safely.
  4. The SAN analyzer receives the relevant FC exchanges needed to isolate the transport fault.

Explanation

Correct Answer

C:

This observation validates cisco mds nondisruptive upgrade prechecks: The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. The corresponding corrective action is: Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method. 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: the selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites.

B:

“Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis” responds to this separate finding: the SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. This question instead needs “Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method”, so the alternative does not meet the stated condition.

D:

The Fibre Channel SPAN session source does not identify the failing interface or service path. “Set a supported FC SPAN monitor source for the affected port and the approved capture destination” applies to that separate problem. The observed case is an MDS maintenance team attempts a nondisruptive SAN switch upgrade while a required redundancy check and supported release-path validation are incomplete; choosing this alternative would address the wrong failure mode.

Question 389

During a Cisco data center readiness review, engineers observe: An engineer applies Terraform changes to network policies without examining the plan, accidentally removing fabric objects that were changed manually after the last state capture. What observation best confirms the configuration now behaves correctly?

  1. The collector processes supported payload variants and flags incomplete metrics without terminating the monitoring job.
  2. The approved plan makes intended changes and leaves unrelated network resources intact.
  3. The switch downloads its own authorized initial configuration and registers in the intended management inventory.
  4. The GPU fabric sustains the benchmark workload with controlled loss and congestion indicators during bursts.

Explanation

Correct Answer

B:

This observation validates terraform plan infrastructure drift: The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. The corresponding corrective action is: Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The parser lacks schema validation and robust handling of absent or differently typed telemetry values. “Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics” would address that alternative cause, not the condition in this question: the infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation.

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 “Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources”, 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 an engineer applies Terraform changes to network policies without examining the plan, accidentally removing fabric objects that were changed manually after the last state capture; choosing this alternative would address the wrong failure mode.

Question 390

A Nexus, UCS or MDS operations team encounters this issue: A UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults. Which corrective change best resolves this problem?

  1. Use an approved updating service profile template and apply governed changes to its associated server profiles.
  2. Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot.
  3. Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend.
  4. Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it.

Explanation

Correct Answer

C:

The root problem is that The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. The selected change addresses it directly: Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend. Verify the outcome: Intersight records the hardware fault and resolution, while workload stability returns after repair.

Incorrect Answers

A:

This action concerns ucs updating service profile templates, where The configuration process bypasses the intended reusable UCS service profile template inheritance model. The reported failure instead stems from The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history.

B:

This action concerns ucs bios virtualization extensions, where The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The corrective response here is “Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend”; this alternative does not provide that response.

D:

This action concerns ucs c series virtual disk raid policy, where The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. The stem reports a UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults; this control addresses a different failure condition.