Server-side session access in NextJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Next.js server component accessing session?

Consider this Next.js server component that reads a user session and renders a greeting. What will it display if the session contains { user: { name: 'Alice' } }?

NextJS

import { getServerSession } from 'next-auth/next';
import { authOptions } from '@/lib/authOptions';

export default async function Greeting() {
  const session = await getServerSession(authOptions);
  return (
    <main>
      <h1>Hello, {session?.user?.name ?? 'Guest'}!</h1>
    </main>
  );
}

A <h1>Hello, Alice!</h1>

B <h1>Hello, Guest!</h1>

C Error: getServerSession is not a function

D <h1>Hello, undefined!</h1>

💡 Hint

Check how the session object is accessed and the fallback value used.

The component uses optional chaining to safely access session.user.name. Since the session has the user name 'Alice', it renders 'Hello, Alice!'.

📝 Syntax

intermediate

Which option correctly imports and uses getServerSession in Next.js 14+?

Next.js 14+ requires correct import paths for server session access. Which option shows the correct import and usage of getServerSession?

A

import { getServerSession } from 'next-auth/client';
const session = await getServerSession(authOptions);

B

import { getServerSession } from 'next-auth/server';
const session = await getServerSession(authOptions);

C

import { getServerSession } from 'next-auth/next';
const session = await getServerSession(authOptions);

D

import getServerSession from 'next-auth';
const session = getServerSession(authOptions);

💡 Hint

Check the official Next.js 14+ documentation for the correct import path.

In Next.js 14+, getServerSession is imported from next-auth/next. Other paths are deprecated or invalid.

❓ state_output

advanced

What is the value of userEmail after this server action runs?

Given this Next.js server action that reads the session and extracts the email, what is the value of userEmail if the session is { user: { email: '[e-mail]' } }?

NextJS

import { getServerSession } from 'next-auth/next';
import { authOptions } from '@/lib/authOptions';

export async function getUserEmail() {
  const session = await getServerSession(authOptions);
  const userEmail = session?.user?.email ?? 'no-email';
  return userEmail;
}

A 'no-email'

B '[e-mail]'

C undefined

D null

💡 Hint

Look at the fallback value used when email is missing.

The session contains the user email '[e-mail]', so userEmail is set to that value, not the fallback.

🔧 Debug

advanced

What error does this Next.js server component raise?

This server component tries to access session but has a bug. What error will it raise?

NextJS

import { getServerSession } from 'next-auth/next';
import { authOptions } from '@/lib/authOptions';

export default function Profile() {
  const session = getServerSession(authOptions);
  return <p>{session?.user?.name}</p>;
}

A Error: authOptions is undefined

B No error, renders user name

C Error: JSX must be wrapped in a fragment

D Error: 'await' is required for getServerSession

💡 Hint

Check if the async function is awaited properly.

getServerSession returns a Promise, so it must be awaited in an async function. Here, the component is not async and does not await, causing a runtime error.

🧠 Conceptual

expert

Which statement about server-side session access in Next.js 14+ is TRUE?

Choose the correct statement about accessing sessions on the server in Next.js 14+ with next-auth.

A getServerSession must be called inside a server component or server action and returns a Promise resolving to the session object or null.

B getServerSession requires passing the HTTP request and response objects explicitly in Next.js 14+.

C Session data is automatically injected into all components without explicit calls to getServerSession.

D getServerSession can be called directly in client components without async/await and returns session synchronously.

💡 Hint

Recall how server components and async data fetching work in Next.js 14+.

In Next.js 14+, getServerSession is async and must be called in server components or server actions. It returns a Promise resolving to the session or null if no session exists. It does not run synchronously in client components, nor is session data injected automatically. Passing request/response is optional depending on setup.