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 5

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.

Question 41

While checking a production data center change, the team finds: An installed UCS blade becomes unreachable when the only mapped I/O module path is disabled although a second IOM is physically available. What technical condition most directly accounts for the failure?

  1. The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy.
  2. The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths.
  3. The configuration process bypasses the intended reusable UCS service profile template inheritance model.
  4. UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements.

Explanation

Correct Answer

B:

The technical cause is The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. The appropriate response is: Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior. Confirm successful repair: The blade retains expected connectivity under an individual fabric path outage within the approved design.

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 chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths.

C:

“Use an approved updating service profile template and apply governed changes to its associated server profiles” responds to this separate finding: the configuration process bypasses the intended reusable UCS service profile template inheritance model. This question instead needs “Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior”, 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 an installed UCS blade becomes unreachable when the only mapped I/O module path is disabled although a second IOM is physically available; choosing this alternative would address the wrong failure mode.

Question 42

A data center implementation team investigates the following fault: A remote tenant workload is connected to a leaf, yet peer VTEPs never learn the workload MAC address from the EVPN control plane. What is the most appropriate remediation for these symptoms?

  1. Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves.
  2. Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF.
  3. Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies.
  4. Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI.

Explanation

Correct Answer

D:

The root problem is that The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. The selected change addresses it directly: Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI. Verify the outcome: The remote leaf learns the intended endpoint MAC through a valid EVPN route and forwards frames correctly.

Incorrect Answers

A:

This action concerns vxlan vlan vni mapping consistency, where The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. The reported failure instead stems from The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy.

B:

This action concerns evpn ip prefix type five advertisement, where The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. The corrective response here is “Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI”; this alternative does not provide that response.

C:

This action concerns vxlan vtep loopback reachability, where The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. The stem reports a remote tenant workload is connected to a leaf, yet peer VTEPs never learn the workload MAC address from the EVPN control plane; this control addresses a different failure condition.

Question 43

A data center implementation team investigates the following fault: A new Fibre Channel port-channel member on MDS remains suspended after a technician applies the wrong VSAN trunk attributes to that physical interface. Which design or configuration error caused the described issue?

  1. The initiator has not completed successful fabric login and thus has no authorized FCID assignment.
  2. The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization.
  3. The FC trunk does not carry the required VSAN membership consistently between the two MDS switches.
  4. The FC port channel and prospective member disagree on required operational attributes for bundling.

Explanation

Correct Answer

D:

The technical cause is The FC port channel and prospective member disagree on required operational attributes for bundling. The appropriate response is: Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member. Confirm successful repair: Both members become operational in the port channel and load distribution remains stable.

Incorrect Answers

A:

The initiator has not completed successful fabric login and thus has no authorized FCID assignment. “Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator” 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.

B:

“Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process” responds to this separate finding: the Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. This question instead needs “Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member”, so the alternative does not meet the stated condition.

C:

The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. “Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status” 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 44

A data center implementation team investigates the following fault: Intermittent Fibre Channel congestion causes storage latency spikes, yet operators rely only on link-up indicators and miss buffer-credit or port-error trends. What ongoing validation should operations establish for this service?

  1. Require SAN path redundancy and release-matrix signoff before MDS firmware activation.
  2. Use capture scope and SAN data sensitivity review before activating port mirroring.
  3. Include EPLD impact and recovery planning when scheduling MDS component software updates.
  4. Review SAN health telemetry and alert thresholds after changes in storage workload patterns.

Explanation

Correct Answer

D:

This safeguard addresses nexus dashboard san performance assurance: The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. The appropriate prevention is: Review SAN health telemetry and alert thresholds after changes in storage workload patterns. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. “Require SAN path redundancy and release-matrix signoff before MDS firmware activation” would address that alternative cause, not the condition in this question: the SAN observability baseline does not collect relevant port performance metrics and historical assurance trends.

B:

“Use capture scope and SAN data sensitivity review before activating port mirroring” responds to this separate finding: the Fibre Channel SPAN session source does not identify the failing interface or service path. This question instead needs “Review SAN health telemetry and alert thresholds after changes in storage workload patterns”, so the alternative does not meet the stated condition.

