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 3

Question 20

During a Cisco data center readiness review, engineers observe: A UCS domain loses management when its primary fabric interconnect is rebooted even though the secondary interconnect is operational. Which approved technology action addresses this incident most directly?

  1. Restore the supported boot policy and required SAN adapter path in the correct boot-device order.
  2. Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network.
  3. Repair the UCS fabric-interconnect cluster and management redundancy configuration and validate supported failover.
  4. Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis.

Explanation

Correct Answer

C:

The root problem is that The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior. The selected change addresses it directly: Repair the UCS fabric-interconnect cluster and management redundancy configuration and validate supported failover. Verify the outcome: The secondary fabric interconnect takes over management duties without losing the approved domain configuration.

Incorrect Answers

A:

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 reported failure instead stems from The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior.

B:

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 corrective response here is “Repair the UCS fabric-interconnect cluster and management redundancy configuration and validate supported failover”; this alternative does not provide that response.

D:

This action concerns ucs blade chassis fabric discovery, where The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. The stem reports a UCS domain loses management when its primary fabric interconnect is rebooted even though the secondary interconnect is operational; this control addresses a different failure condition.

Question 21

A Nexus, UCS or MDS operations team encounters this issue: A new VXLAN segment experiences unnecessary broadcast amplification when unknown unicast and multicast frames are flooded broadly without validating overlay replication. Which root cause best explains this behavior?

  1. The leaf has not completed the supported ACI fabric discovery and node-registration workflow.
  2. BUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model.
  3. The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.
  4. The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups.

Explanation

Correct Answer

B:

The technical cause is BUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model. The appropriate response is: Inspect the bridge-domain BUM replication method and configure only approved VTEP replication membership. Confirm successful repair: Unicast learning and authorized broadcast discovery work without traffic being replicated to unrelated VTEPs.

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: bUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model.

C:

“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 “Inspect the bridge-domain BUM replication method and configure only approved VTEP replication membership”, so the alternative does not meet the stated condition.

D:

The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. “Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment” applies to that separate problem. The observed case is a new VXLAN segment experiences unnecessary broadcast amplification when unknown unicast and multicast frames are flooded broadly without validating overlay replication; choosing this alternative would address the wrong failure mode.

Question 22

A Nexus, UCS or MDS operations team encounters this issue: Multicast receivers connected to a routed leaf cannot join a source in another segment after a PIM sparse-mode domain is extended to a new pod. What is the most appropriate remediation for these symptoms?

  1. Activate the correct EVPN address family for authorized peers and verify route advertisement policy.
  2. Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency.
  3. Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation.
  4. Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups.

Explanation

Correct Answer

D:

The root problem is that The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. The selected change addresses it directly: Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups. Verify the outcome: The intended receivers join and receive source traffic, and PIM control state shows the proper tree.

Incorrect Answers

A:

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 The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range.

B:

This action concerns ospfv2 adjacency mtu mismatch, where The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. The corrective response here is “Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups”; this alternative does not provide that response.

C:

This action concerns ospfv3 ipv6 area consistency, where The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. The stem reports multicast receivers connected to a routed leaf cannot join a source in another segment after a PIM sparse-mode domain is extended to a new pod; this control addresses a different failure condition.

Question 23

A data center implementation team investigates the following fault: A running production blade is reassigned to a different UCS service profile without understanding reboot or identity-change consequences, interrupting applications. What is the most appropriate remediation for these symptoms?

  1. Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks.
  2. Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot.
  3. Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it.
  4. Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend.

Explanation

Correct Answer

A:

The root problem is that The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings. The selected change addresses it directly: Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks. Verify the outcome: The blade receives the intended policy identity after the controlled operation and applications recover as planned.

Incorrect Answers

B:

This action concerns ucs bios virtualization extensions, where The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The reported failure instead stems from The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings.

C:

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 corrective response here is “Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks”; this alternative does not provide that response.

D:

This action concerns intersight hardware telemetry alarm review, where The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. The stem reports a running production blade is reassigned to a different UCS service profile without understanding reboot or identity-change consequences, interrupting applications; this control addresses a different failure condition.

Question 24

While checking a production data center change, the team finds: A server NIC connects to an ACI leaf port, but the configured EPG never becomes operational on that port after the tenant was deployed. Which implementation action should the engineer take first?

  1. Inspect the bridge-domain BUM replication method and configure only approved VTEP replication membership.
  2. Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC.
  3. Correct the supported ACI interface policy selector and physical domain association for the host-facing port.
  4. Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment.

Explanation

Correct Answer

C:

The root problem is that The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. The selected change addresses it directly: Correct the supported ACI interface policy selector and physical domain association for the host-facing port. Verify the outcome: APIC reports the expected interface and EPG deployment, and authorized server traffic is forwarded.

Incorrect Answers

A:

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 reported failure instead stems from The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.

B:

This action concerns aci leaf onboarding discovery, where The leaf has not completed the supported ACI fabric discovery and node-registration workflow. The corrective response here is “Correct the supported ACI interface policy selector and physical domain association for the host-facing port”; this alternative does not provide that response.

D:

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 stem reports a server NIC connects to an ACI leaf port, but the configured EPG never becomes operational on that port after the tenant was deployed; this control addresses a different failure condition.

Question 25

A newly commissioned network, compute or storage service reports: A new Nexus leaf has its VXLAN NVE interface configured but cannot encapsulate traffic to remote VTEPs after the underlay route filters changed. What is the primary technical reason the deployment fails?

  1. The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route.
  2. The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs.
  3. The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain.
  4. The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy.

