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 21

Question 200

A data center administrator identifies the following risk: Two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list. Which root cause best explains this behavior?

  1. The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.
  2. The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups.
  3. The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members.
  4. The failure design does not account for orphan-port behavior and the chosen peer recovery semantics.

Explanation

Correct Answer

A:

The technical cause is The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The appropriate response is: Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms. Confirm successful repair: The host VLAN remains reachable through either peer after a simulated downstream member failure.

Incorrect Answers

B:

The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. “Repair the approved ACI VMM integration and EPG domain association, then validate policy deployment” would address that alternative cause, not the condition in this question: the vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.

C:

“Configure a matching supported LACP mode and port-channel membership across the two endpoints” responds to this separate finding: the port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. This question instead needs “Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms”, so the alternative does not meet the stated condition.

D:

The failure design does not account for orphan-port behavior and the chosen peer recovery semantics. “Review supported orphan-port handling and move or protect the workload on the planned resilient attachment” applies to that separate problem. The observed case is two Nexus switches form a vPC pair, but a VLAN needed by a downstream dual-homed host is missing from the peer-link allowed list; choosing this alternative would address the wrong failure mode.

Question 201

A data center administrator identifies the following risk: A new backup server is placed into the production database VSAN, exposing it to unintended storage fabric control and zoning scope. Which verification result most directly demonstrates successful repair?

  1. The host discovers an iSCSI target LUN and presents the expected block device to the hypervisor.
  2. The backup initiator registers only in its permitted VSAN and cannot discover unrelated production zones.
  3. The authorized target and host appear in the same intended VSAN and storage access succeeds.
  4. The upstream switch sees proxied initiator logins and the access device no longer relies on principal-switch services.

Explanation

Correct Answer

B:

This observation validates fibre channel vsan traffic isolation: VSAN membership is incorrectly shared between isolation domains with different storage access requirements. The corresponding corrective action is: Move the backup server connection into the approved dedicated VSAN and update authorized zoning. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. “Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk” would address that alternative cause, not the condition in this question: vSAN membership is incorrectly shared between isolation domains with different storage access requirements.

C:

“Assign the target port to the approved VSAN and verify its effective FCNS and zone membership” responds to this separate finding: the target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. This question instead needs “Move the backup server connection into the approved dedicated VSAN and update authorized zoning”, so the alternative does not meet the stated condition.

D:

NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. “Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design” applies to that separate problem. The observed case is a new backup server is placed into the production database VSAN, exposing it to unintended storage fabric control and zoning scope; choosing this alternative would address the wrong failure mode.

Question 202

A newly commissioned network, compute or storage service reports: A newly attached service profile cannot create its virtual network adapters because every address in its assigned MAC pool is already allocated. After remediation, which acceptance result is most relevant?

  1. The replacement blade identifies the intended LUN and completes a controlled SAN boot.
  2. A controlled fabric failover retains authorized server network reachability without duplicate MAC or VLAN problems.
  3. All required vNICs receive unique authorized MAC addresses without conflicting with existing profiles.
  4. Both servers log in with their own WWPN identities and see only their authorized storage paths.

Explanation

Correct Answer

C:

This observation validates ucs mac address pool exhaustion: The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. The corresponding corrective action is: Expand or assign a nonoverlapping approved MAC pool and retry the service profile association. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. “Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters” would address that alternative cause, not the condition in this question: the UCS MAC identity pool has insufficient available addresses for the requested vNIC identities.

B:

“Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design” responds to this separate finding: the UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. This question instead needs “Expand or assign a nonoverlapping approved MAC pool and retry the service profile association”, so the alternative does not meet the stated condition.

D:

The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. “Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration” applies to that separate problem. The observed case is a newly attached service profile cannot create its virtual network adapters because every address in its assigned MAC pool is already allocated; choosing this alternative would address the wrong failure mode.

Question 203

A Nexus, UCS or MDS operations team encounters this issue: An automation client retries an administrative NX-API request repeatedly after receiving HTTP 403, misclassifying authorization denial as a transient device failure. Which verification result most directly demonstrates successful repair?

  1. The backup executes at the intended time without repeated unnecessary administrative sessions.
  2. A permitted API call succeeds while denied operations report a clear nonretryable authorization error.
  3. The applet runs only on the targeted peer-down event and preserves the expected diagnostic information.
  4. The script executes within its intended environment without changing unapproved host system files.

