All quizzesHard
Streaming & Suspense — Series 2
Preview — 3 of 10 questions
With PPR enabled, what happens to Time To First Byte compared to the same route rendered fully dynamically?
ATTFB drops to roughly the time it takes to serve the prebuilt static shell — that part requires no per-request server work, so it is served almost instantly, regardless of how slow the dynamic parts are
BTTFB is identical, since the full HTML must be assembled before any bytes are sent
CTTFB increases because Next.js decides static vs dynamic on every request
DPPR only affects Largest Contentful Paint, not TTFB
taintObjectReference marks a specific object instance as unsafe to pass to the client. What does it not protect against?
AAccidentally passing the entire tainted user object to a Client Component
BSomeone destructuring user.passwordHash into a new object and passing that to the client — tainting tracks the object reference, not the underlying value, so a copy is not automatically protected
CPassing user directly as a prop without destructuring
DPassing user to another Server Component
React's automatic per-render fetch memoization applies to which requests?
AAll HTTP methods equally
BOnly requests whose options object is the exact same reference
COnly GET (and HEAD) requests — deduplication is intentionally not applied to POST or other mutating methods, since collapsing a side-effecting request could silently skip an intended mutation
DOnly same-origin requests
Sign up free to play
Answer all 10 questions (7 more), see explanations for every answer, and track your score.