cert
cert-1
cert-2

Pass Cisco 300-640 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
300-640 Exam - Verified By Experts
300-640 Premium File

300-640 Premium File

$89.99
$98.99
  • Premium File 60 Questions & Answers. Last Update: Nov 10, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$98.99
$89.99
accept 10 downloads in the last 7 days
block-screenshots
Cisco 300-640 Practice Test 43

Question 420

The acceptance board must decide whether an AI-infrastructure response to consistent ntp for ai infrastructure is fit for controlled operation. The fictional operating facts are: An Intersight-monitored UCS domain uses an unreachable NTP source and certificates appear invalid during maintenance. Signoff cannot rely on a good-looking utilization graph, a change ticket alone or an unmeasured promise. The response must include an appropriate governing engineering principle, a scoped intervention and a separate measurable acceptance criterion. Choose EXACTLY THREE statements that meet those roles.

  1. Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence.
  2. Time synchronization across UCS, fabric, GPU hosts and monitoring is needed for reliable correlation and operational security.
  3. Stage a validated domain profile update with diff review and a reversible maintenance workflow.
  4. UCS power policy must reflect chassis limits, redundant feed capacity and peak AI workload characteristics.
  5. Nodes remain within the documented clock skew tolerance and cross-system events align.
  6. Maximum approved training load stays within electrical limits without involuntary power capping or host resets.

Explanation

Correct Answer

A:

An Intersight-monitored UCS domain uses an unreachable NTP source and certificates appear invalid during maintenance. Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence. Time synchronization across UCS, fabric, GPU hosts and monitoring is needed for reliable correlation and operational security.

B:

An Intersight-monitored UCS domain uses an unreachable NTP source and certificates appear invalid during maintenance. Time synchronization across UCS, fabric, GPU hosts and monitoring is needed for reliable correlation and operational security. Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence.

E:

An Intersight-monitored UCS domain uses an unreachable NTP source and certificates appear invalid during maintenance. Nodes remain within the documented clock skew tolerance and cross-system events align. Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence.

Incorrect Answers

C:

Stage a validated domain profile update with diff review and a reversible maintenance workflow. It does not implement the governing rule for this approval: An Intersight-monitored UCS domain uses an unreachable NTP source and certificates appear invalid during maintenance. Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence. Nodes remain within the documented clock skew tolerance and cross-system events align.

D:

UCS power policy must reflect chassis limits, redundant feed capacity and peak AI workload characteristics. It is not the rule that supports the proposed change and acceptance test: An Intersight-monitored UCS domain uses an unreachable NTP source and certificates appear invalid during maintenance. Time synchronization across UCS, fabric, GPU hosts and monitoring is needed for reliable correlation and operational security. Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence.

F:

Maximum approved training load stays within electrical limits without involuntary power capping or host resets. It would not independently demonstrate that the control works: An Intersight-monitored UCS domain uses an unreachable NTP source and certificates appear invalid during maintenance. Nodes remain within the documented clock skew tolerance and cross-system events align. Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence.

Question 421

A data-center AI architecture committee considers nexus dashboard operational rollout in its AI Infrastructure Deployment and Data Management review. At the affected site: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. The committee is deliberately not selecting a vendor product or applying a live change yet. It needs the foundational reasoning that makes the next design decision defensible. Which ONE engineering principle directly governs this situation? Choose ONE answer.

  1. APIC-managed ACI deployment should define logical tenant, endpoint-group and contract policies with validated allowed flows.
  2. Server boot and storage policies must match approved boot targets and multipath recovery requirements.
  3. RoCEv2 uses routable IP/UDP transport but requires consistent fabric MTU, QoS marking and endpoint support across its paths.
  4. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

Explanation

Correct Answer

D:

An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

Incorrect Answers

A:

APIC-managed ACI deployment should define logical tenant, endpoint-group and contract policies with validated allowed flows. It does not govern the condition described: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

B:

