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 38

Question 370

A data center administrator identifies the following risk: A blade replacement is delayed because the team assumes MAC addresses and server identities must remain bound to the failed physical blade. What preventive control would best avoid repeating this fault?

  1. Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment.
  2. Maintain service profile templates and identity pools independent of individual server serial numbers.
  3. Validate failover semantics against the host operating system teaming configuration before production use.
  4. Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot.

Explanation

Correct Answer

B:

This safeguard addresses ucs service profile server identity: The server identity has not been abstracted through approved UCS service profile and identity-pool associations. The appropriate prevention is: Maintain service profile templates and identity pools independent of individual server serial numbers. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. “Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment” would address that alternative cause, not the condition in this question: the server identity has not been abstracted through approved UCS service profile and identity-pool associations.

C:

“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 “Maintain service profile templates and identity pools independent of individual server serial numbers”, 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 a blade replacement is delayed because the team assumes MAC addresses and server identities must remain bound to the failed physical blade; choosing this alternative would address the wrong failure mode.

Question 371

A data center administrator identifies the following risk: A new Fibre Channel port-channel member on MDS remains suspended after a technician applies the wrong VSAN trunk attributes to that physical interface. What ongoing validation should operations establish for this service?

  1. Use standardized single-initiator zoning patterns in the SAN access request process.
  2. Include FC port-channel member parameter checks in redundant SAN link commissioning.
  3. Validate domain IDs and fabric merge compatibility before joining independently built SAN fabrics.
  4. Audit VSAN allow-lists and operational trunk membership when adding Fibre Channel ISLs.

Explanation

Correct Answer

B:

This safeguard addresses fibre channel port channel member consistency: The FC port channel and prospective member disagree on required operational attributes for bundling. The appropriate prevention is: Include FC port-channel member parameter checks in redundant SAN link commissioning. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The zone combines initiators beyond the least-privilege single-initiator zoning design. “Use standardized single-initiator zoning patterns in the SAN access request process” would address that alternative cause, not the condition in this question: the FC port channel and prospective member disagree on required operational attributes for bundling.

C:

“Validate domain IDs and fabric merge compatibility before joining independently built SAN fabrics” responds to this separate finding: the Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. This question instead needs “Include FC port-channel member parameter checks in redundant SAN link commissioning”, so the alternative does not meet the stated condition.

D:

The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. “Audit VSAN allow-lists and operational trunk membership when adding Fibre Channel ISLs” applies to that separate problem. The observed case is a new Fibre Channel port-channel member on MDS remains suspended after a technician applies the wrong VSAN trunk attributes to that physical interface; choosing this alternative would address the wrong failure mode.

Question 372

A newly commissioned network, compute or storage service reports: An orchestration script provisions a UCS server through Intersight but associates an unapproved boot policy because it selects objects by an ambiguous display name. Which implementation action should the engineer take first?

  1. Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources.
  2. Update the governed Nexus Dashboard fabric configuration intent and deploy through the supported workflow.
  3. Move credentials to a supported secret store and use a scoped authorized API identity for PowerShell requests.
  4. Use stable approved resource IDs and validate organization scope before assigning Intersight policies.

Explanation

Correct Answer

D:

The root problem is that The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. The selected change addresses it directly: Use stable approved resource IDs and validate organization scope before assigning Intersight policies. Verify the outcome: The target server profile references the expected boot and connectivity policies with no cross-tenant linkage.

Incorrect Answers

A:

This action concerns terraform plan infrastructure drift, where The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. The reported failure instead stems from The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association.

B:

This action concerns nexus dashboard intent orchestration consistency, where Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. The corrective response here is “Use stable approved resource IDs and validate organization scope before assigning Intersight policies”; this alternative does not provide that response.

C:

This action concerns powershell rest secure credentials, where The automation credential is stored insecurely and grants broader privileges than the script requires. The stem reports an orchestration script provisions a UCS server through Intersight but associates an unapproved boot policy because it selects objects by an ambiguous display name; this control addresses a different failure condition.

Question 373

A data center implementation team investigates the following fault: A new stateless UCS blade service profile has its boot policy set to a retired target WWPN, so the host never discovers the correct boot LUN. What ongoing validation should operations establish for this service?

  1. Validate failover semantics against the host operating system teaming configuration before production use.
  2. Maintain service profile templates and identity pools independent of individual server serial numbers.
  3. Revalidate target WWPN and LUN mappings after storage-controller failover or replacement.
  4. Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment.

Explanation

Correct Answer

C:

