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 9

Question 80

A data center implementation team investigates the following fault: 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 corrective change best resolves this problem?

  1. Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event.
  2. Query existing NX-OS state before applying only the necessary authorized configuration differences.
  3. Set the supported scheduler job schedule to the approved daily interval and verify the associated command.
  4. Deploy the script in the approved supported shell environment with required dependencies and bounded permissions.

Explanation

Correct Answer

B:

The root problem is that The script lacks an idempotent precheck to compare desired and current network device state. The selected change addresses it directly: Query existing NX-OS state before applying only the necessary authorized configuration differences. Verify the outcome: Repeated execution converges to the same desired configuration without unintended duplicate changes.

Incorrect Answers

A:

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 reported failure instead stems from The script lacks an idempotent precheck to compare desired and current network device state.

C:

This action concerns nx os scheduler job interval, where The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The corrective response here is “Query existing NX-OS state before applying only the necessary authorized configuration differences”; this alternative does not provide that response.

D:

This action concerns nexus bash shell and guest shell isolation, where The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The stem reports 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; this control addresses a different failure condition.

Question 81

A data center implementation team investigates the following fault: A new MDS F-port physically connects to a storage target but remains in the default VSAN while its allowed initiator is in a separate production VSAN. Which test outcome proves the intended service was restored?

  1. The upstream switch sees proxied initiator logins and the access device no longer relies on principal-switch services.
  2. The converged adapter completes supported FCoE fabric login and discovers the permitted storage target.
  3. The backup initiator registers only in its permitted VSAN and cannot discover unrelated production zones.
  4. The authorized target and host appear in the same intended VSAN and storage access succeeds.

Explanation

Correct Answer

D:

This observation validates san vsan interface assignment at attachment: The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. The corresponding corrective action is: Assign the target port to the approved VSAN and verify its effective FCNS and zone membership. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset.

B:

“Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path” responds to this separate finding: the converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. This question instead needs “Assign the target port to the approved VSAN and verify its effective FCNS and zone membership”, so the alternative does not meet the stated condition.

C:

VSAN membership is incorrectly shared between isolation domains with different storage access requirements. “Move the backup server connection into the approved dedicated VSAN and update authorized zoning” applies to that separate problem. The observed case is a new MDS F-port physically connects to a storage target but remains in the default VSAN while its allowed initiator is in a separate production VSAN; choosing this alternative would address the wrong failure mode.

Question 82

A data center implementation team investigates the following fault: A newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management. What preventive control would best avoid repeating this fault?

  1. Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes.
  2. Review VNI BUM replication scope and flood lists as part of tenant expansion planning.
  3. Maintain a documented node-ID and cabling approval process for new ACI leaf introductions.
  4. Validate leaf interface selectors, domains and EPG paths together in access-policy reviews.

Explanation

Correct Answer

C:

This safeguard addresses aci leaf onboarding discovery: The leaf has not completed the supported ACI fabric discovery and node-registration workflow. The appropriate prevention is: Maintain a documented node-ID and cabling approval process for new ACI leaf introductions. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups. “Test VMM controller credentials and dynamic EPG bindings after virtualization infrastructure changes” would address that alternative cause, not the condition in this question: the leaf has not completed the supported ACI fabric discovery and node-registration workflow.

B:

“Review VNI BUM replication scope and flood lists as part of tenant expansion planning” responds to this separate finding: bUM replication handling does not reflect the intended VNI flood list and supported replication or multicast model. This question instead needs “Maintain a documented node-ID and cabling approval process for new ACI leaf introductions”, so the alternative does not meet the stated condition.

D:

The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. “Validate leaf interface selectors, domains and EPG paths together in access-policy reviews” applies to that separate problem. The observed case is a newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management; choosing this alternative would address the wrong failure mode.

Question 83

A Nexus, UCS or MDS operations team encounters this issue: A Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script. What ongoing validation should operations establish for this service?

  1. Implement identity and organization-scope validation in Intersight automation before execution.
  2. Treat centrally managed fabric intent as authoritative and audit out-of-band changes.
  3. Rotate integration credentials and inspect PowerShell logging and secret-handling policies regularly.
  4. Audit scheduler job frequency and execution history after automation changes.

Explanation

Correct Answer

C:

