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 20

Question 190

A newly commissioned network, compute or storage service reports: An engineer runs a Linux shell script inside the Nexus host environment and assumes it has the same dependencies and resource isolation as a supported Guest Shell container. What observation best confirms the configuration now behaves correctly?

  1. Repeated execution converges to the same desired configuration without unintended duplicate changes.
  2. The device returns a successful structured response and the intended read-only verification completes.
  3. A permitted API call succeeds while denied operations report a clear nonretryable authorization error.
  4. The script executes within its intended environment without changing unapproved host system files.

Explanation

Correct Answer

D:

This observation validates nexus bash shell and guest shell isolation: The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. The corresponding corrective action is: Deploy the script in the approved supported shell environment with required dependencies and bounded permissions. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The script lacks an idempotent precheck to compare desired and current network device state. “Query existing NX-OS state before applying only the necessary authorized configuration differences” would address that alternative cause, not the condition in this question: the deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.

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 “Deploy the script in the approved supported shell environment with required dependencies and bounded permissions”, so the alternative does not meet the stated condition.

C:

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 engineer runs a Linux shell script inside the Nexus host environment and assumes it has the same dependencies and resource isolation as a supported Guest Shell container; choosing this alternative would address the wrong failure mode.

Question 191

A newly commissioned network, compute or storage service reports: A packet-capture appliance shows no useful frames after a SPAN session was configured with the destination set to an ordinary forwarding interface. After remediation, which acceptance result is most relevant?

  1. The analyzer receives copied packets from the target flow without becoming part of normal switching paths.
  2. The time-series reports expose the loss interval and correlate it with the affected interfaces and fabric paths.
  3. Hardware and software component versions match the approved release prerequisites after controlled maintenance.
  4. The collector receives valid sampled flow records with the expected device identity and timestamps.

Explanation

Correct Answer

A:

This observation validates span source and destination isolation: The SPAN session source and dedicated monitor destination roles were assigned incorrectly. The corresponding corrective action is: Configure the authorized SPAN source and monitor-only destination and confirm the capture appliance connection. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. “Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics” would address that alternative cause, not the condition in this question: the SPAN session source and dedicated monitor destination roles were assigned incorrectly.

C:

“Review supported EPLD package requirements and schedule the component update using the prescribed procedure” responds to this separate finding: the planned software transition omits the EPLD compatibility and operational impact assessment. This question instead needs “Configure the authorized SPAN source and monitor-only destination and confirm the capture appliance connection”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a packet-capture appliance shows no useful frames after a SPAN session was configured with the destination set to an ordinary forwarding interface; choosing this alternative would address the wrong failure mode.

Question 192

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. Which implementation action should the engineer take first?

  1. Associate the intended service profile and its identity pools with the supported replacement hardware.
  2. Apply supported vNIC failover and network-fabric policy for the particular adapter and teaming design.
  3. Update the service profile boot policy to use the valid target WWPN and correct boot LUN parameters.
  4. Expand or assign a nonoverlapping approved MAC pool and retry the service profile association.

Explanation

Correct Answer

D:

The root problem is that The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities. The selected change addresses it directly: Expand or assign a nonoverlapping approved MAC pool and retry the service profile association. Verify the outcome: All required vNICs receive unique authorized MAC addresses without conflicting with existing profiles.

Incorrect Answers

A:

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 reported failure instead stems from The UCS MAC identity pool has insufficient available addresses for the requested vNIC identities.

B:

This action concerns ucs vnic fabric failover connectivity, where The UCS vNIC fabric placement and failover policy do not provide the intended redundant network path. The corrective response here is “Expand or assign a nonoverlapping approved MAC pool and retry the service profile association”; this alternative does not provide that response.

C:

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 stem reports a newly attached service profile cannot create its virtual network adapters because every address in its assigned MAC pool is already allocated; this control addresses a different failure condition.

Question 193

A data center implementation team investigates the following fault: 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. What ongoing validation should operations establish for this service?

  1. Review EEM triggers and action privilege requirements whenever NX-OS log formats or releases change.
  2. Validate API schema and content-type handling before enabling configuration-changing requests.
  3. Test rerun behavior and configuration diffs before scheduling on-box Python automation.
  4. Document shell boundaries and supported packages before on-box automation deployment.

Explanation

Correct Answer

A:

