Infrastructure and Automation →hardMultiple SelectObjective-mapped

200-901 Infrastructure and Automation Practice Question

Which THREE of the following are best practices for writing Ansible playbooks for network automation? (Select exactly 3.)

⚠ Common exam trap

Cisco often tests the misconception that ignoring errors (Option A) speeds up automation, but the trap is that network devices require strict error handling to avoid partial configs or unreachable states, making error-checking a mandatory best practice.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Include a validation task after configuration changes

After applying configuration changes via modules like `ios_config` or `junos_config`, a validation task (e.g., using `wait_for` or `assert` to verify operational state) ensures the device is reachable and the changes took effect before proceeding. This prevents cascading failures in multi-device playbooks and aligns with network automation best practices for reliability.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Run all tasks without checking for errors
Why it's wrong here
Error handling is important.
✓
Include a validation task after configuration changes
Why this is correct
Ensures the change took effect.
✓
Use variables for device-specific parameters
Why this is correct
Increases reusability.
✗
Hardcode device IPs in the playbook
Why it's wrong here
IPs should be in inventory.
✓
Use the 'changed_when' condition to ensure idempotency
Why this is correct
Helps report accurate change status.

Go deeper

200-901 Infrastructure and Automation Practice Question

Why each option matters

Option-by-option breakdown

Related to this question