This safeguard addresses powershell rest secure credentials: The automation credential is stored insecurely and grants broader privileges than the script requires. The appropriate prevention is: Rotate integration credentials and inspect PowerShell logging and secret-handling policies regularly. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The API workflow fails to resolve the correct scoped Intersight policy identifier before server profile association. “Implement identity and organization-scope validation in Intersight automation before execution” would address that alternative cause, not the condition in this question: the automation credential is stored insecurely and grants broader privileges than the script requires.

B:

“Treat centrally managed fabric intent as authoritative and audit out-of-band changes” responds to this separate finding: device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. This question instead needs “Rotate integration credentials and inspect PowerShell logging and secret-handling policies regularly”, so the alternative does not meet the stated condition.

D:

The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. “Audit scheduler job frequency and execution history after automation changes” applies to that separate problem. The observed case is a Windows automation job uses PowerShell to invoke Intersight APIs but embeds a long-lived administrative secret in a shared source script; choosing this alternative would address the wrong failure mode.

Question 84

During a Cisco data center readiness review, engineers observe: A newly attached service profile cannot create its virtual network adapters because every address in its assigned MAC pool is already allocated. What technical condition most directly accounts for the failure?

  1. The vHBA WWPN allocation violates uniqueness requirements across server storage initiators.
  2. The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path.
  3. The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities.
  4. The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end.

Explanation

Correct Answer

C:

The technical cause is The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. The appropriate response is: Expand or assign a nonoverlapping approved MAC pool and retry the service profile association. Confirm successful repair: All required vNICs receive unique authorized MAC addresses without conflicting with existing profiles.

Incorrect Answers

A:

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” 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 virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. “Assign the supported vHBA and fabric-facing SAN connectivity to the approved target VSAN” 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 85

During a Cisco data center readiness review, engineers observe: A UCS-adjacent SAN access switch configured for NPV cannot perform independent fabric services, but engineers expect it to act as the fabric principal switch. What observation best confirms the configuration now behaves correctly?

  1. The upstream switch sees proxied initiator logins and the access device no longer relies on principal-switch services.
  2. The fabric accepts a new authorized zoning transaction with consistent configuration distribution.
  3. The authorized target and host appear in the same intended VSAN and storage access succeeds.
  4. The converged adapter completes supported FCoE fabric login and discovers the permitted storage target.

Explanation

Correct Answer

A:

This observation validates npv and npiv switch roles: NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. The corresponding corrective action is: Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

A Cisco Fabric Services zoning transaction lock is still held by an unfinished or failed session. “Identify the legitimate lock owner and safely complete or abort the supported CFS session” would address that alternative cause, not the condition in this question: nPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch.

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 “Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design”, so the alternative does not meet the stated condition.

D:

The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. “Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path” applies to that separate problem. The observed case is a UCS-adjacent SAN access switch configured for NPV cannot perform independent fabric services, but engineers expect it to act as the fabric principal switch; choosing this alternative would address the wrong failure mode.

Question 86

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. What is the most appropriate remediation for these symptoms?

  1. Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms.
  2. Review supported orphan-port handling and move or protect the workload on the planned resilient attachment.
  3. Configure a matching supported LACP mode and port-channel membership across the two endpoints.
  4. Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology.

Explanation

Correct Answer

A:

The root problem is that The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The selected change addresses it directly: Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms. Verify the outcome: The host VLAN remains reachable through either peer after a simulated downstream member failure.

Incorrect Answers

B:

This action concerns vpc orphan port convergence, where The failure design does not account for orphan-port behavior and the chosen peer recovery semantics. The reported failure instead stems from The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements.

C:

This action concerns lacp port channel negotiation, where The port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. The corrective response here is “Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms”; this alternative does not provide that response.

D:

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 stem reports 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; this control addresses a different failure condition.

Question 87

A newly commissioned network, compute or storage service 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. What technical condition most directly accounts for the failure?

  1. The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter.
  2. The OSPF authentication peers are using mismatched active key IDs or validity intervals.
  3. The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring.
  4. The management access policy lacks a tested protected local recovery identity for remote AAA outages.

Explanation

Correct Answer

C:

The technical cause is The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. The appropriate response is: Correct the authorized TACACS command or role mapping without granting full switch administrator permissions. Confirm successful repair: The operator executes the designated monitoring commands while sensitive configuration changes remain denied.

Incorrect Answers

A:

The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. “Correct the ACI contract consumer-provider bindings and permit only the required application port” would address that alternative cause, not the condition in this question: the centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring.

B:

