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 11

Question 100

A data center implementation team investigates the following fault: An MDS monitoring analyst receives a network-admin role and can edit SAN zoning despite requiring only fabric health visibility. Which design or configuration error caused the described issue?

  1. The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs.
  2. Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL.
  3. The contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter.
  4. Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities.

Explanation

Correct Answer

A:

The technical cause is The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. The appropriate response is: Replace the overly broad MDS role with an approved read-only or scoped monitoring role. Confirm successful repair: The analyst inspects FCNS and port health but cannot activate or change production zonesets.

Incorrect Answers

B:

Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. “Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs” would address that alternative cause, not the condition in this question: the MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs.

C:

“Correct the ACI contract consumer-provider bindings and permit only the required application port” responds to this separate finding: the contract association does not connect the intended consumer EPG with the approved provider EPG and allowed filter. This question instead needs “Replace the overly broad MDS role with an approved read-only or scoped monitoring role”, 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 an MDS monitoring analyst receives a network-admin role and can edit SAN zoning despite requiring only fabric health visibility; choosing this alternative would address the wrong failure mode.

Question 101

During a Cisco data center readiness review, engineers observe: A Python script sends a Nexus configuration request to NX-API but receives parsing errors because its payload is XML while the request declares JSON encoding. Which approved technology action addresses this incident most directly?

  1. Constrain the approved Ansible inventory and host patterns, then review the playbook diff before execution.
  2. Query existing NX-OS state before applying only the necessary authorized configuration differences.
  3. Set the supported scheduler job schedule to the approved daily interval and verify the associated command.
  4. Send the supported NX-API request in the correct JSON or XML representation with matching headers.

Explanation

Correct Answer

D:

The root problem is that The NX-API request body and declared content format are inconsistent for the selected endpoint. The selected change addresses it directly: Send the supported NX-API request in the correct JSON or XML representation with matching headers. Verify the outcome: The device returns a successful structured response and the intended read-only verification completes.

Incorrect Answers

A:

This action concerns ansible inventory variable scoping, where The playbook target inventory and variable precedence do not isolate the intended lab device group. The reported failure instead stems from The NX-API request body and declared content format are inconsistent for the selected endpoint.

B:

This action concerns on box python safe idempotence, where The script lacks an idempotent precheck to compare desired and current network device state. The corrective response here is “Send the supported NX-API request in the correct JSON or XML representation with matching headers”; this alternative does not provide that response.

C:

This action concerns nx os scheduler job interval, where The NX-OS scheduler job timing is not aligned with the intended maintenance frequency. The stem reports a Python script sends a Nexus configuration request to NX-API but receives parsing errors because its payload is XML while the request declares JSON encoding; this control addresses a different failure condition.

Question 102

While checking a production data center change, the team finds: A server NIC connects to an ACI leaf port, but the configured EPG never becomes operational on that port after the tenant was deployed. What is the primary technical reason the deployment fails?

  1. The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.
  2. Flow-export destination reachability or the configured source and monitoring VRF are incorrect.
  3. The leaf has not completed the supported ACI fabric discovery and node-registration workflow.
  4. The ACI VMM domain connection does not synchronize the intended endpoint group to its virtual switch port groups.

Explanation

Correct Answer

A:

The technical cause is The interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment. The appropriate response is: Correct the supported ACI interface policy selector and physical domain association for the host-facing port. Confirm successful repair: APIC reports the expected interface and EPG deployment, and authorized server traffic is forwarded.

Incorrect Answers

B:

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 interface selector and policy-group to physical-domain binding do not deliver the intended EPG attachment.

C:

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

D:

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 server NIC connects to an ACI leaf port, but the configured EPG never becomes operational on that port after the tenant was deployed; choosing this alternative would address the wrong failure mode.

Question 103

A newly commissioned network, compute or storage service reports: An unauthorized Fibre Channel switch is connected to a production MDS ISL and attempts to join the fabric without meeting the planned trusted-switch membership. Which approved technology action addresses this incident most directly?

  1. Correct the authorized TACACS command or role mapping without granting full switch administrator permissions.
  2. Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs.
  3. Configure supported MDS port-security bindings for the intended server initiator and affected VSAN.
  4. Replace the overly broad MDS role with an approved read-only or scoped monitoring role.

Explanation

Correct Answer

B:

The root problem is that Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL. The selected change addresses it directly: Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs. Verify the outcome: The approved peer switch joins the SAN while a nonapproved test switch is denied fabric access.

Incorrect Answers

A:

This action concerns nx os tacacs role mapping, where The centralized AAA server returns a role mapping that lacks the specific least-privilege authorization needed for monitoring. The reported failure instead stems from Fabric binding controls are absent or do not identify the trusted peer switch identities permitted on the ISL.

C:

This action concerns mds fibre channel port security binding, where Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. The corrective response here is “Apply the supported MDS fabric-binding policy that restricts membership to authorized switch WWNs”; this alternative does not provide that response.

D:

This action concerns cisco mds administrative role authorization, where The MDS AAA and RBAC permissions grant zoning mutation privileges beyond monitoring needs. The stem reports an unauthorized Fibre Channel switch is connected to a production MDS ISL and attempts to join the fabric without meeting the planned trusted-switch membership; this control addresses a different failure condition.

Question 104

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

  1. Use standardized single-initiator zoning patterns in the SAN access request process.
  2. Document file versus block protocols as separate design decisions in storage onboarding.
  3. Reconcile NFS export client authorization when hypervisor subnets or hosts change.
  4. Validate iSCSI authentication lifecycle and secret rotation with connectivity testing.

Explanation

Correct Answer

B:

This safeguard addresses nfs file storage versus iscsi block storage: The application storage requirements conflate NFS file-sharing semantics with iSCSI block-device presentation. The appropriate prevention is: Document file versus block protocols as separate design decisions in storage onboarding. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The zone combines initiators beyond the least-privilege single-initiator zoning design. “Use standardized single-initiator zoning patterns in the SAN access request process” 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.

C:

“Reconcile NFS export client authorization when hypervisor subnets or hosts change” responds to this separate finding: the NFS export access rules do not authorize the requesting client address or security identity. This question instead needs “Document file versus block protocols as separate design decisions in storage onboarding”, 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. “Validate iSCSI authentication lifecycle and secret rotation with connectivity testing” 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 105

A newly commissioned network, compute or storage service reports: A new Cisco UCS C-Series rack server boots its operating system, yet the remote administrators cannot access CIMC because the out-of-band address is on an unreachable subnet. Which operational guardrail would prevent a similar outage?

  1. Exercise cluster failover and management reachability during controlled platform maintenance.
  2. Verify CIMC routing, management segmentation and administrator access at rack-server acceptance.
  3. Record boot order and recovery expectations alongside BIOS and SAN maintenance procedures.
  4. Test FI-to-IOM connectivity and chassis discovery after moving server-facing cables.

Explanation

Correct Answer

B:

This safeguard addresses ucs c series cimc management networking: The CIMC management interface has incorrect IP addressing or missing management default gateway reachability. The appropriate prevention is: Verify CIMC routing, management segmentation and administrator access at rack-server acceptance. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The clustered fabric-interconnect pair is not configured or tested for the expected management failover behavior. “Exercise cluster failover and management reachability during controlled platform maintenance” would address that alternative cause, not the condition in this question: the CIMC management interface has incorrect IP addressing or missing management default gateway reachability.

C:

“Record boot order and recovery expectations alongside BIOS and SAN maintenance procedures” responds to this separate finding: the configured boot-device order does not select the intended SAN boot path before local storage. This question instead needs “Verify CIMC routing, management segmentation and administrator access at rack-server acceptance”, 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. “Test FI-to-IOM connectivity and chassis discovery after moving server-facing cables” applies to that separate problem. The observed case is a new Cisco UCS C-Series rack server boots its operating system, yet the remote administrators cannot access CIMC because the out-of-band address is on an unreachable subnet; choosing this alternative would address the wrong failure mode.

Question 106

During a Cisco data center readiness review, engineers observe: An automation client retries an administrative NX-API request repeatedly after receiving HTTP 403, misclassifying authorization denial as a transient device failure. What is the primary technical reason the deployment fails?

  1. The REST client does not distinguish insufficient authorization from retryable transport or server errors.
  2. The deployment confuses NX-OS Bash Shell execution with the separately managed Guest Shell environment.
  3. The script lacks an idempotent precheck to compare desired and current network device state.
  4. The NX-OS scheduler job timing is not aligned with the intended maintenance frequency.

Explanation

Correct Answer

A:

The technical cause is The REST client does not distinguish insufficient authorization from retryable transport or server errors. The appropriate response is: Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures. Confirm successful repair: A permitted API call succeeds while denied operations report a clear nonretryable authorization error.

Incorrect Answers

B:

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 REST client does not distinguish insufficient authorization from retryable transport or server errors.

C:

“Query existing NX-OS state before applying only the necessary authorized configuration differences” responds to this separate finding: the script lacks an idempotent precheck to compare desired and current network device state. This question instead needs “Use a least-privilege API identity and handle HTTP authorization responses distinctly from server failures”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an automation client retries an administrative NX-API request repeatedly after receiving HTTP 403, misclassifying authorization denial as a transient device failure; choosing this alternative would address the wrong failure mode.

Question 107

A newly commissioned network, compute or storage service reports: A UCS domain authenticates administrators through a remote server, but a misconfigured AAA order locks out all operators during a network outage. Which operational guardrail would prevent a similar outage?

  1. Verify DAI enablement and binding accuracy whenever DHCP-protected VLANs are added.
  2. Test UCS AAA dependency failure without weakening audit and least-privilege controls.
  3. Periodically audit Intersight role scopes and API account privileges for privilege creep.
  4. Recertify UCS role assignments after team or responsibility changes.

Explanation

Correct Answer

B:

This safeguard addresses ucs remote aaa fallback authentication: The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. The appropriate prevention is: Test UCS AAA dependency failure without weakening audit and least-privilege controls. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

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

