5 exercises — the same verb with a different particle means something completely different. Roll back vs. roll out vs. roll over. Master the particle patterns used in deployments, Git workflows, and code reviews.
Particle patterns in IT phrasal verbs
UP → creation, start, increase: spin up · scale up · set up · stand up · build up
DOWN → stop, remove, decrease, decompose: tear down · scale down · break down · shut down · drill down
BACK → revert, return to previous state: roll back · fall back · revert back · push back
OUT → release, remove, make visible: roll out · phase out · factor out · filter out · call out
INTO → investigate, enter deeper: look into · dig into · break into · tap into
OFF → separate, start from, shut: branch off · kick off · sign off · switch off
0 / 13 completed
1 / 13
A release manager writes in the deployment runbook: "If the error rate exceeds 5% within the first 30 minutes, immediately roll _____ the release to the last stable tag." Which particle is correct?
Roll back = revert to a previous version — go backwards to a known good state.
The particle back signals direction: movement backward in time or to a prior state. This is the critical particle to know in deployment contexts.
The "roll" family in IT — each particle changes the meaning completely:
roll back → revert to a previous version: "Roll back the deployment if errors spike."
roll out → release to users gradually or fully: "Roll out the feature to 10% of users first."
roll up → combine/aggregate into a summary: "Roll up the metrics into a weekly dashboard." OR sleeve: not used technically for deployments.
roll over → transfer/carry over (budgets, IP addresses, subscriptions): "Roll over unused API credits to next month." Also: a loop in protocols — not a deployment term.
Memory trick: When something goes wrong, you go back → roll back. When you release to the world, it goes out → roll out.
2 / 13
A DevOps engineer is writing infrastructure-as-code documentation: "After the load test, _____ the environment to free up resources. We'll spin it _____ again before the next test cycle."
Tear down = shut down and completely remove an environment or resource. More than just stopping — it destroys the infrastructure so it no longer exists and incurs no cost.
Spin up = start / launch / create a resource (server, container, environment). "Spin up" uses the particle up because you're building something up from nothing.
The "up" particle family in IT deployments:
spin up → create and start: "Spin up a container"
scale up → increase capacity: "Scale up from 2 to 8 replicas"
set up → configure and make ready: "Set up the pipeline"
stand up → deploy and make live (architectural): "Stand up a new microservice"
The "down" particle family:
tear down → destroy/remove entirely: "Tear down the test environment"
scale down → decrease capacity: "Scale down overnight to save cost"
shut down → stop: "Shut down the process gracefully"
spin down → stop and deallocate: "Spin down the idle worker"
Pattern: UP = creation, starting, increasing. DOWN = removal, stopping, decreasing.
3 / 13
A developer writes a Git workflow guide. Choose the sentence where all particles are correct:
(1) "Create a feature branch by branching _____ from main." (2) "When the feature is ready, open a PR to merge it _____ main." (3) "After the PR is approved and merged, clean _____ the feature branch."
Git workflow particles:
(1) Branch off (from) = create a new branch that diverges from the source. "Off" signals separation/departure from the base. "Branch off from main" means you're starting a new path away from the main line.
(2) Merge into = incorporate changes into a target branch. "Into" signals you're putting one thing inside another — your feature branch changes go into main. Alternative: "merge in" (also used: "merge in the PR"). "Merge in" and "merge into" are both used; "merge in" treats the branch as the object, "merge into [target]" names the destination.
(3) Clean up = remove, tidy, eliminate unnecessary things. "Clean up stale branches." "Clean up the codebase." The particle "up" with "clean" means to complete the action of removing mess — common in both technical and domestic contexts.
Other Git phrasal verbs with particles:
push to / push up to → send commits to remote: "Push up to origin"
pull in / pull from → fetch and merge from remote: "Pull in the latest changes"
check out → switch to a branch: "Check out feature/login"
squash into → combine commits: "Squash the 3 commits into one before merging"
4 / 13
A senior engineer uses three phrasal verbs in a code review comment: "Can you look into the memory leak? I think we need to refactor out this helper and break down the function into smaller units." Match each phrasal verb to its meaning.
Three "investigation + refactoring" phrasal verbs, each with a different particle:
Look into = investigate, examine in detail. "Into" signals depth — you're going into the problem. "Look into the memory leak" = investigate what's causing it. Compare: look at (observe casually) vs. look into (investigate seriously).
Refactor out = remove something from its current location by restructuring it. "Out" signals removal or extraction. "Refactor out the helper" means take it away from where it is — either delete it or move it somewhere cleaner. Compare: pull out (extract), factor out (extract to a common place).
Break down = divide a complex thing into smaller, understandable parts. "Down" signals decomposition — works like dissection. "Break down the function" = split a large function into focused smaller ones. Note: break down also means "fail to work" (the server broke down), so context matters.
Particle "into" = going deeper or inside: look into · dig into · get into · go into (detail) · tap into Particle "out" = removal or making visible: refactor out · factor out · pull out · call out · point out · filter out Particle "down" = decomposing: break down · drill down · narrow down · whittle down · boil down
5 / 13
A tech lead is reviewing a PR comment. Which sentence uses the particle correctly?
Roll out = release, deploy, or distribute gradually or widely. "Out" signals going from a central point outward — to users, to servers, to the world. "Roll out the feature to 10% of users." "Roll out the change across all regions."
Why the other options are wrong:
Option A — "scale over": ❌ Not a standard IT phrasal verb. You scale up (increase), down (decrease), or out (add more instances horizontally). "Scale out" = add more nodes/instances. "Scale up" = make each node more powerful.
Option B — "break it out": The phrase "break out" exists (escape; or break out into a separate unit), but "break it out into three smaller functions" is slightly unusual. The standard phrasing is "break it down into three smaller functions" (decompose) or "extract into" (refactoring term). "Break it out" is used more for moving something to a separate location, not just dividing it.
Option D — "phase up": ❌ Not standard. You phase in (gradually introduce) or phase out (gradually retire). There is no "phase up."
Scale family summary: • scale up → more powerful resources (vertical scaling) • scale out / scale horizontally → more instances • scale down → reduce resources • scale back → reduce scope or ambition: "We scaled back the feature set for v1"
6 / 13
Sarah, the backend engineer, sent this Slack message to the team: 'We're seeing intermittent failures with the payment gateway integration. I'm going to debug it and try to trace it back to the root cause.' Which particle is most appropriate for her to use in this context?
'Call out' means to identify or highlight a problem. Here, Sarah is pinpointing the specific issue – the payment gateway integration – and drawing attention to it for the team. 'Take down' refers to shutting something down, which doesn't fit the situation. 'Sort out' implies fixing a general problem without specifying the source, and 'work through' suggests a process of investigation rather than identifying the core issue.
7 / 13
David, a developer, wrote this PR description: 'I've refactored the authentication module. I needed to break it down into smaller units to improve maintainability and reduce complexity. After doing so, I had to look into a few edge cases and implemented some additional error handling.' Which particle best describes his actions regarding the module?
'Wrap up' means to finalize or complete a task. In this case, David refactored and broke down the authentication module – 'wrapping it up' signifies completion of that process. The other options don't fit the context of development work; 'put through' suggests processing data, 'iron out' implies smoothing out conflicts, and 'pick up' means to start or acquire something.
8 / 13
Emily, a QA engineer, was writing a test report. Which sentence correctly uses the particle 'get' in this context? (1) 'The application got crashed after running the test.'(2) 'We need to get through these tests quickly.'(3) 'It's getting on my nerves that the tests are failing.'
When 'get' is used to describe an application crashing, it means 'caused to' or 'resulted in'. 'Get over' implies overcoming a feeling, 'get around' suggests finding a way through something, 'get rid of' means to eliminate something, and 'get back' refers to returning to a previous state. The first option accurately conveys the application crashing as a result of the test.
9 / 13
{code}. The team lead needs to clarify which action should be taken next. Which particle best expresses the urgency of the situation?
'Work out' in this context means 'find a solution'. Using 'put out' implies extinguishing a fire, which isn't appropriate for debugging. 'Look into' is too general; it doesn't convey the need to actively solve the problem. 'Check out' refers to verifying information, not resolving an issue.
10 / 13
Mark, a junior developer, is explaining a bug to his senior. He says: 'I've been trying to debug this, but I can't get it to work. I need to look into the logs and see what's going on.' Which particle is most appropriate here?
'Work out' signifies attempting to resolve a difficulty. 'Put through' is often used with processes or systems. 'Get over' suggests dealing with an emotional issue, which isn't suitable for debugging. 'Look into' is the most accurate choice here, indicating a detailed investigation.
11 / 13
A developer is writing a comment on a code review: 'This function needs to be refactored because it's too complex. We need to break it down into smaller units to improve readability and maintainability.' Which particle best describes the action of dividing the function?
'Break down' is the standard phrasal verb used when dividing or simplifying something complex. 'Put through' suggests processing data, and 'get around' implies circumventing restrictions. 'Look after' refers to responsibility and care – irrelevant here.
12 / 13
During a standup meeting, the team lead asks: 'Has anyone encountered any issues with deploying the new feature?'. John responds: 'I'm trying to roll it back, but I can't get the deployment to work.' Which particle is used correctly in this scenario?
'Roll out' is the correct phrasal verb for releasing a new feature. It's often used in deployments. 'Get over' refers to overcoming a challenge, while 'look into' is an investigation. Using 'put through' would imply completing a process – not deploying software.
13 / 13
A developer is responding to a Slack notification: 'The API endpoint is returning 500 errors. I'm going to debug it and trace it back to the root cause.' Which particle is used correctly?
'Get through' means to successfully complete a process or task. It's commonly used when troubleshooting technical issues like API errors. 'Look into' is an investigation, 'put out' refers to extinguishing something, and 'work out' implies finding a solution – the latter two would be less natural in this specific Slack message.
What will I practise in "Choosing the Right Particle"?
This module focuses on Phrasal Verbs — real workplace phrasing you'll use on the job. It contains 13 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 13 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.