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 23

Question 220

A data center implementation team investigates the following fault: A new Cisco UCS C-Series rack server boots its operating system, yet the remote administrators cannot access CIMC because the out-of-band address is on an unreachable subnet. Which design or configuration error caused the described issue?

  1. The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths.
  2. The CIMC management interface has incorrect IP addressing or missing management default gateway reachability.
  3. The configured boot-device order does not select the intended SAN boot path before local storage.
  4. The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured.

Explanation

Correct Answer

B:

The technical cause is The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. The appropriate response is: Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network. Confirm successful repair: Authorized operators can open CIMC over the management path without exposing it on the application data plane.

Incorrect Answers

A:

The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. “Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior” would address that alternative cause, not the condition in this question: the CIMC management interface has incorrect IP addressing or missing management default gateway reachability.

C:

“Restore the supported boot policy and required SAN adapter path in the correct boot-device order” responds to this separate finding: the configured boot-device order does not select the intended SAN boot path before local storage. This question instead needs “Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network”, so the alternative does not meet the stated condition.

D:

The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. “Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis” applies to that separate problem. The observed case is a new Cisco UCS C-Series rack server boots its operating system, yet the remote administrators cannot access CIMC because the out-of-band address is on an unreachable subnet; choosing this alternative would address the wrong failure mode.

Question 221

While checking a production data center change, the team finds: A Nexus on-box Python remediation applet recreates the same VLAN and interface objects every run, producing repeated configuration changes even when state is already correct. Which deployment safeguard most directly reduces this failure risk?

  1. Document shell boundaries and supported packages before on-box automation deployment.
  2. Audit scheduler job frequency and execution history after automation changes.
  3. Validate API schema and content-type handling before enabling configuration-changing requests.
  4. Test rerun behavior and configuration diffs before scheduling on-box Python automation.

Explanation

Correct Answer

D:

This safeguard addresses on box python safe idempotence: The script lacks an idempotent precheck to compare desired and current network device state. The appropriate prevention is: Test rerun behavior and configuration diffs before scheduling on-box Python automation. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. “Document shell boundaries and supported packages before on-box automation deployment” would address that alternative cause, not the condition in this question: the script lacks an idempotent precheck to compare desired and current network device state.

B:

“Audit scheduler job frequency and execution history after automation changes” responds to this separate finding: the NX-OS scheduler job timing is not aligned with the intended maintenance frequency. This question instead needs “Test rerun behavior and configuration diffs before scheduling on-box Python automation”, so the alternative does not meet the stated condition.

C:

The NX-API request body and declared content format are inconsistent for the selected endpoint. “Validate API schema and content-type handling before enabling configuration-changing requests” applies to that separate problem. The observed case is a Nexus on-box Python remediation applet recreates the same VLAN and interface objects every run, producing repeated configuration changes even when state is already correct; choosing this alternative would address the wrong failure mode.

Question 222

A Nexus, UCS or MDS operations team encounters this issue: A Nexus pair is scheduled for supposedly hitless software maintenance even though the target release does not support nondisruptive upgrade for the active feature combination. Which test outcome proves the intended service was restored?

  1. The device returns to the known-good configuration with traffic restored after rollback is exercised.
  2. A staged test establishes the actual traffic impact and the upgrade follows the approved compatibility plan.
  3. The host VLAN remains reachable through either peer after a simulated downstream member failure.
  4. Hardware and software component versions match the approved release prerequisites after controlled maintenance.

Explanation

Correct Answer

B:

This observation validates nx os issu support preflight: The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. The corresponding corrective action is: Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path. Evidence about a different component does not establish the requested service outcome.

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 upgrade plan assumes ISSU support without validating the platform release path and active feature constraints.

C:

“Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms” responds to this separate finding: the vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. This question instead needs “Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path”, so the alternative does not meet the stated condition.

D:

The planned software transition omits the EPLD compatibility and operational impact assessment. “Review supported EPLD package requirements and schedule the component update using the prescribed procedure” applies to that separate problem. The observed case is a Nexus pair is scheduled for supposedly hitless software maintenance even though the target release does not support nondisruptive upgrade for the active feature combination; choosing this alternative would address the wrong failure mode.

Question 223

While checking a production data center change, the team finds: A Nexus operations user can authenticate through TACACS but cannot view the needed interface health command because the returned role is below the approved monitoring privilege level. Which implementation action should the engineer take first?

  1. Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports.
  2. Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions.
  3. Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings.
  4. Correct the authorized TACACS command or role mapping without granting full switch administrator permissions.

Explanation

Correct Answer

D:

