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 33

Question 320

A data center administrator identifies the following risk: A newly cabled Cisco ACI leaf appears physically connected to a spine but never becomes an accepted fabric node under APIC management. Which design or configuration error caused the described issue?

  1. Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root.
  2. The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.
  3. The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups.
  4. The leaf has not completed the supported ACI fabric discovery and node-registration workflow.

Explanation

Correct Answer

D:

The technical cause is The leaf has not completed the supported ACI fabric discovery and node-registration workflow. The appropriate response is: Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC. Confirm successful repair: APIC shows the assigned leaf as an active fabric member with the expected spine adjacency.

Incorrect Answers

A:

Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. “Set approved spanning-tree bridge priorities and validate the intended root and blocked-port topology” 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:

“Correct the supported ACI interface policy selector and physical domain association for the host-facing port” responds to this separate finding: the interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. This question instead needs “Verify fabric ports, discovery connectivity and the intended node identity, then register the new leaf in APIC”, so the alternative does not meet the stated condition.

C:

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

During a Cisco data center readiness review, engineers observe: Two ACI endpoint groups should communicate over a narrowly permitted database port, but the contract is attached in the wrong provider-consumer direction. Which implementation action should the engineer take first?

  1. Assign a supported restricted UCS role and scope matching the storage administration tasks.
  2. Correct the ACI contract consumer-provider bindings and permit only the required application port.
  3. Coordinate the supported authentication keychain parameters and overlapping key transition periods.
  4. Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads.

Explanation

Correct Answer

B:

The root problem is that The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. The selected change addresses it directly: Correct the ACI contract consumer-provider bindings and permit only the required application port. Verify the outcome: Application sessions traverse the authorized EPG path and prohibited traffic remains blocked.

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

C:

This action concerns ospf keychain authentication rotation, where The OSPF authentication peers are using mismatched active key IDs or validity intervals. The corrective response here is “Correct the ACI contract consumer-provider bindings and permit only the required application port”; this alternative does not provide that response.

D:

This action concerns aci microsegmentation useg classification, where The intended microsegmentation EPG classification rules do not distinguish the workload identities. The stem reports two ACI endpoint groups should communicate over a narrowly permitted database port, but the contract is attached in the wrong provider-consumer direction; this control addresses a different failure condition.

Question 322

A data center administrator identifies the following risk: 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. What ongoing validation should operations establish for this service?

  1. Treat centrally managed fabric intent as authoritative and audit out-of-band changes.
  2. Build explicit error classification and bounded retries into every infrastructure API client.
  3. Test PFC deadlock risk and congestion behavior before production AI network scale-out.
  4. Measure AI job communication patterns and model network growth before adding GPU clusters.

Explanation

Correct Answer

C:

This safeguard addresses ai roce lossless class design: The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. The appropriate prevention is: Test PFC deadlock risk and congestion behavior before production AI network scale-out. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

Device-level modifications are not reconciled with the authoritative Nexus Dashboard fabric policy model. “Treat centrally managed fabric intent as authoritative and audit out-of-band changes” 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.

B:

“Build explicit error classification and bounded retries into every infrastructure API client” responds to this separate finding: the REST client does not distinguish insufficient authorization from retryable transport or server errors. This question instead needs “Test PFC deadlock risk and congestion behavior before production AI network scale-out”, 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. “Measure AI job communication patterns and model network growth before adding GPU clusters” 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 323

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 corrective change best resolves this problem?

  1. Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures.
  2. Set the supported scheduler job schedule to the approved daily interval and verify the associated command.
  3. Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event.
  4. Deploy the script in the approved supported shell environment with required dependencies and bounded permissions.

Explanation

Correct Answer

A:

The root problem is that The REST client does not distinguish insufficient authorization from retryable transport or server errors. The selected change addresses it directly: Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures. Verify the outcome: A permitted API call succeeds while denied operations report a clear nonretryable authorization error.

Incorrect Answers

B:

This action concerns nx os scheduler job interval, where The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The reported failure instead stems from The REST client does not distinguish insufficient authorization from retryable transport or server errors.

C:

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 corrective response here is “Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures”; 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 an automation client retries an administrative NX-API request repeatedly after receiving HTTP 403, misclassifying authorization denial as a transient device failure; this control addresses a different failure condition.

Question 324

A Nexus, UCS or MDS operations team encounters this issue: Two SAN-connected server profiles are provisioned with overlapping manually assigned virtual HBA worldwide port names, disrupting their distinct storage identities. Which verification result most directly demonstrates successful repair?

  1. Both servers log in with their own WWPN identities and see only their authorized storage paths.
  2. The replacement blade receives the designated server identity and boots its workload according to policy.
  3. A controlled fabric failover retains authorized server network reachability without duplicate MAC or VLAN problems.
  4. All required vNICs receive unique authorized MAC addresses without conflicting with existing profiles.

