A fair DEVCOR 5.3.a practice item about Ansible network parameters should ask which kind of judgment?
Select an answer to reveal the explanation.
Short Explanation
Fair questions are “which piece fits?”—host, module, or var—not “recite a whole playbook from memory like a phone book.”
Full Explanation
A fair DEVCOR 5.3.a practice item about Ansible network parameters asks which host group, module, or variable placement solves the stated need—snippet-level judgment—not a full dumped playbook. That judgment matches how the objective is tested: candidates recognize where inventory targeting, cisco.ios-style modules, and vars belong for a municipal scenario, without memorizing multi-play production YAML. Good items reward architecture-of-the-workflow thinking over transcription.
Requiring a complete multi-play production YAML pasted from memory with every module argument filled fails fairness and pedagogy: it tests rote dump, not construction judgment. Memorizing the entire cisco.ios module index as a dump of every parameter name fails conceptually for the same reason—index memorization is not scenario-based selection. Rewriting the playbook in Puppet DSL because longer answers score higher fails because length and alternate CM languages are not scoring goals for an Ansible 5.3.a item.
Exam caveat: you still must know enough module purpose and inventory/vars structure to choose correctly; “snippet-level” is not “know nothing,” it is “don’t recite entire playbooks.” Operational check: when authoring civic practice questions or grading rubrics, accept answers that correctly pick group, module family, or vars placement for the stem, and reject grading schemes that require verbatim multi-file playbook dumps from memory.