This safeguard addresses nx os eem syslog event trigger: The embedded event manager event detector does not match the actual authorized BGP neighbor-down message. The appropriate prevention is: Review EEM triggers and action privilege requirements whenever NX-OS log formats or releases change. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

B:

The NX-API request body and declared content format are inconsistent for the selected endpoint. “Validate API schema and content-type handling before enabling configuration-changing requests” 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.

C:

“Test rerun behavior and configuration diffs before scheduling on-box Python automation” responds to this separate finding: the script lacks an idempotent precheck to compare desired and current network device state. This question instead needs “Review EEM triggers and action privilege requirements whenever NX-OS log formats or releases change”, so the alternative does not meet the stated condition.

D:

The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment. “Document shell boundaries and supported packages before on-box automation deployment” 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 194

While checking a production data center change, the team finds: An MDS maintenance team attempts a nondisruptive SAN switch upgrade while a required redundancy check and supported release-path validation are incomplete. Which approved technology action addresses this incident most directly?

  1. Match compatible FC trunk, VSAN and port-channel parameters on every approved bundle member.
  2. Set a supported FC SPAN monitor source for the affected port and the approved capture destination.
  3. Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method.
  4. Enable supported MDS telemetry and Nexus Dashboard fabric views for congestion and error analysis.

Explanation

Correct Answer

C:

The root problem is that The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites. The selected change addresses it directly: Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method. Verify the outcome: A lab or pilot establishes the expected outage characteristics and the approved upgrade completes safely.

Incorrect Answers

A:

This action concerns fibre channel port channel member consistency, where The FC port channel and prospective member disagree on required operational attributes for bundling. The reported failure instead stems from The selected MDS software upgrade path has unverified nondisruptive and fabric redundancy prerequisites.

B:

This action concerns cisco mds span fibre channel troubleshooting, where The Fibre Channel SPAN session source does not identify the failing interface or service path. The corrective response here is “Check Cisco release compatibility and the required VSAN and ISL health before selecting the upgrade method”; this alternative does not provide that response.

D:

This action concerns nexus dashboard san performance assurance, where The SAN observability baseline does not collect relevant port performance metrics and historical assurance trends. The stem reports an MDS maintenance team attempts a nondisruptive SAN switch upgrade while a required redundancy check and supported release-path validation are incomplete; this control addresses a different failure condition.

Question 195

A newly commissioned network, compute or storage service reports: A UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults. What observation best confirms the configuration now behaves correctly?

  1. Both servers log in with their own WWPN identities and see only their authorized storage paths.
  2. Intersight records the hardware fault and resolution, while workload stability returns after repair.
  3. The server recognizes the protected boot volume and tolerates the documented single-disk test condition.
  4. The hypervisor passes hardware virtualization checks and starts a test virtual machine successfully.

Explanation

Correct Answer

B:

This observation validates intersight hardware telemetry alarm review: The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. The corresponding corrective action is: Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend. Evidence about a different component does not establish the requested service outcome.

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 monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history.

C:

“Create and verify the supported redundant local virtual drive and align the BIOS boot entry to it” responds to this separate finding: the server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. This question instead needs “Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend”, so the alternative does not meet the stated condition.

D:

The BIOS policy disables required CPU virtualization support expected by the approved hypervisor. “Enable the supported virtualization features using the appropriate UCS BIOS policy and validate a controlled reboot” applies to that separate problem. The observed case is a UCS rack server remains pingable but begins memory error correction bursts, while monitoring checks only network availability and misses hardware faults; choosing this alternative would address the wrong failure mode.

Question 196

During a Cisco data center readiness review, engineers observe: 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 implementation action should the engineer take first?

  1. Verify target port FLOGI and FCNS registration and restore the authorized target attachment.
  2. Assign the target port to the approved VSAN and verify its effective FCNS and zone membership.
  3. Configure the approved FCoE VLAN and supported Fibre Channel Forwarder connectivity for that host path.
  4. Connect the NPV device to a supported upstream NPIV fabric port and use appropriate proxy login design.

Explanation

Correct Answer

B:

The root problem is that The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset. The selected change addresses it directly: Assign the target port to the approved VSAN and verify its effective FCNS and zone membership. Verify the outcome: The authorized target and host appear in the same intended VSAN and storage access succeeds.

Incorrect Answers

A:

This action concerns fibre channel name server registration, where The target's FCNS registration is absent or stale even though the initiator's local FLOGI succeeded. The reported failure instead stems from The target-facing FC interface belongs to the wrong VSAN and cannot participate in the intended zoneset.

