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 32

Question 310

While checking a production data center change, the team finds: Two VXLAN leaf switches serve the same tenant bridge domain but forward frames to different VXLAN network identifiers due to mismatched local mappings. Which approved technology action addresses this incident most directly?

  1. Review supported EPLD package requirements and schedule the component update using the prescribed procedure.
  2. Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies.
  3. Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves.
  4. Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF.

Explanation

Correct Answer

C:

The root problem is that The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The selected change addresses it directly: Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves. Verify the outcome: Hosts in the authorized segment communicate across leaves while unrelated tenant segments remain separate.

Incorrect Answers

A:

This action concerns nexus epld upgrade safety, where The planned software transition omits the EPLD compatibility and operational impact assessment. The reported failure instead stems from The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs.

B:

This action concerns vxlan vtep loopback reachability, where The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. The corrective response here is “Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves”; this alternative does not provide that response.

D:

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 stem reports two VXLAN leaf switches serve the same tenant bridge domain but forward frames to different VXLAN network identifiers due to mismatched local mappings; this control addresses a different failure condition.

Question 311

During a Cisco data center readiness review, engineers observe: A host sends FCoE storage traffic on an ordinary IP VLAN with no supported Fibre Channel Forwarder or proper FCoE VLAN configuration. What observation best confirms the configuration now behaves correctly?

  1. The converged adapter completes supported FCoE fabric login and discovers the permitted storage target.
  2. Each host discovers its intended target while unrelated initiator WWPNs are not jointly zoned.
  3. The backup initiator registers only in its permitted VSAN and cannot discover unrelated production zones.
  4. The upstream switch sees proxied initiator logins and the access device no longer relies on principal-switch services.

Explanation

Correct Answer

A:

This observation validates fibre channel over ethernet storage vlan mapping: The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. The corresponding corrective action is: Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The zone combines initiators beyond the least-privilege single-initiator zoning design. “Create separate approved zones for each host initiator with its authorized storage target ports” would address that alternative cause, not the condition in this question: the converged network design does not map the FCoE traffic to the required supported FCF and VSAN service.

C:

“Move the backup server connection into the approved dedicated VSAN and update authorized zoning” responds to this separate finding: vSAN membership is incorrectly shared between isolation domains with different storage access requirements. This question instead needs “Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path”, so the alternative does not meet the stated condition.

D:

NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. “Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design” applies to that separate problem. The observed case is a host sends FCoE storage traffic on an ordinary IP VLAN with no supported Fibre Channel Forwarder or proper FCoE VLAN configuration; choosing this alternative would address the wrong failure mode.

Question 312

A newly commissioned network, compute or storage service reports: A rack server intended for local mirrored boot disks reports an absent boot volume after the storage controller was left with unconfigured physical drives. What technical condition most directly accounts for the failure?

  1. The Intersight device claim and account authorization do not match the approved administrative organization.
  2. The BIOS policy disables required CPU virtualization support expected by the approved hypervisor.
  3. The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history.
  4. The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy.

Explanation

Correct Answer

D:

The technical cause is The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. The appropriate response is: Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it. Confirm successful repair: The server recognizes the protected boot volume and tolerates the documented single-disk test condition.

Incorrect Answers

A:

The Intersight device claim and account authorization do not match the approved administrative organization. “Reconcile the claim code and target ownership through supported Intersight claiming and access procedures” would address that alternative cause, not the condition in this question: the server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy.

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 “Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it”, so the alternative does not meet the stated condition.

C:

The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. “Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend” applies to that separate problem. The observed case is a rack server intended for local mirrored boot disks reports an absent boot volume after the storage controller was left with unconfigured physical drives; choosing this alternative would address the wrong failure mode.

Question 313

A data center administrator identifies the following risk: The underlay BGP neighbors are established, but a new VXLAN leaf does not exchange EVPN endpoint routes after its overlay session was commissioned. What ongoing validation should operations establish for this service?

  1. Include EVPN-family capability and received route checks in fabric peer change validation.
  2. Document SPAN source and destination interface restrictions for troubleshooting changes.
  3. Validate peer interface MTU and OSPF state in the routed-uplink commissioning checklist.
  4. Audit IPv6 routing area design and neighbor status during dual-stack network changes.

