A fair DEVCOR item asks which Terraform piece solves a stated need for an IOS XE static route. What kind of answer should candidates expect?
Select an answer to reveal the explanation.
Short Explanation
The exam wants the right Lego brick for the job—not an entire Lego city built from scratch. Snippet-level judgment beats pasting a full root module.
Full Explanation
Fair DEVCOR items about Terraform for an IOS XE static route ask you to identify the correct resource, argument, or workflow command for the stated need—not to paste an entire multi-file root module from memory. Municipal candidates should recognize which resource type or plan/apply step solves the requirement in the stem, matching how the exam scores construction knowledge under 5.3.b.
Pastting a complete multi-file .tf root with every variable from memory overscopes what multiple-choice (and typical short construction) items require. Reciting Puppet class syntax because HCL snippets are “out of scope” fails—the tool under test is Terraform, and Puppet is a discarded distractor. Submitting a full AWS VPC module unrelated to the IOS XE route answers a different domain problem and ignores the campus device requirement.
Exam caveat: know core workflow verbs (init/plan/apply/destroy/state) and that resources represent network parameters; you need not memorize every provider schema field. Distractors often lure you toward Puppet or cloud modules when the stem is IOS XE.
Operational check: for each practice stem, underline the need (route, VLAN, plan preview, destroy), then pick the single resource or command that satisfies it, rejecting encyclopedic dumps.