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 4

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.

Question 31

During a Cisco data center readiness review, engineers observe: Voice-processing virtual machines on UCS blades traverse a shared adapter, but their traffic is treated as best effort because the UCS class settings do not match the approved policy. Which approved technology action addresses this incident most directly?

  1. Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior.
  2. Use an approved updating service profile template and apply governed changes to its associated server profiles.
  3. Correct the supported UCS class-of-service and network QoS policy for the intended application traffic.
  4. Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access.

Explanation

Correct Answer

C:

The root problem is that UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements. The selected change addresses it directly: Correct the supported UCS class-of-service and network QoS policy for the intended application traffic. Verify the outcome: Authorized real-time flows receive the designated priority treatment and bulk traffic retains its separate class.

Incorrect Answers

A:

This action concerns ucs chassis iom fabric path redundancy, where The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. The reported failure instead stems from UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements.

B:

This action concerns ucs updating service profile templates, where The configuration process bypasses the intended reusable UCS service profile template inheritance model. The corrective response here is “Correct the supported UCS class-of-service and network QoS policy for the intended application traffic”; this alternative does not provide that response.

D:

This action concerns ucs vlan uplink permitted configuration, where The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. The stem reports voice-processing virtual machines on UCS blades traverse a shared adapter, but their traffic is treated as best effort because the UCS class settings do not match the approved policy; this control addresses a different failure condition.

Question 32

A data center administrator identifies the following risk: 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. Which corrective change best resolves this problem?

  1. Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity.
  2. Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution.
  3. Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources.
  4. Use stable approved resource IDs and validate organization scope before assigning Intersight policies.

Explanation

Correct Answer

C:

The root problem is that The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. The selected change addresses it directly: Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources. Verify the outcome: The approved plan makes intended changes and leaves unrelated network resources intact.

Incorrect Answers

A:

This action concerns poap initial provisioning ownership, where The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. The reported failure instead stems from The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation.

B:

This action concerns ansible inventory variable scoping, where The playbook target inventory and variable precedence do not isolate the intended lab device group. The corrective response here is “Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources”; this alternative does not provide that response.

D:

This action concerns intersight api server policy automation, where The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. The stem reports 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; this control addresses a different failure condition.

Question 33

A Nexus, UCS or MDS operations team encounters this issue: A storage administrator is given a full UCS administrator role even though the job requires only SAN and vHBA policy visibility. Which design or configuration error caused the described issue?

  1. The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path.
  2. The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities.
  3. The OSPF authentication peers are using mismatched active key IDs or validity intervals.
  4. The Intersight role assignment is not scoped to the authorized organization and permitted resource actions.

Explanation

Correct Answer

B:

The technical cause is The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. The appropriate response is: Assign a supported restricted UCS role and scope matching the storage administration tasks. Confirm successful repair: The user can inspect authorized SAN settings but cannot change unrelated server identity and LAN policies.

Incorrect Answers

A:

The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. “Correct the supported UCS authentication realm order and emergency access procedure under change control” would address that alternative cause, not the condition in this question: the UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities.

C:

“Coordinate the supported authentication keychain parameters and overlapping key transition periods” responds to this separate finding: the OSPF authentication peers are using mismatched active key IDs or validity intervals. This question instead needs “Assign a supported restricted UCS role and scope matching the storage administration tasks”, so the alternative does not meet the stated condition.

D:

The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. “Apply the approved organization-scoped Intersight RBAC role for the automation identity” applies to that separate problem. The observed case is a storage administrator is given a full UCS administrator role even though the job requires only SAN and vHBA policy visibility; choosing this alternative would address the wrong failure mode.

Question 34

A data center administrator identifies the following risk: Multicast video receivers remain connected at layer two, but group membership ages out because there is no active IGMP querier in their VLAN. What preventive control would best avoid repeating this fault?

  1. Document SPAN source and destination interface restrictions for troubleshooting changes.
  2. Require a NIST model classification review during cloud migration architecture approvals.
  3. Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover.
  4. Confirm querier presence and snooping tables in every multicast-capable access VLAN.

Explanation

Correct Answer

D:

