[Solved] Why is it important to implement ngOnDestroy even if Angular destroys the component automatically? — Ans: Because Angular does not automatically clean up subscriptions or timers | Angular

Angular - Lifecycle Hooks

Why is it important to implement ngOnDestroy even if Angular destroys the component automatically?

ABecause ngOnDestroy is required to render the component

BBecause ngOnDestroy improves component initialization speed

CBecause Angular does not automatically clean up subscriptions or timers

DBecause Angular uses ngOnDestroy to reload data

Step-by-Step Solution

Solution:

Step 1: Understand Angular component destruction
Angular removes the component from the DOM automatically but does not clean up resources like subscriptions or timers.
Step 2: Recognize ngOnDestroy role
ngOnDestroy is the place to manually clean these resources to prevent memory leaks.
Final Answer:
Because Angular does not automatically clean up subscriptions or timers -> Option C
Quick Check:
Angular auto-destroys but manual cleanup needed [OK]

Quick Trick: Angular destroys component but you clean resources in ngOnDestroy [OK]

Common Mistakes:

Master "Lifecycle Hooks" in Angular

9 interactive learning modes - each teaches the same concept differently

More Angular Quizzes

Why is it important to implement ngOnDestroy even if Angular destroys the component automatically?