codejump

Frontend Architecture (RADIO)

Preview — 3 of 10 questions

Before designing a collaborative editor's component tree, which question most affects the architecture?

AShould imports be sorted alphabetically by the formatter?
BShould local variables use camelCase or snake_case?
CMust editing continue offline, and how should concurrent changes merge?
DShould the save button have rounded or square corners?

A UI component directly embeds fetch URLs, retries, cache policies and rendering. What separation improves reuse and testability?

AMove every local interaction flag into a remote database.
BHave each component coordinate its own cache invalidation through unrelated effects.
CDuplicate the fetch logic in every component that needs it.
DMove remote-data access behind a defined client data layer.

A photo editor has a saved caption, an unsaved draft caption and an open/closed help popup. Which classification is useful?

ASaved server data, editable draft state and ephemeral UI state.
BThree global variables that every component should mutate directly.
CThree interchangeable cache entries with identical expiry policies.
DThree authoritative server records that must be fetched before every keystroke.

Sign up free to play

Answer all 10 questions (7 more), see explanations for every answer, and track your score.