Cisco 350-601 Practice Test 28
Question 270
A maintenance review discovers that a hardware-programmable logic update may interrupt forwarding despite a stable NX-OS release. The observed failure is: assuming EPLD updates are merely configuration changes can cause unplanned module or port interruption. Which recovery action addresses the underlying technical fault?
- The controlled remediation is to erase a switch checkpoint before evaluating the firmware procedure.
- The controlled remediation is to schedule supported EPLD procedure, protect redundant paths, and test impacted interfaces afterward.
- The controlled remediation is to install EPLD files as if they were ordinary text configuration templates.
- The controlled remediation is to ignore module redundancy because firmware updates cannot affect traffic.
Explanation
Correct Answer
B:Validate against platform EPLD package version, release notes, affected components, and redundancy and traffic impact checks. EPLD updates modify hardware logic components and may have disruption characteristics distinct from system software.
Incorrect Answers
A:Erase a switch checkpoint before evaluating the firmware procedure. This would not reliably restore service after the stated fault. Assuming EPLD updates are merely configuration changes can cause unplanned module or port interruption. The controlled recovery is to schedule supported EPLD procedure, protect redundant paths, and test impacted interfaces afterward.
C:Install EPLD files as if they were ordinary text configuration templates. This would not reliably restore service after the stated fault. Assuming EPLD updates are merely configuration changes can cause unplanned module or port interruption. The controlled recovery is to schedule supported EPLD procedure, protect redundant paths, and test impacted interfaces afterward.
D:Ignore module redundancy because firmware updates cannot affect traffic. This would not reliably restore service after the stated fault. Assuming EPLD updates are merely configuration changes can cause unplanned module or port interruption. The controlled recovery is to schedule supported EPLD procedure, protect redundant paths, and test impacted interfaces afterward.
Question 271
An operator accidentally changes a port-channel VLAN allow list and needs to restore the known-good configuration. Which next step should the data center engineer select?
- Delete all startup configurations instead of restoring a known checkpoint.
- Replace port-channel settings with a random new MTU.
- Use validated NX-OS checkpoint or configuration backup and rollback procedures for the supported change scope.
- Assume a checkpoint proves the restored network is healthy without validation.
Explanation
Correct Answer
C:This directly addresses NX-OS configuration checkpoints because configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. Confirm the change against checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
Incorrect Answers
A:Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. The relevant correction is to use validated NX-OS checkpoint or configuration backup and rollback procedures for the supported change scope.
B:Replace port-channel settings with a random new MTU. The proposed change targets the wrong mechanism or lacks essential validation. Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. Relevant evidence is checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
D:Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. The appropriate action remains to use validated NX-OS checkpoint or configuration backup and rollback procedures for the supported change scope.
Question 272
An operator accidentally changes a port-channel VLAN allow list and needs to restore the known-good configuration. Which diagnostic record would most strongly confirm the result?
- An up management interface without the relevant routing or forwarding table.
- A pre-change network diagram with no live control-plane state.
- An interface description without the effective peer or VXLAN policy.
- Checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
Explanation
Correct Answer
D:These observations test the actual NX-OS configuration checkpoints mechanism rather than a superficial management status. Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
Incorrect Answers
A:An up management interface without the relevant routing or forwarding table. This information cannot independently verify NX-OS configuration checkpoints. The decisive records instead include checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation. Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
B:A pre-change network diagram with no live control-plane state. This information cannot independently verify NX-OS configuration checkpoints. The decisive records instead include checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation. Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
C:An interface description without the effective peer or VXLAN policy. This information cannot independently verify NX-OS configuration checkpoints. The decisive records instead include checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation. Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
Question 273
An operator accidentally changes a port-channel VLAN allow list and needs to restore the known-good configuration. Which platform concept should guide the engineer’s assessment?
- Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
- A working management-plane ping proves every tenant and application path is healthy.
- A device description always determines actual forwarding policy regardless of running configuration.
- Physical link carrier guarantees all overlay and routing states are correct.
Explanation
Correct Answer
A:This explains why the most appropriate response is to use validated NX-OS checkpoint or configuration backup and rollback procedures for the supported change scope. Validation depends on checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
Incorrect Answers
B:A working management-plane ping proves every tenant and application path is healthy. This is an incorrect generalization for NX-OS configuration checkpoints. The applicable technical behavior is that configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. The operator should verify checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
C:A device description always determines actual forwarding policy regardless of running configuration. This is an incorrect generalization for NX-OS configuration checkpoints. The applicable technical behavior is that configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. The operator should verify checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
D:Physical link carrier guarantees all overlay and routing states are correct. This is an incorrect generalization for NX-OS configuration checkpoints. The applicable technical behavior is that configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. The operator should verify checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
Question 274
An operator accidentally changes a port-channel VLAN allow list and needs to restore the known-good configuration. Assume an engineer instead chooses to delete all startup configurations instead of restoring a known checkpoint. Which root-cause observation follows from that incorrect change?
- The defect exists solely because the engineer documented the change.
- Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric.
- Preserving neighbor-state evidence is itself the source of the observed outage.
- Investigating the forwarding table is the reason a broken route cannot converge.
Explanation
Correct Answer
B:Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
A:This does not explain the actual NX-OS configuration checkpoints defect after the shortcut. The meaningful failure is that manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric.
C:This does not explain the actual NX-OS configuration checkpoints defect after the shortcut. The relevant evidence is checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
D:This does not explain the actual NX-OS configuration checkpoints defect after the shortcut. Investigating the forwarding table is the reason a broken route cannot converge.
Question 275
An operator accidentally changes a port-channel VLAN allow list and needs to restore the known-good configuration. The observed failure is: manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. Which recovery action addresses the underlying technical fault?
- Replace port-channel settings with a random new MTU.
- Assume a checkpoint proves the restored network is healthy without validation.
- Restore the verified checkpoint scope and test reachability, interfaces and policy consistency.
- Delete all startup configurations instead of restoring a known checkpoint.
Explanation
Correct Answer
C:Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. This addresses the observable fault while preserving a check of the expected result.
Incorrect Answers
A:Replace port-channel settings with a random new MTU. This would not reliably restore service after the stated fault. Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. The controlled recovery is to restore the verified checkpoint scope and test reachability, interfaces and policy consistency.
B:Assume a checkpoint proves the restored network is healthy without validation. This would not reliably restore service after the stated fault. Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. The controlled recovery is to restore the verified checkpoint scope and test reachability, interfaces and policy consistency.
D:Delete all startup configurations instead of restoring a known checkpoint. This would not reliably restore service after the stated fault. Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. The controlled recovery is to restore the verified checkpoint scope and test reachability, interfaces and policy consistency.
Question 276
A Nexus maintenance script partially applies policy changes and engineers require a controlled rollback to the earlier state. What is the BEST supported implementation or corrective action?
- On this affected device, the engineer should replace port-channel settings with a random new MTU.
- On this affected device, the engineer should assume a checkpoint proves the restored network is healthy without validation.
- On this affected device, the engineer should delete all startup configurations instead of restoring a known checkpoint.
- On this affected device, the engineer should use validated NX-OS checkpoint or configuration backup and rollback procedures for the supported change scope.
Explanation
Correct Answer
D:This directly addresses NX-OS configuration checkpoints because configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
Incorrect Answers
A:Replace port-channel settings with a random new MTU. The proposed change targets the wrong mechanism or lacks essential validation. Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. Relevant evidence is checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
B:Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. Assume a checkpoint proves the restored network is healthy without validation.
C:Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. Delete all startup configurations instead of restoring a known checkpoint.
Question 277
A Nexus maintenance script partially applies policy changes and engineers require a controlled rollback to the earlier state. Which evidence BEST verifies the intended technical behavior?
- For this deployment, examine checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
- For this deployment, examine a healthy optical light without checking protocol neighbors or forwarding entries.
- For this deployment, examine an up management interface without the relevant routing or forwarding table.
- For this deployment, examine a pre-change network diagram with no live control-plane state.
Explanation
Correct Answer
A:These observations test the actual NX-OS configuration checkpoints mechanism rather than a superficial management status. They should be checked after use validated NX-OS checkpoint or configuration backup and rollback procedures for the supported change scope.
Incorrect Answers
B:A healthy optical light without checking protocol neighbors or forwarding entries. This information cannot independently verify NX-OS configuration checkpoints. The decisive records instead include checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation. Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
C:An up management interface without the relevant routing or forwarding table. This information cannot independently verify NX-OS configuration checkpoints. The decisive records instead include checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation. Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
D:A pre-change network diagram with no live control-plane state. This information cannot independently verify NX-OS configuration checkpoints. The decisive records instead include checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation. Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
Question 278
A Nexus maintenance script partially applies policy changes and engineers require a controlled rollback to the earlier state. Which principle BEST explains why the recommended solution is appropriate?
- For this condition, the applicable principle is that physical link carrier guarantees all overlay and routing states are correct.
- For this condition, the applicable principle is that configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback.
- For this condition, the applicable principle is that a working management-plane ping proves every tenant and application path is healthy.
- For this condition, the applicable principle is that all control-plane protocols exchange state automatically after a cable is inserted.
Explanation
Correct Answer
B:This explains why the most appropriate response is to use validated NX-OS checkpoint or configuration backup and rollback procedures for the supported change scope.
Incorrect Answers
A:Physical link carrier guarantees all overlay and routing states are correct. This is an incorrect generalization for NX-OS configuration checkpoints. The applicable technical behavior is that configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. The operator should verify checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
C:A working management-plane ping proves every tenant and application path is healthy. This is an incorrect generalization for NX-OS configuration checkpoints. The applicable technical behavior is that configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. The operator should verify checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
D:All control-plane protocols exchange state automatically after a cable is inserted. This is an incorrect generalization for NX-OS configuration checkpoints. The applicable technical behavior is that configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. The operator should verify checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
Question 279
A Nexus maintenance script partially applies policy changes and engineers require a controlled rollback to the earlier state. Assume an engineer instead chooses to delete all startup configurations instead of restoring a known checkpoint. What is the MOST significant failure introduced by that shortcut?
- The resulting defect is that investigating the forwarding table is the reason a broken route cannot converge.
- The resulting defect is that the only consequence of the wrong change is a different device description.
- The resulting defect is that manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric.
- The resulting defect is that preserving neighbor-state evidence is itself the source of the observed outage.
Explanation
Correct Answer
C:Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. The proper corrective action is to use validated NX-OS checkpoint or configuration backup and rollback procedures for the supported change scope.
Incorrect Answers
A:This does not explain the actual NX-OS configuration checkpoints defect after the shortcut. In the given case, a Nexus maintenance script partially applies policy changes and engineers require a controlled rollback to the earlier state.
B:This does not explain the actual NX-OS configuration checkpoints defect after the shortcut. The only consequence of the wrong change is a different device description.
D:This does not explain the actual NX-OS configuration checkpoints defect after the shortcut. Preserving neighbor-state evidence is itself the source of the observed outage.
Question 280
A Nexus maintenance script partially applies policy changes and engineers require a controlled rollback to the earlier state. The observed failure is: manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. What is the BEST controlled recovery once this failure is recognized?
- The controlled remediation is to assume a checkpoint proves the restored network is healthy without validation.
- The controlled remediation is to delete all startup configurations instead of restoring a known checkpoint.
- The controlled remediation is to replace port-channel settings with a random new MTU.
- The controlled remediation is to restore the verified checkpoint scope and test reachability, interfaces and policy consistency.
Explanation
Correct Answer
D:Configuration checkpoints allow controlled recovery from unwanted changes when the platform and features support the rollback. Validate against checkpoint listing, running-config diff, rollback result, vPC state, and traffic validation.
Incorrect Answers
A:Assume a checkpoint proves the restored network is healthy without validation. This would not reliably restore service after the stated fault. Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. The controlled recovery is to restore the verified checkpoint scope and test reachability, interfaces and policy consistency.
B:Delete all startup configurations instead of restoring a known checkpoint. This would not reliably restore service after the stated fault. Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. The controlled recovery is to restore the verified checkpoint scope and test reachability, interfaces and policy consistency.
C:Replace port-channel settings with a random new MTU. This would not reliably restore service after the stated fault. Manually guessing every prior command can leave hidden inconsistencies in an interconnected fabric. The controlled recovery is to restore the verified checkpoint scope and test reachability, interfaces and policy consistency.