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 19

Question 180

A data center administrator identifies the following risk: A newly installed blade chassis has power but its I/O modules and blades never appear under fabric-interconnect inventory after uplink cabling was changed. Which corrective change best resolves this problem?

  1. Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria.
  2. Repair the UCS fabric-interconnect cluster and management redundancy configuration and validate supported failover.
  3. Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis.
  4. Restore the supported boot policy and required SAN adapter path in the correct boot-device order.

Explanation

Correct Answer

C:

The root problem is that The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. The selected change addresses it directly: Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis. Verify the outcome: Both intended fabric paths enumerate the chassis and associated blades under UCS management.

Incorrect Answers

A:

This action concerns ucs disruptive firmware activation planning, where The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. The reported failure instead stems from The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured.

B:

This action concerns ucs fabric interconnect management failover, where The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior. The corrective response here is “Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis”; this alternative does not provide that response.

D:

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 stem reports a newly installed blade chassis has power but its I/O modules and blades never appear under fabric-interconnect inventory after uplink cabling was changed; this control addresses a different failure condition.

Question 181

A Nexus, UCS or MDS operations team encounters this issue: A running production blade is reassigned to a different UCS service profile without understanding reboot or identity-change consequences, interrupting applications. Which root cause best explains this behavior?

  1. The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy.
  2. The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings.
  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

B:

The technical cause is The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings. The appropriate response is: Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks. Confirm successful repair: The blade receives the intended policy identity after the controlled operation and applications recover as planned.

Incorrect Answers

A:

The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. “Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access” would address that alternative cause, not the condition in this question: the service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings.

C:

“Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend” responds to this separate finding: the monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. This question instead needs “Perform an approved service profile reassociation during maintenance with identity, boot and rollback checks”, 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 running production blade is reassigned to a different UCS service profile without understanding reboot or identity-change consequences, interrupting applications; choosing this alternative would address the wrong failure mode.

Question 182

A newly commissioned network, compute or storage service reports: A rack server must boot from an approved SAN LUN but repeatedly starts the local disk after a BIOS update changes its boot device priority. What is the primary technical reason the deployment fails?

  1. The Intersight device claim and account authorization do not match the approved administrative organization.
  2. The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured.
  3. The configured boot-device order does not select the intended SAN boot path before local storage.
  4. The CIMC management interface has incorrect IP addressing or missing management default gateway reachability.

Explanation

Correct Answer

C:

The technical cause is The configured boot-device order does not select the intended SAN boot path before local storage. The appropriate response is: Restore the supported boot policy and required SAN adapter path in the correct boot-device order. Confirm successful repair: A controlled reboot starts the server from the authorized SAN boot target and reaches the expected OS.

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 configured boot-device order does not select the intended SAN boot path before local storage.

B:

“Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis” responds to this separate finding: the chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. This question instead needs “Restore the supported boot policy and required SAN adapter path in the correct boot-device order”, so the alternative does not meet the stated condition.

D:

The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. “Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network” applies to that separate problem. The observed case is a rack server must boot from an approved SAN LUN but repeatedly starts the local disk after a BIOS update changes its boot device priority; choosing this alternative would address the wrong failure mode.

Question 183

A Nexus, UCS or MDS operations team encounters this issue: Two distribution switches provide HSRP default gateways, but the active switch continues answering for the virtual gateway after losing its only upstream path. Which test outcome proves the intended service was restored?

  1. The two routers establish an OSPFv3 Full adjacency and learn the expected IPv6 prefixes.
  2. The leaf receives the intended EVPN routes and remote workloads become reachable over VXLAN.
  3. Both peers reach Full state and exchange the intended routes without retransmission or MTU errors.
  4. After an uplink failure, the standby switch becomes active and application traffic uses its available upstream path.

Explanation

Correct Answer

D:

This observation validates hsrp uplink tracking failover: The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. The corresponding corrective action is: Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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

“Activate the correct EVPN address family for authorized peers and verify route advertisement policy” responds to this separate finding: the BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. This question instead needs “Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role”, so the alternative does not meet the stated condition.

