Build fluency in the vocabulary of hydrating only the small interactive parts of a mostly static page.
0 / 5 completed
1 / 5
A teammate explains that a page is rendered mostly as static HTML on the server, and only the small, specific components that actually need client-side interactivity, like a shopping-cart widget, are individually hydrated with JavaScript, while the surrounding static content, like an article's body text, ships with zero JavaScript attached to it. What frontend rendering architecture is being described?
Islands architecture renders a page mostly as static HTML on the server and individually hydrates only the small, specific components that actually need client-side interactivity, like a shopping-cart widget, treating each one as an isolated 'island' of interactivity, while the surrounding static content, like an article's body text, ships with zero JavaScript attached to it at all, unlike a traditional single-page app that hydrates the entire page as one large JavaScript bundle regardless of how much of it is actually interactive. A DNS zone transfer is an unrelated concept about replicating name server records. This hydrate-only-the-small-interactive-islands approach is exactly why islands architecture is favored for content-heavy sites because it ships JavaScript proportional to how much of the page is actually interactive, instead of shipping a full framework bundle for a page that is mostly static text.
2 / 5
During a design review, the team adopts islands architecture for a content-heavy news site where an article's body text never changes after render but a small comments widget and a shopping-cart icon do need interactivity, specifically so the vast majority of the page's static text ships with zero JavaScript attached. Which capability does this provide?
Islands architecture here provides JavaScript payload proportional to actual interactivity, since only the small comments widget and cart icon are hydrated as isolated islands while the article's static body text ships with no JavaScript at all. A traditional single-page app that hydrates the entire page, including the static article body text, as one large JavaScript bundle regardless of how little of the page is actually interactive is the alternative this avoids. This behavior is exactly why islands architecture is favored in this kind of scenario.
3 / 5
In a code review, a dev notices a content-heavy news site hydrates its entire page, including the static article body text that never changes after render, as one large single-page-app JavaScript bundle, instead of using an islands architecture that would hydrate only the small comments widget and cart icon as isolated islands. What does this represent?
This is a missed islands architecture-opportunity, since islands architecture would ship JavaScript only for the small interactive components instead of hydrating the entire static article body as part of one large bundle. 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 content-heavy news site's time-to-interactive was several seconds slower than competitors, because the entire page, including static article text that never changes after render, was hydrated as one large single-page-app JavaScript bundle regardless of how little of the page was actually interactive. What practice would prevent this?
Adopting an islands architecture so only the small interactive components, like the comments widget and cart icon, are individually hydrated, while the static article text ships with no JavaScript at all. 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 islands architecture instead of a traditional single-page app that hydrates the entire page as one bundle. What is the reasoning?
islands architecture trades the added framework complexity of coordinating multiple independently hydrated islands for a JavaScript payload proportional to actual interactivity, while a traditional single-page app is simpler to reason about as one unit but ships a full framework bundle even for a page that is mostly static text. This is exactly why islands architecture is favored when a site is content-heavy with only a small fraction of the page actually needing interactivity, while a traditional single-page app that hydrates the entire page as one bundle remains acceptable when most of the page is genuinely interactive and benefits from being managed as one cohesive application.
What does the "Islands Architecture Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to islands architecture 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.