Server boot and storage policies must match approved boot targets and multipath recovery requirements. It does not govern the condition described: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

C:

RoCEv2 uses routable IP/UDP transport but requires consistent fabric MTU, QoS marking and endpoint support across its paths. It does not govern the condition described: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

Question 422

An infrastructure diagnostician is investigating nexus dashboard operational rollout for the AI Infrastructure Deployment and Data Management team. The reported incident reads: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Competing teams attribute the symptoms to different layers of the AI stack. Before accepting a hypothesis or touching production settings, the investigator must choose a discriminating set of measurements. Which ONE evidence package is MOST relevant? Choose ONE answer.

  1. Examine proposed diff, current device state, execution identity, idempotence report and rollback plan.
  2. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.
  3. Review claimed server identity, organization roles, assigned policies, compliance drift and rollout scope.
  4. Capture baseline queue health, job completion time, path MTU, host/leaf settings, change-window dependencies and rollback triggers.

Explanation

Correct Answer

B:

An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

Incorrect Answers

A:

Examine proposed diff, current device state, execution identity, idempotence report and rollback plan. That check would not establish the decisive facts for this condition: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

C:

Review claimed server identity, organization roles, assigned policies, compliance drift and rollout scope. That check would not establish the decisive facts for this condition: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

D:

Capture baseline queue health, job completion time, path MTU, host/leaf settings, change-window dependencies and rollback triggers. That check would not establish the decisive facts for this condition: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

Question 423

During a bounded AI-platform change-control review concerning nexus dashboard operational rollout, the site owner reports: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. The proposed work must have a narrow implementation scope, first be validated against the failure evidence and avoid unrelated system-wide tuning. Which ONE intervention should the engineers pilot before any wider rollout? Choose ONE answer.

  1. Choose supported load-distribution behavior and adjust flow placement or links without creating packet reordering hazards.
  2. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.
  3. Apply a supported UCS power policy after confirming rack and chassis electrical budgets.
  4. Configure supported ETS class weights to protect essential shares without starving management and storage traffic.

Explanation

Correct Answer

B:

An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

Incorrect Answers

A:

Choose supported load-distribution behavior and adjust flow placement or links without creating packet reordering hazards. That change would leave the reported problem unresolved: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

C:

Apply a supported UCS power policy after confirming rack and chassis electrical budgets. That change would leave the reported problem unresolved: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

D:

Configure supported ETS class weights to protect essential shares without starving management and storage traffic. That change would leave the reported problem unresolved: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

Question 424

Two independent technical reviewers examine a AI Infrastructure Deployment and Data Management problem involving nexus dashboard operational rollout. Their shared incident log states: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. One reviewer requires measurements capable of separating the observed problem from neighboring failure modes; the other requires a bounded action that follows those measurements. Choose EXACTLY TWO statements that together supply those two parts.

  1. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.
  2. Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence.
  3. Inspect vNIC-to-fabric mappings, adapter queue settings, MAC identity, VLAN membership and actual path MTU.
  4. Review claimed server identity, organization roles, assigned policies, compliance drift and rollout scope.
  5. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

Explanation

Correct Answer

A:

An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

E:

An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

Incorrect Answers

B:

Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence. It is not the scoped response supported by the accompanying evidence: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

C:

Inspect vNIC-to-fabric mappings, adapter queue settings, MAC identity, VLAN membership and actual path MTU. It would not provide the evidence needed for the paired diagnosis and follow-up: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

D:

Review claimed server identity, organization roles, assigned policies, compliance drift and rollout scope. It would not provide the evidence needed for the paired diagnosis and follow-up: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

Question 425

