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 34

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.

Question 331

A Nexus, UCS or MDS operations team encounters this issue: A factory-default Nexus switch runs PowerOn Auto Provisioning but fetches a bootstrap configuration intended for a different rack due to an incorrect DHCP-supplied file path. Which corrective change best resolves this problem?

  1. Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources.
  2. Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity.
  3. Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures.
  4. Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology.

Explanation

Correct Answer

B:

The root problem is that The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. The selected change addresses it directly: Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity. Verify the outcome: The switch downloads its own authorized initial configuration and registers in the intended management inventory.

Incorrect Answers

A:

This action concerns terraform plan infrastructure drift, where The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. The reported failure instead stems from The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement.

C:

This action concerns rest api authorization status handling, where The REST client does not distinguish insufficient authorization from retryable transport or server errors. The corrective response here is “Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity”; this alternative does not provide that response.

D:

This action concerns ai workload high bandwidth east west paths, where The data center fabric bandwidth and latency design do not match the high-throughput GPU collective workload. The stem reports a factory-default Nexus switch runs PowerOn Auto Provisioning but fetches a bootstrap configuration intended for a different rack due to an incorrect DHCP-supplied file path; this control addresses a different failure condition.

Question 332

During a Cisco data center readiness review, engineers observe: A storage administrator is given a full UCS administrator role even though the job requires only SAN and vHBA policy visibility. What observation best confirms the configuration now behaves correctly?

  1. Authorized operators authenticate normally through remote AAA and recover access through the documented fallback during an outage.
  2. The identity updates permitted server profiles in its organization and receives denials elsewhere.
  3. The user can inspect authorized SAN settings but cannot change unrelated server identity and LAN policies.
  4. The approved HBA logs in while a test unapproved WWPN is rejected by the protected fabric port.

Explanation

Correct Answer

C:

This observation validates ucs manager role based access: The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. The corresponding corrective action is: Assign a supported restricted UCS role and scope matching the storage administration tasks. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. “Correct the supported UCS authentication realm order and emergency access procedure under change control” would address that alternative cause, not the condition in this question: the UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities.

B:

“Apply the approved organization-scoped Intersight RBAC role for the automation identity” responds to this separate finding: the Intersight role assignment is not scoped to the authorized organization and permitted resource actions. This question instead needs “Assign a supported restricted UCS role and scope matching the storage administration tasks”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a storage administrator is given a full UCS administrator role even though the job requires only SAN and vHBA policy visibility; choosing this alternative would address the wrong failure mode.

Question 333

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 deployment safeguard most directly reduces this failure risk?

  1. Document file versus block protocols as separate design decisions in storage onboarding.
  2. Include EPLD impact and recovery planning when scheduling MDS component software updates.
  3. Use capture scope and SAN data sensitivity review before activating port mirroring.
  4. Review SAN health telemetry and alert thresholds after changes in storage workload patterns.

Explanation

Correct Answer

B:

This safeguard addresses cisco mds epld hardware dependency: The storage switch plan omits an EPLD package compatibility assessment for the target hardware and image. The appropriate prevention is: Include EPLD impact and recovery planning when scheduling MDS component software updates. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. “Document file versus block protocols as separate design decisions in storage onboarding” would address that alternative cause, not the condition in this question: the storage switch plan omits an EPLD package compatibility assessment for the target hardware and image.

C:

“Use capture scope and SAN data sensitivity review before activating port mirroring” responds to this separate finding: the Fibre Channel SPAN session source does not identify the failing interface or service path. This question instead needs “Include EPLD impact and recovery planning when scheduling MDS component software updates”, so the alternative does not meet the stated condition.

D:

The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. “Review SAN health telemetry and alert thresholds after changes in storage workload patterns” applies to that separate problem. The observed case is an MDS chassis upgrade plan ignores a line-card EPLD requirement even though Cisco's release prerequisites identify hardware programming compatibility work; choosing this alternative would address the wrong failure mode.

Question 334

