Build fluency in the vocabulary of abstract syntax tree (AST).
0 / 5 completed
1 / 5
A teammate explains that a compiler's parser reads a stream of tokens and builds a tree structure where each node represents a language construct like a function call or a binary expression, discarding punctuation and whitespace but preserving the nested structure needed to reason about the program. What is being described?
An abstract syntax tree (AST) is exactly what is described here. A DNS zone transfer is an unrelated concept about replicating name server records. Understanding an AST is exactly why it comes up so often in real engineering discussions of this kind of problem.
2 / 5
During a design review, the team adopts an AST, specifically to gain a concrete benefit. Which capability does this provide?
An AST here provides a structured representation that every later compiler pass can walk and transform without re-parsing the raw token stream. Treating the source code as a flat list of tokens and pattern-matching directly against that stream for every later pass is the alternative this avoids. This behavior is exactly why an AST is favored in this kind of scenario.
3 / 5
In a code review, a dev notices a system relies on treating the source code as a flat list of tokens and pattern-matching directly against that token stream for every later compiler pass, instead of building an AST. What does this represent?
This is a missed AST-opportunity, since an AST would provide a structured representation every later compiler pass can walk and transform without re-parsing the token stream. A cache eviction policy is an unrelated concept about discarded cache entries. This pattern is exactly the kind of gap a reviewer flags once the tradeoffs are understood.
4 / 5
An incident report shows a new compiler pass kept re-scanning the raw token stream to find matching brackets and misidentified a nested expression's boundaries because there was no structural intermediate representation to walk. What practice would prevent this?
Parsing the token stream into an abstract syntax tree once, so every later pass walks the tree's nested structure instead of re-parsing the flat token stream from scratch. Continuing the prior approach regardless of the risk it has already caused is exactly what led to the incident described here. This fix is the standard remedy once the root cause is confirmed.
5 / 5
During a PR review, a teammate asks why the team reaches for an AST instead of treating the source code as a flat list of tokens and pattern-matching directly against that stream for every later compiler pass. What is the reasoning?
Building an AST trades the upfront cost of a parsing pass for a structured representation every later compiler stage can walk directly, while working straight off the token stream avoids that cost but forces every later pass to re-derive the code's structure itself. This is exactly why an AST is favored in scenarios that call for it, while the alternative remains acceptable in simpler cases that don't.
What does the "Abstract syntax tree (AST) Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to abstract syntax tree (ast) 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.