The acceptance board must decide whether an AI-infrastructure response to nexus dashboard operational rollout is fit for controlled operation. The fictional operating facts are: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Signoff cannot rely on a good-looking utilization graph, a change ticket alone or an unmeasured promise. The response must include an appropriate governing engineering principle, a scoped intervention and a separate measurable acceptance criterion. Choose EXACTLY THREE statements that meet those roles.

  1. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.
  2. The targeted fabric change is visible and verified while unrelated sites remain unaffected.
  3. Maximum approved training load stays within electrical limits without involuntary power capping or host resets.
  4. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.
  5. RoCE deployments may need priority flow control on designated loss-sensitive classes, but PFC is not a blanket cure for congestion.
  6. Apply a version-compatible storage or boot policy and test both normal boot and controlled path loss.

Explanation

Correct Answer

A:

An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

B:

An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. The targeted fabric change is visible and verified while unrelated sites remain unaffected. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

D:

An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

Incorrect Answers

C:

Maximum approved training load stays within electrical limits without involuntary power capping or host resets. It would not independently demonstrate that the control works: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. The targeted fabric change is visible and verified while unrelated sites remain unaffected. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

E:

RoCE deployments may need priority flow control on designated loss-sensitive classes, but PFC is not a blanket cure for congestion. It is not the rule that supports the proposed change and acceptance test: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

F:

Apply a version-compatible storage or boot policy and test both normal boot and controlled path loss. It does not implement the governing rule for this approval: An AI center onboards a second fabric into Nexus Dashboard and an operator attempts to push the first fabric's profile without site validation. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

Question 426

A data-center AI architecture committee considers nexus dashboard operational rollout in its AI Infrastructure Deployment and Data Management review. At the affected site: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. The committee is deliberately not selecting a vendor product or applying a live change yet. It needs the foundational reasoning that makes the next design decision defensible. Which ONE engineering principle directly governs this situation? Choose ONE answer.

  1. Server boot and storage policies must match approved boot targets and multipath recovery requirements.
  2. RoCEv2 uses routable IP/UDP transport but requires consistent fabric MTU, QoS marking and endpoint support across its paths.
  3. AI-ready fabric automation should follow the currently supported Cisco Hyperfabric deployment and hardware prerequisites.
  4. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

Explanation

Correct Answer

D:

A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

Incorrect Answers

A:

Server boot and storage policies must match approved boot targets and multipath recovery requirements. It does not govern the condition described: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

B:

RoCEv2 uses routable IP/UDP transport but requires consistent fabric MTU, QoS marking and endpoint support across its paths. It does not govern the condition described: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

C:

AI-ready fabric automation should follow the currently supported Cisco Hyperfabric deployment and hardware prerequisites. It does not govern the condition described: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

Question 427

An infrastructure diagnostician is investigating nexus dashboard operational rollout for the AI Infrastructure Deployment and Data Management team. The reported incident reads: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Competing teams attribute the symptoms to different layers of the AI stack. Before accepting a hypothesis or touching production settings, the investigator must choose a discriminating set of measurements. Which ONE evidence package is MOST relevant? Choose ONE answer.

  1. Check UCS domain profiles, fabric interconnect state, policy inheritance, version support and planned change impact.
  2. Compare clock offset, NTP source reachability, drift, log timestamps and monitoring collector time bases.
  3. Correlate ECN marking, switch queue depth, RTT, endpoint congestion control and packet loss during collective bursts.
  4. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

Explanation

Correct Answer

D:

A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

Incorrect Answers

A:

Check UCS domain profiles, fabric interconnect state, policy inheritance, version support and planned change impact. That check would not establish the decisive facts for this condition: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

B:

Compare clock offset, NTP source reachability, drift, log timestamps and monitoring collector time bases. That check would not establish the decisive facts for this condition: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

C:

Correlate ECN marking, switch queue depth, RTT, endpoint congestion control and packet loss during collective bursts. That check would not establish the decisive facts for this condition: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

Question 428

During a bounded AI-platform change-control review concerning nexus dashboard operational rollout, the site owner reports: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. The proposed work must have a narrow implementation scope, first be validated against the failure evidence and avoid unrelated system-wide tuning. Which ONE intervention should the engineers pilot before any wider rollout? Choose ONE answer.

  1. Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence.
  2. Choose supported load-distribution behavior and adjust flow placement or links without creating packet reordering hazards.
  3. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.
  4. Apply a version-compatible storage or boot policy and test both normal boot and controlled path loss.

