SSR vs CSR mental model in Angular - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Server-Side Rendering (SSR) vs Client-Side Rendering (CSR)

Which statement best describes the main difference between SSR and CSR in Angular applications?

A SSR renders the initial HTML on the server before sending it to the browser, while CSR renders the HTML entirely in the browser after loading JavaScript.

B CSR renders the initial HTML on the server, and SSR renders HTML only after user interaction in the browser.

C SSR requires no JavaScript on the client, while CSR requires JavaScript only on the server.

D CSR sends fully rendered HTML from the server, and SSR sends only JSON data to the client.

💡 Hint

Think about where the first HTML content is created: server or browser.

SSR means the server creates the HTML before sending it to the browser, so users see content faster. CSR means the browser builds the HTML after downloading JavaScript.

❓ component_behavior

intermediate

Behavior of Angular Components in SSR vs CSR

In an Angular app using SSR, what happens to component lifecycle hooks like ngOnInit during server rendering?

A ngOnInit does not run during SSR; it only runs in the browser after hydration.

B ngOnInit runs twice: once on the server and once again on the client after hydration.

C ngOnInit runs on the server during SSR, so data can be fetched before sending HTML to the client.

D ngOnInit is replaced by a special SSR lifecycle hook that runs only on the server.

💡 Hint

Consider when Angular runs component code during server rendering.

During SSR, Angular runs component lifecycle hooks like ngOnInit on the server to prepare data before sending HTML. This helps show ready content immediately.

❓ state_output

advanced

State Transfer Between SSR and CSR in Angular

Consider an Angular app using SSR with state transfer. After server rendering, what happens to the application state when the client bootstraps?

A The client re-fetches all data ignoring the server state, causing duplicate requests.

B The client merges server state with local storage data, which can cause conflicts.

C The client clears all server state and starts fresh with empty data.

D The client uses the transferred state from the server to avoid re-fetching data, speeding up hydration.

💡 Hint

Think about how SSR can improve client startup performance.

Angular's state transfer mechanism passes data fetched during SSR to the client, so the client can reuse it and avoid extra network calls.

📝 Syntax

advanced

Identifying SSR-Compatible Angular Code

Which Angular code snippet is NOT compatible with SSR and will cause errors during server rendering?

Angular

import { Component, OnInit } from '@angular/core';

@Component({
  selector: 'app-example',
  template: `<p>{{message}}</p>`
})
export class ExampleComponent implements OnInit {
  message = '';

  ngOnInit() {
    this.message = window.navigator.userAgent;
  }
}

A The code uses window.navigator in ngOnInit, which is undefined on the server and causes errors.

B The code uses a template string with interpolation, which is fully supported in SSR.

C The component uses OnInit lifecycle hook, which runs on the server during SSR.

D The component defines a class property and updates it in ngOnInit, which is valid in SSR.

💡 Hint

Remember that some browser APIs do not exist on the server.

Accessing window or browser-only objects during SSR causes errors because the server environment lacks these APIs.

🔧 Debug

expert

Debugging Hydration Mismatch in Angular SSR

An Angular SSR app shows a hydration mismatch warning in the browser console after loading. Which cause is most likely responsible?

A The server failed to send any HTML, so the client renders everything from scratch.

B The server rendered HTML and client app have different initial states causing DOM differences during hydration.

C The client app is missing JavaScript files, so hydration cannot run.

D The server rendered HTML uses deprecated Angular syntax not supported by the client.

💡 Hint

Hydration mismatch means the browser sees different HTML than expected from the client app.

Hydration mismatch happens when the HTML generated on the server does not match what the client app expects, often due to differing initial data or state.

Practice

1. What is the main difference between Server-Side Rendering (SSR) and Client-Side Rendering (CSR) in Angular?

easy

A. SSR builds the page on the server and sends full HTML to the browser, while CSR builds the page in the browser using JavaScript.

B. SSR uses JavaScript in the browser to build pages, while CSR builds pages on the server.

C. SSR and CSR both build pages only on the client side.

D. SSR sends only JavaScript files to the browser, CSR sends full HTML.

Solution

1. Step 1: Understand SSR behavior

   SSR builds the full HTML page on the server and sends it to the browser ready to display.

2. Step 2: Understand CSR behavior

   CSR sends minimal HTML and JavaScript to the browser, which then builds the page dynamically.