A data center implementation team investigates the following fault: 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 preventive control would best avoid repeating this fault?

  1. Exercise break-glass access and credential rotation under controlled audit conditions.
  2. Test actual AAA command authorization and accounting for each approved Nexus support role.
  3. Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes.
  4. Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added.

Explanation

Correct Answer

B:

This safeguard addresses nx os tacacs role mapping: The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. The appropriate prevention is: Test actual AAA command authorization and accounting for each approved Nexus support role. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The management access policy lacks a tested protected local recovery identity for remote AAA outages. “Exercise break-glass access and credential rotation under controlled audit conditions” 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.

C:

“Audit trusted DHCP-snooping interfaces and VLAN activation during access-layer changes” responds to this separate finding: dHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. This question instead needs “Test actual AAA command authorization and accounting for each approved Nexus support role”, so the alternative does not meet the stated condition.

D:

DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. “Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added” 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 335

While checking a production data center change, the team finds: An MDS inter-switch link is online but initiators in VSAN 30 cannot reach targets on the far switch after a new trunk was introduced. After remediation, which acceptance result is most relevant?

  1. A time-aligned report identifies the affected SAN ports and correlates counters with storage latency.
  2. The initiator completes FLOGI and receives a valid FCID in the correct SAN fabric.
  3. The target and initiator register and exchange traffic inside VSAN 30 without affecting other VSANs.
  4. Both members become operational in the port channel and load distribution remains stable.

Explanation

Correct Answer

C:

This observation validates fibre channel isl trunk vsan allowance: The FC trunk does not carry the required VSAN membership consistently between the two MDS switches. The corresponding corrective action is: Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. “Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis” would address that alternative cause, not the condition in this question: the FC trunk does not carry the required VSAN membership consistently between the two MDS switches.

B:

“Correct the supported F-port settings and investigate FLOGI exchange for the intended initiator” responds to this separate finding: the initiator has not completed successful fabric login and thus has no authorized FCID assignment. This question instead needs “Permit the authorized VSAN on both ends of the FC trunk and verify its active trunk status”, so the alternative does not meet the stated condition.

D:

The FC port channel and prospective member disagree on required operational attributes for bundling. “Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member” applies to that separate problem. The observed case is an MDS inter-switch link is online but initiators in VSAN 30 cannot reach targets on the far switch after a new trunk was introduced; choosing this alternative would address the wrong failure mode.

Question 336

While checking a production data center change, the team finds: A rack server must boot from an approved SAN LUN but repeatedly starts the local disk after a BIOS update changes its boot device priority. What observation best confirms the configuration now behaves correctly?

  1. The replacement blade receives the designated server identity and boots its workload according to policy.
  2. A controlled reboot starts the server from the authorized SAN boot target and reaches the expected OS.
  3. Both intended fabric paths enumerate the chassis and associated blades under UCS management.
  4. Authorized operators can open CIMC over the management path without exposing it on the application data plane.

Explanation

Correct Answer

B:

This observation validates ucs c series boot policy device order: The configured boot-device order does not select the intended SAN boot path before local storage. The corresponding corrective action is: Restore the supported boot policy and required SAN adapter path in the correct boot-device order. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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 configured boot-device order does not select the intended SAN boot path before local storage.

C:

“Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis” responds to this separate finding: the chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. This question instead needs “Restore the supported boot policy and required SAN adapter path in the correct boot-device order”, so the alternative does not meet the stated condition.

D:

The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. “Configure the approved CIMC out-of-band address, gateway and management VLAN from a secured administration network” applies to that separate problem. The observed case is a rack server must boot from an approved SAN LUN but repeatedly starts the local disk after a BIOS update changes its boot device priority; choosing this alternative would address the wrong failure mode.

Question 337

During a Cisco data center readiness review, engineers observe: A new access switch unexpectedly becomes the spanning-tree root and traffic now follows a slow backup inter-switch link across the data center. Which operational guardrail would prevent a similar outage?

  1. Audit IPv6 routing area design and neighbor status during dual-stack network changes.
  2. Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover.
  3. Apply consistent STP root-guard and bridge-priority review when adding access switches.
  4. Document orphan workloads and test their failure conditions independently of dual-homed vPC hosts.

