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 29

Question 280

A data center administrator identifies the following risk: A UCS domain authenticates administrators through a remote server, but a misconfigured AAA order locks out all operators during a network outage. Which verification result most directly demonstrates successful repair?

  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 two workloads receive their distinct security policies while permitted shared services remain reachable.
  4. The user can inspect authorized SAN settings but cannot change unrelated server identity and LAN policies.

Explanation

Correct Answer

A:

This observation validates ucs remote aaa fallback authentication: The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. The corresponding corrective action is: Correct the supported UCS authentication realm order and emergency access procedure under change control. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

B:

The Intersight role assignment is not scoped to the authorized organization and permitted resource actions. “Apply the approved organization-scoped Intersight RBAC role for the automation identity” would address that alternative cause, not the condition in this question: the UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path.

C:

“Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads” responds to this separate finding: the intended microsegmentation EPG classification rules do not distinguish the workload identities. This question instead needs “Correct the supported UCS authentication realm order and emergency access procedure under change control”, so the alternative does not meet the stated condition.

D:

The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. “Assign a supported restricted UCS role and scope matching the storage administration tasks” applies to that separate problem. The observed case is a UCS domain authenticates administrators through a remote server, but a misconfigured AAA order locks out all operators during a network outage; choosing this alternative would address the wrong failure mode.

Question 281

While checking a production data center change, the team finds: A virtualization platform needs a block device for a raw LUN but the proposed integration offers only an NFS file-system export as though it were an iSCSI target. What observation best confirms the configuration now behaves correctly?

  1. The backup initiator registers only in its permitted VSAN and cannot discover unrelated production zones.
  2. The new host mounts the intended export while an unauthorized client remains denied.
  3. The host discovers an iSCSI target LUN and presents the expected block device to the hypervisor.
  4. The iSCSI login authenticates successfully and the host discovers its authorized block LUN.

Explanation

Correct Answer

C:

This observation validates nfs file storage versus iscsi block storage: The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. The corresponding corrective action is: Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation.

B:

“Update the scoped NFS export policy to include only the approved new hypervisor client addresses” responds to this separate finding: the NFS export access rules do not authorize the requesting client address or security identity. This question instead needs “Select and provision the required supported iSCSI block LUN rather than treating an NFS export as a raw disk”, so the alternative does not meet the stated condition.

D:

The iSCSI initiator and storage target do not agree on the configured CHAP authentication credentials. “Update the approved initiator and target CHAP secret settings using the supported secure workflow” applies to that separate problem. The observed case is a virtualization platform needs a block device for a raw LUN but the proposed integration offers only an NFS file-system export as though it were an iSCSI target; choosing this alternative would address the wrong failure mode.

Question 282

During a Cisco data center readiness review, engineers observe: 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. After remediation, which acceptance result is most relevant?

  1. The backup executes at the intended time without repeated unnecessary administrative sessions.
  2. The approved plan makes intended changes and leaves unrelated network resources intact.
  3. The switch downloads its own authorized initial configuration and registers in the intended management inventory.
  4. Collective workload tests meet the required throughput and latency targets without sustained link oversubscription.

Explanation

Correct Answer

C:

This observation validates poap initial provisioning ownership: The POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. The corresponding corrective action is: Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. “Set the supported scheduler job schedule to the approved daily interval and verify the associated command” would address that alternative cause, not the condition in this question: the POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement.

B:

“Refresh and inspect the Terraform plan, reconcile authorized drift and then apply only approved resources” responds to this separate finding: the infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. This question instead needs “Correct the controlled DHCP provisioning information and match the bootstrap script to the switch identity”, 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. “Size and validate the supported high-bandwidth fabric links and traffic distribution for the AI training topology” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 283

A Nexus, UCS or MDS operations team encounters this issue: A service profile template should deploy only to blades with a required adapter model, but a broad server pool includes incompatible hardware. Which design or configuration error caused the described issue?

  1. The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths.
  2. The server pool qualification policy does not limit placement to servers with the required hardware capabilities.
  3. The configuration process bypasses the intended reusable UCS service profile template inheritance model.
  4. The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy.

Explanation

Correct Answer

B:

The technical cause is The server pool qualification policy does not limit placement to servers with the required hardware capabilities. The appropriate response is: Create the supported UCS server pool qualification and associate the workload profile with eligible members. Confirm successful repair: The profile associates only with hardware satisfying its documented adapter and compute requirements.

Incorrect Answers

A:

The chassis fabric attachment and server adapter mapping have not been configured for both intended IOM paths. “Restore the supported redundant IOM-to-fabric-interconnect attachments and verify adapter pinning behavior” would address that alternative cause, not the condition in this question: the server pool qualification policy does not limit placement to servers with the required hardware capabilities.

C:

“Use an approved updating service profile template and apply governed changes to its associated server profiles” responds to this separate finding: the configuration process bypasses the intended reusable UCS service profile template inheritance model. 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.

D:

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 284

