The official DEVCOR lab runs Terraform from GitLab CI/CD against IOS XE. A question asks what the 5.3.b construction actually is. What is the right focus?
Select an answer to reveal the explanation.
Short Explanation
GitLab is the conveyor belt; Terraform is still the product being shipped. Scoring YAML stages or AUTOCOR pipeline lore misses the 5.3.b construction.
Full Explanation
Official labs may drive Terraform from GitLab CI/CD against IOS XE, but the scored 5.3.b construction is still the Terraform workflow itself: provider configuration plus plan and apply, with state tracking ownership. CI is only the runner that executes those steps for the civic pipeline. Candidates who memorize stage names in .gitlab-ci.yml without understanding provider, plan, apply, and state miss what the blueprint actually numbers.
Treating authorship of GitLab stage names as the scored 5.3.b skill fails the Terraform focus. Diagnosing unrelated pipeline failure codes under Domain 4 as the 5.3.b answer confuses domains and skills on the exam. Replacing Terraform with a Puppet agent install inside the CI job reintroduces the discarded tool the v1.1 update removed from this blueprint slot.
Exam caveat: knowing how pipelines invoke terraform plan and apply is operationally useful for city DevOps teams, yet multiple-choice items still hinge on Terraform concepts. An Ansible-only CI job does not satisfy a Terraform-construction question.
Operational check: in a GitLab job log, identify the terraform plan and apply invocations and how provider credentials are supplied to the job—not merely the YAML stage labels.