Why services are needed in Angular - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use services in Angular?

In Angular, why do we use services instead of putting all logic inside components?

A Services are only used to style components with CSS.

B Services help share data and logic between components, avoiding code duplication.

C Services replace components and handle the user interface directly.

D Services are used to write HTML templates inside TypeScript files.

💡 Hint

Think about how multiple friends might need to use the same recipe without rewriting it.

Services in Angular allow you to keep logic and data separate from the user interface. This way, multiple components can use the same service to share data or functions, making the code cleaner and easier to maintain.

❓ component_behavior

intermediate

Service data sharing behavior

If two Angular components inject the same service instance, what happens when one component changes a value in the service?

A The change is visible to the other component because they share the same service instance.

B The change is not visible because each component gets a new service instance.

C The service resets automatically after each component uses it.

D The service throws an error when multiple components try to use it.

💡 Hint

Imagine two friends sharing the same notebook; if one writes something, the other sees it too.

Angular services are typically singletons within an injector scope. This means components that inject the same service share one instance, so changes in one component affect the others.

📝 Syntax

advanced

Correct service injection syntax

Which option shows the correct way to inject a service named DataService into an Angular component's constructor?

Angular

import { Component } from '@angular/core';
import { DataService } from './data.service';

@Component({
  selector: 'app-example',
  template: '<p>Example works!</p>',
  standalone: true
})
export class ExampleComponent {
  constructor( /* What goes here? */ ) {}
}

A dataService: DataService = new DataService()

B public DataService dataService

C inject(DataService) dataService

D private dataService: DataService

💡 Hint

Remember how Angular uses constructor parameters with access modifiers for injection.

Angular injects services by declaring them as constructor parameters with an access modifier like private or public. This tells Angular to provide the service instance automatically.

🔧 Debug

advanced

Why is the service data not shared?

Two components inject the same service, but changes in one component are not seen in the other. What is the most likely cause?

A The service is provided in the component decorator, creating separate instances.

B The service class is missing the @Injectable() decorator.

C The components are not declared in the same module.

D The service is imported but never injected in the constructor.

💡 Hint

Check where the service is provided; providing it in components creates new instances.

If a service is provided in a component's providers array, Angular creates a new instance for that component only. To share data, the service should be provided at a higher level like root.

❓ lifecycle

expert

Service lifecycle and state retention

Consider an Angular service provided in root. If a component using this service is destroyed and recreated, what happens to the service's stored data?

A The service data is saved to local storage automatically.

B The service instance is destroyed with the component, so data resets.

C The service instance persists, so stored data remains intact across component recreation.

D Angular creates a new service instance each time the component is created.

💡 Hint

Think about a library book that stays on the shelf even if a reader leaves and returns.

Services provided in root are singletons that live as long as the app runs. Destroying a component does not destroy the service, so its data stays available.