C:

The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. “Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency” 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 184

While checking a production data center change, the team finds: 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 observation best confirms the configuration now behaves correctly?

  1. A controlled fabric failover retains authorized server network reachability without duplicate MAC or VLAN problems.
  2. The server HBA registers in the correct VSAN and discovers the authorized target storage port.
  3. The replacement blade identifies the intended LUN and completes a controlled SAN boot.
  4. All required vNICs receive unique authorized MAC addresses without conflicting with existing profiles.

Explanation

Correct Answer

C:

This observation validates ucs san boot target identifiers: The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. The corresponding corrective action is: Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. “Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design” 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:

“Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN” responds to this separate finding: the virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. This question instead needs “Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters”, so the alternative does not meet the stated condition.

D:

The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. “Expand or assign a nonoverlapping approved MAC pool and retry the service profile association” 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 185

A data center implementation team investigates the following fault: An infrastructure automation identity can edit server policies in several unrelated Intersight organizations even though it supports just one business unit. What preventive control would best avoid repeating this fault?

  1. Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes.
  2. Periodically audit Intersight role scopes and API account privileges for privilege creep.
  3. Test UCS AAA dependency failure without weakening audit and least-privilege controls.
  4. Recertify UCS role assignments after team or responsibility changes.

Explanation

Correct Answer

B:

This safeguard addresses intersight organization scoped administrative role: The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. The appropriate prevention is: Periodically audit Intersight role scopes and API account privileges for privilege creep. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. “Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes” would address that alternative cause, not the condition in this question: the Intersight role assignment is not scoped to the authorized organization and permitted resource actions.

C:

“Test UCS AAA dependency failure without weakening audit and least-privilege controls” responds to this separate finding: the UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. This question instead needs “Periodically audit Intersight role scopes and API account privileges for privilege creep”, so the alternative does not meet the stated condition.

D:

The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. “Recertify UCS role assignments after team or responsibility changes” applies to that separate problem. The observed case is an infrastructure automation identity can edit server policies in several unrelated Intersight organizations even though it supports just one business unit; choosing this alternative would address the wrong failure mode.

Question 186

While checking a production data center change, the team finds: 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. What is the primary technical reason the deployment fails?

  1. Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.
  2. The management access policy lacks a tested protected local recovery identity for remote AAA outages.
  3. The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring.
  4. The OSPF authentication peers are using mismatched active key IDs or validity intervals.

Explanation

Correct Answer

B:

The technical cause is The management access policy lacks a tested protected local recovery identity for remote AAA outages. The appropriate response is: Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions. Confirm successful repair: An authorized emergency operator can enter through the recovery path while normal remote AAA remains primary.

Incorrect Answers

A:

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 management access policy lacks a tested protected local recovery identity for remote AAA outages.

C:

“Correct the authorized TACACS command or role mapping without granting full switch administrator permissions” responds to this separate finding: the centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. This question instead needs “Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions”, so the alternative does not meet the stated condition.

D:

The OSPF authentication peers are using mismatched active key IDs or validity intervals. “Coordinate the supported authentication keychain parameters and overlapping key transition periods” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 187

A data center administrator identifies the following risk: Two Nexus routed neighbors stop forming OSPF adjacencies during key rotation because their configured keychain accept and send lifetimes do not overlap. Which test outcome proves the intended service was restored?

  1. The link shows an operational encrypted MACsec association and permitted traffic continues normally.
  2. The operator executes the designated monitoring commands while sensitive configuration changes remain denied.
  3. An authorized emergency operator can enter through the recovery path while normal remote AAA remains primary.
  4. The intended OSPF adjacency remains authenticated across the key-rotation window with old keys retired safely.

Explanation

Correct Answer

D:

This observation validates ospf keychain authentication rotation: The OSPF authentication peers are using mismatched active key IDs or validity intervals. The corresponding corrective action is: Coordinate the supported authentication keychain parameters and overlapping key transition periods. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. “Configure supported MACsec policy and secure key agreement on both authorized switch endpoints” would address that alternative cause, not the condition in this question: the OSPF authentication peers are using mismatched active key IDs or validity intervals.

