Cisco 300-640 Practice Test 60
Question 590
The acceptance board must decide whether an AI-infrastructure response to thermal and power event correlation is fit for controlled operation. The fictional operating facts are: A model-serving farm slows after a new power cap is applied during rack consolidation but application metrics show no code change. 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.
- Sporadic AI slowdown can result from thermal throttling or electrical power caps rather than code regression.
- Sustained training no longer throttles and rack electrical limits remain satisfied.
- Restore validated cooling or power headroom after facility review and verify under sustained load.
- The repaired node rejoins service with normal health and controlled workload restoration.
- Correct the evidenced storage or pipeline bottleneck before increasing accelerator capacity.
- Congestion remediation must distinguish healthy ECN signaling from persistent oversubscription and unstable thresholds.
Explanation
Correct Answer
A:A model-serving farm slows after a new power cap is applied during rack consolidation but application metrics show no code change. Sporadic AI slowdown can result from thermal throttling or electrical power caps rather than code regression. Restore validated cooling or power headroom after facility review and verify under sustained load.
B:A model-serving farm slows after a new power cap is applied during rack consolidation but application metrics show no code change. Sustained training no longer throttles and rack electrical limits remain satisfied. Restore validated cooling or power headroom after facility review and verify under sustained load.
C:A model-serving farm slows after a new power cap is applied during rack consolidation but application metrics show no code change. Restore validated cooling or power headroom after facility review and verify under sustained load. Sporadic AI slowdown can result from thermal throttling or electrical power caps rather than code regression.
Incorrect Answers
D:The repaired node rejoins service with normal health and controlled workload restoration. It would not independently demonstrate that the control works: A model-serving farm slows after a new power cap is applied during rack consolidation but application metrics show no code change. Sustained training no longer throttles and rack electrical limits remain satisfied. Restore validated cooling or power headroom after facility review and verify under sustained load.
E:Correct the evidenced storage or pipeline bottleneck before increasing accelerator capacity. It does not implement the governing rule for this approval: A model-serving farm slows after a new power cap is applied during rack consolidation but application metrics show no code change. Restore validated cooling or power headroom after facility review and verify under sustained load. Sustained training no longer throttles and rack electrical limits remain satisfied.
F:Congestion remediation must distinguish healthy ECN signaling from persistent oversubscription and unstable thresholds. It is not the rule that supports the proposed change and acceptance test: A model-serving farm slows after a new power cap is applied during rack consolidation but application metrics show no code change. Sporadic AI slowdown can result from thermal throttling or electrical power caps rather than code regression. Restore validated cooling or power headroom after facility review and verify under sustained load.
Question 591
A data-center AI architecture committee considers canary rollback after infrastructure changes in its AI Infrastructure Operations and Troubleshooting review. At the affected site: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. 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.
- Operational telemetry and certificate validation depend on reliable time across fabric and compute components.
- Congestion remediation must distinguish healthy ECN signaling from persistent oversubscription and unstable thresholds.
- Reliable troubleshooting requires a synchronized incident timeline spanning application, GPU, network, compute and storage telemetry.
- Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
Explanation
Correct Answer
D:A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
Incorrect Answers
A:Operational telemetry and certificate validation depend on reliable time across fabric and compute components. It does not govern the condition described: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
B:Congestion remediation must distinguish healthy ECN signaling from persistent oversubscription and unstable thresholds. It does not govern the condition described: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
C:Reliable troubleshooting requires a synchronized incident timeline spanning application, GPU, network, compute and storage telemetry. It does not govern the condition described: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
Question 592
An infrastructure diagnostician is investigating canary rollback after infrastructure changes for the AI Infrastructure Operations and Troubleshooting team. The reported incident reads: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. 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.
- Check shared correlation IDs, NTP offsets, job start times, network event sequence and storage logs.
- Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
- Compare data-loader wait, storage read p99, metadata latency, network path and GPU kernel occupancy.
- Audit alert frequency, baselines, on-call response, suppression windows and missed failure examples.
Explanation
Correct Answer
B:A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
Incorrect Answers
A:Check shared correlation IDs, NTP offsets, job start times, network event sequence and storage logs. That check would not establish the decisive facts for this condition: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
C:Compare data-loader wait, storage read p99, metadata latency, network path and GPU kernel occupancy. That check would not establish the decisive facts for this condition: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
D:Audit alert frequency, baselines, on-call response, suppression windows and missed failure examples. That check would not establish the decisive facts for this condition: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
Question 593
During a bounded AI-platform change-control review concerning canary rollback after infrastructure changes, the site owner reports: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. 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.
- Tune symptom-based alerts and route to responsible teams with runbook-linked evidence.
- Restore validated cooling or power headroom after facility review and verify under sustained load.
- Restore supported redundant time synchronization and verify event ordering before further root-cause changes.
- Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
Explanation
Correct Answer
D:A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
Incorrect Answers
A:Tune symptom-based alerts and route to responsible teams with runbook-linked evidence. That change would leave the reported problem unresolved: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
B:Restore validated cooling or power headroom after facility review and verify under sustained load. That change would leave the reported problem unresolved: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
C:Restore supported redundant time synchronization and verify event ordering before further root-cause changes. That change would leave the reported problem unresolved: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
Question 594
Two independent technical reviewers examine a AI Infrastructure Operations and Troubleshooting problem involving canary rollback after infrastructure changes. Their shared incident log states: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. 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.
- Measure NTP reachability, UTC offset, source hierarchy, log timestamps and drift during node restarts.
- Trace per-priority pause duration, ingress queue depth, flow source and blocked unrelated classes across hops.
- Normalize clocks and correlate the first causal infrastructure event with impacted job transactions.
- Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
- Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
Explanation
Correct Answer
D:A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time. The canary returns to baseline and other clusters retain their validated configuration.
E:A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. The canary returns to baseline and other clusters retain their validated configuration.
Incorrect Answers
A:Measure NTP reachability, UTC offset, source hierarchy, log timestamps and drift during node restarts. It would not provide the evidence needed for the paired diagnosis and follow-up: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time. The canary returns to baseline and other clusters retain their validated configuration.
B:Trace per-priority pause duration, ingress queue depth, flow source and blocked unrelated classes across hops. It would not provide the evidence needed for the paired diagnosis and follow-up: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time. The canary returns to baseline and other clusters retain their validated configuration.
C:Normalize clocks and correlate the first causal infrastructure event with impacted job transactions. It is not the scoped response supported by the accompanying evidence: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. The canary returns to baseline and other clusters retain their validated configuration.
Question 595
The acceptance board must decide whether an AI-infrastructure response to canary rollback after infrastructure changes is fit for controlled operation. The fictional operating facts are: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. 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.
- Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
- Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
- Sporadic AI slowdown can result from thermal throttling or electrical power caps rather than code regression.
- Training throughput improves and measured input wait falls under representative concurrency.
- Isolate the affected host and apply the documented hardware maintenance procedure without mass model redeployment.
- The canary returns to baseline and other clusters retain their validated configuration.
Explanation
Correct Answer
A:A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
B:A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
F:A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. The canary returns to baseline and other clusters retain their validated configuration. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
Incorrect Answers
C:Sporadic AI slowdown can result from thermal throttling or electrical power caps rather than code regression. It is not the rule that supports the proposed change and acceptance test: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
D:Training throughput improves and measured input wait falls under representative concurrency. It would not independently demonstrate that the control works: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. The canary returns to baseline and other clusters retain their validated configuration. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
E:Isolate the affected host and apply the documented hardware maintenance procedure without mass model redeployment. It does not implement the governing rule for this approval: A new QoS rollout causes p99 inference latency to double in the pilot rack while the deployment tool reports success. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. The canary returns to baseline and other clusters retain their validated configuration.
Question 596
A data-center AI architecture committee considers canary rollback after infrastructure changes in its AI Infrastructure Operations and Troubleshooting review. At the affected site: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. 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.
- Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
- Infrastructure benchmarking must hold workload, dataset, software and concurrency consistent to isolate hardware changes.
- Server health incidents need correlated power, thermal, adapter and inventory evidence before blaming the AI model.
- Frequent priority pauses can indicate congestion spreading or head-of-line blocking rather than healthy lossless delivery.
Explanation
Correct Answer
A:A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
Incorrect Answers
B:Infrastructure benchmarking must hold workload, dataset, software and concurrency consistent to isolate hardware changes. It does not govern the condition described: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
C:Server health incidents need correlated power, thermal, adapter and inventory evidence before blaming the AI model. It does not govern the condition described: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
D:Frequent priority pauses can indicate congestion spreading or head-of-line blocking rather than healthy lossless delivery. It does not govern the condition described: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
Question 597
An infrastructure diagnostician is investigating canary rollback after infrastructure changes for the AI Infrastructure Operations and Troubleshooting team. The reported incident reads: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. 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.
- Audit alert frequency, baselines, on-call response, suppression windows and missed failure examples.
- Check shared correlation IDs, NTP offsets, job start times, network event sequence and storage logs.
- Compare Nexus Dashboard fabric health alerts, interface errors, queue telemetry, topology changes and affected job IDs.
- Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
Explanation
Correct Answer
D:A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
Incorrect Answers
A:Audit alert frequency, baselines, on-call response, suppression windows and missed failure examples. That check would not establish the decisive facts for this condition: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
B:Check shared correlation IDs, NTP offsets, job start times, network event sequence and storage logs. That check would not establish the decisive facts for this condition: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
C:Compare Nexus Dashboard fabric health alerts, interface errors, queue telemetry, topology changes and affected job IDs. That check would not establish the decisive facts for this condition: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
Question 598
During a bounded AI-platform change-control review concerning canary rollback after infrastructure changes, the site owner reports: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. 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.
- Repair the measured inconsistency on the affected path and retest with the same RDMA workload.
- Identify and relieve the root congestion source, then confine PFC and verify queue policy safely.
- Isolate the affected host and apply the documented hardware maintenance procedure without mass model redeployment.
- Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
Explanation
Correct Answer
D:A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
Incorrect Answers
A:Repair the measured inconsistency on the affected path and retest with the same RDMA workload. That change would leave the reported problem unresolved: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
B:Identify and relieve the root congestion source, then confine PFC and verify queue policy safely. That change would leave the reported problem unresolved: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
C:Isolate the affected host and apply the documented hardware maintenance procedure without mass model redeployment. That change would leave the reported problem unresolved: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
Question 599
Two independent technical reviewers examine a AI Infrastructure Operations and Troubleshooting problem involving canary rollback after infrastructure changes. Their shared incident log states: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. 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.
- Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
- Correlate GPU clock rate, power limit flags, inlet temperature, UCS faults and workload intensity.
- Restore supported redundant time synchronization and verify event ordering before further root-cause changes.
- Compare known-good and canary job metrics, error rates, fabric health and rollback completion time.
- Compare Nexus Dashboard fabric health alerts, interface errors, queue telemetry, topology changes and affected job IDs.
Explanation
Correct Answer
A:A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. The canary returns to baseline and other clusters retain their validated configuration.
D:A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time. The canary returns to baseline and other clusters retain their validated configuration.
Incorrect Answers
B:Correlate GPU clock rate, power limit flags, inlet temperature, UCS faults and workload intensity. It would not provide the evidence needed for the paired diagnosis and follow-up: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time. The canary returns to baseline and other clusters retain their validated configuration.
C:Restore supported redundant time synchronization and verify event ordering before further root-cause changes. It is not the scoped response supported by the accompanying evidence: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. The canary returns to baseline and other clusters retain their validated configuration.
E:Compare Nexus Dashboard fabric health alerts, interface errors, queue telemetry, topology changes and affected job IDs. It would not provide the evidence needed for the paired diagnosis and follow-up: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Compare known-good and canary job metrics, error rates, fabric health and rollback completion time. The canary returns to baseline and other clusters retain their validated configuration.
Question 600
The acceptance board must decide whether an AI-infrastructure response to canary rollback after infrastructure changes is fit for controlled operation. The fictional operating facts are: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. 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.
- Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
- Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
- Restore supported redundant time synchronization and verify event ordering before further root-cause changes.
- Training throughput improves and measured input wait falls under representative concurrency.
- Infrastructure benchmarking must hold workload, dataset, software and concurrency consistent to isolate hardware changes.
- The canary returns to baseline and other clusters retain their validated configuration.
Explanation
Correct Answer
A:A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response.
B:A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
F:A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. The canary returns to baseline and other clusters retain their validated configuration. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
Incorrect Answers
C:Restore supported redundant time synchronization and verify event ordering before further root-cause changes. It does not implement the governing rule for this approval: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework. The canary returns to baseline and other clusters retain their validated configuration.
D:Training throughput improves and measured input wait falls under representative concurrency. It would not independently demonstrate that the control works: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. The canary returns to baseline and other clusters retain their validated configuration. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.
E:Infrastructure benchmarking must hold workload, dataset, software and concurrency consistent to isolate hardware changes. It is not the rule that supports the proposed change and acceptance test: A compute profile update leaves several training nodes without storage access, but the automation system marks every API call successful. Operational changes should have independent service acceptance and a bounded rollback trigger rather than trust a successful automation response. Stop rollout on breached acceptance criteria and restore a tested configuration before root-cause rework.