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 22

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.

Question 211

A data center administrator identifies the following risk: 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 root cause best explains this behavior?

  1. Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL.
  2. The management access policy lacks a tested protected local recovery identity for remote AAA outages.
  3. Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.
  4. The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs.

Explanation

Correct Answer

C:

The technical cause is Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. The appropriate response is: Configure supported MDS port-security bindings for the intended server initiator and affected VSAN. Confirm successful repair: The approved HBA logs in while a test unapproved WWPN is rejected by the protected fabric port.

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: fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.

B:

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

D:

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

While checking a production data center change, the team finds: An HBA completes fabric login but the intended target WWPN cannot be discovered because the target never registers with the Fibre Channel name server. Which implementation action should the engineer take first?

  1. Activate the approved zoneset containing the authorized initiator-target zone and verify effective zoning.
  2. Identify the legitimate lock owner and safely complete or abort the supported CFS session.
  3. Verify target port FLOGI and FCNS registration and restore the authorized target attachment.
  4. Create separate approved zones for each host initiator with its authorized storage target ports.

Explanation

Correct Answer

C:

The root problem is that The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. The selected change addresses it directly: Verify target port FLOGI and FCNS registration and restore the authorized target attachment. Verify the outcome: The MDS name-server database contains the correct target and initiator identities for the relevant VSAN.

Incorrect Answers

A:

This action concerns active fibre channel zoneset validation, where An inactive zoning database edit does not change the effective active zoneset on the SAN fabric. The reported failure instead stems from The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded.

B:

This action concerns cisco fabric services configuration distribution, where A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. The corrective response here is “Verify target port FLOGI and FCNS registration and restore the authorized target attachment”; this alternative does not provide that response.

D:

This action concerns single initiator target zoning design, where The zone combines initiators beyond the least-privilege single-initiator zoning design. The stem reports an HBA completes fabric login but the intended target WWPN cannot be discovered because the target never registers with the Fibre Channel name server; this control addresses a different failure condition.

Question 213

During a Cisco data center readiness review, engineers observe: An engineer changes a Nexus port-channel policy and several interfaces stop passing traffic, but no approved prechange rollback point exists. After remediation, which acceptance result is most relevant?

  1. Hardware and software component versions match the approved release prerequisites after controlled maintenance.
  2. A staged test establishes the actual traffic impact and the upgrade follows the approved compatibility plan.
  3. Interested ports retain multicast group membership and nonmembers do not receive unwanted replicated streams.
  4. The device returns to the known-good configuration with traffic restored after rollback is exercised.

Explanation

Correct Answer

D:

This observation validates nexus configuration checkpoint recovery: The change process omitted a recoverable NX-OS configuration checkpoint and validation plan. The corresponding corrective action is: Create and use a supported configuration checkpoint or approved rollback before editing the production policy. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the change process omitted a recoverable NX-OS configuration checkpoint and validation plan.

B:

“Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path” responds to this separate finding: the upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. This question instead needs “Create and use a supported configuration checkpoint or approved rollback before editing the production policy”, so the alternative does not meet the stated condition.

C:

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 an engineer changes a Nexus port-channel policy and several interfaces stop passing traffic, but no approved prechange rollback point exists; choosing this alternative would address the wrong failure mode.

Question 214

A Nexus, UCS or MDS operations team encounters this issue: A UCS blade can reach its Ethernet network but cannot discover a SAN boot target because the vHBA has been assigned to a different VSAN from its storage uplink. Which corrective change best resolves this problem?

  1. Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN.
  2. Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters.
  3. Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration.
  4. Associate the intended service profile and its identity pools with the supported replacement hardware.

Explanation

Correct Answer

A:

The root problem is that The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. The selected change addresses it directly: Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN. Verify the outcome: The server HBA registers in the correct VSAN and discovers the authorized target storage port.

Incorrect Answers

B:

This action concerns ucs san boot target identifiers, where The SAN boot policy refers to an unavailable storage target identity rather than the authorized active target. The reported failure instead stems from The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end.

C:

This action concerns ucs wwpn pool uniqueness, where The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. The corrective response here is “Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN”; this alternative does not provide that response.

D:

This action concerns ucs service profile server identity, where The server identity has not been abstracted through approved UCS service profile and identity-pool associations. The stem reports a UCS blade can reach its Ethernet network but cannot discover a SAN boot target because the vHBA has been assigned to a different VSAN from its storage uplink; this control addresses a different failure condition.

Question 215

A data center implementation team investigates the following fault: A two-member uplink from a server-facing switch carries traffic on only one physical member because one end was configured for a static bundle. Which corrective change best resolves this problem?

  1. Configure a matching supported LACP mode and port-channel membership across the two endpoints.
  2. Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies.
  3. Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology.
  4. Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms.

Explanation

Correct Answer

A:

The root problem is that The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. The selected change addresses it directly: Configure a matching supported LACP mode and port-channel membership across the two endpoints. Verify the outcome: Both intended interfaces are bundled and load-balanced without individual or suspended member state.

Incorrect Answers

B:

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 reported failure instead stems from The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members.

C:

