Mutations and Optimistic Updates — Concept Check
Questions on Mutations and Optimistic Updates. A mutation changes server data and then has to make every affected view agree. Invalidation is the safe default; an optimistic update is what makes an interface feel instant.
Questions in this quiz
8 questions on Mutations and Optimistic Updates — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.After submitting a solution, which query keys should be invalidated to ensure data consistency?
- AOnly ['submissions', problemId]
- BOnly ['progress']
- C['submissions', problemId] and ['progress']
- DNo need to invalidate any query keys
2.You toggle a 'done' status in a todo app with optimistic updates. What should happen if the server update fails?
- AKeep the optimistic state and ignore the error
- BRemove the todo item entirely
- CRevert to the previous state and show an error message
- DRetry the update immediately without reverting
3.Which scenario is NOT suitable for optimistic updates?
- ALiking a post
- BReordering a list
- CMarking an email as read
- DSubmitting a payment
4.A user submits a form, but the submission fails. What is the best practice for handling the form data?
- AKeep the form data as is
- BClear the form data
- CDisable the submit button
- DShow a generic error banner
5.What is the main benefit of using optimistic updates in a UI?
- ASimplifies error handling
- BEnsures data consistency
- CReduces server load
- DProvides instant feedback to the user
6.Why is it important to cancel in-flight refetches during optimistic updates?
- ATo simplify code logic
- BTo prevent overwriting the optimistic value
- CTo reduce server load
- DTo avoid duplicate network requests
7.In the context of mutations, what does 'invalidate' mean?
- ARefresh the page immediately
- BLock the data to prevent changes
- CMark data as stale to trigger a refetch
- DDelete the data from the server
8.What should you do before a user leaves a page with unsaved changes?
- AIgnore and let them leave
- BWarn the user about unsaved work
- CAutomatically save the changes
- DClear the unsaved data