This safeguard addresses ucs san boot target identifiers: The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. The appropriate prevention is: Revalidate target WWPN and LUN mappings after storage-controller failover or replacement. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. “Validate failover semantics against the host operating system teaming configuration before production use” would address that alternative cause, not the condition in this question: the SAN boot policy refers to an unavailable storage target identity rather than the authorized active target.

B:

“Maintain service profile templates and identity pools independent of individual server serial numbers” responds to this separate finding: the server identity has not been abstracted through approved UCS service profile and identity-pool associations. This question instead needs “Revalidate target WWPN and LUN mappings after storage-controller failover or replacement”, so the alternative does not meet the stated condition.

D:

The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. “Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment” applies to that separate problem. The observed case is a new stateless UCS blade service profile has its boot policy set to a retired target WWPN, so the host never discovers the correct boot LUN; choosing this alternative would address the wrong failure mode.

Question 374

While checking a production data center change, the team finds: An external service subnet must be reached through an EVPN VXLAN fabric, but peer leaves learn endpoint MACs without the expected IP prefix route. What technical condition most directly accounts for the failure?

  1. The change process omitted a recoverable NX-OS configuration checkpoint and validation plan.
  2. The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs.
  3. The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy.
  4. The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route.

Explanation

Correct Answer

D:

The technical cause is The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. The appropriate response is: Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF. Confirm successful repair: Remote VTEPs learn the required IP prefix in the correct VRF and forward traffic toward its reachable next hop.

Incorrect Answers

A:

The change process omitted a recoverable NX-OS configuration checkpoint and validation plan. “Create and use a supported configuration checkpoint or approved rollback before editing the production policy” would address that alternative cause, not the condition in this question: the routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route.

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 “Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF”, so the alternative does not meet the stated condition.

C:

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 an external service subnet must be reached through an EVPN VXLAN fabric, but peer leaves learn endpoint MACs without the expected IP prefix route; choosing this alternative would address the wrong failure mode.

Question 375

A data center implementation team investigates the following fault: A server NIC connects to an ACI leaf port, but the configured EPG never becomes operational on that port after the tenant was deployed. What preventive control would best avoid repeating this fault?

  1. Validate leaf interface selectors, domains and EPG paths together in access-policy reviews.
  2. Monitor flow exporter reachability and collector acceptance after telemetry network changes.
  3. Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes.
  4. Maintain a documented node-ID and cabling approval process for new ACI leaf introductions.

Explanation

Correct Answer

A:

This safeguard addresses aci access policy interface selector binding: The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. The appropriate prevention is: Validate leaf interface selectors, domains and EPG paths together in access-policy reviews. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

Flow-export destination reachability or the configured source and monitoring VRF are incorrect. “Monitor flow exporter reachability and collector acceptance after telemetry network changes” would address that alternative cause, not the condition in this question: the interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.

C:

“Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes” responds to this separate finding: the ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. This question instead needs “Validate leaf interface selectors, domains and EPG paths together in access-policy reviews”, so the alternative does not meet the stated condition.

D:

The leaf has not completed the supported ACI fabric discovery and node-registration workflow. “Maintain a documented node-ID and cabling approval process for new ACI leaf introductions” applies to that separate problem. The observed case is a server NIC connects to an ACI leaf port, but the configured EPG never becomes operational on that port after the tenant was deployed; choosing this alternative would address the wrong failure mode.

Question 376

A newly commissioned network, compute or storage service reports: Two Nexus switches share an OSPFv2 segment, but their neighbors remain stuck in ExStart immediately after one uplink was changed to a larger MTU. After remediation, which acceptance result is most relevant?

  1. After an uplink failure, the standby switch becomes active and application traffic uses its available upstream path.
  2. The intended receivers join and receive source traffic, and PIM control state shows the proper tree.
  3. The two routers establish an OSPFv3 Full adjacency and learn the expected IPv6 prefixes.
  4. Both peers reach Full state and exchange the intended routes without retransmission or MTU errors.

Explanation

Correct Answer

D:

This observation validates ospfv2 adjacency mtu mismatch: The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. The corresponding corrective action is: Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. “Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role” would address that alternative cause, not the condition in this question: the neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably.

B:

“Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups” 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 “Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency”, so the alternative does not meet the stated condition.

C:

The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. “Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation” applies to that separate problem. The observed case is two Nexus switches share an OSPFv2 segment, but their neighbors remain stuck in ExStart immediately after one uplink was changed to a larger MTU; choosing this alternative would address the wrong failure mode.

Question 377

