TOPIC
Frameworks
These are the same questions found in the library, grouped here by the capability each one mainly examines.
15 questions
A · Professional problem solving and implementation15
- A sign-up form ends up in inconsistent states because of duplicate submissions and weak-network retries. How would you map its states and transitions, and decide which logic to extract into its own unit?
- A user backgrounds the app while editing, and the operating system may kill its process. On return, which state should be restored and which should be reloaded, and how would you avoid losing a draft or overwriting newer data?
- The framework allows concurrent background UI updates, but a slow response occasionally overwrites a newer selection. How would you design concurrent state updates?
- A complex form has field validation, cross-field rules, and server errors that overwrite one another during edits. How would you divide framework state from business state?
- Several pages share server data and framework caching reduces requests, but stale results appear after users switch accounts. How would you design cache keys and invalidation boundaries?
- After a frontend framework upgrade, compilation succeeds, but render timing, default caching, or side-effect order changes. How would you verify product behavior remains correct?
- A third-party SDK callback updates data, but the UI does not refresh; forcing a refresh causes duplicate updates. How would you identify the framework’s change-detection boundary and choose the right integration point?
- After a service is registered as a singleton, different user requests occasionally see one another’s temporary state. How would you explain dependency-injection lifetimes and design a safe object boundary?
- After adding authentication, logging, and error-handling middleware, some failures lack trace IDs and unauthorized requests still trigger expensive parsing. How would you analyze pipeline order and boundaries?
- After a list item changes from record A to record B, its input still contains A’s draft. How would you explain component identity, keys, and state reuse, and choose where to fix it?
- A page has valid server-rendered HTML, but content flickers after hydration and the console reports a warning. How would you locate the difference between server and client rendering?
- Several callers read a configuration file whose fields keep growing; older fields may be absent, and new versions must allow unknown extension fields. How would you design a parsing interface so callers can understand defaults, validation errors, and backward-compatibility behavior?
- A shared library releases a backward-compatible version, but application repositories cannot upgrade promptly because of pinned dependencies, generated code, or different release windows; a security fix remains blocked. How would you design compatibility policy and the dependency-upgrade process?
- An API adds a new state, but older clients may not recognize it; some must still display the record, while critical operations must reject unknown states. How would you design parsing and defaults so an unknown value is not mistaken for a valid state?
- A model begins returning structured JSON, while mobile, server, and analytics consumers upgrade at different rates; new fields may be absent or enum values may change. How would you define the output contract, handle validation failures, and preserve compatibility?
No questions in this section match your target. ·