Blueprint task 5.3.b asks the team to construct a workflow that configures network parameters with the official v1.1 tool. Which tool is correct?
Select an answer to reveal the explanation.
Short Explanation
Version 1.1 swapped the old Puppet lane for Terraform—you still configure network parameters, just with the new official tool. Chef alone and Cisco NSO aren’t the numbered DEVCOR 5.3.b answer.
Full Explanation
On DEVCOR v1.1, blueprint task 5.3.b asks candidates to construct a workflow that configures network parameters with Terraform. Terraform replaced Puppet for that numbered objective. When a municipal team still has older notes praising Puppet manifests for 5.3.b, those notes are outdated relative to the current blueprint—select the Terraform choice as the official tool for configuring network parameters in this construction item. The Puppet-manifest choice, which says v1.0 notes still assign 5.3.b network settings, fails the v1.1 update. The Chef-alone choice, which makes Chef the primary DEVCOR 5.3.b construction tool, misses the official replacement path entirely. The Cisco NSO choice, which calls NSO the only official 5.3.b replacement for Puppet, overscopes—NSO may appear in broader automation discussions but is not the v1.1 substitution named for this item. Exam caveat: Ansible remains the correct answer for 5.3.a agentless playbooks; do not answer Ansible when the stem explicitly targets 5.3.b Terraform workflows. Puppet distractors remain common on updated practice banks and live exams. Operational check: maintain study cards labeled “5.3.a Ansible / 5.3.b Terraform” and deliberately reject Puppet-based choices on v1.1-style practice items during weekly review.