Explanation

Correct Answer

A:

This safeguard addresses mp-BGP evpn address family activation: The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. The appropriate prevention is: Include EVPN-family capability and received route checks in fabric peer change validation. 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 BGP peers lack the required L2VPN EVPN address-family activation and exchange capability.

C:

“Validate peer interface MTU and OSPF state in the routed-uplink commissioning checklist” responds to this separate finding: the neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. This question instead needs “Include EVPN-family capability and received route checks in fabric peer change validation”, so the alternative does not meet the stated condition.

D:

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

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 test outcome proves the intended service was restored?

  1. Repeated execution converges to the same desired configuration without unintended duplicate changes.
  2. A permitted API call succeeds while denied operations report a clear nonretryable authorization error.
  3. The backup executes at the intended time without repeated unnecessary administrative sessions.
  4. The applet runs only on the targeted peer-down event and preserves the expected diagnostic information.

Explanation

Correct Answer

A:

This observation validates on box python safe idempotence: The script lacks an idempotent precheck to compare desired and current network device state. The corresponding corrective action is: Query existing NX-OS state before applying only the necessary authorized configuration differences. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The REST client does not distinguish insufficient authorization from retryable transport or server errors. “Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures” would address that alternative cause, not the condition in this question: the script lacks an idempotent precheck to compare desired and current network device state.

C:

“Set the supported scheduler job schedule to the approved daily interval and verify the associated command” responds to this separate finding: the NX-OS scheduler job timing is not aligned with the intended maintenance frequency. This question instead needs “Query existing NX-OS state before applying only the necessary authorized configuration differences”, so the alternative does not meet the stated condition.

D:

The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. “Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 315

A data center implementation team investigates the following fault: A Nexus switch loses its remote AAA connection during maintenance and administrators have no approved emergency login route because all local recovery credentials were disabled. Which corrective change best resolves this problem?

  1. Replace the overly broad MDS role with an approved read-only or scoped monitoring role.
  2. Apply the approved organization-scoped Intersight RBAC role for the automation identity.
  3. Correct the authorized TACACS command or role mapping without granting full switch administrator permissions.
  4. Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions.

Explanation

Correct Answer

D:

The root problem is that The management access policy lacks a tested protected local recovery identity for remote AAA outages. The selected change addresses it directly: Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions. Verify the outcome: An authorized emergency operator can enter through the recovery path while normal remote AAA remains primary.

Incorrect Answers

A:

This action concerns cisco mds administrative role authorization, where The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. The reported failure instead stems from The management access policy lacks a tested protected local recovery identity for remote AAA outages.

B:

This action concerns intersight organization scoped administrative role, where The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. The corrective response here is “Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions”; this alternative does not provide that response.

C:

This action concerns nx os tacacs role mapping, where The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. The stem reports a Nexus switch loses its remote AAA connection during maintenance and administrators have no approved emergency login route because all local recovery credentials were disabled; this control addresses a different failure condition.

Question 316

A data center implementation team investigates the following fault: 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 design or configuration error caused the described issue?

  1. The NX-API request body and declared content format are inconsistent for the selected endpoint.
  2. The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association.
  3. The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.
  4. The script lacks an idempotent precheck to compare desired and current network device state.

Explanation

Correct Answer

A:

The technical cause is The NX-API request body and declared content format are inconsistent for the selected endpoint. The appropriate response is: Send the supported NX-API request in the correct JSON or XML representation with matching headers. Confirm successful repair: The device returns a successful structured response and the intended read-only verification completes.

Incorrect Answers

B:

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: the NX-API request body and declared content format are inconsistent for the selected endpoint.

C:

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

D:

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 317

