Neon is a serverless Postgres platform with Git-like branching and scale-to-zero compute. These exercises cover Neon's architecture, branching model, and the features that make it unique for developer workflows.
0 / 5 completed
1 / 5
At standup, a colleague asks what a Neon branch is. What is the correct answer?
Neon branches use copy-on-write storage: a new branch is created instantly because it shares the parent's page files and only diverges when writes occur. Each branch has its own compute endpoint (connection string), allowing completely independent read/write access. This enables Git-like workflows — create a branch for each PR, run migrations and tests against it, then delete it, all without affecting the parent database.
2 / 5
During a PR review, a teammate asks what compute endpoints are in Neon and why a branch without one cannot accept connections. What is accurate?
In Neon's architecture, storage and compute are separate. A branch is a storage concept (copy-on-write page files), while a compute endpoint is the actual Postgres process that reads and writes those pages. A branch without a compute endpoint has no running Postgres — you cannot connect to it. You create a compute endpoint for a branch explicitly (or Neon creates one automatically for the main branch) to enable SQL connections.
3 / 5
In a design review, the team discusses scale-to-zero on Neon. A junior engineer asks what happens when a Neon compute scales to zero. What is correct?
Scale-to-zero suspends the Postgres compute process after a configurable idle period (default 5 minutes). The compute costs drop to zero because no server is running, but storage (and all data) is preserved. The next incoming connection triggers an automatic cold start — typically around 500ms — before queries can be served. This makes Neon cost-effective for development databases and intermittent workloads.
4 / 5
An incident report shows connection pool exhaustion on a Neon database. A senior engineer asks what connection pooling option Neon provides. What is correct?
Neon provides built-in PgBouncer connection pooling. Each compute endpoint has two connection strings: a direct string (standard Postgres port) and a pooled string (typically port 6543) that routes through PgBouncer in transaction mode. The pooled connection supports far more concurrent clients than the Postgres process's max_connections, making it essential for serverless environments where many short-lived connections are common.
5 / 5
During a code review, a senior engineer asks about branch protection in Neon. What does it prevent?
Branch protection in Neon marks a branch (typically main/production) so it cannot be accidentally deleted via the API or console. Protected branches show a lock icon in the Neon dashboard. This safeguard prevents destructive operations on production data. It does not automatically make the branch read-only or enforce schema review workflows — it is purely a deletion guard.
What does the "Neon Postgres Branching Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to neon postgres branching 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.