Questions

2 of 20

1What is static site generation (SSG) in Next.js?

2What are the benefits of Static Site Generation in Next.js?

3What is Incremental Static Regeneration (ISR)?

4What is are different revalidation strategies in Incremental Static Regeneration (ISR)?

5How do we generate static pages in a NextJS project with the app router?

6Discuss getStaticProps in brief

7Discuss briefly getStaticPaths

8What are the fallback options in getStaticPaths?

9What is generateStaticParams in the App Router?

10What types of pages are best suited for SSG?

11How does SSG differ from SSR and CSR?

12How does Next.js handle cache invalidation in ISR, and what are the pitfalls?

13What is the difference between revalidatePath and revalidateTag? When do you use each?

14How does SSG interact with middleware in Next.js?

15What are the trade-offs between full static export (output: 'export') vs standard SSG with ISR?

16How do you avoid build-time data staleness in SSG?

17What is Partial Prerendering (PPR) and how does it relate to SSG?

18How would you architect SSG for a site with 100,000+ pages?

19How does SSG work in a monorepo or multi-zone Next.js architecture?

20How would you debug a page that should be static but is being rendered dynamically?

02 / 20

What are the benefits of Static Site Generation in Next.js?

1
Lightning-Fast Load Times: Static files can be delivered quickly to users, reducing the time needed for initial page loads.
2
SEO Friendliness: Search engines can easily crawl and index static HTML content, improving SEO performance.
3
Reduced Server Load: Since HTML files are pre-generated during the build process, there's less load on the server during user requests.
4
Cost Savings: Hosting static files on CDNs is often more cost-effective than traditional server hosting.
5
Improved Security: Serving static files can reduce the risk of certain security vulnerabilities associated with server-side rendering.