C:

This action concerns fibre channel over ethernet storage vlan mapping, where The converged network design does not map the FCoE traffic to the required supported FCF and VSAN service. The corrective response here is “Assign the target port to the approved VSAN and verify its effective FCNS and zone membership”; this alternative does not provide that response.

D:

This action concerns npv and npiv switch roles, where NPV mode provides proxy forwarding for connected initiators and relies on an upstream NPIV-capable fabric switch. The stem reports 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; this control addresses a different failure condition.

Question 197

A data center administrator identifies the following risk: A rack server intended for local mirrored boot disks reports an absent boot volume after the storage controller was left with unconfigured physical drives. What ongoing validation should operations establish for this service?

  1. Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot.
  2. Check local RAID configuration, disk health and boot target during UCS C-Series acceptance.
  3. Include hardware sensors and fault trend alerts in the standard UCS server health baseline.
  4. Review association change previews, reboot implications and backout steps before production reassignment.

Explanation

Correct Answer

B:

This safeguard addresses ucs c series virtual disk raid policy: The server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy. The appropriate prevention is: Check local RAID configuration, disk health and boot target during UCS C-Series acceptance. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The virtual HBA path is not participating in the intended Fibre Channel VSAN end to end. “Check UCS vHBA VSAN mapping and the upstream storage fabric when provisioning SAN boot” would address that alternative cause, not the condition in this question: the server's local storage controller lacks the approved mirrored virtual drive configuration for the boot policy.

C:

“Include hardware sensors and fault trend alerts in the standard UCS server health baseline” responds to this separate finding: the monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. This question instead needs “Check local RAID configuration, disk health and boot target during UCS C-Series acceptance”, so the alternative does not meet the stated condition.

D:

The service profile reassociation workflow ignores its potential disruptive impact on server identities and boot settings. “Review association change previews, reboot implications and backout steps before production reassignment” applies to that separate problem. The observed case is a rack server intended for local mirrored boot disks reports an absent boot volume after the storage controller was left with unconfigured physical drives; choosing this alternative would address the wrong failure mode.

Question 198

A data center administrator identifies the following risk: An Intersight-managed UCS X blade receives a server profile but fails its deployment because mandatory network and storage policy references are missing. Which corrective change best resolves this problem?

  1. Complete the required Intersight policies and deploy the server profile with validated resource assignments.
  2. Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies.
  3. Enable supported hardware inventory and fault monitoring, then investigate the affected DIMM and operational trend.
  4. Reconcile the claim code and target ownership through supported Intersight claiming and access procedures.

Explanation

Correct Answer

A:

The root problem is that The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies. The selected change addresses it directly: Complete the required Intersight policies and deploy the server profile with validated resource assignments. Verify the outcome: The profile deploys without unresolved policy references and the server boots with intended connections.

Incorrect Answers

B:

This action concerns ucs x series intersight managed mode, where The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. The reported failure instead stems from The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies.

C:

This action concerns intersight hardware telemetry alarm review, where The monitoring coverage does not include relevant server hardware health telemetry and Intersight fault history. The corrective response here is “Complete the required Intersight policies and deploy the server profile with validated resource assignments”; this alternative does not provide that response.

D:

This action concerns cisco intersight target claim ownership, where The Intersight device claim and account authorization do not match the approved administrative organization. The stem reports an Intersight-managed UCS X blade receives a server profile but fails its deployment because mandatory network and storage policy references are missing; this control addresses a different failure condition.

Question 199

A data center implementation team investigates the following fault: Two workloads in a shared ACI subnet require different policies, but both inherit the same broad EPG because no microsegmentation attributes are matched. Which design or configuration error caused the described issue?

  1. The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter.
  2. The intended microsegmentation EPG classification rules do not distinguish the workload identities.
  3. Link-layer encryption is not enabled or negotiated for the intended MACsec-protected connection.
  4. DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN.

Explanation

Correct Answer

B:

The technical cause is The intended microsegmentation EPG classification rules do not distinguish the workload identities. The appropriate response is: Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads. Confirm successful repair: The two workloads receive their distinct security policies while permitted shared services remain reachable.

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.

C:

“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 “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:

DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN. “Enable supported dynamic ARP inspection and validate binding data and trusted uplink settings” 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 200

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

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

Explanation

Correct Answer

A:

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

Incorrect Answers

B:

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

C:

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

D:

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