DRAG DROP Drag and drop the code from the bottom onto the box where the code is missing the snippet to complete this Ansible Playbook. Not all options are used.
I remember seeing a similar Ansible playbook on some practice sets, and the pattern is usually variable assignment followed by list reference for looping. Pretty sure name-servers is just there to trip you up. If anyone solved it differently, let me know!
Not 100% convinced since if the variable was actually mistyped in the code (like dna_servers instead of dns_servers), it'd flip the mapping. But using Cisco/Ansible conventions, I'd map 208.67.222.222 to Target 1, dns_servers to Target 2. Anyone disagree?
Matches the usual Cisco Ansible patterns for sure: 208.67.222.222 goes in Target 1, and dns_servers fits Target 2 since that's the playbook's loop variable. The other choices are mostly distractors here in my opinion, unless I missed some detail.
I thought Target 1 would need dns_servers and Target 2 would get 208.67.222.222. I've seen similar variable ordering in some practice sets, and it looked logical to call out the variable before assigning an IP. I might be missing a trick with how the playbook loops reference vars though, so let me know if that's off.
