You want to optimize performance by running a heavy calculation without triggering Angular change detection until it finishes. Which approach is best?

hard🚀 Application Q8 of 15

Angular - Change Detection

ARun the calculation inside runOutsideAngular, then update UI inside run() after completion

BRun the calculation inside run() to keep Angular aware

CRun the calculation outside Angular and never update UI

DRun the calculation inside a setTimeout without zones

Step-by-Step Solution

Solution:

Step 1: Understand performance optimization with zones
Heavy calculations outside Angular zone avoid unnecessary change detection cycles.
Step 2: Update UI after calculation
After calculation, re-enter Angular zone with run() to update UI safely.
Final Answer:
Run the calculation inside runOutsideAngular, then update UI inside run() after completion -> Option A
Quick Check:
Heavy work outside zone + UI update inside zone = Run the calculation inside runOutsideAngular, then update UI inside run() after completion [OK]

Quick Trick: Heavy work outside zone, UI update inside zone [OK]

Common Mistakes:

MISTAKES

Running heavy work inside Angular zone causing slow UI
Not updating UI after calculation
Ignoring zone boundaries

Master "Change Detection" in Angular

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Perf

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Angular Quizzes

You want to optimize performance by running a heavy calculation without triggering Angular change detection until it finishes. Which approach is best?

Step 1: Understand performance optimization with zones

Step 2: Update UI after calculation

Final Answer:

Quick Check:

Want More Practice?