“Coordinate the supported authentication keychain parameters and overlapping key transition periods” responds to this separate finding: the OSPF authentication peers are using mismatched active key IDs or validity intervals. This question instead needs “Correct the authorized TACACS command or role mapping without granting full switch administrator permissions”, so the alternative does not meet the stated condition.

D:

The management access policy lacks a tested protected local recovery identity for remote AAA outages. “Configure a secured local break-glass account using Cisco-supported AAA fallback settings and access restrictions” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 88

During a Cisco data center readiness review, engineers observe: A Nexus maintenance plan upgrades only the system image while a documented line-card hardware programming device update is required for the target release. Which approved technology action addresses this incident most directly?

  1. Check the published release and ISSU compatibility matrix and select a supported maintenance or disruptive path.
  2. Configure the approved EVPN IP-prefix advertisement and tenant route-target policy for that service VRF.
  3. Create and use a supported configuration checkpoint or approved rollback before editing the production policy.
  4. Review supported EPLD package requirements and schedule the component update using the prescribed procedure.

Explanation

Correct Answer

D:

The root problem is that The planned software transition omits the EPLD compatibility and operational impact assessment. The selected change addresses it directly: Review supported EPLD package requirements and schedule the component update using the prescribed procedure. Verify the outcome: Hardware and software component versions match the approved release prerequisites after controlled maintenance.

Incorrect Answers

A:

This action concerns nx os issu support preflight, where The upgrade plan assumes ISSU support without validating the platform release path and active feature constraints. The reported failure instead stems from The planned software transition omits the EPLD compatibility and operational impact assessment.

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 “Review supported EPLD package requirements and schedule the component update using the prescribed procedure”; this alternative does not provide that response.

C:

This action concerns nexus configuration checkpoint recovery, where The change process omitted a recoverable NX-OS configuration checkpoint and validation plan. The stem reports a Nexus maintenance plan upgrades only the system image while a documented line-card hardware programming device update is required for the target release; this control addresses a different failure condition.

Question 89

A data center implementation team investigates the following fault: An infrastructure automation identity can edit server policies in several unrelated Intersight organizations even though it supports just one business unit. Which corrective change best resolves this problem?

  1. Assign a supported restricted UCS role and scope matching the storage administration tasks.
  2. Configure supported MACsec policy and secure key agreement on both authorized switch endpoints.
  3. Correct the supported UCS authentication realm order and emergency access procedure under change control.
  4. Apply the approved organization-scoped Intersight RBAC role for the automation identity.

Explanation

Correct Answer

D:

The root problem is that The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. The selected change addresses it directly: Apply the approved organization-scoped Intersight RBAC role for the automation identity. Verify the outcome: The identity updates permitted server profiles in its organization and receives denials elsewhere.

Incorrect Answers

A:

This action concerns ucs manager role based access, where The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. The reported failure instead stems from The Intersight role assignment is not scoped to the authorized organization and permitted resource actions.

B:

This action concerns macsec encrypted inter switch links, where Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection. The corrective response here is “Apply the approved organization-scoped Intersight RBAC role for the automation identity”; this alternative does not provide that response.

C:

This action concerns ucs remote aaa fallback authentication, where The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. The stem reports an infrastructure automation identity can edit server policies in several unrelated Intersight organizations even though it supports just one business unit; this control addresses a different failure condition.

Question 90

While checking a production data center change, the team finds: A dual-fabric UCS server unexpectedly loses the same application VLAN when one fabric interconnect fails because its vNIC failover behavior is not coordinated. Which implementation action should the engineer take first?

  1. Expand or assign a nonoverlapping approved MAC pool and retry the service profile association.
  2. Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration.
  3. Associate the intended service profile and its identity pools with the supported replacement hardware.
  4. Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design.

Explanation

Correct Answer

D:

The root problem is that The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. The selected change addresses it directly: Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design. Verify the outcome: A controlled fabric failover retains authorized server network reachability without duplicate MAC or VLAN problems.

Incorrect Answers

A:

This action concerns ucs mac address pool exhaustion, where The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. The reported failure instead stems from The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path.

B:

This action concerns ucs wwpn pool uniqueness, where The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. The corrective response here is “Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design”; this alternative does not provide that response.

C:

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 dual-fabric UCS server unexpectedly loses the same application VLAN when one fabric interconnect fails because its vNIC failover behavior is not coordinated; this control addresses a different failure condition.