“Periodically audit Intersight role scopes and API account privileges for privilege creep” responds to this separate finding: the Intersight role assignment is not scoped to the authorized organization and permitted resource actions. This question instead needs “Test UCS AAA dependency failure without weakening audit and least-privilege controls”, so the alternative does not meet the stated condition.

D:

The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. “Recertify UCS role assignments after team or responsibility changes” 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 108

While checking a production data center change, the team finds: A UCS service profile contains the correct vNIC VLAN, but the upstream fabric interconnect uplink does not carry the server's new application VLAN. What technical condition most directly accounts for the failure?

  1. The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy.
  2. UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements.
  3. The server pool qualification policy does not limit placement to servers with the required hardware capabilities.
  4. The configuration process bypasses the intended reusable UCS service profile template inheritance model.

Explanation

Correct Answer

A:

The technical cause is The VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy. The appropriate response is: Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access. Confirm successful repair: The guest and external hosts exchange traffic over the authorized VLAN on both supported fabric paths.

Incorrect Answers

B:

UCS system QoS class and vNIC network-control treatment are not aligned to the traffic priority requirements. “Correct the supported UCS class-of-service and network QoS policy for the intended application traffic” would address that alternative cause, not the condition in this question: the VLAN is absent from the approved UCS LAN uplink connectivity or external switch trunk policy.

C:

“Create the supported UCS server pool qualification and associate the workload profile with eligible members” responds to this separate finding: the server pool qualification policy does not limit placement to servers with the required hardware capabilities. This question instead needs “Permit the intended VLAN on the correct UCS fabric uplink and downstream network policies without broad wildcard access”, so the alternative does not meet the stated condition.

D:

The configuration process bypasses the intended reusable UCS service profile template inheritance model. “Use an approved updating service profile template and apply governed changes to its associated server profiles” applies to that separate problem. The observed case is a UCS service profile contains the correct vNIC VLAN, but the upstream fabric interconnect uplink does not carry the server's new application VLAN; choosing this alternative would address the wrong failure mode.

Question 109

A data center administrator identifies the following risk: A critical database server uses a single-homed orphan port on one vPC peer and loses service during peer-link failure despite other paths remaining up. What preventive control would best avoid repeating this fault?

  1. Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover.
  2. Check channel mode, speed, VLAN and allowed-interface consistency before bringing up bundled links.
  3. Document orphan workloads and test their failure conditions independently of dual-homed vPC hosts.
  4. Apply consistent STP root-guard and bridge-priority review when adding access switches.

Explanation

Correct Answer

C:

This safeguard addresses vpc orphan port convergence: The failure design does not account for orphan-port behavior and the chosen peer recovery semantics. The appropriate prevention is: Document orphan workloads and test their failure conditions independently of dual-homed vPC hosts. Other subsystem controls would not address the specified recurring failure.

Incorrect Answers

A:

The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. “Audit peer-link trunk coverage alongside vPC member VLAN changes before cutover” would address that alternative cause, not the condition in this question: the failure design does not account for orphan-port behavior and the chosen peer recovery semantics.

B:

“Check channel mode, speed, VLAN and allowed-interface consistency before bringing up bundled links” responds to this separate finding: the port-channel peers use incompatible LACP negotiation settings and cannot aggregate all intended members. This question instead needs “Document orphan workloads and test their failure conditions independently of dual-homed vPC hosts”, so the alternative does not meet the stated condition.

D:

Bridge priority design does not select the intended distribution switches as the RSTP root and secondary root. “Apply consistent STP root-guard and bridge-priority review when adding access switches” applies to that separate problem. The observed case is a critical database server uses a single-homed orphan port on one vPC peer and loses service during peer-link failure despite other paths remaining up; choosing this alternative would address the wrong failure mode.

Question 110

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. Which approved technology action addresses this incident most directly?

  1. Correct the supported UCS authentication realm order and emergency access procedure under change control.
  2. Assign a supported restricted UCS role and scope matching the storage administration tasks.
  3. Configure supported MDS port-security bindings for the intended server initiator and affected VSAN.
  4. Apply the approved organization-scoped Intersight RBAC role for the automation identity.

Explanation

Correct Answer

B:

The root problem is that The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities. The selected change addresses it directly: Assign a supported restricted UCS role and scope matching the storage administration tasks. Verify the outcome: The user can inspect authorized SAN settings but cannot change unrelated server identity and LAN policies.

Incorrect Answers

A:

This action concerns ucs remote aaa fallback authentication, where The UCS login realm and remote AAA fallback policy do not provide the documented secured recovery path. The reported failure instead stems from The UCS administrative role assignment grants privileges beyond the user's defined operational responsibilities.

C:

This action concerns mds fibre channel port security binding, where Fibre Channel port security does not restrict fabric logins to the designated authorized WWPN identities. The corrective response here is “Assign a supported restricted UCS role and scope matching the storage administration tasks”; 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 storage administrator is given a full UCS administrator role even though the job requires only SAN and vHBA policy visibility; this control addresses a different failure condition.