This set builds vocabulary for reproducible, ephemeral cloud development workspaces.
0 / 5 completed
1 / 5
At standup, a dev mentions a configuration file in the repository that declares the exact Docker image, tasks, and ports needed to spin up a ready-to-code workspace. What is this file called?
A workspace configuration file, like Gitpod's .gitpod.yml, declares the exact Docker image, startup tasks, and ports a project needs, letting the platform automatically provision a fully ready-to-code environment from that declarative definition. This removes manual setup steps and keeps the environment definition version-controlled alongside the code itself. It's the core mechanism that makes an ephemeral cloud workspace reproducible on demand.
2 / 5
During a design review, the team wants a workspace to be pre-built in the background as soon as a commit is pushed, so it's instantly ready when a developer opens it. Which capability supports this?
Prebuilds run the workspace's setup steps, like dependency installation, in the background as soon as a commit is pushed, so that when a developer actually opens the workspace it's already prepared rather than making them wait through the full build process. This significantly reduces the perceived startup latency of an ephemeral cloud environment. It's a performance optimization layered on top of the basic on-demand provisioning model.
3 / 5
In a code review, a dev notices closing a workspace without merging discards all its state, since each one is spun up fresh from the repository each time. What does this reflect?
The ephemeral nature of a cloud workspace means it's spun up fresh from the repository's committed state and configuration each time, so any uncommitted local changes or manual environment tweaks are lost once that workspace is closed and not reopened. This disposability encourages committing meaningful changes and configuration into version control rather than relying on undocumented local state. It's a deliberate design tradeoff favoring reproducibility over persistent customization.
4 / 5
An incident report shows a developer lost hours of uncommitted work because an idle ephemeral workspace was automatically terminated. What practice would prevent this?
Since an ephemeral workspace can be automatically terminated after a period of inactivity, regularly committing or otherwise saving work-in-progress avoids losing hours of uncommitted changes when that termination happens. Assuming a workspace will simply persist indefinitely misunderstands the disposable model these platforms are built around. This habit of frequent committing is a reasonable adaptation to working in any ephemeral compute environment.
5 / 5
During a PR review, a teammate asks why the team relies on ephemeral, disposable cloud workspaces instead of a persistent, always-available development machine. What is the reasoning?
A persistent development machine can accumulate undocumented local changes and configuration drift over time, while an ephemeral workspace is rebuilt fresh from the repository's declared configuration every time, guaranteeing it matches what's actually committed. This reproducibility is valuable for catching "works on my machine" issues early. The tradeoff is losing any convenience of long-lived local customization that isn't captured in the workspace configuration.
What does the "Gitpod Cloud Development Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to gitpod cloud development vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.