Explanation

Correct Answer

C:

A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.

Incorrect Answers

A:

Use approved redundant time sources and consistent UCS or host NTP policy, then verify convergence. That change would leave the reported problem unresolved: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

B:

Choose supported load-distribution behavior and adjust flow placement or links without creating packet reordering hazards. That change would leave the reported problem unresolved: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

D:

Apply a version-compatible storage or boot policy and test both normal boot and controlled path loss. That change would leave the reported problem unresolved: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

Question 429

Two independent technical reviewers examine a AI Infrastructure Deployment and Data Management problem involving nexus dashboard operational rollout. Their shared incident log states: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. One reviewer requires measurements capable of separating the observed problem from neighboring failure modes; the other requires a bounded action that follows those measurements. Choose EXACTLY TWO statements that together supply those two parts.

  1. Inspect UCS boot order, SAN or local disk identifiers, storage paths, driver support and recovery logs.
  2. Sample packet DSCP, priority map, switch policy counters, application flow identity and egress queue assignments.
  3. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.
  4. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs.
  5. Apply a version-compatible storage or boot policy and test both normal boot and controlled path loss.

Explanation

Correct Answer

C:

A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

D:

A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

Incorrect Answers

A:

Inspect UCS boot order, SAN or local disk identifiers, storage paths, driver support and recovery logs. It would not provide the evidence needed for the paired diagnosis and follow-up: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

B:

Sample packet DSCP, priority map, switch policy counters, application flow identity and egress queue assignments. It would not provide the evidence needed for the paired diagnosis and follow-up: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Verify onboarded site inventory, supported features, access roles, software versions and configuration diffs. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

E:

Apply a version-compatible storage or boot policy and test both normal boot and controlled path loss. It is not the scoped response supported by the accompanying evidence: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

Question 430

The acceptance board must decide whether an AI-infrastructure response to nexus dashboard operational rollout is fit for controlled operation. The fictional operating facts are: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Signoff cannot rely on a good-looking utilization graph, a change ticket alone or an unmeasured promise. The response must include an appropriate governing engineering principle, a scoped intervention and a separate measurable acceptance criterion. Choose EXACTLY THREE statements that meet those roles.

  1. An affected node boots correctly and maintains supported storage access during a planned single-path failure.
  2. RoCE deployments may need priority flow control on designated loss-sensitive classes, but PFC is not a blanket cure for congestion.
  3. Correct UCS LAN connectivity policies with staged host-by-host validation and independent uplink paths.
  4. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.
  5. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.
  6. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

Explanation

Correct Answer

D:

A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks.

E:

A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

F:

A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. The targeted fabric change is visible and verified while unrelated sites remain unaffected. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

Incorrect Answers

A:

An affected node boots correctly and maintains supported storage access during a planned single-path failure. It would not independently demonstrate that the control works: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. The targeted fabric change is visible and verified while unrelated sites remain unaffected. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

B:

RoCE deployments may need priority flow control on designated loss-sensitive classes, but PFC is not a blanket cure for congestion. It is not the rule that supports the proposed change and acceptance test: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Nexus Dashboard enables supported fabric visibility and management workflows but policy changes require version and scope checks. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback.

C:

Correct UCS LAN connectivity policies with staged host-by-host validation and independent uplink paths. It does not implement the governing rule for this approval: A managed switch estate adopts new Nexus Dashboard monitoring policies but administrators ignore role boundaries between tenants. Stage and audit the intended Nexus Dashboard workflow with least-privilege roles and controlled rollback. The targeted fabric change is visible and verified while unrelated sites remain unaffected.

Implementing Cisco Data Center AI Infrastructure (DCAI) (300-640) Practice Tests