The root problem is that The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. The selected change addresses it directly: Correct the authorized TACACS command or role mapping without granting full switch administrator permissions. Verify the outcome: The operator executes the designated monitoring commands while sensitive configuration changes remain denied.

Incorrect Answers

A:

This action concerns ipv6 router advertisement guard, where The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. The reported failure instead stems from The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring.

B:

This action concerns nx os local emergency account control, where The management access policy lacks a tested protected local recovery identity for remote AAA outages. The corrective response here is “Correct the authorized TACACS command or role mapping without granting full switch administrator permissions”; this alternative does not provide that response.

C:

This action concerns dynamic arp inspection binding validation, where DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. The stem reports a Nexus operations user can authenticate through TACACS but cannot view the needed interface health command because the returned role is below the approved monitoring privilege level; this control addresses a different failure condition.

Question 224

A Nexus, UCS or MDS operations team encounters this issue: An AI training fabric uses RoCEv2 GPU collective traffic, but bursts are repeatedly dropped because the Ethernet switches lack the supported priority flow-control and congestion management plan. Which root cause best explains this behavior?

  1. The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards.
  2. The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement.
  3. The REST client does not distinguish insufficient authorization from retryable transport or server errors.
  4. The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload.

Explanation

Correct Answer

A:

The technical cause is The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. The appropriate response is: Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path. Confirm successful repair: The GPU fabric sustains the benchmark workload with controlled loss and congestion indicators during bursts.

Incorrect Answers

B:

The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. “Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity” would address that alternative cause, not the condition in this question: the RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards.

C:

“Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures” responds to this separate finding: the REST client does not distinguish insufficient authorization from retryable transport or server errors. This question instead needs “Evaluate supported PFC and ECN settings for the RDMA class and validate them across the intended switch path”, so the alternative does not meet the stated condition.

D:

The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload. “Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology” applies to that separate problem. The observed case is an AI training fabric uses RoCEv2 GPU collective traffic, but bursts are repeatedly dropped because the Ethernet switches lack the supported priority flow-control and congestion management plan; choosing this alternative would address the wrong failure mode.

Question 225

During a Cisco data center readiness review, engineers observe: A regulated east-west inter-switch link must protect Ethernet frames in transit, but an approved MACsec session is absent even though the physical port is up. What is the primary technical reason the deployment fails?

  1. Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL.
  2. The intended microsegmentation EPG classification rules do not distinguish the workload identities.
  3. Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection.
  4. The OSPF authentication peers are using mismatched active key IDs or validity intervals.

Explanation

Correct Answer

C:

The technical cause is Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. The appropriate response is: Configure supported MACsec policy and secure key agreement on both authorized switch endpoints. Confirm successful repair: The link shows an operational encrypted MACsec association and permitted traffic continues normally.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection.

B:

“Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads” responds to this separate finding: the intended microsegmentation EPG classification rules do not distinguish the workload identities. This question instead needs “Configure supported MACsec policy and secure key agreement on both authorized switch endpoints”, 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 regulated east-west inter-switch link must protect Ethernet frames in transit, but an approved MACsec session is absent even though the physical port is up; choosing this alternative would address the wrong failure mode.

Question 226

A Nexus, UCS or MDS operations team encounters this issue: Two ACI endpoint groups should communicate over a narrowly permitted database port, but the contract is attached in the wrong provider-consumer direction. Which test outcome proves the intended service was restored?

  1. Authorized operators authenticate normally through remote AAA and recover access through the documented fallback during an outage.
  2. The identity updates permitted server profiles in its organization and receives denials elsewhere.
  3. Application sessions traverse the authorized EPG path and prohibited traffic remains blocked.
  4. The two workloads receive their distinct security policies while permitted shared services remain reachable.

Explanation

Correct Answer

C:

This observation validates aci contract consumer provider policy: The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. The corresponding corrective action is: Correct the ACI contract consumer-provider bindings and permit only the required application port. Evidence about a different component does not establish the requested service outcome.

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 contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter.

B:

“Apply the approved organization-scoped Intersight RBAC role for the automation identity” responds to this separate finding: the Intersight role assignment is not scoped to the authorized organization and permitted resource actions. This question instead needs “Correct the ACI contract consumer-provider bindings and permit only the required application port”, so the alternative does not meet the stated condition.

D:

The intended microsegmentation EPG classification rules do not distinguish the workload identities. “Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads” applies to that separate problem. The observed case is two ACI endpoint groups should communicate over a narrowly permitted database port, but the contract is attached in the wrong provider-consumer direction; choosing this alternative would address the wrong failure mode.

Question 227