A newly commissioned network, compute or storage service reports: The underlay BGP neighbors are established, but a new VXLAN leaf does not exchange EVPN endpoint routes after its overlay session was commissioned. What observation best confirms the configuration now behaves correctly?

  1. After an uplink failure, the standby switch becomes active and application traffic uses its available upstream path.
  2. The two routers establish an OSPFv3 Full adjacency and learn the expected IPv6 prefixes.
  3. The leaf receives the intended EVPN routes and remote workloads become reachable over VXLAN.
  4. The intended receivers join and receive source traffic, and PIM control state shows the proper tree.

Explanation

Correct Answer

C:

This observation validates mp-BGP evpn address family activation: The BGP peers lack the required L2VPN EVPN address-family activation and exchange capability. The corresponding corrective action is: Activate the correct EVPN address family for authorized peers and verify route advertisement policy. Evidence about a different component does not establish the requested service outcome.

Incorrect Answers

A:

The first-hop redundancy design lacks effective upstream object tracking and priority adjustment for the failed link. “Configure supported HSRP tracking and priority decrement so the healthy upstream switch takes the active role” would address that alternative cause, not the condition in this question: the BGP peers lack the required L2VPN EVPN address-family activation and exchange capability.

B:

“Configure matching OSPFv3 area assignments and verify the intended IPv6 interface participation” responds to this separate finding: the OSPFv3 processes attach the shared IPv6 link to incompatible OSPF area contexts. This question instead needs “Activate the correct EVPN address family for authorized peers and verify route advertisement policy”, so the alternative does not meet the stated condition.

D:

The routers do not agree on or reach the required rendezvous-point mapping for the multicast group range. “Restore the approved rendezvous-point mapping and multicast routing reachability for the affected groups” applies to that separate problem. The observed case is the underlay BGP neighbors are established, but a new VXLAN leaf does not exchange EVPN endpoint routes after its overlay session was commissioned; choosing this alternative would address the wrong failure mode.

Question 285

A newly commissioned network, compute or storage service reports: An unauthorized workstation sends IPv6 router advertisements on a Nexus access VLAN, causing nearby hosts to adopt an attacker-controlled default router. What technical condition most directly accounts for the failure?

  1. The intended microsegmentation EPG classification rules do not distinguish the workload identities.
  2. DHCP-snooping address bindings are not being enforced by dynamic ARP inspection on the affected VLAN.
  3. The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements.
  4. DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies.

Explanation

Correct Answer

C:

The technical cause is The access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements. The appropriate response is: Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports. Confirm successful repair: Hosts ignore the unauthorized router advertisement and retain the approved IPv6 default gateway.

Incorrect Answers

A:

The intended microsegmentation EPG classification rules do not distinguish the workload identities. “Configure the approved ACI uSeg EPG attribute matching and contract policy for the separated workloads” would address that alternative cause, not the condition in this question: the access ports lack the supported first-hop security policy needed to restrict untrusted IPv6 router advertisements.

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 “Apply the approved IPv6 RA guard behavior to untrusted host-facing ports while permitting designated router ports”, so the alternative does not meet the stated condition.

D:

DHCP snooping trust is applied to an untrusted edge port and allows unauthorized DHCP server replies. “Remove DHCP-snooping trust from the host access port and retain trust only on authorized server-facing paths” applies to that separate problem. The observed case is an unauthorized workstation sends IPv6 router advertisements on a Nexus access VLAN, causing nearby hosts to adopt an attacker-controlled default router; choosing this alternative would address the wrong failure mode.

Question 286

A data center administrator identifies the following risk: A remote tenant workload is connected to a leaf, yet peer VTEPs never learn the workload MAC address from the EVPN control plane. Which design or configuration error caused the described issue?

  1. IGMP snooping membership state is not refreshed because the VLAN lacks a reachable supported multicast querier.
  2. The tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs.
  3. The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain.
  4. The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy.

Explanation

Correct Answer

D:

The technical cause is The Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy. The appropriate response is: Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI. Confirm successful repair: The remote leaf learns the intended endpoint MAC through a valid EVPN route and forwards frames correctly.

Incorrect Answers

A:

The VLAN lacks a reachable supported multicast querier. “Provide a valid IGMP querier through the routed gateway or supported switching configuration” would address that alternative cause, not the condition in this question: the Ethernet VPN MAC/IP route advertisement for the endpoint is not present or is blocked by policy.

B:

“Align the intended VLAN-to-VNI bindings and associated NVE membership on the participating leaves” responds to this separate finding: the tenant VLAN-to-VNI mappings do not identify the same approved layer-two segment across VTEPs. This question instead needs “Inspect and restore the supported EVPN MAC/IP route export and import for the appropriate tenant VNI”, so the alternative does not meet the stated condition.

C:

The NVE source loopback and remote VTEP reachability are not present in the required underlay routing domain. “Restore routed reachability to authorized NVE source loopbacks before changing endpoint overlay policies” applies to that separate problem. The observed case is a remote tenant workload is connected to a leaf, yet peer VTEPs never learn the workload MAC address from the EVPN control plane; choosing this alternative would address the wrong failure mode.

Question 287