A data center implementation team investigates the following fault: A new backup server is placed into the production database VSAN, exposing it to unintended storage fabric control and zoning scope. Which root cause best explains this behavior?

  1. The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image.
  2. VSAN membership is incorrectly shared between isolation domains with different storage access requirements.
  3. The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service.
  4. NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch.

Explanation

Correct Answer

B:

The technical cause is VSAN membership is incorrectly shared between isolation domains with different storage access requirements. The appropriate response is: Move the backup server connection into the approved dedicated VSAN and update authorized zoning. Confirm successful repair: The backup initiator registers only in its permitted VSAN and cannot discover unrelated production zones.

Incorrect Answers

A:

The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. “Review the applicable MDS EPLD package and schedule the correct supported component update” would address that alternative cause, not the condition in this question: vSAN membership is incorrectly shared between isolation domains with different storage access requirements.

C:

“Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path” responds to this separate finding: the converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. This question instead needs “Move the backup server connection into the approved dedicated VSAN and update authorized zoning”, so the alternative does not meet the stated condition.

D:

NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. “Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design” applies to that separate problem. The observed case is a new backup server is placed into the production database VSAN, exposing it to unintended storage fabric control and zoning scope; choosing this alternative would address the wrong failure mode.

Question 318

A newly commissioned network, compute or storage service reports: Two distribution switches provide HSRP default gateways, but the active switch continues answering for the virtual gateway after losing its only upstream path. Which deployment safeguard most directly reduces this failure risk?

  1. Validate peer interface MTU and OSPF state in the routed-uplink commissioning checklist.
  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

C:

This safeguard addresses hsrp uplink tracking failover: The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. The appropriate prevention is: Test upstream failure, HSRP role transitions, and gateway reachability during each redundancy exercise. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. “Validate peer interface MTU and OSPF state in the routed-uplink commissioning checklist” would address that alternative cause, not the condition in this question: the first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link.

B:

“Validate rendezvous-point redundancy and group mapping whenever multicast domains expand” responds to this separate finding: the routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. This question instead needs “Test upstream failure, HSRP role transitions, and gateway reachability during each redundancy exercise”, 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 two distribution switches provide HSRP default gateways, but the active switch continues answering for the virtual gateway after losing its only upstream path; choosing this alternative would address the wrong failure mode.

Question 319

During a Cisco data center readiness review, engineers observe: The team activates an I/O module and fabric-interconnect firmware change simultaneously without scheduling expected service impact for dependent blades. Which implementation action should the engineer take first?

  1. Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria.
  2. Create or restore an authorized UCS configuration backup and validate the documented recovery procedure.
  3. Select a compatible validated firmware package and update the affected server policy under change control.
  4. Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network.

Explanation

Correct Answer

A:

The root problem is that The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. The selected change addresses it directly: Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria. Verify the outcome: The intended firmware versions activate while the measured service interruption remains within the planned window.

Incorrect Answers

B:

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 reported failure instead stems from The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints.

C:

This action concerns ucs firmware policy package compatibility, where The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. The corrective response here is “Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria”; this alternative does not provide that response.

D:

This action concerns ucs c series cimc management networking, where The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. The stem reports the team activates an I/O module and fabric-interconnect firmware change simultaneously without scheduling expected service impact for dependent blades; this control addresses a different failure condition.

Question 320

A data center administrator identifies the following risk: A newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management. Which design or configuration error caused the described issue?

  1. Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root.
  2. The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.
  3. The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups.
  4. The leaf has not completed the supported ACI fabric discovery and node-registration workflow.

Explanation

Correct Answer

D:

The technical cause is The leaf has not completed the supported ACI fabric discovery and node-registration workflow. The appropriate response is: Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC. Confirm successful repair: APIC shows the assigned leaf as an active fabric member with the expected spine adjacency.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the leaf has not completed the supported ACI fabric discovery and node-registration workflow.

B:

“Correct the supported ACI interface policy selector and physical domain association for the host-facing port” 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 “Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC”, 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 newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management; choosing this alternative would address the wrong failure mode.