Explanation

Correct Answer

A:

This observation validates ucs wwpn pool uniqueness: The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. The corresponding corrective action is: Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The server identity has not been abstracted through approved UCS service profile and identity-pool associations. “Associate the intended service profile and its identity pools with the supported replacement hardware” would address that alternative cause, not the condition in this question: the vHBA WWPN allocation violates uniqueness requirements across server storage initiators.

C:

“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 “Replace conflicting values with separate approved WWPN pool allocations and verify SAN fabric registration”, so the alternative does not meet the stated condition.

D:

The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. “Expand or assign a nonoverlapping approved MAC pool and retry the service profile association” applies to that separate problem. The observed case is two SAN-connected server profiles are provisioned with overlapping manually assigned virtual HBA worldwide port names, disrupting their distinct storage identities; choosing this alternative would address the wrong failure mode.

Question 325

A newly commissioned network, compute or storage service reports: An installed UCS blade becomes unreachable when the only mapped I/O module path is disabled although a second IOM is physically available. Which deployment safeguard most directly reduces this failure risk?

  1. Update UCS server pool qualifications as new hardware revisions enter the chassis.
  2. Reconcile UCS VLAN definitions with upstream trunk allow-lists during every server network expansion.
  3. Inspect chassis IOM inventory and dual-fabric paths during blade server deployment.
  4. Review template association and change propagation before broad UCS configuration updates.

Explanation

Correct Answer

C:

This safeguard addresses ucs chassis iom fabric path redundancy: The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. The appropriate prevention is: Inspect chassis IOM inventory and dual-fabric paths during blade server deployment. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The server pool qualification policy does not limit placement to servers with the required hardware capabilities. “Update UCS server pool qualifications as new hardware revisions enter the chassis” would address that alternative cause, not the condition in this question: the chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths.

B:

“Reconcile UCS VLAN definitions with upstream trunk allow-lists during every server network expansion” responds to this separate finding: the VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. This question instead needs “Inspect chassis IOM inventory and dual-fabric paths during blade server deployment”, so the alternative does not meet the stated condition.

D:

The configuration process bypasses the intended reusable UCS service profile template inheritance model. “Review template association and change propagation before broad UCS configuration updates” applies to that separate problem. The observed case is an installed UCS blade becomes unreachable when the only mapped I/O module path is disabled although a second IOM is physically available; choosing this alternative would address the wrong failure mode.

Question 326

A Nexus, UCS or MDS operations team encounters this issue: A UCS domain authenticates administrators through a remote server, but a misconfigured AAA order locks out all operators during a network outage. What is the most appropriate remediation for these symptoms?

  1. Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads.
  2. Correct the supported UCS authentication realm order and emergency access procedure under change control.
  3. Assign a supported restricted UCS role and scope matching the storage administration tasks.
  4. Apply the approved organization-scoped Intersight RBAC role for the automation identity.

Explanation

Correct Answer

B:

The root problem is that The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. The selected change addresses it directly: Correct the supported UCS authentication realm order and emergency access procedure under change control. Verify the outcome: Authorized operators authenticate normally through remote AAA and recover access through the documented fallback during an outage.

Incorrect Answers

A:

This action concerns aci microsegmentation useg classification, where The intended microsegmentation EPG classification rules do not distinguish the workload identities. The reported failure instead stems from The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path.

C:

This action concerns ucs manager role based access, where The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. The corrective response here is “Correct the supported UCS authentication realm order and emergency access procedure under change control”; this alternative does not provide that response.

D:

This action concerns intersight organization scoped administrative role, where The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. The stem reports a UCS domain authenticates administrators through a remote server, but a misconfigured AAA order locks out all operators during a network outage; this control addresses a different failure condition.

Question 327

A Nexus, UCS or MDS operations team encounters this issue: An NX-OS switch loses a critical BGP peer, but an automated EEM diagnostic applet never runs because it listens for a different syslog message pattern. Which verification result most directly demonstrates successful repair?

  1. The script executes within its intended environment without changing unapproved host system files.
  2. The device returns a successful structured response and the intended read-only verification completes.
  3. The applet runs only on the targeted peer-down event and preserves the expected diagnostic information.
  4. A permitted API call succeeds while denied operations report a clear nonretryable authorization error.

Explanation

Correct Answer

C:

This observation validates nx os eem syslog event trigger: The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. The corresponding corrective action is: Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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

B:

“Send the supported NX-API request in the correct JSON or XML representation with matching headers” responds to this separate finding: the NX-API request body and declared content format are inconsistent for the selected endpoint. This question instead needs “Correct the supported EEM event trigger and test its approved diagnostic action against a safe simulated event”, so the alternative does not meet the stated condition.

D:

The REST client does not distinguish insufficient authorization from retryable transport or server errors. “Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures” applies to that separate problem. The observed case is an NX-OS switch loses a critical BGP peer, but an automated EEM diagnostic applet never runs because it listens for a different syslog message pattern; choosing this alternative would address the wrong failure mode.

Question 328

A data center administrator identifies the following risk: A rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping. Which test outcome proves the intended service was restored?

  1. The analyst inspects FCNS and port health but cannot activate or change production zonesets.
  2. Spoofed ARP replies are discarded while authorized clients retain normal gateway connectivity.
  3. Hosts ignore the unauthorized router advertisement and retain the approved IPv6 default gateway.
  4. Unauthorized DHCP offers are dropped while valid clients receive leases from the approved server.

Explanation

Correct Answer

D:

This observation validates dhcp snooping trusted server interface: DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. The corresponding corrective action is: Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. “Replace the overly broad MDS role with an approved read-only or scoped monitoring role” would address that alternative cause, not the condition in this question: dHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies.

B:

“Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings” responds to this separate finding: dHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. This question instead needs “Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths”, so the alternative does not meet the stated condition.

C:

The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. “Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports” applies to that separate problem. The observed case is a rogue DHCP server plugged into a Nexus access port supplies unauthorized gateways because the port was mistakenly configured as trusted for DHCP snooping; choosing this alternative would address the wrong failure mode.

Question 329

A data center implementation team investigates the following fault: A replacement UCS fabric interconnect has been installed, but operators have no recent recoverable configuration backup for the domain's identity pools and policies. What is the most appropriate remediation for these symptoms?

  1. Follow a supported staged firmware activation sequence and use a maintenance plan with rollback criteria.
  2. Create or restore an authorized UCS configuration backup and validate the documented recovery procedure.
  3. Create the supported UCS server pool qualification and associate the workload profile with eligible members.
  4. Select a compatible validated firmware package and update the affected server policy under change control.

Explanation

Correct Answer

B:

The root problem is that The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow. The selected change addresses it directly: Create or restore an authorized UCS configuration backup and validate the documented recovery procedure. Verify the outcome: The recovered management domain contains consistent service profiles, pools and fabric policies after restoration.

Incorrect Answers

A:

This action concerns ucs disruptive firmware activation planning, where The upgrade schedule ignores disruptive firmware activation dependencies and data-path redundancy constraints. The reported failure instead stems from The UCS domain disaster-recovery process lacks a tested full configuration backup and restoration workflow.

C:

This action concerns ucs server pool qualification matching, where The server pool qualification policy does not limit placement to servers with the required hardware capabilities. The corrective response here is “Create or restore an authorized UCS configuration backup and validate the documented recovery procedure”; this alternative does not provide that response.

D:

This action concerns ucs firmware policy package compatibility, where The effective UCS host firmware package is inconsistent with the server adapter feature prerequisites. The stem reports a replacement UCS fabric interconnect has been installed, but operators have no recent recoverable configuration backup for the domain's identity pools and policies; this control addresses a different failure condition.

Question 330

During a Cisco data center readiness review, engineers observe: A service profile template should deploy only to blades with a required adapter model, but a broad server pool includes incompatible hardware. What observation best confirms the configuration now behaves correctly?

  1. The chassis and compute nodes are managed through the expected Intersight policy and profile model.
  2. Authorized real-time flows receive the designated priority treatment and bulk traffic retains its separate class.
  3. The guest and external hosts exchange traffic over the authorized VLAN on both supported fabric paths.
  4. The profile associates only with hardware satisfying its documented adapter and compute requirements.

Explanation

Correct Answer

D:

This observation validates ucs server pool qualification matching: The server pool qualification policy does not limit placement to servers with the required hardware capabilities. The corresponding corrective action is: Create the supported UCS server pool qualification and associate the workload profile with eligible members. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. “Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies” would address that alternative cause, not the condition in this question: the server pool qualification policy does not limit placement to servers with the required hardware capabilities.

B:

“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 “Create the supported UCS server pool qualification and associate the workload profile with eligible members”, so the alternative does not meet the stated condition.

C:

The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. “Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access” applies to that separate problem. The observed case is a service profile template should deploy only to blades with a required adapter model, but a broad server pool includes incompatible hardware; choosing this alternative would address the wrong failure mode.