Question 1

What are React Server Components (RSC)?

Accepted Answer

Components that render on the server and send UI payload to the client without shipping their code. They can access backend resources directly. They cannot use state/effects or browser APIs.

Question 2

Server vs Client Components — boundaries?

Accepted Answer

Add 'use client' to modules that need interactivity; server components can import client children. Keep client islands small. Pass serializable props across the boundary.

Question 3

Why can't RSCs use useState?

Accepted Answer

They don't run on the client as interactive instances; state/effects require client runtime. Push interactivity into client children. Fetch on server instead of effects.

Question 4

How do you share data from a server parent to client children?

Accepted Answer

Fetch in the server component and pass props; or use endorsed framework patterns. Avoid duplicate fetches when possible. Mind serialization limits.

Question 5

Security implication of RSCs?

Accepted Answer

Don't leak secrets into props sent to the client; server-only modules must stay server-only. Treat the client boundary as public. Validate auth on the server.

Question 6

How do RSCs interact with Suspense?

Accepted Answer

Wrap slow server fetches in Suspense to stream fallbacks then content. Enables progressive rendering. Design boundaries intentionally to avoid waterfalls.

Server Components React Interview Questions

Other React interview topics