Why SSR enables dynamic content in Astro - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to render dynamic content on the server.

Astro

export async function get() {
  const time = new Date().toLocaleTimeString();
  return {
    body: `Current time is: [1]`
  };
}

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

AtoLocaleString()

BDate.now()

Cnew Date()

Dtime

Attempts:

3 left

💡 Hint

Common Mistakes

Using a Date object directly instead of the formatted string.

The variable time holds the formatted current time string, which is returned as dynamic content.

2fill in blank

medium

Complete the code to fetch data dynamically during server rendering.

Astro

export async function get() {
  const response = await fetch('[1]');
  const data = await response.json();
  return {
    body: JSON.stringify(data)
  };
}

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

A'https://example.com/api/data'

B'/api/data'

C'data.json'

D'/static/data.json'

Attempts:

3 left

💡 Hint

Common Mistakes

Using a relative path that may not fetch dynamic data during SSR.

Using a full URL like 'https://example.com/api/data' fetches dynamic data from an external API during SSR.

3fill in blank

hard

Fix the error in the server-side rendering function to correctly return dynamic props.

Astro

export async function get() {
  const user = await fetchUser();
  return {
    [1]: { props: { user } }
  };
}

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

Aprops

Bdata

Cbody

Dresponse

Attempts:

3 left

💡 Hint

Common Mistakes

Using props instead of body in the return object.

In Astro SSR, the get function should return an object with a body property containing the response data.

4fill in blank

hard

Fill both blanks to create a dynamic Astro component that fetches and displays user data.

Astro

---
const user = await fetchUser();
---
<h1>Hello, [1]!</h1>
<p>Your email is [2].</p>

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

Auser.name

Buser.email

Cuser.id

Duser.username

Attempts:

3 left

💡 Hint

Common Mistakes

Using user.id or user.username instead of name or email.

The component uses user.name for the greeting and user.email to show the email address dynamically.

5fill in blank

hard

Fill all three blanks to build a server-rendered Astro page that fetches posts and displays their titles.

Astro

---
const posts = await fetchPosts();
---
<ul>
  {posts.map(post => (
    <li key=[1]>[2]</li>
  ))}
</ul>
<p>Total posts: [3]</p>

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

Apost.id

Bpost.title

Cposts.length

Dpost.content

Attempts:

3 left

💡 Hint

Common Mistakes

Using post content instead of title, or missing keys in list items.

The list uses post.id as the key, displays post.title, and shows the total count with posts.length.

Practice

1. Why does Server-Side Rendering (SSR) enable dynamic content in web pages?

easy

A. Because SSR caches pages permanently and never updates them.

B. Because SSR sends a static HTML file that never changes after deployment.

C. Because SSR runs all JavaScript only in the browser after loading the page.

D. Because SSR builds the page on the server each time a user requests it, allowing fresh data.

Solution

1. Step 1: Understand SSR page generation

   SSR builds the page on the server every time a user visits, not just once.

2. Step 2: Connect SSR to dynamic data

   This means the server can include fresh or user-specific data before sending the page.

3. Final Answer:

   Because SSR builds the page on the server each time a user requests it, allowing fresh data. -> Option D

4. Quick Check:

   SSR = fresh server-built pages [OK]

Hint: SSR builds pages on demand, so content can change [OK]

Common Mistakes:

• Thinking SSR sends static files only
• Confusing SSR with client-side rendering
• Assuming SSR caches pages forever

2. Which of the following is the correct way to enable SSR in an Astro component?

easy

A. export const prerender = true;

B. export const prerender = false;

C. import prerender from 'astro';

D. const prerender = 'enabled';

Solution

1. Step 1: Recall SSR enabling syntax in Astro

   Astro uses export const prerender = false; to enable server-side rendering.

2. Step 2: Check other options for correctness

   Exporting prerender = true; results in static rendering, the import is invalid, and the const assignment uses wrong syntax.

3. Final Answer:

   export const prerender = false; -> Option B

4. Quick Check:

   SSR enabled by export const prerender = false; [OK]

Hint: Look for exact prerender export syntax in Astro [OK]

Common Mistakes:

• Using prerender = true instead of false to enable SSR
• Trying to import prerender as a module
• Assigning prerender as a string instead of boolean

3. Given this Astro component code with SSR enabled:

export const prerender = false;
const time = new Date().toLocaleTimeString();
---
<div>Current time: {time}</div>

What will the user see when they reload the page multiple times?

medium

A. The time shown updates on each reload to the current server time.

B. The time shown is fixed to when the page was first built and never changes.

C. The time updates only after client-side JavaScript runs.

D. The page will show an error because Date is not allowed in SSR.

Solution

1. Step 1: Understand SSR effect on dynamic values

   With prerender = false, the server runs the code on each request, so new Date() is fresh every time.

2. Step 2: Predict output on reload

   Reloading the page triggers server to build new HTML with current time, so time updates.

3. Final Answer:

   The time shown updates on each reload to the current server time. -> Option A

4. Quick Check:

   SSR runs code fresh each request [OK]

Hint: SSR runs code on server per request, so output changes [OK]

Common Mistakes:

• Thinking time is fixed after first build
• Assuming client JS updates time instead
• Believing Date is disallowed in SSR

4. This Astro component is intended to show the current user name dynamically using SSR:

export const prerender = false;
const userName = fetchUserName();
---
<div>Hello, {userName}!</div>

But it shows "Hello, undefined!" What is the likely problem?

medium

A. Astro does not support variables in templates.

B. SSR is disabled by default, so dynamic code does not run.

C. fetchUserName() is asynchronous but used without await.

D. The variable userName must be declared inside the template.

Solution

1. Step 1: Identify async function usage

   fetchUserName() likely returns a Promise, so it must be awaited to get the value.

2. Step 2: Understand why undefined appears

   Without await, userName is a Promise object, which renders as undefined in template.

3. Final Answer:

   fetchUserName() is asynchronous but used without await. -> Option C

4. Quick Check:

   Async functions need await to get values [OK]

Hint: Await async calls to get real values in SSR [OK]

Common Mistakes:

• Forgetting to await async functions
• Assuming SSR is off by default
• Thinking variables must be inside template tags

5. You want to show a personalized greeting on your Astro page that updates every time a user visits, using SSR. Which approach correctly achieves this?

export const prerender = false;
async function getUserName() {
  return await fetch('/api/user').then(res => res.json()).then(data => data.name);
}
const userName = await getUserName();
---
<h1>Welcome back, {userName}!</h1>

Why does this work to show dynamic content?

hard

A. Because SSR runs the async function on the server per request, fetching fresh user data each time.

B. Because Astro caches the userName forever after first fetch, so it never changes.

C. Because the client browser runs getUserName() after page loads to update content.

D. Because SSR disables async functions to improve performance.

Solution

1. Step 1: Analyze async data fetching in SSR

   The async function runs on the server every time a user requests the page, so it fetches fresh data.

2. Step 2: Understand dynamic content generation

   Since SSR builds the page per request, the greeting updates with the latest user info.

3. Final Answer:

   Because SSR runs the async function on the server per request, fetching fresh user data each time. -> Option A

4. Quick Check:

   SSR + async fetch = fresh dynamic content [OK]

Hint: SSR runs async code fresh on server per request [OK]

Common Mistakes:

• Thinking Astro caches async results forever
• Assuming client runs async fetch after load
• Believing SSR disables async functions