During a Cisco data center readiness review, engineers observe: An engineer applies Terraform changes to network policies without examining the plan, accidentally removing fabric objects that were changed manually after the last state capture. Which operational guardrail would prevent a similar outage?

  1. Document shell boundaries and supported packages before on-box automation deployment.
  2. Version and authenticate POAP bootstrap artifacts while testing device-to-rack mapping before rollout.
  3. Require drift detection and reviewed plan artifacts in Terraform change-control procedures.
  4. Review inventory membership and variable precedence before every network automation deployment.

Explanation

Correct Answer

C:

This safeguard addresses terraform plan infrastructure drift: The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. The appropriate prevention is: Require drift detection and reviewed plan artifacts in Terraform change-control procedures. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation.

B:

“Version and authenticate POAP bootstrap artifacts while testing device-to-rack mapping before rollout” responds to this separate finding: the POAP discovery data identifies the wrong approved bootstrap artifact for the device's placement. This question instead needs “Require drift detection and reviewed plan artifacts in Terraform change-control procedures”, so the alternative does not meet the stated condition.

D:

The playbook target inventory and variable precedence do not isolate the intended lab device group. “Review inventory membership and variable precedence before every network automation deployment” applies to that separate problem. The observed case is an engineer applies Terraform changes to network policies without examining the plan, accidentally removing fabric objects that were changed manually after the last state capture; choosing this alternative would address the wrong failure mode.

Question 288

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

  1. Verify the supported UCS generation and management mode before migrating service policies.
  2. Test FI-to-IOM connectivity and chassis discovery after moving server-facing cables.
  3. Record boot order and recovery expectations alongside BIOS and SAN maintenance procedures.
  4. Verify CIMC routing, management segmentation and administrator access at rack-server acceptance.

Explanation

Correct Answer

C:

This safeguard addresses ucs c series boot policy device order: The configured boot-device order does not select the intended SAN boot path before local storage. The appropriate prevention is: Record boot order and recovery expectations alongside BIOS and SAN maintenance procedures. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. “Verify the supported UCS generation and management mode before migrating service policies” 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.

B:

“Test FI-to-IOM connectivity and chassis discovery after moving server-facing cables” 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 “Record boot order and recovery expectations alongside BIOS and SAN maintenance procedures”, so the alternative does not meet the stated condition.

D:

The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. “Verify CIMC routing, management segmentation and administrator access at rack-server acceptance” 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 289

While checking a production data center change, the team finds: A new UCS server is physically reachable but cannot be managed from the organization's Intersight account because its device claim was associated with a different account. What technical condition most directly accounts for the failure?

  1. The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies.
  2. The platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture.
  3. The Intersight device claim and account authorization do not match the approved administrative organization.
  4. The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured.

Explanation

Correct Answer

C:

The technical cause is The Intersight device claim and account authorization do not match the approved administrative organization. The appropriate response is: Reconcile the claim code and target ownership through supported Intersight claiming and access procedures. Confirm successful repair: The server appears as a manageable authorized target in the correct Intersight organization.

Incorrect Answers

A:

The Intersight server profile lacks a complete set of supported adapter, boot and connectivity policies. “Complete the required Intersight policies and deploy the server profile with validated resource assignments” would address that alternative cause, not the condition in this question: the Intersight device claim and account authorization do not match the approved administrative organization.

B:

“Use the supported UCS X-Series Intersight Managed Mode workflow and associate appropriate server profile policies” responds to this separate finding: the platform deployment assumes a management mode inconsistent with the intended UCS X-Series architecture. This question instead needs “Reconcile the claim code and target ownership through supported Intersight claiming and access procedures”, so the alternative does not meet the stated condition.

D:

The chassis discovery path between the fabric interconnect and its I/O modules is absent or misconfigured. “Correct the supported fabric-interconnect server-port and chassis connectivity assignments, then rediscover the chassis” applies to that separate problem. The observed case is a new UCS server is physically reachable but cannot be managed from the organization's Intersight account because its device claim was associated with a different account; choosing this alternative would address the wrong failure mode.

Question 290

While checking a production data center change, the team finds: A fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes. Which implementation action should the engineer take first?

  1. Configure the authorized SPAN source and monitor-only destination and confirm the capture appliance connection.
  2. Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics.
  3. Repair the approved flow exporter source, destination and transport route, and verify collector acceptance.
  4. Add the authorized VLAN to the peer-link trunk and resolve the corresponding vPC consistency alarms.

Explanation

Correct Answer

B:

The root problem is that The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. The selected change addresses it directly: Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics. Verify the outcome: The time-series reports expose the loss interval and correlate it with the affected interfaces and fabric paths.

Incorrect Answers

A:

This action concerns span source and destination isolation, where The SPAN session source and dedicated monitor destination roles were assigned incorrectly. The reported failure instead stems from The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events.

C:

This action concerns netflow exporter reachability, where Flow-export destination reachability or the configured source and monitoring VRF are incorrect. The corrective response here is “Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics”; this alternative does not provide that response.

D:

This action concerns vpc peer link consistency, where The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The stem reports a fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes; this control addresses a different failure condition.