Why caching is central to Next.js - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Next.js use caching for server components?

Next.js uses caching for server components mainly to:

A Store user passwords securely on the server

B Automatically update the UI without developer input

C Reduce repeated data fetching and speed up page rendering

D Enable client-side routing without page reloads

💡 Hint

Think about how caching helps avoid doing the same work multiple times.

Next.js caches server components to avoid fetching the same data repeatedly. This makes pages load faster and reduces server work.

❓ component_behavior

intermediate

What happens when cached data in Next.js expires?

In Next.js, when cached data for a page expires, the framework will:

A Delete the page and show a 404 error

B Force the user to reload the browser manually

C Serve stale data indefinitely without updating

D Fetch fresh data and update the cache before serving the page

💡 Hint

Consider how caching systems keep data fresh.

Next.js uses cache expiration to know when to fetch new data. When expired, it fetches fresh data and updates the cache automatically.

📝 Syntax

advanced

Which Next.js code snippet correctly enables caching for a server component?

Select the code snippet that properly uses Next.js caching for a server component fetching data.

NextJS

import { cache } from 'react';

const fetchData = cache(async () => {
  const res = await fetch('https://api.example.com/data');
  return res.json();
});

export default async function Page() {
  const data = await fetchData();
  return <div>{data.message}</div>;
}

A Calls fetch() directly inside the component without caching

B Uses the cache() wrapper around the async fetch function to memoize results

C Caches data by storing it in a global variable manually

D Uses useState hook to cache data on the client side

💡 Hint

Look for the official React cache() function usage.

Next.js recommends using React's cache() to memoize async data fetching in server components. This avoids repeated fetches.

🔧 Debug

advanced

Why does this Next.js server component fetch data on every request despite caching?

Given this code, why is data fetched every time instead of cached? import { cache } from 'react'; async function getData() { return await fetch('https://api.example.com/data').then(res => res.json()); } const cachedGetData = cache(getData); export default async function Page() { const data = await getData(); return

{data.title}

; }

A The component calls getData() directly instead of cachedGetData(), so caching is bypassed

B The cache() function is used incorrectly and does not memoize async functions

C Next.js disables caching by default in server components

D The fetch URL is dynamic and prevents caching

💡 Hint

Check which function is actually called inside the component.

The component calls getData() directly, ignoring the cached version cachedGetData. So caching does not happen.

❓ lifecycle

expert

How does Next.js caching interact with Incremental Static Regeneration (ISR)?

In Next.js, when using ISR with a revalidate time, caching works by:

A Serving a cached static page until the revalidate time expires, then regenerating the page in the background

B Regenerating the page on every request without caching

C Disabling caching completely to always show fresh data

D Serving stale pages indefinitely without regeneration

💡 Hint

Think about how ISR balances caching and freshness.

ISR caches static pages and serves them instantly. When the revalidate time passes, Next.js regenerates the page in the background for future requests.