When identifying a configuration-management solution on this DEVCOR v1.1 bank, how should Puppet be treated relative to Ansible and Terraform?
Select an answer to reveal the explanation.
Short Explanation
Puppet is the museum piece on the distractor shelf—useful only to catch outdated study guides. Score Ansible versus Terraform against the stated requirements.
Full Explanation
On this DEVCOR v1.1 practice bank, Puppet should be treated as a discarded v1.0 leftover distractor—not the official correct answer for 5.3.b and not the primary answer for 5.4 tool identification when Ansible or Terraform fit the requirements. Updated blueprints moved network-parameter construction to Terraform and kept Ansible for playbooks; Puppet options remain mainly to catch outdated study habits in municipal training programs that never refreshed after the blueprint change.
Treating Puppet as required whenever network parameters are mentioned fails current v1.1 guidance. Treating Puppet as a third official primary alongside Ansible and Terraform for every 5.3 item overstates its role on the current exam. Treating Puppet as a synonym for NSO that always beats Terraform is incorrect on both product identity and blueprint priority.
Exam caveat: knowing what Puppet is historically can help you eliminate it quickly; do not spend scarce study time building Puppet catalogs for this bank. Focus practice on Ansible plays and Terraform plan, apply, and state instead.
Operational check: in practice sets, mark every Puppet option as a distractor unless a stem explicitly asks a historical comparison, and verify your correct picks are Ansible or Terraform per section numbering.