F Fox Root • 490 Points Goal Maker Q. Why might a team migrate from BehaviorSubject to NgRx? (A) For styling (B) For better architecture and maintainability (C) For routing (D) For faster compilation
F Fox Root • 490 Points Goal Maker Q. Which solution provides better scalability? (A) BehaviorSubject (B) NgRx Store (C) Local component state (D) Template variables
F Fox Root • 490 Points Goal Maker Q. Which solution is easier to learn for beginners? (A) NgRx (B) BehaviorSubject service (C) Both equally complex (D) Redux DevTools
F Fox Root • 490 Points Goal Maker Q. BehaviorSubject emits value to new subscriber: (A) Never (B) Only once (C) Immediately last value (D) After HTTP call
F Fox Root • 490 Points Goal Maker Q. In NgRx, components should: (A) Modify state directly (B) Dispatch actions only (C) Call reducers (D) Write to store variable
F Fox Root • 490 Points Goal Maker Q. Which approach has more boilerplate code? (A) BehaviorSubject (B) NgRx Store (C) Both equal (D) Neither
F Fox Root • 490 Points Goal Maker Q. What is a major drawback of BehaviorSubject-based state management? (A) Cannot share data (B) No centralized predictable flow (C) Does not support Observables (D) Cannot be injected
F Fox Root • 490 Points Goal Maker Q. Which approach enforces immutability? (A) BehaviorSubject automatically (B) NgRx Store (C) Angular services (D) Components
F Fox Root • 490 Points Goal Maker Q. Which provides better debugging and time-travel debugging? (A) BehaviorSubject (B) NgRx Store (C) Both same (D) Angular Router
F Fox Root • 490 Points Goal Maker Q. In BehaviorSubject service, state update usually happens via: Code: this.userSubject.next(user); (A) dispatch() (B) setState() (C) next() (D) emit()