Explanation

Correct Answer

C:

This safeguard addresses rstp root bridge placement: Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. The appropriate prevention is: Apply consistent STP root-guard and bridge-priority review when adding access switches. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

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: bridge priority design does not select the intended distribution switches as the RSTP root and secondary root.

B:

“Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover” responds to this separate finding: the vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. This question instead needs “Apply consistent STP root-guard and bridge-priority review when adding access switches”, 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. “Document orphan workloads and test their failure conditions independently of dual-homed vPC hosts” applies to that separate problem. The observed case is a new access switch unexpectedly becomes the spanning-tree root and traffic now follows a slow backup inter-switch link across the data center; choosing this alternative would address the wrong failure mode.

Question 338

During a Cisco data center readiness review, engineers observe: Two workloads in a shared ACI subnet require different policies, but both inherit the same broad EPG because no microsegmentation attributes are matched. What observation best confirms the configuration now behaves correctly?

  1. Application sessions traverse the authorized EPG path and prohibited traffic remains blocked.
  2. The intended OSPF adjacency remains authenticated across the key-rotation window with old keys retired safely.
  3. The two workloads receive their distinct security policies while permitted shared services remain reachable.
  4. The analyst inspects FCNS and port health but cannot activate or change production zonesets.

Explanation

Correct Answer

C:

This observation validates aci microsegmentation useg classification: The intended microsegmentation EPG classification rules do not distinguish the workload identities. The corresponding corrective action is: Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads. Evidence about a different component does not establish the requested service outcome.

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

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 “Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads”, 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 two workloads in a shared ACI subnet require different policies, but both inherit the same broad EPG because no microsegmentation attributes are matched; choosing this alternative would address the wrong failure mode.

Question 339

A data center administrator identifies the following risk: A fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes. 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 time-series reports expose the loss interval and correlate it with the affected interfaces and fabric paths.
  3. A staged test establishes the actual traffic impact and the upgrade follows the approved compatibility plan.
  4. The analyzer receives copied packets from the target flow without becoming part of normal switching paths.

Explanation

Correct Answer

B:

This observation validates nexus dashboard assurance and streaming telemetry: The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. The corresponding corrective action is: Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

Flow-export destination reachability or the configured source and monitoring VRF are incorrect. “Repair the approved flow exporter source, destination and transport route, and verify collector acceptance” would address that alternative cause, not the condition in this question: the monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events.

C:

“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 “Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes; choosing this alternative would address the wrong failure mode.

Question 340

During a Cisco data center readiness review, engineers observe: 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 operational guardrail would prevent a similar outage?

  1. Validate failover semantics against the host operating system teaming configuration before production use.
  2. Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment.
  3. Monitor pool utilization and reserve addresses before deploying large numbers of server profiles.
  4. Maintain service profile templates and identity pools independent of individual server serial numbers.

Explanation

Correct Answer

A:

This safeguard addresses ucs vnic fabric failover connectivity: The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. The appropriate prevention is: Validate failover semantics against the host operating system teaming configuration before production use. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The vHBA WWPN allocation violates uniqueness requirements across server storage initiators. “Audit WWPN pool ranges and identity assignment for uniqueness before UCS service profile deployment” would address that alternative cause, not the condition in this question: the UCS vNIC fabric placement and failover policy do not provide the intended redundant network path.

C:

“Monitor pool utilization and reserve addresses before deploying large numbers of server profiles” responds to this separate finding: the UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. This question instead needs “Validate failover semantics against the host operating system teaming configuration before production use”, so the alternative does not meet the stated condition.

D:

The server identity has not been abstracted through approved UCS service profile and identity-pool associations. “Maintain service profile templates and identity pools independent of individual server serial numbers” applies to that separate problem. The observed case is a dual-fabric UCS server unexpectedly loses the same application VLAN when one fabric interconnect fails because its vNIC failover behavior is not coordinated; choosing this alternative would address the wrong failure mode.