3. Final Answer:

   SSR builds the page on the server and sends full HTML to the browser, while CSR builds the page in the browser using JavaScript. -> Option A

4. Quick Check:

   SSR = server builds HTML, CSR = browser builds HTML [OK]

Hint: SSR sends full HTML, CSR builds page in browser [OK]

Common Mistakes:

• Confusing which side builds the page
• Thinking SSR uses browser JavaScript first
• Believing CSR sends full HTML from server

2. Which Angular feature is primarily used to enable Server-Side Rendering (SSR)?

easy

A. Angular Universal

B. Angular CLI

C. Angular Material

D. Angular Forms

Solution

1. Step 1: Identify Angular SSR tool

   Angular Universal is the official Angular tool to enable SSR by rendering pages on the server.

2. Step 2: Recognize other options

   Angular CLI helps with project setup, Angular Material is UI components, Angular Forms handles forms, none enable SSR.

3. Final Answer:

   Angular Universal -> Option A

4. Quick Check:

   SSR tool = Angular Universal [OK]

Hint: Angular Universal enables SSR in Angular [OK]

Common Mistakes:

• Choosing Angular CLI as SSR tool
• Confusing Angular Material with SSR
• Thinking Angular Forms enables SSR

3. Consider an Angular app using SSR. What will the browser receive on the first page load?

medium

A. A blank page and JavaScript files to build content

B. Fully rendered HTML content from the server

C. Only CSS files, no HTML or JavaScript

D. JavaScript code that builds the page after user interaction

Solution

1. Step 1: Recall SSR behavior on first load

   SSR sends fully rendered HTML from the server so the browser can display content immediately.

2. Step 2: Compare other options

   Options A and D describe CSR behavior; Only CSS files, no HTML or JavaScript is incorrect as CSS alone cannot render content.

3. Final Answer:

   Fully rendered HTML content from the server -> Option B

4. Quick Check:

   SSR first load = full HTML sent [OK]

Hint: SSR sends full HTML on first load, not blank page [OK]

Common Mistakes:

• Thinking SSR sends blank page first
• Confusing CSS files with page content
• Believing JavaScript builds page immediately in SSR

4. You notice your Angular app using SSR is not showing updated data after navigation. What is a likely cause?

medium

A. Angular Universal is not installed

B. The server is sending blank HTML pages

C. The browser does not support JavaScript

D. The app is not hydrating the server-rendered HTML properly on the client

Solution

1. Step 1: Understand hydration in SSR

   Hydration is the process where client JavaScript takes over server-rendered HTML to make it interactive and update data.

2. Step 2: Identify cause of stale data

   If hydration fails, the page looks static and does not update after navigation, causing stale data display.

3. Final Answer:

   The app is not hydrating the server-rendered HTML properly on the client -> Option D

4. Quick Check:

   Hydration failure causes stale data in SSR [OK]

Hint: Hydration failure causes stale SSR pages [OK]

Common Mistakes:

• Assuming server sends blank pages
• Blaming browser JavaScript support without checking hydration
• Thinking Angular Universal missing causes this specific issue

5. You want your Angular app to load fast for SEO but also have rich interactivity after load. Which approach best fits this need?

hard

A. Use static HTML files without Angular

B. Use only Client-Side Rendering (CSR) for all pages

C. Use Server-Side Rendering (SSR) for initial load and hydrate with CSR for interactivity

D. Load pages with SSR but disable JavaScript on client

Solution

1. Step 1: Identify SEO and fast load needs

   SSR provides fast initial load and full HTML for SEO benefits.

2. Step 2: Add interactivity after load

   Hydrating SSR pages with CSR JavaScript enables rich interactivity after the fast initial load.

3. Step 3: Evaluate other options

   CSR alone delays first meaningful paint; static HTML lacks interactivity; disabling JavaScript breaks interactivity.

4. Final Answer:

   Use Server-Side Rendering (SSR) for initial load and hydrate with CSR for interactivity -> Option C

5. Quick Check:

   SSR + hydration = fast SEO + interactivity [OK]

Hint: SSR first, then hydrate with CSR for best SEO and interactivity [OK]

Common Mistakes:

• Choosing only CSR and ignoring SEO
• Using static HTML losing interactivity
• Disabling JavaScript breaks app functionality