Practice English vocabulary for collaborating on infrastructure code: PR reviews, plan output as PR comments, production approvals, and team IaC module ownership.
0 / 15 completed
1 / 15
What does 'the PR reviews the infrastructure change' mean?
Treating IaC like application code means infrastructure changes are proposed as pull requests, reviewed by peers, and only merged after approval. This catches mistakes, shares knowledge, and creates an audit trail of every infrastructure change.
2 / 15
What does 'the terraform plan output is posted as a PR comment' mean?
Tools like Atlantis, Terraform Cloud, or GitHub Actions workflows automatically run 'terraform plan' and post the diff as a PR comment. Reviewers see the exact additions, changes, and deletions before approving, making reviews meaningful rather than just code inspection.
3 / 15
What does 'the change requires a second approver for production' mean?
Four-eyes principles (two-person approval) for production IaC changes reduce the risk of mistakes. Tools like Atlantis enforce approval policies: for example, prod workspace changes require two approvals while dev workspace changes may only need one.
4 / 15
What does 'the infrastructure code review vocabulary' include?
Reviewing IaC requires specific vocabulary to discuss plans and changes: reviewers comment on plan output interpretation, resource lifecycle changes (create/update/replace/destroy), module versions, variable validation, and compliance with organizational standards.
5 / 15
What does 'the team owns the IaC modules' mean?
In large organizations, platform or infrastructure teams own shared IaC modules (e.g., a VPC module, an RDS module). They act as the maintainers, versioning releases, handling breaking changes, and providing support to consumer teams.
6 / 15
Alex from the Infrastructure team sent this Slack message: 'Just merged the new Kubernetes deployment. The Terraform plan output is attached as a PR comment – @Ben, please review it before we update the staging environment.' What does @Ben's response need to focus on?
Ben's primary responsibility here is to validate that the changes reflected in the PR comment align with the Terraform plan. This ensures consistency between the infrastructure definition and its implementation. The other options are less directly relevant – cost analysis and policy adherence should be handled by separate teams or processes.
7 / 15
Sarah is writing a PR description for a Terraform module update. She includes the following: 'This change introduces support for Azure Virtual Network integration. It requires a second approver for production deployments to mitigate potential network configuration issues.' What's the *most* important implication of this statement?
Sarah's statement highlights a critical control – requiring a second approver. This indicates that changes to this specific module (particularly those affecting network configurations) have significant impact on production and necessitate careful validation before deployment. The other options present incorrect assumptions about the module's behavior or user responsibilities.
8 / 15
David is giving a standup update: 'We've finalized the IaC modules for our new database service. The team owns the modules and we're actively maintaining them – applying security patches and documenting updates.' What does David *primarily* want the team to understand?
David emphasizes ownership – the team's responsibility for maintaining and evolving the IaC modules. This is fundamental to collaborative Infrastructure-as-Code practices, ensuring long-term stability, security, and adaptability. Ownership implies accountability for updates, documentation, and resolving issues.
9 / 15
Maria received this API response from the IaC automation tool: `{"status": "error", "message": "Invalid Terraform configuration – missing required attributes for resource 'aws_instance'."}`. What is Maria's immediate next step?
Maria's first action must be to investigate the API response. The 'error' status indicates a configuration problem within the Terraform code itself. Contacting the automation team is the appropriate step to seek assistance in debugging and resolving the issue before deploying any changes.
10 / 15
Tom says: 'We're using IaC to manage our infrastructure, so we need a shared vocabulary for describing changes – things like 'drift detection,' 'immutable deployments,' and 'version control.''. Why is this important?
Establishing a shared vocabulary is crucial for effective collaboration in IaC. Terms like 'drift detection,' 'immutable deployments,' and 'version control' represent core concepts within the practice. Without a common understanding, communication becomes ambiguous and errors are more likely to occur during development and deployment.
11 / 15
Alex from the Infrastructure team sent this Slack message: 'Just merged the new Kubernetes deployment. The Terraform plan output is attached as a PR comment – @Ben, please review it before we update the staging environment.' What does @Ben's response need to focus on?
Ben's primary responsibility here is to validate that the changes reflected in the PR comment align with the Terraform plan. This ensures consistency between the infrastructure definition and its implementation. The other options are less directly relevant – cost analysis and policy adherence should be handled by separate teams or processes.
12 / 15
Sarah is writing a PR description for a Terraform module update. She includes the following: 'This change introduces support for Azure Virtual Network integration. It requires a second approver for production deployments to mitigate potential network configuration issues.' What's the *most* important implication of this statement?
Sarah's statement highlights a critical control – requiring a second approver. This indicates that changes to this specific module (particularly those affecting network configurations) have significant impact on production and necessitate careful validation before deployment. The other options present incorrect assumptions about the module's behavior or user responsibilities.
13 / 15
David is giving a standup update: 'We've finalized the IaC modules for our new database service. The team owns the modules and we're actively maintaining them – applying security patches and documenting updates.' What does David *primarily* want the team to understand?
David emphasizes ownership – the team's responsibility for maintaining and evolving the IaC modules. This is fundamental to collaborative Infrastructure-as-Code practices, ensuring long-term stability, security, and adaptability. Ownership implies accountability for updates, documentation, and resolving issues.
14 / 15
Maria received this API response from the IaC automation tool: `{"status": "error", "message": "Invalid Terraform configuration – missing required attributes for resource 'aws_instance'."}`. What is Maria's immediate next step?
Maria's first action must be to investigate the API response. The 'error' status indicates a configuration problem within the Terraform code itself. Contacting the automation team is the appropriate step to seek assistance in debugging and resolving the issue before deploying any changes.
15 / 15
Tom says: 'We're using IaC to manage our infrastructure, so we need a shared vocabulary for describing changes – things like 'drift detection,' 'immutable deployments,' and 'version control.''. Why is this important?
Establishing a shared vocabulary is crucial for effective collaboration in IaC. Terms like 'drift detection,' 'immutable deployments,' and 'version control' represent core concepts within the practice. Without a common understanding, communication becomes ambiguous and errors are more likely to occur during development and deployment.
What will I practise in "IaC Collaboration Vocabulary"?
Practice English vocabulary for collaborating on infrastructure code: PR reviews, plan output as PR comments, production approvals, and team IaC module ownership.
How many exercises are in this module?
This module has 15 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Infrastructure as Code (IaC) exercises?
Browse the full Infrastructure as Code (IaC) hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.