Hybrid rendering (static + server) in Astro - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to export a static Astro component.

Astro

export const prerender = [1];

---
<h1>Hello, Astro!</h1>

Drag options to blanks, or click blank then click option'

Atrue

Bfalse

Cundefined

Dnull

Attempts:

3 left

💡 Hint

Common Mistakes

Using false disables static prerendering.

Using null or undefined causes build errors.

Setting prerender = true tells Astro to generate the page statically at build time.

2fill in blank

medium

Complete the code to fetch data on the server during rendering.

Astro

---
const data = await fetch('[1]').then(res => res.json());
---
<p>{data.message}</p>

Drag options to blanks, or click blank then click option'

A'./localfile.json'

B'/static/message.json'

C'https://example.com/api/message'

D'/api/message'

Attempts:

3 left

💡 Hint

Common Mistakes

Using static files does not fetch dynamic server data.

Local file paths may not work in server fetch.

Using '/api/message' fetches data from a server endpoint during rendering.

3fill in blank

hard

Fix the error in the Astro component to enable hybrid rendering.

Astro

export const prerender = [1];

---
<p>Current time: {new Date().toISOString()}</p>

Drag options to blanks, or click blank then click option'

Afalse

Bundefined

Cnull

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Setting prerender to true causes static output with stale data.

Using null or undefined causes build errors.

Setting prerender = false disables static generation, allowing server rendering for dynamic content.

4fill in blank

hard

Fill both blanks to create a hybrid Astro component that statically renders but fetches server data.

Astro

export const prerender = [1];

---
const serverData = await [2]('/api/data');

<p>{serverData.info}</p>

Drag options to blanks, or click blank then click option'

Atrue

Bfalse

Cfetch

DgetStaticProps

Attempts:

3 left

💡 Hint

Common Mistakes

Using false disables static prerendering.

Using getStaticProps is not an Astro method.

Setting prerender = true enables static generation, and using fetch fetches data on the server during rendering.

5fill in blank

hard

Fill all three blanks to build an Astro component that statically prerenders and uses server data with a fallback.

Astro

export const prerender = [1];
export const hydrate = '[2]';

---
const data = await [3]('/api/info');

<p>{data.detail}</p>

Drag options to blanks, or click blank then click option'

Atrue

Bclient

Cfetch

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Setting hydrate to false disables client hydration.

Using false for prerender disables static generation.

Static prerendering is enabled with true. Hydration on the client is set with 'client'. Server data is fetched using fetch.

Practice

1. What is the main benefit of using hybrid rendering in Astro?

easy

A. It only renders pages fully on the client side.

B. It combines fast static content with fresh server data.

C. It disables server-side rendering completely.

D. It requires no data fetching at all.

Solution

1. Step 1: Understand hybrid rendering purpose

   Hybrid rendering mixes static and server-rendered content to get the best of both worlds: speed and fresh data.

2. Step 2: Compare options

   Only 'It combines fast static content with fresh server data.' correctly describes this benefit. The other options misunderstand hybrid rendering.

3. Final Answer:

   It combines fast static content with fresh server data. -> Option B

4. Quick Check:

   Hybrid rendering = fast + fresh [OK]

Hint: Hybrid means mixing static speed with server freshness [OK]

Common Mistakes:

• Thinking hybrid disables server rendering
• Assuming hybrid is client-only rendering
• Believing hybrid needs no data fetching

2. Which Astro syntax correctly fetches data on the server side for hybrid rendering?

easy

A. fetch('https://api.example.com').then(data => setData(data))

B. const data = fetch('https://api.example.com')

C. ---
const data = await fetch('https://api.example.com')
---

D. useEffect(() => { fetch('https://api.example.com') })

Solution

1. Step 1: Identify Astro frontmatter usage

   Astro uses frontmatter (---) to run server-side code before rendering.

2. Step 2: Check options for server-side fetch

   --- const data = await fetch('https://api.example.com') --- uses frontmatter with await fetch, which is correct. The other options lack frontmatter or use client-side hooks.

3. Final Answer:

   ---\nconst data = await fetch('https://api.example.com')\n--- -> Option C

4. Quick Check:

   Server fetch = frontmatter + await [OK]

Hint: Use frontmatter (---) with await for server fetch [OK]

Common Mistakes:

• Omitting frontmatter for server code
• Using client hooks like useEffect in Astro
• Not awaiting fetch in server code

3. Given this Astro component code, what will be rendered?

---
const time = new Date().toLocaleTimeString();
---

  
    
Current Time:
    
{time}
  

medium

A. The time when the page was built (static time).

B. The current time updated every second.

C. An error because {time} is invalid syntax.

D. Nothing, because time is not defined.

Solution

1. Step 1: Understand Astro frontmatter timing

   Code inside frontmatter runs once at build or server render time, so time is fixed then.

2. Step 2: Check rendering behavior

   The rendered page shows the time captured during rendering, not live updates. So The time when the page was built (static time). is correct.

3. Final Answer:

   The time when the page was built (static time). -> Option A

4. Quick Check:

   Frontmatter time = fixed render time [OK]

Hint: Frontmatter runs once; time is static, not live [OK]

Common Mistakes:

• Thinking time updates live on client
• Confusing Astro syntax with React JSX
• Assuming {time} causes error

4. What is wrong with this Astro code snippet for hybrid rendering?

---
const data = fetch('https://api.example.com/data');
---
{data.json()}

medium

A. fetch is not awaited, so data is a Promise, causing an error.

B. Using fetch inside frontmatter is not allowed.

C. The <p> tag cannot contain JavaScript expressions.

D. data.json() returns a string, which cannot be rendered.

Solution

1. Step 1: Check fetch usage

   fetch returns a Promise; without await, data is a Promise, not the response.

2. Step 2: Understand rendering error

   Calling data.json() on a Promise causes an error because data is not resolved yet.

3. Final Answer:

   fetch is not awaited, so data is a Promise, causing an error. -> Option A

4. Quick Check:

   Always await fetch in frontmatter [OK]

Hint: Always await fetch to get response, not Promise [OK]

Common Mistakes:

• Forgetting to await fetch
• Misunderstanding frontmatter fetch rules
• Thinking data.json() returns string directly

5. You want to build a blog page in Astro that shows static posts but also displays the current number of visitors fetched live from the server. Which approach best uses hybrid rendering?

hard

A. Render everything statically with no data fetching.

B. Fetch both posts and visitor count inside frontmatter only.

C. Fetch posts on client side with useEffect, visitor count in frontmatter.

D. Fetch posts in frontmatter for static build, then fetch visitor count inside a server component.

Solution

1. Step 1: Separate static and dynamic data

   Posts are mostly static, so fetching them in frontmatter for static build is efficient.

2. Step 2: Use server component for live data

   Visitor count changes often, so fetching it in a server component ensures fresh data on each request.

3. Step 3: Evaluate options

   Fetch posts in frontmatter for static build, then fetch visitor count inside a server component. correctly mixes static and server rendering. The other options do not use hybrid rendering properly.

4. Final Answer:

   Fetch posts in frontmatter for static build, then fetch visitor count inside a server component. -> Option D

5. Quick Check:

   Static + server fetch = hybrid rendering [OK]

Hint: Static data in frontmatter, dynamic in server component [OK]

Common Mistakes:

• Fetching all data statically losing freshness
• Fetching static data on client unnecessarily
• Not separating static and dynamic concerns