Default change detection strategy in Angular - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does Angular's default change detection strategy behave?

Consider a component using Angular's default change detection strategy. What happens when a parent component updates a property that a child component uses in its template?

A The child component does not update unless manually triggered by a method call.

B The child component automatically updates its view to reflect the new property value.

C The child component updates only if the property is an object and its reference changes.

D The child component updates only if the property is a primitive type.

💡 Hint

Think about how Angular checks for changes by default in the component tree.

Angular's default change detection strategy checks all components in the component tree whenever an event occurs or data changes. This means child components automatically update their views when parent properties change.

❓ state_output

intermediate

What is the output after updating a nested object property with default change detection?

Given a component with a nested object property used in the template, if you update a nested property without changing the object reference, what will Angular's default change detection do?

Angular

export class MyComponent {
  user = { name: 'Alice', age: 30 };

  updateAge() {
    this.user.age = 31;
  }
}

A The template updates to show the new age immediately.

B The template updates only after manually calling detectChanges().

C Angular throws an error due to direct mutation.

D The template does not update because the object reference did not change.

💡 Hint

Remember how Angular's default change detection checks all bindings on every cycle.

Angular's default change detection checks all bindings on every cycle, so even if the object reference stays the same, changes to nested properties are detected and the view updates.

📝 Syntax

advanced

Identify the correct way to set default change detection in an Angular component

Which of the following code snippets correctly sets the default change detection strategy in an Angular component?

A

@Component({ selector: 'app-test', template: '', changeDetection: ChangeDetection.Default })
export class TestComponent {}

B

@Component({ selector: 'app-test', template: '', changeDetection: 'Default' })
export class TestComponent {}

C

@Component({ selector: 'app-test', template: '', changeDetection: ChangeDetectionStrategy.Default })
export class TestComponent {}

D

@Component({ selector: 'app-test', template: '', changeDetectionStrategy: ChangeDetectionStrategy.Default })
export class TestComponent {}

💡 Hint

Check the exact property name and enum usage in Angular component metadata.

The correct property name is changeDetection and the value is the enum ChangeDetectionStrategy.Default. It must be imported from '@angular/core'.

🔧 Debug

advanced

Why does a child component not update after parent property change with default strategy?

A parent component updates a property bound to a child component's input. The child uses the default change detection strategy but its view does not update. What is the most likely cause?

A The child component's input property is not decorated with @Input().

B The child component has a syntax error preventing change detection.

C The parent property was updated asynchronously without triggering Angular's zone.

D The parent updated a nested property without changing the object reference, and the child uses OnPush strategy instead of default.

💡 Hint

Check if Angular knows the property is an input binding.

If the child input property lacks the @Input() decorator, Angular does not detect changes to it, so the view does not update even with default change detection.

🧠 Conceptual

expert

How does Angular's default change detection strategy handle event-triggered updates?

When a user clicks a button in an Angular app using the default change detection strategy, what happens behind the scenes regarding change detection?

A Angular runs change detection only for the component where the event occurred.

B Angular runs change detection only for components with OnPush strategy.

C Angular does not run change detection automatically; it must be triggered manually.

D Angular runs change detection for the entire component tree starting from the root component.

💡 Hint

Think about how Angular detects changes after user interactions.

With the default strategy, Angular runs change detection for the whole component tree starting at the root whenever an event like a click occurs, ensuring all components update as needed.

Practice

1. What does the default change detection strategy in Angular do?

easy

A. Requires manual updates to the view

B. Automatically updates the view when data changes

C. Disables change detection entirely

D. Only updates the view on user interaction

Solution

1. Step 1: Understand default change detection behavior

   The default strategy automatically checks for data changes and updates the view accordingly.

2. Step 2: Compare with other options

   Other options require manual updates or disable detection, which is not the default behavior.

3. Final Answer:

   Automatically updates the view when data changes -> Option B

4. Quick Check:

   Default strategy = automatic update [OK]

Hint: Default means automatic view update on data change [OK]

Common Mistakes:

• Thinking manual update is default
• Confusing default with OnPush strategy
• Believing change detection is disabled by default

2. Which of the following is the correct way to set the default change detection strategy in an Angular component?