A Nexus, UCS or MDS operations team encounters this issue: Two Nexus routed neighbors stop forming OSPF adjacencies during key rotation because their configured keychain accept and send lifetimes do not overlap. Which corrective change best resolves this problem?

  1. Coordinate the supported authentication keychain parameters and overlapping key transition periods.
  2. Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs.
  3. Replace the overly broad MDS role with an approved read-only or scoped monitoring role.
  4. Configure supported MACsec policy and secure key agreement on both authorized switch endpoints.

Explanation

Correct Answer

A:

The root problem is that The OSPF authentication peers are using mismatched active key IDs or validity intervals. The selected change addresses it directly: Coordinate the supported authentication keychain parameters and overlapping key transition periods. Verify the outcome: The intended OSPF adjacency remains authenticated across the key-rotation window with old keys retired safely.

Incorrect Answers

B:

This action concerns mds fibre channel fabric binding, where Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. The reported failure instead stems from The OSPF authentication peers are using mismatched active key IDs or validity intervals.

C:

This action concerns cisco mds administrative role authorization, where The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. The corrective response here is “Coordinate the supported authentication keychain parameters and overlapping key transition periods”; this alternative does not provide that response.

D:

This action concerns macsec encrypted inter switch links, where Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. The stem reports two Nexus routed neighbors stop forming OSPF adjacencies during key rotation because their configured keychain accept and send lifetimes do not overlap; this control addresses a different failure condition.

Question 378

While checking a production data center change, the team finds: A UCS service profile contains the correct vNIC VLAN, but the upstream fabric interconnect uplink does not carry the server's new application VLAN. Which operational guardrail would prevent a similar outage?

  1. Reconcile UCS VLAN definitions with upstream trunk allow-lists during every server network expansion.
  2. Verify CIMC routing, management segmentation and administrator access at rack-server acceptance.
  3. Inspect chassis IOM inventory and dual-fabric paths during blade server deployment.
  4. Review template association and change propagation before broad UCS configuration updates.

Explanation

Correct Answer

A:

This safeguard addresses ucs vlan uplink permitted configuration: The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. The appropriate prevention is: Reconcile UCS VLAN definitions with upstream trunk allow-lists during every server network expansion. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. “Verify CIMC routing, management segmentation and administrator access at rack-server acceptance” would address that alternative cause, not the condition in this question: the VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy.

C:

“Inspect chassis IOM inventory and dual-fabric paths during blade server deployment” responds to this separate finding: the chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. This question instead needs “Reconcile UCS VLAN definitions with upstream trunk allow-lists during every server network expansion”, so the alternative does not meet the stated condition.

D:

The configuration process bypasses the intended reusable UCS service profile template inheritance model. “Review template association and change propagation before broad UCS configuration updates” applies to that separate problem. The observed case is a UCS service profile contains the correct vNIC VLAN, but the upstream fabric interconnect uplink does not carry the server's new application VLAN; choosing this alternative would address the wrong failure mode.

Question 379

A data center implementation team investigates the following fault: A UCS service profile requires a newer adapter firmware feature, but the applied host firmware package omits the compatible adapter release. What ongoing validation should operations establish for this service?

  1. Pilot the firmware sequence and test fabric redundancy before simultaneous domain-wide activation.
  2. Verify CIMC routing, management segmentation and administrator access at rack-server acceptance.
  3. Schedule encrypted UCS configuration backups and perform periodic isolated restore tests.
  4. Check platform and adapter compatibility matrices before changing UCS host firmware policies.

Explanation

Correct Answer

D:

This safeguard addresses ucs firmware policy package compatibility: The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. The appropriate prevention is: Check platform and adapter compatibility matrices before changing UCS host firmware policies. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. “Pilot the firmware sequence and test fabric redundancy before simultaneous domain-wide activation” would address that alternative cause, not the condition in this question: the effective UCS host firmware package is inconsistent with the server adapter feature prerequisites.

B:

“Verify CIMC routing, management segmentation and administrator access at rack-server acceptance” responds to this separate finding: the CIMC management interface has incorrect IP addressing or missing management default gateway reachability. This question instead needs “Check platform and adapter compatibility matrices before changing UCS host firmware policies”, so the alternative does not meet the stated condition.

C:

The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. “Schedule encrypted UCS configuration backups and perform periodic isolated restore tests” applies to that separate problem. The observed case is a UCS service profile requires a newer adapter firmware feature, but the applied host firmware package omits the compatible adapter release; choosing this alternative would address the wrong failure mode.

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.