Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
162 results across 1 active filter
Page 7 of 7
Keeps input and direct feedback urgent while rendering expensive navigation or result updates as interruptible work.
Chooses between blocking navigation for essential data and rendering a page-owned loading state.
Connects layouts and templates to navigation, state lifetime, Effects, and deliberate remounting in the App Router.
Chooses between synchronous UI state and asynchronous event streams without treating either model as a replacement for the other.
Distinguishes render-driving state from instance-local mutable values and DOM references.
Chooses between UI-coupled mutations and explicit HTTP contracts without treating either as a hidden trust boundary.
Distinguishes one-way data, events, and deliberate two-way component contracts without hiding ownership.
Chooses post-paint synchronization by default and reserves layout effects for pre-paint measurement or correction.
Layers optimistic routing checks with secure data-layer authorization across components, actions, and handlers.
Finds missing render notifications that forced test change detection can hide and uses production-like stability checks.
Diagnoses server fallback rules, deployment base paths, asset URLs, and cache behavior rather than changing Angular routes blindly.
Defines a coherent subscription and snapshot contract for state owned outside React, including server rendering.
Uses development-only repeated rendering, Effects, and ref callbacks to expose impurity and missing cleanup.
Connects modern template blocks and stable list identity to DOM reuse, component state, and rendering correctness.
Uses guards for navigation UX while keeping permissions and data enforcement on the trusted server.
Diagnoses in-place mutation, equality rules, missing reactive reads, and incorrect use of untracked state.
Explains how to choose an E2E flow, control test data, avoid brittleness, and cover frontend/API integration risk.
Uses browser and direct HTTP checks to verify nested route entry, reload, base paths, assets, genuine 404s, and API boundaries after deployment.