GitHub Copilot for DevOps & Infrastructure assessment

GitHub Copilot for DevOps & Infrastructure — assessment

Ten questions on infrastructure work. The recurring risk here is different from application code: a wrong suggestion may be applied to something running, and the feedback loop is production.

10 questions · 80% to pass · unlimited retries · nothing is recorded outside this browser

— best score %.

Copilot writes a Terraform change and you are about to apply it. What is the non-negotiable step?
- Check the configuration is formatted with `terraform fmt`.
- Read `terraform plan` in full, checking specifically for resources marked for replacement or destruction.
- Run `terraform apply` and watch for errors.
- Confirm it validates with `terraform validate`.
Which of these are sound ways to reduce the risk of Copilot-generated infrastructure changes? Select all that apply.
Select all that apply.
- Keep state and credentials out of the working directory the agent can read.
- Apply to production first so problems surface quickly.
- Require a reviewed plan output on the pull request before any apply.
- Give the agent broad permissions so it can fix its own mistakes.
Copilot suggests a Dockerfile that installs build tooling and leaves it in the final image. What is the substantive objection?
- Docker forbids compilers in images.
- It will not build.
- It enlarges the image and increases the attack surface shipped to production; a multi-stage build keeps the toolchain out of the final layer.
- Nothing — image size is cosmetic.
A generated Kubernetes manifest has no resource requests or limits. What happens?
- The pod is given unlimited resources safely.
- The scheduler cannot reason about the pod's needs, so it may be placed poorly and may consume enough to disturb neighbours on the node.
- The manifest is rejected by the API server.
- Kubernetes infers sensible values from image metadata.
Why does the Academy treat OpenTofu and Terraform as separate lessons rather than one?
- OpenTofu uses a different language entirely.
- OpenTofu is unrelated to Terraform.
- Copilot supports only one of them.
- They have diverged, so provider, syntax and tooling assumptions that hold for one may not hold for the other.
You ask Copilot for a GitHub Actions workflow and it references a third-party action by a floating tag such as `@v3`. What is the security consideration?
- There is none; GitHub reviews all published actions.
- `@v3` is invalid syntax.
- A tag can be moved to different code, so pinning to a commit SHA is what makes the dependency reproducible and tamper-evident.
- Third-party actions cannot be used in private repositories.
Copilot proposes an Ansible playbook using a shell command where a module exists. Why prefer the module?
- Shell commands cannot be used with `become`.
- Shell commands are not permitted in Ansible.
- Modules run faster.
- Modules are idempotent and report changed state accurately, whereas a raw shell command runs every time and reports change it may not have made.
What is the strongest argument for keeping Copilot out of the apply step of a CI/CD pipeline, even when it writes the configuration?
- It would be too slow.
- Generation and authorisation should stay separate, so a human decision stands between a proposed change and a change to running infrastructure.
- Copilot cannot authenticate to cloud providers.
- Pipelines cannot run AI tools.
A suggested Linux administration command includes `chmod 777`. What is the correct reaction?
- Accept it temporarily and tighten later.
- Accept it; 777 is the standard permission for web directories.
- Reject it and set the narrowest permissions that make the task work — it is a symptom of guessing at a permissions problem rather than diagnosing it.
- Accept it only on the local machine.
Which single practice most reduces the chance that a generated infrastructure change causes an outage?
- Running the change out of hours.
- Using the largest available model.
- Writing longer prompts.
- Reviewing the diff of what will actually change before authorising it.

of 10 answered

Unanswered questions are marked incorrect.

Your score

Academy milestone recorded in this browser. This is not a certification, and no organisation is told about it.

Every question

Answers are scored and stored in this browser only. Nothing is sent anywhere, no account is required, and this is not a certification —the Academy explains how progress works.

GitHub Copilot for DevOps & Infrastructure — assessment

GitHub Copilot for DevOps & Infrastructure — assessment

Solid

Worth rereading

Every question