Explanation

Correct Answer

B:

This observation validates rest api authorization status handling: The REST client does not distinguish insufficient authorization from retryable transport or server errors. The corresponding corrective action is: Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the REST client does not distinguish insufficient authorization from retryable transport or server errors.

C:

“Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event” responds to this separate finding: the embedded event manager event detector does not match the actual authorized BGP neighbor-down message. This question instead needs “Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an automation client retries an administrative NX-API request repeatedly after receiving HTTP 403, misclassifying authorization denial as a transient device failure; choosing this alternative would address the wrong failure mode.

Question 204

A newly commissioned network, compute or storage service reports: An Ansible playbook meant for lab Nexus switches changes production switch banners because its inventory group variables include production hosts inadvertently. Which approved technology action addresses this incident most directly?

  1. Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics.
  2. Query existing NX-OS state before applying only the necessary authorized configuration differences.
  3. Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution.
  4. Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event.

Explanation

Correct Answer

C:

The root problem is that The playbook target inventory and variable precedence do not isolate the intended lab device group. The selected change addresses it directly: Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution. Verify the outcome: Only the designated lab devices receive changes and production targets remain unchanged.

Incorrect Answers

A:

This action concerns python structured telemetry parsing, where The parser lacks schema validation and robust handling of absent or differently typed telemetry values. The reported failure instead stems from The playbook target inventory and variable precedence do not isolate the intended lab device group.

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 corrective response here is “Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution”; this alternative does not provide that response.

D:

This action concerns nx os eem syslog event trigger, where The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. The stem reports an Ansible playbook meant for lab Nexus switches changes production switch banners because its inventory group variables include production hosts inadvertently; this control addresses a different failure condition.

Question 205

A data center implementation team investigates the following fault: A Cisco Nexus switch locally observes abnormal traffic, but the monitoring platform receives no NetFlow records after the exporter destination was moved. Which test outcome proves the intended service was restored?

  1. The collector receives valid sampled flow records with the expected device identity and timestamps.
  2. The analyzer receives copied packets from the target flow without becoming part of normal switching paths.
  3. Both peers reach Full state and exchange the intended routes without retransmission or MTU errors.
  4. The time-series reports expose the loss interval and correlate it with the affected interfaces and fabric paths.

Explanation

Correct Answer

A:

This observation validates netflow exporter reachability: Flow-export destination reachability or the configured source and monitoring VRF are incorrect. The corresponding corrective action is: Repair the approved flow exporter source, destination and transport route, and verify collector acceptance. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The SPAN session source and dedicated monitor destination roles were assigned incorrectly. “Configure the authorized SPAN source and monitor-only destination and confirm the capture appliance connection” would address that alternative cause, not the condition in this question: flow-export destination reachability or the configured source and monitoring VRF are incorrect.

C:

“Align the approved interface MTU settings on both ends and then reestablish the OSPF adjacency” responds to this separate finding: the neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. This question instead needs “Repair the approved flow exporter source, destination and transport route, and verify collector acceptance”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a Cisco Nexus switch locally observes abnormal traffic, but the monitoring platform receives no NetFlow records after the exporter destination was moved; choosing this alternative would address the wrong failure mode.

Question 206

While checking a production data center change, the team finds: Two Nexus switches share an OSPFv2 segment, but their neighbors remain stuck in ExStart immediately after one uplink was changed to a larger MTU. Which deployment safeguard most directly reduces this failure risk?

  1. Validate peer interface MTU and OSPF state in the routed-uplink commissioning checklist.
  2. Audit IPv6 routing area design and neighbor status during dual-stack network changes.
  3. Test upstream failure, HSRP role transitions, and gateway reachability during each redundancy exercise.
  4. Include EVPN-family capability and received route checks in fabric peer change validation.

Explanation

Correct Answer

A:

This safeguard addresses ospfv2 adjacency mtu mismatch: The neighboring OSPF interfaces disagree on MTU and database description negotiation cannot complete reliably. The appropriate prevention is: Validate peer interface MTU and OSPF state in the routed-uplink commissioning checklist. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. “Audit IPv6 routing area design and neighbor status during dual-stack network changes” 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.

C:

“Test upstream failure, HSRP role transitions, and gateway reachability during each redundancy exercise” responds to this separate finding: the first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. This question instead needs “Validate peer interface MTU and OSPF state in the routed-uplink commissioning checklist”, so the alternative does not meet the stated condition.

