Why patterns improve architecture in NextJS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Next.js Link component correctly.

NextJS

import [1] from 'next/link';

Drag options to blanks, or click blank then click option'

Alink

BRouterLink

CLinkComponent

DLink

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase or incorrect component names in import statements.

The Next.js Link component must be imported with the exact name Link to work properly.

2fill in blank

medium

Complete the code to create a functional component that returns a main HTML element.

NextJS

export default function Home() {
  return <[1]>Welcome to Next.js!</[1]>;
}

Drag options to blanks, or click blank then click option'

Adiv

Bsection

Cmain

Dheader

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic div instead of semantic elements.

Using the main element improves accessibility by indicating the main content area.

3fill in blank

hard

Fix the error in the Next.js page component by completing the export statement correctly.

NextJS

function About() {
  return <p>About us page</p>;
}

export default [1];

Drag options to blanks, or click blank then click option'

AAbout

Babout

Cabout()

DAbout()

Attempts:

3 left

💡 Hint

Common Mistakes

Exporting lowercase or calling the function instead of exporting the function itself.

The component name About must be exported exactly as declared, without parentheses.

4fill in blank

hard

Fill both blanks to create a reusable button component with a click handler.

NextJS

export function Button({ onClick }) {
  return <button [1]=[2]>Click me</button>;
}

Drag options to blanks, or click blank then click option'

AonClick

BhandleClick

CclickHandler

DonPress

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect event attribute names or handler function names.

The button element uses the onClick attribute to handle clicks, and the handler function is passed as the onClick prop.

5fill in blank

hard

Fill all three blanks to create a Next.js page that fetches data server-side and displays it.

NextJS

import [1] from 'next';

export const getServerSideProps: [2] = async () => {
  const res = await fetch('https://api.example.com/data');
  const data = await res.json();
  return { props: { data } };
};

export default function Page({ data }) {
  return <pre>{JSON.stringify([3], null, 2)}</pre>;
}

Drag options to blanks, or click blank then click option'

A{ GetServerSideProps }

BGetServerSideProps

Cdata

Dprops

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong import names or rendering incorrect variables.

GetServerSideProps is the correct type for the server-side props function, and data is the prop passed to the component to display.

Practice

1. Why is using design patterns important in Next.js app architecture?

easy

A. They organize code for clarity and make it easier to maintain

B. They make the app run faster by default

C. They automatically fix bugs in the code

D. They reduce the need for testing

Solution

1. Step 1: Understand the role of patterns in code organization

   Patterns help structure code so it is clear and easy to follow.

2. Step 2: Recognize maintenance benefits

   Clear code is easier to update and fix, which helps teams work smoothly.

3. Final Answer:

   They organize code for clarity and make it easier to maintain -> Option A

4. Quick Check:

   Patterns improve clarity and maintenance = D [OK]

Hint: Patterns help keep code clear and easy to update [OK]

Common Mistakes:

• Thinking patterns speed up app runtime automatically
• Believing patterns fix bugs without developer effort
• Assuming patterns remove the need for testing

2. Which of the following is a correct way to organize a Next.js component using a pattern?

easy

A. Separate UI, data fetching, and styles into different files or hooks

B. Place all logic, styles, and markup in one large file without separation

C. Write all code inside getStaticProps only

D. Use inline styles only and avoid components

Solution

1. Step 1: Identify best practice for component organization

   Separating concerns (UI, data, styles) improves readability and reuse.

2. Step 2: Compare options

   Separate UI, data fetching, and styles into different files or hooks follows this pattern; others mix concerns or misuse Next.js features.

3. Final Answer:

   Separate UI, data fetching, and styles into different files or hooks -> Option A

4. Quick Check:

   Separation of concerns = A [OK]

Hint: Keep UI, data, and styles separate for clarity [OK]

Common Mistakes:

• Putting all code in one file without separation
• Misusing getStaticProps for UI logic
• Avoiding components and styles separation

3. Given this Next.js code snippet using a pattern for data fetching, what will be the rendered output?

export default function Page({ data }) {
  return <div>{data.message}</div>
}

export async function getStaticProps() {
  return { props: { data: { message: 'Hello Patterns!' } } }
}

medium

A. Empty div with no content

B. Error: data is undefined

C. <div>Hello Patterns!</div>

D. Loading spinner

Solution

1. Step 1: Understand getStaticProps role

   getStaticProps runs at build time and passes props to the component.

2. Step 2: Check component rendering

   The component receives data with message 'Hello Patterns!' and renders it inside a div.

3. Final Answer:

   <div>Hello Patterns!</div> -> Option C

4. Quick Check:

   Static props pass data correctly = C [OK]

Hint: getStaticProps passes props to component at build time [OK]

Common Mistakes:

• Assuming data is undefined without props
• Expecting loading state without client fetching
• Thinking component renders empty without data

4. Identify the error in this Next.js pattern usage:

export default function Page() {
  const data = fetch('/api/data')
  return <div>{data.message}</div>
}

medium

A. The component should not return JSX

B. data.message is not a valid property

C. API routes cannot be called from components

D. fetch is used incorrectly inside the component without async/await

Solution

1. Step 1: Check fetch usage in component

   fetch returns a promise and must be awaited or handled asynchronously.

2. Step 2: Identify missing async/await

   Without async/await, data is a promise, so data.message causes error.

3. Final Answer:

   fetch is used incorrectly inside the component without async/await -> Option D

4. Quick Check:

   Async fetch requires await = B [OK]

Hint: Always await fetch or use data fetching methods outside component [OK]

Common Mistakes:

• Calling fetch without await inside component
• Thinking API routes can't be called client-side
• Assuming data.message exists without resolving promise

5. You want to improve your Next.js app architecture by applying patterns. Which approach best combines clarity, reuse, and performance?

hard

A. Write all logic and UI in one component and fetch data on the client side only

B. Use separate components for UI, hooks for data logic, and getStaticProps for static data fetching

C. Avoid components and use only API routes to serve HTML

D. Use inline styles and fetch data inside useEffect without caching

Solution

1. Step 1: Identify best practices for architecture

   Separating UI, logic, and data fetching improves clarity and reuse.

2. Step 2: Consider performance benefits

   Using getStaticProps fetches data at build time, improving performance.

3. Final Answer:

   Use separate components for UI, hooks for data logic, and getStaticProps for static data fetching -> Option B

4. Quick Check:

   Separation + static fetching = A [OK]

Hint: Separate concerns and fetch static data for best architecture [OK]

Common Mistakes:

• Mixing UI and logic in one component
• Fetching data only on client causing slower loads
• Ignoring static generation benefits