Questions
6 of 33
1Explain server-side rendering (SSR) in Next.js.
2List the benefits of Server-Side Rendering in Next.js.
3What are server components?
4How to use server components in next js?
5What is the React Server Component Payload (RSC)?
6Describe how server components are rendered.
7Describe server rendering strategies
8How can you keep Server-only Code out of the Client Environment
9What are the issues of using context provider at the root of the application?
10List dynamic functions available to server components.
11List all Dynamic APIs.
12How do we opt for Static Rendering, Dynamic Rendering and Streaming?
13Explain the difference between SSR, SSG, ISR, and CSR in Next.js. When would you choose each?
14How does getServerSideProps work internally? What is its execution context?
15What are the performance trade-offs of SSR vs SSG in a high-traffic production app?
16How does Next.js handle hydration? What is a hydration mismatch, and how do you debug it?
17What happens when getServerSideProps throws an error? How do you handle it gracefully?
18How would you architect a Next.js app that needs both personalised (SSR) and cacheable (SSG) pages at scale?
19Explain the App Router vs Pages Router SSR model differences. How does React Server Components change the SSR paradigm?
20How do React Server Components (RSC) differ from traditional SSR? Can they be used together?
21How does streaming SSR work in Next.js 13+? What role does Suspense play?
22How would you implement partial hydration or Islands Architecture in Next.js?
23Explain how Next.js handles data fetching waterfall problems in SSR and how you'd mitigate them.
24How would you implement partial hydration or Islands Architecture in Next.js?
25How do you implement caching strategies for SSR responses in Next.js? (CDN, Cache-Control, stale-while-revalidate)
26How would you reduce TTFB (Time to First Byte) in an SSR-heavy Next.js app?
27What's the difference between fetch caching in the App Router vs traditional getServerSideProps?
28How do you avoid redundant database/API calls across multiple server components on the same page?
29How do you securely handle authentication in SSR? What are the risks of passing tokens via cookies vs headers?
30How do you prevent sensitive server-side data from leaking to the client bundle?
31How would you implement role-based rendering on the server without exposing protected routes to the client?
32How do you debug SSR-only issues that don't appear in local development?
33How can we control dynamic rendering behaviour in next js?
06 / 33

Describe how server components are rendered.

Difficulty: 5/10
rendering pipeline, streaming, client vs server components
On the server, Next.js uses React's APIs to orchestrate rendering. The rendering work is split into chunks:
  1. 1

    by individual route segments

  2. 2

    and Suspense Boundaries.

Each chunk is rendered in two steps:
  1. 1

    React renders Server Components into a special data format called the React Server Component Payload (RSC Payload).

  2. 2

    Next.js uses the RSC Payload and Client Component JavaScript instructions to render HTML on the server.

Then, on the client:
  1. 1

    The HTML is used to show a fast non-interactive preview of the route immediately - this is for the initial page load only.

  2. 2

    The React Server Components Payload reconciles the Client and Server Component trees and updates the DOM.

  3. 3

    The JavaScript instructions hydrate Client Components and make the application interactive.

Scenario Questions

0-2 years experience

  1. 1If you need to fetch data for a page that doesn't require any client-side interactivity, how would you use a server component in Next.js to render it, and what steps does Next.js take to render that component?
  2. 2What happens when you import a React component that is marked as a server component inside a client component? How does Next.js handle the rendering?

2-5 years experience

  1. 1We have a product detail page that mixes server‑only data fetching with a client‑side carousel. Walk me through how you would structure the components and what you’d expect Next.js to do during rendering.
  2. 2During a recent release, a server component started throwing a 'ReferenceError: window is not defined'. How would you debug this, and what does it tell you about the rendering lifecycle?

5-8 years experience

  1. 1Our team is considering moving a large portion of the UI to server components to improve TTFB, but we have concerns about streaming and caching. How would you evaluate the trade‑offs and design a rendering strategy?
  2. 2Explain how Next.js streams server component HTML to the client and how you would handle a scenario where a downstream API is slow, ensuring the page remains responsive.

8+ years experience

  1. 1We have a monorepo with multiple Next.js apps, some still using traditional pages and others using the new app directory with server components. How would you plan a migration strategy that minimizes disruption and aligns with long‑term maintainability?
  2. 2Discuss the architectural implications of using server components for shared UI libraries across teams, especially regarding versioning, bundle size, and deployment pipelines.

Follow-up Questions

  • Can you elaborate on how streaming interacts with Suspense boundaries?
  • What impact does this rendering model have on SEO and initial load performance?
  • How would you handle errors that occur during server component rendering?
Share

Share via WhatsApp, X, Facebook, LinkedIn or copy link. Open Graph preview enabled.