Why lifecycle hooks matter in Angular - Challenge Your Understanding

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a component uses the ngOnInit lifecycle hook?

Consider an Angular component that implements the ngOnInit lifecycle hook. What is the main purpose of this hook?

Angular

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

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

  ngOnInit() {
    this.message = 'Component initialized';
  }
}

A It runs just before the component is destroyed to clean up resources.

B It runs every time the component's input properties change.

C It runs after the component's view and child views have been checked.

D It runs once after the component's data-bound properties are initialized, perfect for setup tasks.

💡 Hint

Think about when you want to prepare data or start processes after the component is ready.

The ngOnInit hook runs once after Angular sets up the component's input properties. It's the right place to perform initialization like fetching data or setting initial values.

❓ lifecycle

intermediate

Which lifecycle hook is best for cleaning up subscriptions?

In Angular, when should you clean up subscriptions or detach event handlers to avoid memory leaks?

A ngOnDestroy

B ngAfterViewInit

C ngOnChanges

D ngDoCheck

💡 Hint

Think about when the component is about to be removed from the page.

The ngOnDestroy hook is called just before Angular destroys the component. It's the right place to clean up subscriptions and resources to prevent memory leaks.

📝 Syntax

advanced

What error occurs if you forget to implement OnInit but define ngOnInit?

Given this Angular component code, what happens if the class defines ngOnInit() but does not implement the OnInit interface?

Angular

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

@Component({
  selector: 'app-test',
  template: `<p>Test</p>`
})
export class TestComponent {
  ngOnInit() {
    console.log('Init');
  }
}

A Compile-time error because ngOnInit must be declared only if OnInit is implemented.

B No error; ngOnInit runs normally because implementing OnInit interface is optional.

C Runtime error because Angular cannot find the lifecycle hook without the interface.

D The component will not render because lifecycle hooks are ignored without the interface.

💡 Hint

Interfaces in TypeScript are for type checking, not runtime behavior.

Implementing the OnInit interface is optional. Angular calls ngOnInit if it exists on the component class regardless of interface implementation.

🔧 Debug

advanced

Why does ngAfterViewInit run after ngOnInit?

Look at this Angular component lifecycle sequence. Why does ngAfterViewInit run after ngOnInit?

Angular

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

@Component({
  selector: 'app-demo',
  template: `<child-comp></child-comp>`
})
export class DemoComponent implements OnInit, AfterViewInit {
  ngOnInit() {
    console.log('OnInit');
  }
  ngAfterViewInit() {
    console.log('AfterViewInit');
  }
}

A ngAfterViewInit runs first but logs appear later due to asynchronous behavior.

B ngOnInit and ngAfterViewInit run simultaneously but logs are buffered.

C ngAfterViewInit waits until the component's view and child views are fully initialized, which happens after ngOnInit.

D ngAfterViewInit runs only if ngOnInit throws an error.

💡 Hint

Think about when the component's template and child components are ready.

The ngAfterViewInit hook runs after Angular fully initializes the component's view and its child views. This always happens after ngOnInit, which runs earlier during initialization.

🧠 Conceptual

expert

Why are lifecycle hooks critical for resource management in Angular?

Why do Angular lifecycle hooks like ngOnInit and ngOnDestroy matter for managing resources and app performance?

A They allow developers to initialize data and clean up resources at precise moments, preventing memory leaks and ensuring smooth user experience.

B They automatically optimize Angular's change detection without developer intervention.

C They enable Angular to skip rendering components that are not visible on the screen.

D They replace the need for services by handling all data fetching and storage inside components.

💡 Hint

Think about when you start and stop things in real life to keep things tidy and efficient.

Lifecycle hooks let developers run code at key moments: ngOnInit to set up data or start processes, and ngOnDestroy to clean up subscriptions or timers. This careful management avoids memory leaks and keeps the app fast and stable.