This action concerns rstp root bridge placement, where Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. The corrective response here is “Configure a matching supported LACP mode and port-channel membership across the two endpoints”; this alternative does not provide that response.

D:

This action concerns vpc peer link consistency, where The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The stem reports a two-member uplink from a server-facing switch carries traffic on only one physical member because one end was configured for a static bundle; this control addresses a different failure condition.

Question 216

A Nexus, UCS or MDS operations team encounters this issue: A host sends FCoE storage traffic on an ordinary IP VLAN with no supported Fibre Channel Forwarder or proper FCoE VLAN configuration. What is the most appropriate remediation for these symptoms?

  1. Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path.
  2. Commit the approved device alias database transaction and verify resolution across the affected switches.
  3. Assign the target port to the approved VSAN and verify its effective FCNS and zone membership.
  4. Move the backup server connection into the approved dedicated VSAN and update authorized zoning.

Explanation

Correct Answer

A:

The root problem is that The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. The selected change addresses it directly: Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path. Verify the outcome: The converged adapter completes supported FCoE fabric login and discovers the permitted storage target.

Incorrect Answers

B:

This action concerns cisco mds device alias commit behavior, where Device alias changes have not been committed and distributed through the supported fabric database workflow. The reported failure instead stems from The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service.

C:

This action concerns san vsan interface assignment at attachment, where The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. The corrective response here is “Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path”; this alternative does not provide that response.

D:

This action concerns fibre channel vsan traffic isolation, where VSAN membership is incorrectly shared between isolation domains with different storage access requirements. The stem reports a host sends FCoE storage traffic on an ordinary IP VLAN with no supported Fibre Channel Forwarder or proper FCoE VLAN configuration; this control addresses a different failure condition.

Question 217

A newly commissioned network, compute or storage service reports: A new Nexus leaf has its VXLAN NVE interface configured but cannot encapsulate traffic to remote VTEPs after the underlay route filters changed. Which operational guardrail would prevent a similar outage?

  1. Test VTEP source reachability as a prerequisite for every fabric underlay policy change.
  2. Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover.
  3. Review tenant L3VNI and route-target controls when adding external routed service networks.
  4. Maintain a controlled VNI allocation register and validate mappings before extending tenant VLANs.

Explanation

Correct Answer

A:

This safeguard addresses vxlan vtep loopback reachability: The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. The appropriate prevention is: Test VTEP source reachability as a prerequisite for every fabric underlay policy change. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. “Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover” would address that alternative cause, not the condition in this question: the NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain.

C:

“Review tenant L3VNI and route-target controls when adding external routed service networks” responds to this separate finding: the routed tenant VRF prefix is not being exported or imported as an appropriate EVPN IP-prefix route. This question instead needs “Test VTEP source reachability as a prerequisite for every fabric underlay policy change”, 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. “Maintain a controlled VNI allocation register and validate mappings before extending tenant VLANs” applies to that separate problem. The observed case is a new Nexus leaf has its VXLAN NVE interface configured but cannot encapsulate traffic to remote VTEPs after the underlay route filters changed; choosing this alternative would address the wrong failure mode.

Question 218

During a Cisco data center readiness review, engineers observe: A new Fibre Channel port-channel member on MDS remains suspended after a technician applies the wrong VSAN trunk attributes to that physical interface. What observation best confirms the configuration now behaves correctly?

  1. Both switches participate in one stable fabric with unique domain IDs and expected FSPF reachability.
  2. The target and initiator register and exchange traffic inside VSAN 30 without affecting other VSANs.
  3. Both members become operational in the port channel and load distribution remains stable.
  4. The initiator completes FLOGI and receives a valid FCID in the correct SAN fabric.

Explanation

Correct Answer

C:

This observation validates fibre channel port channel member consistency: The FC port channel and prospective member disagree on required operational attributes for bundling. The corresponding corrective action is: Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The Fibre Channel fabric merge contains conflicting domain identifiers that prevent normal fabric initialization. “Resolve the FC domain ID conflict using the approved principal-switch and fabric reconfiguration process” 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:

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

D:

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

A Nexus, UCS or MDS operations team encounters this issue: Two workloads in a shared ACI subnet require different policies, but both inherit the same broad EPG because no microsegmentation attributes are matched. 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. Correct the ACI contract consumer-provider bindings and permit only the required application port.
  3. Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads.
  4. Coordinate the supported authentication keychain parameters and overlapping key transition periods.

Explanation

Correct Answer

C:

The root problem is that The intended microsegmentation EPG classification rules do not distinguish the workload identities. The selected change addresses it directly: Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads. Verify the outcome: The two workloads receive their distinct security policies while permitted shared services remain reachable.

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 intended microsegmentation EPG classification rules do not distinguish the workload identities.

B:

This action concerns aci contract consumer provider policy, where The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. The corrective response here is “Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads”; this alternative does not provide that response.

D:

This action concerns ospf keychain authentication rotation, where The OSPF authentication peers are using mismatched active key IDs or validity intervals. The stem reports two workloads in a shared ACI subnet require different policies, but both inherit the same broad EPG because no microsegmentation attributes are matched; this control addresses a different failure condition.

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.