D:

The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. “Include EVPN-family capability and received route checks in fabric peer change validation” 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 207

A newly commissioned network, compute or storage service reports: An MDS chassis upgrade plan ignores a line-card EPLD requirement even though Cisco's release prerequisites identify hardware programming compatibility work. Which approved technology action addresses this incident most directly?

  1. Update the scoped NFS export policy to include only the approved new hypervisor client addresses.
  2. Set a supported FC SPAN monitor source for the affected port and the approved capture destination.
  3. Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method.
  4. Review the applicable MDS EPLD package and schedule the correct supported component update.

Explanation

Correct Answer

D:

The root problem is that The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. The selected change addresses it directly: Review the applicable MDS EPLD package and schedule the correct supported component update. Verify the outcome: The module and operating system versions satisfy Cisco's documented compatibility requirements after the change.

Incorrect Answers

A:

This action concerns nfs export client authorization, where The NFS export access rules do not authorize the requesting client address or security identity. The reported failure instead stems from The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image.

B:

This action concerns cisco mds span fibre channel troubleshooting, where The Fibre Channel SPAN session source does not identify the failing interface or service path. The corrective response here is “Review the applicable MDS EPLD package and schedule the correct supported component update”; this alternative does not provide that response.

C:

This action concerns cisco mds nondisruptive upgrade prechecks, where The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. The stem reports an MDS chassis upgrade plan ignores a line-card EPLD requirement even though Cisco's release prerequisites identify hardware programming compatibility work; this control addresses a different failure condition.

Question 208

A data center implementation team investigates the following fault: An MDS monitoring analyst receives a network-admin role and can edit SAN zoning despite requiring only fabric health visibility. What is the most appropriate remediation for these symptoms?

  1. Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions.
  2. Replace the overly broad MDS role with an approved read-only or scoped monitoring role.
  3. Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs.
  4. Configure supported MDS port-security bindings for the intended server initiator and affected VSAN.

Explanation

Correct Answer

B:

The root problem is that The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. The selected change addresses it directly: Replace the overly broad MDS role with an approved read-only or scoped monitoring role. Verify the outcome: The analyst inspects FCNS and port health but cannot activate or change production zonesets.

Incorrect Answers

A:

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 reported failure instead stems from The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs.

C:

This action concerns mds fibre channel fabric binding, where Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. The corrective response here is “Replace the overly broad MDS role with an approved read-only or scoped monitoring role”; this alternative does not provide that response.

D:

This action concerns mds fibre channel port security binding, where Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. The stem reports an MDS monitoring analyst receives a network-admin role and can edit SAN zoning despite requiring only fabric health visibility; this control addresses a different failure condition.

Question 209

A Nexus, UCS or MDS operations team encounters this issue: 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. Which root cause best explains this behavior?

  1. The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture.
  2. The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies.
  3. UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements.
  4. The Intersight device claim and account authorization do not match the approved administrative organization.

Explanation

Correct Answer

A:

The technical cause is The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. The appropriate response is: Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies. Confirm successful repair: The chassis and compute nodes are managed through the expected Intersight policy and profile model.

Incorrect Answers

B:

The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies. “Complete the required Intersight policies and deploy the server profile with validated resource assignments” 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:

“Correct the supported UCS class-of-service and network QoS policy for the intended application traffic” responds to this separate finding: uCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements. This question instead needs “Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies”, so the alternative does not meet the stated condition.

D:

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

While checking a production data center change, the team finds: Two Nexus routed neighbors stop forming OSPF adjacencies during key rotation because their configured keychain accept and send lifetimes do not overlap. What technical condition most directly accounts for the failure?

  1. Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.
  2. Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection.
  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

D:

The technical cause is The OSPF authentication peers are using mismatched active key IDs or validity intervals. The appropriate response is: Coordinate the supported authentication keychain parameters and overlapping key transition periods. Confirm successful repair: The intended OSPF adjacency remains authenticated across the key-rotation window with old keys retired safely.

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 OSPF authentication peers are using mismatched active key IDs or validity intervals.

B:

“Configure supported MACsec policy and secure key agreement on both authorized switch endpoints” responds to this separate finding: link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. 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 centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. “Correct the authorized TACACS command or role mapping without granting full switch administrator permissions” 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.