C:

The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. “Include EPLD impact and recovery planning when scheduling MDS component software updates” applies to that separate problem. The observed case is intermittent Fibre Channel congestion causes storage latency spikes, yet operators rely only on link-up indicators and miss buffer-credit or port-error trends; choosing this alternative would address the wrong failure mode.

Question 45

A data center implementation team investigates the following fault: A replacement HBA connects to an open MDS F-port and can enter the SAN even though the port should accept only preauthorized initiator identities. Which test outcome proves the intended service was restored?

  1. The analyst inspects FCNS and port health but cannot activate or change production zonesets.
  2. Application sessions traverse the authorized EPG path and prohibited traffic remains blocked.
  3. The approved peer switch joins the SAN while a nonapproved test switch is denied fabric access.
  4. The approved HBA logs in while a test unapproved WWPN is rejected by the protected fabric port.

Explanation

Correct Answer

D:

This observation validates mds fibre channel port security binding: Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. The corresponding corrective action is: Configure supported MDS port-security bindings for the intended server initiator and affected VSAN. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. “Replace the overly broad MDS role with an approved read-only or scoped monitoring role” would address that alternative cause, not the condition in this question: fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.

B:

“Correct the ACI contract consumer-provider bindings and permit only the required application port” responds to this separate finding: the contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. This question instead needs “Configure supported MDS port-security bindings for the intended server initiator and affected VSAN”, so the alternative does not meet the stated condition.

C:

Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. “Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs” applies to that separate problem. The observed case is a replacement HBA connects to an open MDS F-port and can enter the SAN even though the port should accept only preauthorized initiator identities; choosing this alternative would address the wrong failure mode.

Question 46

While checking a production data center change, the team finds: An NX-OS switch loses a critical BGP peer, but an automated EEM diagnostic applet never runs because it listens for a different syslog message pattern. What is the primary technical reason the deployment fails?

  1. The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.
  2. The NX-API request body and declared content format are inconsistent for the selected endpoint.
  3. The embedded event manager event detector does not match the actual authorized BGP neighbor-down message.
  4. The NX-OS scheduler job timing is not aligned with the intended maintenance frequency.

Explanation

Correct Answer

C:

The technical cause is The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. The appropriate response is: Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event. Confirm successful repair: The applet runs only on the targeted peer-down event and preserves the expected diagnostic information.

Incorrect Answers

A:

The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. “Deploy the script in the approved supported shell environment with required dependencies and bounded permissions” would address that alternative cause, not the condition in this question: the embedded event manager event detector does not match the actual authorized BGP neighbor-down message.

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 “Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event”, so the alternative does not meet the stated condition.

D:

The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. “Set the supported scheduler job schedule to the approved daily interval and verify the associated command” applies to that separate problem. The observed case is an NX-OS switch loses a critical BGP peer, but an automated EEM diagnostic applet never runs because it listens for a different syslog message pattern; choosing this alternative would address the wrong failure mode.

Question 47

During a Cisco data center readiness review, engineers observe: A Python script sends a Nexus configuration request to NX-API but receives parsing errors because its payload is XML while the request declares JSON encoding. Which deployment safeguard most directly reduces this failure risk?

  1. Validate API schema and content-type handling before enabling configuration-changing requests.
  2. Audit scheduler job frequency and execution history after automation changes.
  3. Build explicit error classification and bounded retries into every infrastructure API client.
  4. Review EEM triggers and action privilege requirements whenever NX-OS log formats or releases change.

Explanation

Correct Answer

A:

This safeguard addresses nx api json content encoding: The NX-API request body and declared content format are inconsistent for the selected endpoint. The appropriate prevention is: Validate API schema and content-type handling before enabling configuration-changing requests. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. “Audit scheduler job frequency and execution history after automation changes” would address that alternative cause, not the condition in this question: the NX-API request body and declared content format are inconsistent for the selected endpoint.

C:

“Build explicit error classification and bounded retries into every infrastructure API client” responds to this separate finding: the REST client does not distinguish insufficient authorization from retryable transport or server errors. This question instead needs “Validate API schema and content-type handling before enabling configuration-changing requests”, so the alternative does not meet the stated condition.