This safeguard addresses igmp snooping querier requirement: IGMP snooping membership state is not refreshed because the VLAN lacks a reachable supported multicast querier. The appropriate prevention is: Confirm querier presence and snooping tables in every multicast-capable access VLAN. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

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 VLAN lacks a reachable supported multicast querier.

B:

“Require a NIST model classification review during cloud migration architecture approvals” responds to this separate finding: cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. This question instead needs “Confirm querier presence and snooping tables in every multicast-capable access VLAN”, so the alternative does not meet the stated condition.

C:

The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. “Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover” applies to that separate problem. The observed case is multicast video receivers remain connected at layer two, but group membership ages out because there is no active IGMP querier in their VLAN; choosing this alternative would address the wrong failure mode.

Question 35

A data center administrator identifies the following risk: Two workloads in a shared ACI subnet require different policies, but both inherit the same broad EPG because no microsegmentation attributes are matched. What ongoing validation should operations establish for this service?

  1. Stage keychain changes and check device time synchronization before routing-authentication rotation.
  2. Review uSeg classification stability during virtual machine moves and tag changes.
  3. Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added.
  4. Test both allowed and denied EPG flows after modifying any ACI contracts or filters.

Explanation

Correct Answer

B:

This safeguard addresses aci microsegmentation useg classification: The intended microsegmentation EPG classification rules do not distinguish the workload identities. The appropriate prevention is: Review uSeg classification stability during virtual machine moves and tag changes. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The OSPF authentication peers are using mismatched active key IDs or validity intervals. “Stage keychain changes and check device time synchronization before routing-authentication rotation” would address that alternative cause, not the condition in this question: the intended microsegmentation EPG classification rules do not distinguish the workload identities.

C:

“Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added” 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 “Review uSeg classification stability during virtual machine moves and tag changes”, so the alternative does not meet the stated condition.

D:

The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. “Test both allowed and denied EPG flows after modifying any ACI contracts or filters” applies to that separate problem. The observed case is two workloads in a shared ACI subnet require different policies, but both inherit the same broad EPG because no microsegmentation attributes are matched; choosing this alternative would address the wrong failure mode.

Question 36

During a Cisco data center readiness review, engineers observe: Two Nexus switches share an OSPFv2 segment, but their neighbors remain stuck in ExStart immediately after one uplink was changed to a larger MTU. What is the primary technical reason the deployment fails?

  1. The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability.
  2. The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range.
  3. The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link.
  4. The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably.

Explanation

Correct Answer

D:

The technical cause is The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. The appropriate response is: Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency. Confirm successful repair: Both peers reach Full state and exchange the intended routes without retransmission or MTU errors.

Incorrect Answers

A:

The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. “Activate the correct EVPN address family for authorized peers and verify route advertisement policy” 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 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” 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 37

During a Cisco data center readiness review, engineers observe: A data center hypervisor installation fails hardware virtualization preflight on otherwise compatible UCS blades after a generic BIOS profile disabled virtualization features. What observation best confirms the configuration now behaves correctly?

  1. The hypervisor passes hardware virtualization checks and starts a test virtual machine successfully.
  2. The intended firmware versions activate while the measured service interruption remains within the planned window.
  3. The blade receives the intended policy identity after the controlled operation and applications recover as planned.
  4. The server recognizes the protected boot volume and tolerates the documented single-disk test condition.

Explanation

Correct Answer

A:

This observation validates ucs bios virtualization extensions: The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. The corresponding corrective action is: Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. “Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria” would address that alternative cause, not the condition in this question: the BIOS policy disables required CPU virtualization support expected by the approved hypervisor.

C:

“Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks” responds to this separate finding: the service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings. This question instead needs “Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot”, so the alternative does not meet the stated condition.

D:

The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. “Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it” applies to that separate problem. The observed case is a data center hypervisor installation fails hardware virtualization preflight on otherwise compatible UCS blades after a generic BIOS profile disabled virtualization features; choosing this alternative would address the wrong failure mode.

Question 38

