Caching & Rendering — Chapter Quiz

Question 1

1

Which of these forces a route to be rendered dynamically?

ACalling await fetch(url)BCalling await cookies()CExporting const dynamic = 'force-static'DUsing a [slug] segment

Reading cookies, headers, or dynamic searchParams forces SSR. A cached fetch is the opposite — it lets the route stay static.

Question 2

2

What does export const revalidate = 60 do at the top of a page?

ATriggers SSR every 60 secondsBSets a 60-second TTL for cached data on this route (ISR)CDisables all caching for 60 secondsDAdds a 60-second timeout to fetches

That export turns the route into ISR with a 60-second TTL — stale-while-revalidate behaviour.

Question 3

3

What is the default cache behaviour of fetch(url) in a Server Component?

ANever cachedBCached for 60 secondsCCached in the Data Cache (effectively forever) unless overriddenDCached only in the browser

Without options, fetch results are stored in the Data Cache across requests and users. Add cache: 'no-store' or next.revalidate to change that.

Question 4

4

The Router Cache lives on the server and is shared between users.

TTrueFFalse

The Router Cache is per-user, per-browser-session. The Data Cache and Full Route Cache are server-side and shared.

Question 5

5

Within a single render, two components call fetch(sameUrl). How many network requests fire?

AZeroBOne (request memoization)CTwoDDepends on the user agent

Request memoization deduplicates identical fetches within a single render — the same call anywhere in the tree only hits the network once.

Question 6

6

Which function invalidates every cached fetch tagged with a given string?

ArevalidatePathBrevalidateTagCrouter.refreshDunstable_noStore

revalidateTag(tag) drops every Data Cache entry with that tag, regardless of which URLs depend on it.

Question 7

7

In the build output, the symbol ○ means a route is ________.

○ = static (prerendered HTML). ƒ = dynamic. ◐ = ISR.

Question 8

8

Which approaches opt a fetch out of the Data Cache?

Select all that apply.

Afetch(url, { cache: 'no-store' })BCalling unstable_noStore() before the fetchCTagging the fetch with next.tagsDfetch(url, { next: { revalidate: 0 } })

no-store, noStore(), and revalidate: 0 all bypass the cache. Tagging only labels the entry — it does not opt out.

Test what you learned.