Cisco 350-601 Practice Test 92
Question 910
An on-box Python health-check tool fails when it parses a CLI table with unstable column spacing. The observed failure is: brittle string slicing can misinterpret operational output and make incorrect configuration decisions. Which recovery action addresses the underlying technical fault?
- The controlled remediation is to replace operational telemetry with random hard-coded status strings.
- The controlled remediation is to correct the command invocation and parser and retest against representative device outputs.
- The controlled remediation is to treat the command output as always identical after every software release.
- The controlled remediation is to run the Python exception handler with no logging and silently ignore failures.
Explanation
Correct Answer
B:On-box Python can automate NX-OS operations but must use supported methods and reliable result formats. Validate against Python exception trace, command API return, stable fields and comparison with device operational state.
Incorrect Answers
A:Replace operational telemetry with random hard-coded status strings. This would not reliably restore service after the stated fault. Brittle string slicing can misinterpret operational output and make incorrect configuration decisions. The controlled recovery is to correct the command invocation and parser and retest against representative device outputs.
C:Treat the command output as always identical after every software release. This would not reliably restore service after the stated fault. Brittle string slicing can misinterpret operational output and make incorrect configuration decisions. The controlled recovery is to correct the command invocation and parser and retest against representative device outputs.
D:Run the Python exception handler with no logging and silently ignore failures. This would not reliably restore service after the stated fault. Brittle string slicing can misinterpret operational output and make incorrect configuration decisions. The controlled recovery is to correct the command invocation and parser and retest against representative device outputs.
Question 911
An Ansible playbook reports changes to NX-OS on every run even when intended interface configuration already exists. Which next step should the data center engineer select?
- Always erase the switch running configuration before each playbook.
- Use ad hoc terminal keystrokes with no state comparison as desired-state automation.
- Use state-aware Ansible modules and explicit desired-state assertions rather than repeated blind commands.
- Disable configuration backups to avoid tracking repeat changes.
Explanation
Correct Answer
C:This directly addresses ansible idempotent configuration because idempotent automation converges toward a defined state without making unnecessary repeated changes. Confirm the change against first and second playbook run changes, device configuration diff and idempotence test results.
Incorrect Answers
A:A non-idempotent script can generate repeated disruption and configuration drift. The relevant correction is to use state-aware Ansible modules and explicit desired-state assertions rather than repeated blind commands.
B:Use ad hoc terminal keystrokes with no state comparison as desired-state automation. The proposed change targets the wrong mechanism or lacks essential validation. Idempotent automation converges toward a defined state without making unnecessary repeated changes. Relevant evidence is first and second playbook run changes, device configuration diff and idempotence test results.
D:A non-idempotent script can generate repeated disruption and configuration drift. The appropriate action remains to use state-aware Ansible modules and explicit desired-state assertions rather than repeated blind commands.
Question 912
An Ansible playbook reports changes to NX-OS on every run even when intended interface configuration already exists. Which diagnostic record would most strongly confirm the result?
- An old CI job name without run records or configuration diffs.
- An API endpoint returning HTML instead of validated inventory or outcome.
- A dashboard snapshot detached from actual target configuration and logs.
- First and second playbook run changes, device configuration diff and idempotence test results.
Explanation
Correct Answer
D:These observations test the actual ansible idempotent configuration mechanism rather than a superficial management status. Idempotent automation converges toward a defined state without making unnecessary repeated changes.
Incorrect Answers
A:An old CI job name without run records or configuration diffs. This information cannot independently verify ansible idempotent configuration. The decisive records instead include first and second playbook run changes, device configuration diff and idempotence test results. Idempotent automation converges toward a defined state without making unnecessary repeated changes.
B:An API endpoint returning HTML instead of validated inventory or outcome. This information cannot independently verify ansible idempotent configuration. The decisive records instead include first and second playbook run changes, device configuration diff and idempotence test results. Idempotent automation converges toward a defined state without making unnecessary repeated changes.
C:A dashboard snapshot detached from actual target configuration and logs. This information cannot independently verify ansible idempotent configuration. The decisive records instead include first and second playbook run changes, device configuration diff and idempotence test results. Idempotent automation converges toward a defined state without making unnecessary repeated changes.
Question 913
An Ansible playbook reports changes to NX-OS on every run even when intended interface configuration already exists. Which platform concept should guide the engineer’s assessment?
- Idempotent automation converges toward a defined state without making unnecessary repeated changes.
- One initial successful run guarantees all later automation remains correct.
- Cloud or on-box automation removes the need to validate inputs and outcomes.
- The existence of a state file proves all remote resources match desired state.
Explanation
Correct Answer
A:This explains why the most appropriate response is to use state-aware Ansible modules and explicit desired-state assertions rather than repeated blind commands. Validation depends on first and second playbook run changes, device configuration diff and idempotence test results.
Incorrect Answers
B:One initial successful run guarantees all later automation remains correct. This is an incorrect generalization for ansible idempotent configuration. The applicable technical behavior is that idempotent automation converges toward a defined state without making unnecessary repeated changes. The operator should verify first and second playbook run changes, device configuration diff and idempotence test results.
C:Cloud or on-box automation removes the need to validate inputs and outcomes. This is an incorrect generalization for ansible idempotent configuration. The applicable technical behavior is that idempotent automation converges toward a defined state without making unnecessary repeated changes. The operator should verify first and second playbook run changes, device configuration diff and idempotence test results.
D:The existence of a state file proves all remote resources match desired state. This is an incorrect generalization for ansible idempotent configuration. The applicable technical behavior is that idempotent automation converges toward a defined state without making unnecessary repeated changes. The operator should verify first and second playbook run changes, device configuration diff and idempotence test results.
Question 914
An Ansible playbook reports changes to NX-OS on every run even when intended interface configuration already exists. Assume an engineer instead chooses to always erase the switch running configuration before each playbook. Which root-cause observation follows from that incorrect change?
- Using a dry-run test inherently disables every network management API.
- A non-idempotent script can generate repeated disruption and configuration drift.
- Storing execution logs causes the original script to use invalid parameters.
- Verifying server policy references is the reason the missing references occurred.
Explanation
Correct Answer
B:The proper corrective action is to use state-aware Ansible modules and explicit desired-state assertions rather than repeated blind commands. Idempotent automation converges toward a defined state without making unnecessary repeated changes.
Incorrect Answers
A:This does not explain the actual ansible idempotent configuration defect after the shortcut. The meaningful failure is that a non-idempotent script can generate repeated disruption and configuration drift.
C:This does not explain the actual ansible idempotent configuration defect after the shortcut. The relevant evidence is first and second playbook run changes, device configuration diff and idempotence test results.
D:This does not explain the actual ansible idempotent configuration defect after the shortcut. In the given case, an Ansible playbook reports changes to NX-OS on every run even when intended interface configuration already exists.
Question 915
An Ansible playbook reports changes to NX-OS on every run even when intended interface configuration already exists. The observed failure is: a non-idempotent script can generate repeated disruption and configuration drift. Which recovery action addresses the underlying technical fault?
- Use ad hoc terminal keystrokes with no state comparison as desired-state automation.
- Disable configuration backups to avoid tracking repeat changes.
- Replace unsafe tasks with idempotent modules, run check or diff tests, and confirm stable subsequent runs.
- Always erase the switch running configuration before each playbook.
Explanation
Correct Answer
C:Validate against first and second playbook run changes, device configuration diff and idempotence test results. This addresses the observable fault while preserving a check of the expected result.
Incorrect Answers
A:Use ad hoc terminal keystrokes with no state comparison as desired-state automation. This would not reliably restore service after the stated fault. A non-idempotent script can generate repeated disruption and configuration drift. The controlled recovery is to replace unsafe tasks with idempotent modules, run check or diff tests, and confirm stable subsequent runs.
B:Disable configuration backups to avoid tracking repeat changes. This would not reliably restore service after the stated fault. A non-idempotent script can generate repeated disruption and configuration drift. The controlled recovery is to replace unsafe tasks with idempotent modules, run check or diff tests, and confirm stable subsequent runs.
D:Always erase the switch running configuration before each playbook. This would not reliably restore service after the stated fault. A non-idempotent script can generate repeated disruption and configuration drift. The controlled recovery is to replace unsafe tasks with idempotent modules, run check or diff tests, and confirm stable subsequent runs.
Question 916
A nightly network automation job recreates the same VLANs and disrupts services because its tasks are imperative and non-idempotent. What is the BEST supported implementation or corrective action?
- On this affected device, the engineer should use ad hoc terminal keystrokes with no state comparison as desired-state automation.
- On this affected device, the engineer should disable configuration backups to avoid tracking repeat changes.
- On this affected device, the engineer should always erase the switch running configuration before each playbook.
- On this affected device, the engineer should use state-aware Ansible modules and explicit desired-state assertions rather than repeated blind commands.
Explanation
Correct Answer
D:This directly addresses ansible idempotent configuration because idempotent automation converges toward a defined state without making unnecessary repeated changes.
Incorrect Answers
A:Use ad hoc terminal keystrokes with no state comparison as desired-state automation. The proposed change targets the wrong mechanism or lacks essential validation. Idempotent automation converges toward a defined state without making unnecessary repeated changes. Relevant evidence is first and second playbook run changes, device configuration diff and idempotence test results.
B:A non-idempotent script can generate repeated disruption and configuration drift. In the given case, a nightly network automation job recreates the same VLANs and disrupts services because its tasks are imperative and non-idempotent.
C:A non-idempotent script can generate repeated disruption and configuration drift. Always erase the switch running configuration before each playbook.
Question 917
A nightly network automation job recreates the same VLANs and disrupts services because its tasks are imperative and non-idempotent. Which evidence BEST verifies the intended technical behavior?
- For this deployment, examine first and second playbook run changes, device configuration diff and idempotence test results.
- For this deployment, examine a successful SSH session without script output, API responses or resulting state.
- For this deployment, examine an old CI job name without run records or configuration diffs.
- For this deployment, examine an API endpoint returning HTML instead of validated inventory or outcome.
Explanation
Correct Answer
A:These observations test the actual ansible idempotent configuration mechanism rather than a superficial management status. They should be checked after use state-aware Ansible modules and explicit desired-state assertions rather than repeated blind commands.
Incorrect Answers
B:A successful SSH session without script output, API responses or resulting state. This information cannot independently verify ansible idempotent configuration. The decisive records instead include first and second playbook run changes, device configuration diff and idempotence test results. Idempotent automation converges toward a defined state without making unnecessary repeated changes.
C:An old CI job name without run records or configuration diffs. This information cannot independently verify ansible idempotent configuration. The decisive records instead include first and second playbook run changes, device configuration diff and idempotence test results. Idempotent automation converges toward a defined state without making unnecessary repeated changes.
D:An API endpoint returning HTML instead of validated inventory or outcome. This information cannot independently verify ansible idempotent configuration. The decisive records instead include first and second playbook run changes, device configuration diff and idempotence test results. Idempotent automation converges toward a defined state without making unnecessary repeated changes.
Question 918
A nightly network automation job recreates the same VLANs and disrupts services because its tasks are imperative and non-idempotent. Which principle BEST explains why the recommended solution is appropriate?
- For this condition, the applicable principle is that the existence of a state file proves all remote resources match desired state.
- For this condition, the applicable principle is that idempotent automation converges toward a defined state without making unnecessary repeated changes.
- For this condition, the applicable principle is that one initial successful run guarantees all later automation remains correct.
- For this condition, the applicable principle is that a script saved on a controller always runs successfully on every target.
Explanation
Correct Answer
B:This explains why the most appropriate response is to use state-aware Ansible modules and explicit desired-state assertions rather than repeated blind commands. In the given case, a nightly network automation job recreates the same VLANs and disrupts services because its tasks are imperative and non-idempotent.
Incorrect Answers
A:The existence of a state file proves all remote resources match desired state. This is an incorrect generalization for ansible idempotent configuration. The applicable technical behavior is that idempotent automation converges toward a defined state without making unnecessary repeated changes. The operator should verify first and second playbook run changes, device configuration diff and idempotence test results.
C:One initial successful run guarantees all later automation remains correct. This is an incorrect generalization for ansible idempotent configuration. The applicable technical behavior is that idempotent automation converges toward a defined state without making unnecessary repeated changes. The operator should verify first and second playbook run changes, device configuration diff and idempotence test results.
D:A script saved on a controller always runs successfully on every target. This is an incorrect generalization for ansible idempotent configuration. The applicable technical behavior is that idempotent automation converges toward a defined state without making unnecessary repeated changes. The operator should verify first and second playbook run changes, device configuration diff and idempotence test results.
Question 919
A nightly network automation job recreates the same VLANs and disrupts services because its tasks are imperative and non-idempotent. Assume an engineer instead chooses to always erase the switch running configuration before each playbook. What is the MOST significant failure introduced by that shortcut?
- The resulting defect is that verifying server policy references is the reason the missing references occurred.
- The resulting defect is that keeping API error responses is the underlying cause of failed automation.
- The resulting defect is that a non-idempotent script can generate repeated disruption and configuration drift.
- The resulting defect is that storing execution logs causes the original script to use invalid parameters.
Explanation
Correct Answer
C:The proper corrective action is to use state-aware Ansible modules and explicit desired-state assertions rather than repeated blind commands. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
A:This does not explain the actual ansible idempotent configuration defect after the shortcut. In the given case, a nightly network automation job recreates the same VLANs and disrupts services because its tasks are imperative and non-idempotent.
B:This does not explain the actual ansible idempotent configuration defect after the shortcut. Keeping API error responses is the underlying cause of failed automation.
D:This does not explain the actual ansible idempotent configuration defect after the shortcut. Storing execution logs causes the original script to use invalid parameters.
Question 920
A nightly network automation job recreates the same VLANs and disrupts services because its tasks are imperative and non-idempotent. The observed failure is: a non-idempotent script can generate repeated disruption and configuration drift. What is the BEST controlled recovery once this failure is recognized?
- The controlled remediation is to disable configuration backups to avoid tracking repeat changes.
- The controlled remediation is to always erase the switch running configuration before each playbook.
- The controlled remediation is to use ad hoc terminal keystrokes with no state comparison as desired-state automation.
- The controlled remediation is to replace unsafe tasks with idempotent modules, run check or diff tests, and confirm stable subsequent runs.
Explanation
Correct Answer
D:Validate against first and second playbook run changes, device configuration diff and idempotence test results. Idempotent automation converges toward a defined state without making unnecessary repeated changes.
Incorrect Answers
A:Disable configuration backups to avoid tracking repeat changes. This would not reliably restore service after the stated fault. A non-idempotent script can generate repeated disruption and configuration drift. The controlled recovery is to replace unsafe tasks with idempotent modules, run check or diff tests, and confirm stable subsequent runs.
B:Always erase the switch running configuration before each playbook. This would not reliably restore service after the stated fault. A non-idempotent script can generate repeated disruption and configuration drift. The controlled recovery is to replace unsafe tasks with idempotent modules, run check or diff tests, and confirm stable subsequent runs.
C:Use ad hoc terminal keystrokes with no state comparison as desired-state automation. This would not reliably restore service after the stated fault. A non-idempotent script can generate repeated disruption and configuration drift. The controlled recovery is to replace unsafe tasks with idempotent modules, run check or diff tests, and confirm stable subsequent runs.