5 exercises — the same phrasal verb can mean completely different things depending on the situation. Master check out, spin up, roll back, pull in, and set up across Git, DevOps, and workplace contexts.
Why disambiguation matters
Many IT phrasal verbs have both a technical and a general English meaning
"Check out the branch" (Git) vs. "everything checks out" (is valid) vs. "check out this article" (look at)
Context clues: who is speaking, what system they're talking about, what surrounds the phrase
Getting the wrong meaning can lead to miscommunication in code reviews, incidents, and team discussions
0 / 30 completed
1 / 30
The phrasal verb "check out" appears in three different IT contexts below. Match the correct meaning to the third example:
① "Check out the new Redis caching PR I submitted." — look at / review ② "Check out the feature/auth branch before you start." — switch to (Git) ③ "Tested the payment flow — everything checks out."
What does "checks out" mean in context ③?
"Checks out" in context ③ means validates / is correct / looks good — the payment flow has been inspected and no problems were found. It's the everyday-English meaning of "check out": to verify something is in order.
Three meanings of "check out" in IT:
① Review / look at — "check out my PR" = look at it and consider it. Very common in Slack and PR comment culture.
② Switch to a branch (Git) — git checkout feature/auth — switch your working directory to that branch.
③ Validates / is fine — "the logic checks out" = the reasoning or code is correct when inspected.
Why this matters: Non-native speakers often default to only the Git meaning. In a sprint review, when the PM says "the acceptance criteria check out", they mean "they are valid/met" — not that anyone ran a git checkout. Context (Git command discussion vs. general review discussion) always disambiguates.
2 / 30
The phrasal verb "spin up" appears in two different contexts. What does it mean in each?
① "Give me five minutes to spin up a Docker container for the demo." ② "We need to spin up a new team to handle platform migrations."
Both uses of "spin up" share the same core meaning: create and bring something into an operational state.
① Infrastructure context: "spin up a Docker container" = create and start a new container instance so it's running and ready. Extends to: "spin up a VM," "spin up a Kubernetes pod," "spin up a dev environment."
② Organisational context: "spin up a team" = assemble and operationalise a new team — recruit, onboard, give them a mission, and get them working. Extends to: "spin up a task force," "spin up a working group."
The pattern: "spin up" always means going from zero (or near-zero) to a fully running state — whether it's infrastructure or human organisation. The same mental model applies.
Contrast with: • spin off — create a separate entity (a spin-off company, a spin-off project) • scale up — increase capacity of something already running • set up — configure, often more manual/permanent than "spin up"
3 / 30
Your team uses "roll back" in two different conversations. Choose the correct meaning for each:
① Senior DBA: "If the migration fails at step 3, we'll roll back the schema changes." ② Release manager: "The new deploy broke the checkout API — triggering a rollback to v2.9.1."
Are the two meanings the same or different?
Same core meaning, different targets. "Roll back" always means: revert to a previous known-good state. The concept is identical — only the subject differs:
① Database migration rollback: undo schema changes that were applied during a migration step. Tools: Flyway, Liquibase, Django `migrate --fake`, raw `ALTER TABLE`. The schema returns to the state before the migration ran.
② Deployment rollback: revert from the current (broken) application version to the previous stable release. The infrastructure serves the older code again.
The universal IT definition of "roll back": Return a system to a previous state, undoing recent changes that caused or may cause a problem.
Other things you "roll back" in IT: • Config changes (git revert of an infra config) • Feature flags (disable a flag that enabled a problematic feature) • Database transactions (implicit in ROLLBACK; SQL statement — any uncommitted changes are undone)
4 / 30
The phrasal verb "pull in" appears in two very different contexts. What does it mean in each?
① A tech lead in a Slack thread: "Can you pull in the latest changes from main before your PR review tomorrow?" ② A project manager in a planning meeting: "We need to pull in the security team for this feature — it touches user data."
"Pull in" shares a directional metaphor — bringing something INTO your current context — but it applies to different subjects:
① Git context: "pull in the latest changes from main" = fetch and incorporate recent upstream commits into your feature branch. Commands: git pull origin main or git fetch && git rebase origin/main. The "in" emphasises directionality: bringing those changes INTO your branch.
② Team/project context: "pull in the security team" = invite them to join and contribute to this work. The "in" is the same directional metaphor: bringing them INTO the project or conversation. Used widely: "pull in a consultant," "pull in QA early," "pull in legal before we release."
Pattern: "pull in [thing]" = bring [thing] into your current scope. Whether [thing] is code changes, a team, or an external resource, the pattern is consistent.
Contrast with similar verbs: • pull out — withdraw (pull out of a project, pull out a feature) • pull off — succeed at something difficult ("I can't believe they pulled off that migration")
5 / 30
The phrasal verb "set up" appears in three contexts. Which option correctly identifies what is different about context ③?
① "I'll set up the local dev environment for the new joiners." ② "The CI pipeline is already set up — you just need to push." ③ "Someone set up the junior dev — the merge broke main and they got blamed."
"Set up" has three distinct meanings depending on context:
① Configure/prepare (technical) — "set up the dev environment" = install dependencies, configure tools, initialise databases. The most common IT meaning. Noun: "the setup took 20 minutes."
② Already configured (adjective/passive) — "the CI is set up" = it was configured previously and is now in a ready state. This is the past participle used adjectivally.
③ Frame/manipulate (informal, non-technical) — "someone set up the dev" = deliberately arranged circumstances so the junior developer would be blamed for something they didn't cause. This has NOTHING to do with technical configuration.
Why this matters for non-native speakers: In a heated post-incident review, if a senior engineer says "I think someone set him up," they're accusing a person of deliberate manipulation — not talking about system configuration. Misunderstanding this could lead to a very embarrassing and tense conversation.
Noun form clue: "It was a set-up (or setup)" = a scam or frame. "The setup was straightforward" = the configuration process was easy.
6 / 30
John: "I'm trying to debug this persistent connection issue. The logs show the server keeps timing out after a few seconds. I've tried restarting the service, but it just keeps happening. It really checks out – nothing seems obviously wrong."
The phrase "checks out" here indicates a feeling of uncertainty or suspicion. John isn't stating a definitive solution; rather, he's expressing that despite his efforts, the situation *still* seems problematic and requires further investigation. This is common in debugging when initial troubleshooting steps fail.
7 / 30
Sarah (a DevOps engineer) sends a Slack message: "Hey team, can someone spin up a temporary Kubernetes cluster for testing the new microservice deployment? We need to quickly validate the integration before pushing to production."
The verb 'spin up' in this context refers to initiating or starting a temporary system – a Kubernetes cluster – for testing purposes. This aligns with its common usage in DevOps related to quickly setting up environments for development and testing. It does *not* mean creating a permanent installation.
8 / 30
David (a Release Manager) writes in a PR description: "Following the recent deployment to staging, we've had to roll back to version 2.8.1 due to a critical bug impacting user authentication."
When used in this scenario, 'roll back' means to revert or undo a recent change – specifically, reverting the software to an earlier, stable version. This is a standard practice when a deployment introduces issues and needs immediate correction before further updates are applied.
9 / 30
Maria (a Tech Lead) posts in a Slack channel: "Can someone please pull in the database migration scripts from our shared repository? I need them for the upcoming feature implementation."
In this context, 'pull in' means to obtain or incorporate resources – specifically, the database migration scripts – into an existing workflow. It's a common command (git pull) used for synchronizing changes from a remote repository.
10 / 30
Robert (a Senior Developer) says in a standup: "I've been working on integrating the new API. I'm going to set up a local development environment with Docker and PostgreSQL so I can test it thoroughly before submitting a pull request."
When used here, 'set up' means to configure or establish an environment – in this case, a local development environment using Docker and PostgreSQL – for testing purposes. It's about preparing the tools and resources needed to work on the code effectively.
11 / 30
John: "I'm trying to debug this persistent connection issue. The logs show the server keeps timing out after a few seconds. I've tried restarting the service, but it just keeps happening. It really checks out – nothing seems obviously wrong."
The phrase "checks out" here indicates a feeling of uncertainty or suspicion. John isn't stating a definitive solution; rather, he's expressing that despite his efforts, the situation *still* seems problematic and requires further investigation. This is common in debugging when initial troubleshooting steps fail.
12 / 30
Sarah (a DevOps engineer) sends a Slack message: "Hey team, can someone spin up a temporary Kubernetes cluster for testing the new microservice deployment? We need to quickly validate the integration before pushing to production."
The verb 'spin up' in this context refers to initiating or starting a temporary system – a Kubernetes cluster – for testing purposes. This aligns with its common usage in DevOps related to quickly setting up environments for development and testing. It does *not* mean creating a permanent installation.
13 / 30
David (a Release Manager) writes in a PR description: "Following the recent deployment to staging, we've had to roll back to version 2.8.1 due to a critical bug impacting user authentication."
When used in this scenario, 'roll back' means to revert or undo a recent change – specifically, reverting the software to an earlier, stable version. This is a standard practice when a deployment introduces issues and needs immediate correction before further updates are applied.
14 / 30
Maria (a Tech Lead) posts in a Slack channel: "Can someone please pull in the database migration scripts from our shared repository? I need them for the upcoming feature implementation."
In this context, 'pull in' means to obtain or incorporate resources – specifically, the database migration scripts – into an existing workflow. It's a common command (git pull) used for synchronizing changes from a remote repository.
15 / 30
Robert (a Senior Developer) says in a standup: "I've been working on integrating the new API. I'm going to set up a local development environment with Docker and PostgreSQL so I can test it thoroughly before submitting a pull request."
When used here, 'set up' means to configure or establish an environment – in this case, a local development environment using Docker and PostgreSQL – for testing purposes. It's about preparing the tools and resources needed to work on the code effectively.
16 / 30
John: "I'm trying to debug this persistent connection issue. The logs show the server keeps timing out after a few seconds. I've tried restarting the service, but it just keeps happening. It really checks out – nothing seems obviously wrong."
The phrase "checks out" here indicates a feeling of uncertainty or suspicion. John isn't stating a definitive solution; rather, he's expressing that despite his efforts, the situation *still* seems problematic and requires further investigation. This is common in debugging when initial troubleshooting steps fail.
17 / 30
Sarah (a DevOps engineer) sends a Slack message: "Hey team, can someone spin up a temporary Kubernetes cluster for testing the new microservice deployment? We need to quickly validate the integration before pushing to production."
The verb 'spin up' in this context refers to initiating or starting a temporary system – a Kubernetes cluster – for testing purposes. This aligns with its common usage in DevOps related to quickly setting up environments for development and testing. It does *not* mean creating a permanent installation.
18 / 30
David (a Release Manager) writes in a PR description: "Following the recent deployment to staging, we've had to roll back to version 2.8.1 due to a critical bug impacting user authentication."
When used in this scenario, 'roll back' means to revert or undo a recent change – specifically, reverting the software to an earlier, stable version. This is a standard practice when a deployment introduces issues and needs immediate correction before further updates are applied.
19 / 30
Maria (a Tech Lead) posts in a Slack channel: "Can someone please pull in the database migration scripts from our shared repository? I need them for the upcoming feature implementation."
In this context, 'pull in' means to obtain or incorporate resources – specifically, the database migration scripts – into an existing workflow. It's a common command (git pull) used for synchronizing changes from a remote repository.
20 / 30
Robert (a Senior Developer) says in a standup: "I've been working on integrating the new API. I'm going to set up a local development environment with Docker and PostgreSQL so I can test it thoroughly before submitting a pull request."
When used here, 'set up' means to configure or establish an environment – in this case, a local development environment using Docker and PostgreSQL – for testing purposes. It's about preparing the tools and resources needed to work on the code effectively.
21 / 30
John: "I'm trying to debug this persistent connection issue. The logs show the server keeps timing out after a few seconds. I've tried restarting the service, but it just keeps happening. It really checks out – nothing seems obviously wrong."
The phrase "checks out" here indicates a feeling of uncertainty or suspicion. John isn't stating a definitive solution; rather, he's expressing that despite his efforts, the situation *still* seems problematic and requires further investigation. This is common in debugging when initial troubleshooting steps fail.
22 / 30
Sarah (a DevOps engineer) sends a Slack message: "Hey team, can someone spin up a temporary Kubernetes cluster for testing the new microservice deployment? We need to quickly validate the integration before pushing to production."
The verb 'spin up' in this context refers to initiating or starting a temporary system – a Kubernetes cluster – for testing purposes. This aligns with its common usage in DevOps related to quickly setting up environments for development and testing. It does *not* mean creating a permanent installation.
23 / 30
David (a Release Manager) writes in a PR description: "Following the recent deployment to staging, we've had to roll back to version 2.8.1 due to a critical bug impacting user authentication."
When used in this scenario, 'roll back' means to revert or undo a recent change – specifically, reverting the software to an earlier, stable version. This is a standard practice when a deployment introduces issues and needs immediate correction before further updates are applied.
24 / 30
Maria (a Tech Lead) posts in a Slack channel: "Can someone please pull in the database migration scripts from our shared repository? I need them for the upcoming feature implementation."
In this context, 'pull in' means to obtain or incorporate resources – specifically, the database migration scripts – into an existing workflow. It's a common command (git pull) used for synchronizing changes from a remote repository.
25 / 30
Robert (a Senior Developer) says in a standup: "I've been working on integrating the new API. I'm going to set up a local development environment with Docker and PostgreSQL so I can test it thoroughly before submitting a pull request."
When used here, 'set up' means to configure or establish an environment – in this case, a local development environment using Docker and PostgreSQL – for testing purposes. It's about preparing the tools and resources needed to work on the code effectively.
26 / 30
John: "I'm trying to debug this persistent connection issue. The logs show the server keeps timing out after a few seconds. I've tried restarting the service, but it just keeps happening. It really checks out – nothing seems obviously wrong."
The phrase "checks out" here indicates a feeling of uncertainty or suspicion. John isn't stating a definitive solution; rather, he's expressing that despite his efforts, the situation *still* seems problematic and requires further investigation. This is common in debugging when initial troubleshooting steps fail.
27 / 30
Sarah (a DevOps engineer) sends a Slack message: "Hey team, can someone spin up a temporary Kubernetes cluster for testing the new microservice deployment? We need to quickly validate the integration before pushing to production."
The verb 'spin up' in this context refers to initiating or starting a temporary system – a Kubernetes cluster – for testing purposes. This aligns with its common usage in DevOps related to quickly setting up environments for development and testing. It does *not* mean creating a permanent installation.
28 / 30
David (a Release Manager) writes in a PR description: "Following the recent deployment to staging, we've had to roll back to version 2.8.1 due to a critical bug impacting user authentication."
When used in this scenario, 'roll back' means to revert or undo a recent change – specifically, reverting the software to an earlier, stable version. This is a standard practice when a deployment introduces issues and needs immediate correction before further updates are applied.
29 / 30
Maria (a Tech Lead) posts in a Slack channel: "Can someone please pull in the database migration scripts from our shared repository? I need them for the upcoming feature implementation."
In this context, 'pull in' means to obtain or incorporate resources – specifically, the database migration scripts – into an existing workflow. It's a common command (git pull) used for synchronizing changes from a remote repository.
30 / 30
Robert (a Senior Developer) says in a standup: "I've been working on integrating the new API. I'm going to set up a local development environment with Docker and PostgreSQL so I can test it thoroughly before submitting a pull request."
When used here, 'set up' means to configure or establish an environment – in this case, a local development environment using Docker and PostgreSQL – for testing purposes. It's about preparing the tools and resources needed to work on the code effectively.
What will I practise in "🔀 Contextual Disambiguation"?
This module focuses on Phrasal Verbs — real workplace phrasing you'll use on the job. It contains 30 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 30 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasal Verbs exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasal verbs — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasal Verbs exercises?
See the Phrasal Verbs hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.