Why file-based routing simplifies navigation in NextJS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does Next.js file-based routing map URLs?

In Next.js, how does the file structure inside the app directory relate to the URLs users visit?

A Files inside <code>app</code> need manual URL mapping in a config file to create routes.

B Each file or folder inside <code>app</code> automatically becomes a URL path segment matching its name.

C Only files named <code>index.js</code> inside <code>app</code> are accessible as URLs.

D Next.js ignores the <code>app</code> folder for routing and uses a separate <code>routes.js</code> file.

💡 Hint

Think about how folder names become parts of the website address.

Next.js uses the file and folder names inside the app directory to create URL paths automatically. This means if you have a folder named about, it becomes the /about URL.

❓ component_behavior

intermediate

What happens when you add a new folder in Next.js app?

If you add a new folder named blog inside the app directory with a page file inside, what URL will Next.js serve for that page?

A The page will be served at the root URL <code>/</code> ignoring the folder.

B You must update a routing config to make <code>/blog</code> work.

C Next.js will throw an error because nested folders are not allowed.

D The page will be served at <code>/blog</code> automatically.

💡 Hint

Remember how folder names become URL parts.

Next.js automatically creates routes based on folder names. Adding a blog folder creates the /blog URL path.

📝 Syntax

advanced

Identify the correct file structure for nested routes

Which folder and file structure correctly creates the nested URL /products/shoes in Next.js?

A <code>app/products/shoes/page.js</code>

B <code>app/products/shoes.js</code>

C <code>app/products-shoes/page.js</code>

D <code>app/products_shoes/page.js</code>

💡 Hint

Folders create URL segments, files named page.js define pages.

To create nested routes, you use folders for each segment. The file page.js inside app/products/shoes creates the /products/shoes URL.

🔧 Debug

advanced

Why does this Next.js route not work as expected?

Given this folder structure:
app/blog/page.js
and inside page.js you export a React component.
Why might navigating to /blog show a 404 error?

A Next.js requires a <code>route.js</code> file inside <code>blog</code> for routing.

B The folder <code>blog</code> must be named <code>blogs</code> to work.

C The <code>page.js</code> file is missing the default export of a React component.

D The <code>app</code> folder must be renamed to <code>pages</code> for routing.

💡 Hint

Check the component export inside the page file.

Next.js requires that page.js files export a React component as the default export. Without it, the route won't render and may show 404.

❓ state_output

expert

What is the rendered output of this Next.js page component?

Consider this Next.js page component inside app/home/page.js:

export default function HomePage() {
  return (
    <main>
      <h1>Welcome</h1>
      <p>You are at /home</p>
    </main>
  )
}

What will a user see when visiting /home?

A A page with a heading 'Welcome' and a paragraph 'You are at /home'.

B A blank page because the component is missing a return statement.

C An error because JSX tags are not allowed in Next.js page components.

D A page showing only the text '/home' without any heading.

💡 Hint

Look at the JSX returned by the component.

The component returns JSX with a main section containing a heading and paragraph. This renders exactly as described in option A.