A newly commissioned network, compute or storage service reports: A UCS service profile contains the correct vNIC VLAN, but the upstream fabric interconnect uplink does not carry the server's new application VLAN. After remediation, which acceptance result is most relevant?

  1. All attached eligible blades receive consistent policy changes with documented exceptions and maintenance impact.
  2. The guest and external hosts exchange traffic over the authorized VLAN on both supported fabric paths.
  3. The profile associates only with hardware satisfying its documented adapter and compute requirements.
  4. Authorized real-time flows receive the designated priority treatment and bulk traffic retains its separate class.

Explanation

Correct Answer

B:

This observation validates ucs vlan uplink permitted configuration: The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. The corresponding corrective action is: Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The configuration process bypasses the intended reusable UCS service profile template inheritance model. “Use an approved updating service profile template and apply governed changes to its associated server profiles” 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:

“Create the supported UCS server pool qualification and associate the workload profile with eligible members” responds to this separate finding: the server pool qualification policy does not limit placement to servers with the required hardware capabilities. This question instead needs “Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access”, so the alternative does not meet the stated condition.

D:

UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements. “Correct the supported UCS class-of-service and network QoS policy for the intended application traffic” 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 39

A data center implementation team investigates the following fault: A UCS X-Series chassis is onboarded with a legacy UCS Manager policy workflow that does not provide the supported Intersight-managed server configuration model. What ongoing validation should operations establish for this service?

  1. Verify the supported UCS generation and management mode before migrating service policies.
  2. Review Intersight target claims and account lifecycle as part of server ownership transfers.
  3. Run Intersight profile validation and dependency checks before assigning profiles to production servers.
  4. Maintain service profile templates and identity pools independent of individual server serial numbers.

Explanation

Correct Answer

A:

This safeguard addresses ucs x series intersight managed mode: The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. The appropriate prevention is: Verify the supported UCS generation and management mode before migrating service policies. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The Intersight device claim and account authorization do not match the approved administrative organization. “Review Intersight target claims and account lifecycle as part of server ownership transfers” would address that alternative cause, not the condition in this question: the platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture.

C:

“Run Intersight profile validation and dependency checks before assigning profiles to production servers” responds to this separate finding: the Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies. This question instead needs “Verify the supported UCS generation and management mode before migrating service policies”, so the alternative does not meet the stated condition.

D:

The server identity has not been abstracted through approved UCS service profile and identity-pool associations. “Maintain service profile templates and identity pools independent of individual server serial numbers” applies to that separate problem. The observed case is a UCS X-Series chassis is onboarded with a legacy UCS Manager policy workflow that does not provide the supported Intersight-managed server configuration model; choosing this alternative would address the wrong failure mode.

Question 40

During a Cisco data center readiness review, engineers observe: Two Nexus routed neighbors stop forming OSPF adjacencies during key rotation because their configured keychain accept and send lifetimes do not overlap. Which operational guardrail would prevent a similar outage?

  1. Review uSeg classification stability during virtual machine moves and tag changes.
  2. Stage keychain changes and check device time synchronization before routing-authentication rotation.
  3. Test IPv6 first-hop security along with DHCP and ARP controls during access-switch turnup.
  4. Monitor MACsec security associations and key rotation without assuming link-up equals encryption.

Explanation

Correct Answer

B:

This safeguard addresses ospf keychain authentication rotation: The OSPF authentication peers are using mismatched active key IDs or validity intervals. The appropriate prevention is: Stage keychain changes and check device time synchronization before routing-authentication rotation. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The intended microsegmentation EPG classification rules do not distinguish the workload identities. “Review uSeg classification stability during virtual machine moves and tag changes” would address that alternative cause, not the condition in this question: the OSPF authentication peers are using mismatched active key IDs or validity intervals.

C:

“Test IPv6 first-hop security along with DHCP and ARP controls during access-switch turnup” responds to this separate finding: the access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. This question instead needs “Stage keychain changes and check device time synchronization before routing-authentication rotation”, so the alternative does not meet the stated condition.

D:

Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. “Monitor MACsec security associations and key rotation without assuming link-up equals encryption” applies to that separate problem. The observed case is two Nexus routed neighbors stop forming OSPF adjacencies during key rotation because their configured keychain accept and send lifetimes do not overlap; choosing this alternative would address the wrong failure mode.