Explanation

Correct Answer

C:

The technical cause is The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. The appropriate response is: Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies. Confirm successful repair: Remote VTEP loopbacks resolve correctly and workload frames traverse the VXLAN overlay.

Incorrect Answers

A:

The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. “Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF” 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:

“Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves” responds to this separate finding: the tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. 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 Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. “Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI” 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 26

While checking a production data center change, the team finds: 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. Which implementation action should the engineer take first?

  1. Set the supported scheduler job schedule to the approved daily interval and verify the associated command.
  2. Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures.
  3. Query existing NX-OS state before applying only the necessary authorized configuration differences.
  4. Deploy the script in the approved supported shell environment with required dependencies and bounded permissions.

Explanation

Correct Answer

D:

The root problem is that The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The selected change addresses it directly: Deploy the script in the approved supported shell environment with required dependencies and bounded permissions. Verify the outcome: The script executes within its intended environment without changing unapproved host system files.

Incorrect Answers

A:

This action concerns nx os scheduler job interval, where The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The reported failure instead stems from The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.

B:

This action concerns rest api authorization status handling, where The REST client does not distinguish insufficient authorization from retryable transport or server errors. The corrective response here is “Deploy the script in the approved supported shell environment with required dependencies and bounded permissions”; this alternative does not provide that response.

C:

This action concerns on box python safe idempotence, where The script lacks an idempotent precheck to compare desired and current network device state. The stem 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; this control addresses a different failure condition.

Question 27

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. What ongoing validation should operations establish for this service?

  1. Check each SAN port VSAN assignment before activating new production zones.
  2. Document NPV versus NPIV responsibilities before configuring UCS and MDS fabric attachment.
  3. Review VSAN boundaries independently of physical switch and trunk connectivity.
  4. Review FCoE VLAN and lossless Ethernet prerequisites separately from ordinary LAN configuration.

Explanation

Correct Answer

C:

This safeguard addresses fibre channel vsan traffic isolation: VSAN membership is incorrectly shared between isolation domains with different storage access requirements. The appropriate prevention is: Review VSAN boundaries independently of physical switch and trunk connectivity. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. “Check each SAN port VSAN assignment before activating new production zones” would address that alternative cause, not the condition in this question: vSAN membership is incorrectly shared between isolation domains with different storage access requirements.

B:

“Document NPV versus NPIV responsibilities before configuring UCS and MDS fabric attachment” responds to this separate finding: nPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. This question instead needs “Review VSAN boundaries independently of physical switch and trunk connectivity”, so the alternative does not meet the stated condition.

D:

The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. “Review FCoE VLAN and lossless Ethernet prerequisites separately from ordinary LAN configuration” 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 28

A data center implementation team investigates the following fault: An unauthorized workstation sends IPv6 router advertisements on a Nexus access VLAN, causing nearby hosts to adopt an attacker-controlled default router. Which verification result most directly demonstrates successful repair?

  1. Hosts ignore the unauthorized router advertisement and retain the approved IPv6 default gateway.
  2. The approved HBA logs in while a test unapproved WWPN is rejected by the protected fabric port.
  3. Spoofed ARP replies are discarded while authorized clients retain normal gateway connectivity.
  4. Unauthorized DHCP offers are dropped while valid clients receive leases from the approved server.

Explanation

Correct Answer

A:

This observation validates ipv6 router advertisement guard: The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. The corresponding corrective action is: Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. “Configure supported MDS port-security bindings for the intended server initiator and affected VSAN” would address that alternative cause, not the condition in this question: the access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements.

C:

“Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings” responds to this separate finding: dHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. This question instead needs “Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports”, 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. “Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths” 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 29

During a Cisco data center readiness review, engineers observe: Two SAN-connected server profiles are provisioned with overlapping manually assigned virtual HBA worldwide port names, disrupting their distinct storage identities. Which deployment safeguard most directly reduces this failure risk?

  1. Revalidate target WWPN and LUN mappings after storage-controller failover or replacement.
  2. Validate failover semantics against the host operating system teaming configuration before production use.
  3. Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment.
  4. Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot.

Explanation

Correct Answer

C:

This safeguard addresses ucs wwpn pool uniqueness: The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. The appropriate prevention is: Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. “Revalidate target WWPN and LUN mappings after storage-controller failover or replacement” would address that alternative cause, not the condition in this question: the vHBA WWPN allocation violates uniqueness requirements across server storage initiators.

B:

“Validate failover semantics against the host operating system teaming configuration before production use” responds to this separate finding: the UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. This question instead needs “Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment”, so the alternative does not meet the stated condition.

D:

The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. “Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot” applies to that separate problem. The observed case is two SAN-connected server profiles are provisioned with overlapping manually assigned virtual HBA worldwide port names, disrupting their distinct storage identities; choosing this alternative would address the wrong failure mode.

Question 30

During a Cisco data center readiness review, engineers observe: An MDS maintenance team attempts a nondisruptive SAN switch upgrade while a required redundancy check and supported release-path validation are incomplete. What is the primary technical reason the deployment fails?

  1. The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends.
  2. The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image.
  3. The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites.
  4. The Fibre Channel SPAN session source does not identify the failing interface or service path.

Explanation

Correct Answer

C:

The technical cause is The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. The appropriate response is: Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method. Confirm successful repair: A lab or pilot establishes the expected outage characteristics and the approved upgrade completes safely.

Incorrect Answers

A:

The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. “Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis” 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:

“Review the applicable MDS EPLD package and schedule the correct supported component update” responds to this separate finding: the storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. 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.