A newly commissioned network, compute or storage service reports: A blade replacement is delayed because the team assumes MAC addresses and server identities must remain bound to the failed physical blade. Which implementation action should the engineer take first?

  1. Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration.
  2. Associate the intended service profile and its identity pools with the supported replacement hardware.
  3. Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN.
  4. Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design.

Explanation

Correct Answer

B:

The root problem is that The server identity has not been abstracted through approved UCS service profile and identity-pool associations. The selected change addresses it directly: Associate the intended service profile and its identity pools with the supported replacement hardware. Verify the outcome: The replacement blade receives the designated server identity and boots its workload according to policy.

Incorrect Answers

A:

This action concerns ucs wwpn pool uniqueness, where The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. The reported failure instead stems from The server identity has not been abstracted through approved UCS service profile and identity-pool associations.

C:

This action concerns ucs vhba vsan assignment consistency, where The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. The corrective response here is “Associate the intended service profile and its identity pools with the supported replacement hardware”; this alternative does not provide that response.

D:

This action concerns ucs vnic fabric failover connectivity, where The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. The stem reports a blade replacement is delayed because the team assumes MAC addresses and server identities must remain bound to the failed physical blade; this control addresses a different failure condition.

Question 228

During a Cisco data center readiness review, engineers observe: A data center team calls a privately operated dedicated cloud a public cloud merely because users reach it remotely through the Internet. What observation best confirms the configuration now behaves correctly?

  1. The intended receivers join and receive source traffic, and PIM control state shows the proper tree.
  2. The design describes the private deployment and any genuinely shared public components without conflating connectivity.
  3. The remote leaf learns the intended endpoint MAC through a valid EVPN route and forwards frames correctly.
  4. Interested ports retain multicast group membership and nonmembers do not receive unwanted replicated streams.

Explanation

Correct Answer

B:

This observation validates nist public private hybrid cloud models: Cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility. The corresponding corrective action is: Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. “Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups” would address that alternative cause, not the condition in this question: cloud deployment models are determined by ownership and audience characteristics, not simply by Internet accessibility.

C:

“Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI” responds to this separate finding: the Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. This question instead needs “Classify the environment using NIST deployment-model definitions and document any hybrid integration boundaries”, so the alternative does not meet the stated condition.

D:

The VLAN lacks a reachable supported multicast querier. “Provide a valid IGMP querier through the routed gateway or supported switching configuration” applies to that separate problem. The observed case is a data center team calls a privately operated dedicated cloud a public cloud merely because users reach it remotely through the Internet; choosing this alternative would address the wrong failure mode.

Question 229

While checking a production data center change, the team finds: An IPv6-only data center link has working layer-three connectivity but an OSPFv3 neighbor never forms because opposite ends use different area assignments. Which operational guardrail would prevent a similar outage?

  1. Validate peer interface MTU and OSPF state in the routed-uplink commissioning checklist.
  2. Include EVPN-family capability and received route checks in fabric peer change validation.
  3. Audit IPv6 routing area design and neighbor status during dual-stack network changes.
  4. Validate rendezvous-point redundancy and group mapping whenever multicast domains expand.

Explanation

Correct Answer

C:

This safeguard addresses ospfv3 ipv6 area consistency: The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. The appropriate prevention is: Audit IPv6 routing area design and neighbor status during dual-stack network changes. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. “Validate peer interface MTU and OSPF state in the routed-uplink commissioning checklist” would address that alternative cause, not the condition in this question: the OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts.

B:

“Include EVPN-family capability and received route checks in fabric peer change validation” responds to this separate finding: the BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. This question instead needs “Audit IPv6 routing area design and neighbor status during dual-stack network changes”, so the alternative does not meet the stated condition.

D:

The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. “Validate rendezvous-point redundancy and group mapping whenever multicast domains expand” applies to that separate problem. The observed case is an IPv6-only data center link has working layer-three connectivity but an OSPFv3 neighbor never forms because opposite ends use different area assignments; choosing this alternative would address the wrong failure mode.

Question 230

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 observation best confirms the configuration now behaves correctly?

  1. The time-series reports expose the loss interval and correlate it with the affected interfaces and fabric paths.
  2. Remote VTEPs learn the required IP prefix in the correct VRF and forward traffic toward its reachable next hop.
  3. Remote VTEP loopbacks resolve correctly and workload frames traverse the VXLAN overlay.
  4. Hosts in the authorized segment communicate across leaves while unrelated tenant segments remain separate.

Explanation

Correct Answer

B:

This observation validates evpn ip prefix type five advertisement: The routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. The corresponding corrective action is: Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. “Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics” 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.

C:

“Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies” responds to this separate finding: the NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. 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.

D:

The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. “Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves” 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.