easy

A. @Component({ changeDetection: ChangeDetectionStrategy.OnPush })

B. @Component({ changeDetection: 'default' })

C. @Component({ changeDetection: ChangeDetectionStrategy.Default })

D. @Component({ changeDetection: 'Default' })

Solution

1. Step 1: Recall Angular syntax for change detection

   The changeDetection property expects a value from the ChangeDetectionStrategy enum, not a string.

2. Step 2: Identify correct enum usage

   ChangeDetectionStrategy.Default is the correct enum value for default strategy.

3. Final Answer:

   @Component({ changeDetection: ChangeDetectionStrategy.Default }) -> Option C

4. Quick Check:

   Use enum, not string, for changeDetection [OK]

Hint: Use ChangeDetectionStrategy.Default enum, not string [OK]

Common Mistakes:

• Using strings instead of enum values
• Confusing 'default' with 'Default' string
• Mixing OnPush with default strategy

3. Consider this Angular component using the default change detection strategy:

@Component({
  selector: 'app-counter',
  template: `Count: {{count}}`
})
export class CounterComponent {
  count = 0;
  increment() {
    this.count++;
  }
}

What will happen when the button is clicked?

medium

A. An error will occur because change detection is disabled

B. The displayed count will not change until manually refreshed

C. The count will increase but the view will not update

D. The displayed count will increase by 1 automatically

Solution

1. Step 1: Understand default change detection behavior on event

   Default strategy runs change detection automatically after events like button clicks.

2. Step 2: Predict view update

   When increment() updates count, the view updates automatically to show the new count.

3. Final Answer:

   The displayed count will increase by 1 automatically -> Option D

4. Quick Check:

   Default strategy updates view on event [OK]

Hint: Default strategy updates view after events automatically [OK]

Common Mistakes:

• Thinking manual refresh is needed
• Assuming change detection is off
• Believing count changes but view stays same

4. You have this Angular component:

@Component({
  selector: 'app-sample',
  template: `{{value}}`
})
export class SampleComponent {
  value = 10;

  updateValue() {
    this.value = 20;
  }
}

After calling updateValue(), the view does not update. What is the most likely cause?

medium

A. The updateValue method is not called inside Angular zone

B. The default change detection strategy is disabled by mistake

C. The component uses OnPush strategy but input did not change

D. The value property is private and not accessible in template

Solution

1. Step 1: Check default strategy behavior

   Default strategy updates view automatically unless changes happen outside Angular zone.

2. Step 2: Identify cause of no update

   If updateValue() runs outside Angular zone, change detection won't trigger, so view stays old.

3. Final Answer:

   The updateValue method is not called inside Angular zone -> Option A

4. Quick Check:

   Outside Angular zone blocks default detection [OK]

Hint: Changes outside Angular zone don't trigger default detection [OK]

Common Mistakes:

• Assuming default strategy is disabled
• Confusing OnPush input change with default strategy
• Thinking private properties cause no update

5. In a large Angular app, you want to optimize performance by reducing unnecessary view updates. You decide to keep the default change detection strategy but want to limit checks on a specific component. Which approach fits best?

hard

A. Use ChangeDetectorRef.detach() to stop change detection on that component manually

B. Set changeDetection: ChangeDetectionStrategy.Default on that component

C. Use markForCheck() to force detection every time

D. Replace default strategy with OnPush on all components

Solution

1. Step 1: Understand default strategy limits

   Default strategy runs change detection frequently, which can be costly in large apps.

2. Step 2: Identify how to limit detection on one component

   Using ChangeDetectorRef.detach() stops change detection on that component until manually reattached.

3. Step 3: Evaluate other options

   Setting default again does nothing new; markForCheck forces detection; OnPush changes strategy globally, not selectively.

4. Final Answer:

   Use ChangeDetectorRef.detach() to stop change detection on that component manually -> Option A

5. Quick Check:

   Detach stops detection selectively [OK]

Hint: Detach change detector to pause updates on specific component [OK]

Common Mistakes:

• Thinking setting default again limits detection
• Confusing markForCheck with stopping detection
• Assuming OnPush is selective per component