B:

“Correct the authorized TACACS command or role mapping without granting full switch administrator permissions” responds to this separate finding: the centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. This question instead needs “Coordinate the supported authentication keychain parameters and overlapping key transition periods”, so the alternative does not meet the stated condition.

C:

The management access policy lacks a tested protected local recovery identity for remote AAA outages. “Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions” 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.

Question 188

A Nexus, UCS or MDS operations team encounters this issue: The team activates an I/O module and fabric-interconnect firmware change simultaneously without scheduling expected service impact for dependent blades. Which design or configuration error caused the described issue?

  1. The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints.
  2. The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites.
  3. The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow.
  4. The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture.

Explanation

Correct Answer

A:

The technical cause is The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. The appropriate response is: Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria. Confirm successful repair: The intended firmware versions activate while the measured service interruption remains within the planned window.

Incorrect Answers

B:

The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. “Select a compatible validated firmware package and update the affected server policy under change control” would address that alternative cause, not the condition in this question: the upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints.

C:

“Create or restore an authorized UCS configuration backup and validate the documented recovery procedure” responds to this separate finding: the UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. This question instead needs “Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria”, so the alternative does not meet the stated condition.

D:

The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. “Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies” applies to that separate problem. The observed case is the team activates an I/O module and fabric-interconnect firmware change simultaneously without scheduling expected service impact for dependent blades; choosing this alternative would address the wrong failure mode.

Question 189

A data center implementation team investigates the following fault: The underlay BGP neighbors are established, but a new VXLAN leaf does not exchange EVPN endpoint routes after its overlay session was commissioned. What is the most appropriate remediation for these symptoms?

  1. Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency.
  2. Activate the correct EVPN address family for authorized peers and verify route advertisement policy.
  3. Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role.
  4. Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups.

Explanation

Correct Answer

B:

The root problem is that The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. The selected change addresses it directly: Activate the correct EVPN address family for authorized peers and verify route advertisement policy. Verify the outcome: The leaf receives the intended EVPN routes and remote workloads become reachable over VXLAN.

Incorrect Answers

A:

This action concerns ospfv2 adjacency mtu mismatch, where The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. The reported failure instead stems from The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability.

C:

This action concerns hsrp uplink tracking failover, where The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. The corrective response here is “Activate the correct EVPN address family for authorized peers and verify route advertisement policy”; this alternative does not provide that response.

D:

This action concerns pim multicast rendezvous point reachability, where The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. The stem reports the underlay BGP neighbors are established, but a new VXLAN leaf does not exchange EVPN endpoint routes after its overlay session was commissioned; this control addresses a different failure condition.

Question 190

A newly commissioned network, compute or storage service reports: An engineer runs a Linux shell script inside the Nexus host environment and assumes it has the same dependencies and resource isolation as a supported Guest Shell container. What observation best confirms the configuration now behaves correctly?

  1. Repeated execution converges to the same desired configuration without unintended duplicate changes.
  2. The device returns a successful structured response and the intended read-only verification completes.
  3. A permitted API call succeeds while denied operations report a clear nonretryable authorization error.
  4. The script executes within its intended environment without changing unapproved host system files.

Explanation

Correct Answer

D:

This observation validates nexus bash shell and guest shell isolation: The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The corresponding corrective action is: Deploy the script in the approved supported shell environment with required dependencies and bounded permissions. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.

B:

“Send the supported NX-API request in the correct JSON or XML representation with matching headers” responds to this separate finding: the NX-API request body and declared content format are inconsistent for the selected endpoint. This question instead needs “Deploy the script in the approved supported shell environment with required dependencies and bounded permissions”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is an engineer runs a Linux shell script inside the Nexus host environment and assumes it has the same dependencies and resource isolation as a supported Guest Shell container; choosing this alternative would address the wrong failure mode.