D:

The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. “Review EEM triggers and action privilege requirements whenever NX-OS log formats or releases change” applies to that separate problem. The observed case is a Python script sends a Nexus configuration request to NX-API but receives parsing errors because its payload is XML while the request declares JSON encoding; choosing this alternative would address the wrong failure mode.

Question 48

A data center implementation team investigates the following fault: A scheduled Nexus configuration backup runs continuously instead of once nightly because the job's scheduler interval was entered with the wrong units. Which corrective change best resolves this problem?

  1. Set the supported scheduler job schedule to the approved daily interval and verify the associated command.
  2. Query existing NX-OS state before applying only the necessary authorized configuration differences.
  3. Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures.
  4. Send the supported NX-API request in the correct JSON or XML representation with matching headers.

Explanation

Correct Answer

A:

The root problem is that The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The selected change addresses it directly: Set the supported scheduler job schedule to the approved daily interval and verify the associated command. Verify the outcome: The backup executes at the intended time without repeated unnecessary administrative sessions.

Incorrect Answers

B:

This action concerns on box python safe idempotence, where The script lacks an idempotent precheck to compare desired and current network device state. The reported failure instead stems from The NX-OS scheduler job timing is not aligned with the intended maintenance frequency.

C:

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 “Set the supported scheduler job schedule to the approved daily interval and verify the associated command”; this alternative does not provide that response.

D:

This action concerns nx api json content encoding, where The NX-API request body and declared content format are inconsistent for the selected endpoint. The stem reports a scheduled Nexus configuration backup runs continuously instead of once nightly because the job's scheduler interval was entered with the wrong units; this control addresses a different failure condition.

Question 49

A Nexus, UCS or MDS operations team encounters this issue: A factory-default Nexus switch runs PowerOn Auto Provisioning but fetches a bootstrap configuration intended for a different rack due to an incorrect DHCP-supplied file path. Which design or configuration error caused the described issue?

  1. The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement.
  2. The REST client does not distinguish insufficient authorization from retryable transport or server errors.
  3. The NX-OS scheduler job timing is not aligned with the intended maintenance frequency.
  4. The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation.

Explanation

Correct Answer

A:

The technical cause is The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. The appropriate response is: Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity. Confirm successful repair: The switch downloads its own authorized initial configuration and registers in the intended management inventory.

Incorrect Answers

B:

The REST client does not distinguish insufficient authorization from retryable transport or server errors. “Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures” would address that alternative cause, not the condition in this question: the POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement.

C:

“Set the supported scheduler job schedule to the approved daily interval and verify the associated command” responds to this separate finding: the NX-OS scheduler job timing is not aligned with the intended maintenance frequency. This question instead needs “Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity”, so the alternative does not meet the stated condition.

D:

The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. “Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources” applies to that separate problem. The observed case is a factory-default Nexus switch runs PowerOn Auto Provisioning but fetches a bootstrap configuration intended for a different rack due to an incorrect DHCP-supplied file path; choosing this alternative would address the wrong failure mode.

Question 50

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. 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. Use an approved updating service profile template and apply governed changes to its associated server profiles.
  3. Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis.
  4. Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network.

Explanation

Correct Answer

A:

The root problem is that The configured boot-device order does not select the intended SAN boot path before local storage. The selected change addresses it directly: Restore the supported boot policy and required SAN adapter path in the correct boot-device order. Verify the outcome: A controlled reboot starts the server from the authorized SAN boot target and reaches the expected OS.

Incorrect Answers

B:

This action concerns ucs updating service profile templates, where The configuration process bypasses the intended reusable UCS service profile template inheritance model. The reported failure instead stems from The configured boot-device order does not select the intended SAN boot path before local storage.

C:

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 corrective response here is “Restore the supported boot policy and required SAN adapter path in the correct boot-device order”; this alternative does not provide that response.

D:

This action concerns ucs c series cimc management networking, where The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. The stem reports 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; this control addresses a different failure condition.