Multi-Step Forms and Wizards — Concept Check
Questions on Multi-Step Forms and Wizards. One state object, per-step validation, and a step in the URL. The hard parts are surviving a refresh and letting the user go backwards without losing anything.
Questions in this quiz
8 questions on Multi-Step Forms and Wizards — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.During a multi-step form process, a user refreshes the page. What ensures they don't lose their place?
- ASession storage
- BComponent state management
- CCookies
- DStep index stored in URL
2.A user completes the 'account' step but skips 'profile' by manipulating the URL. What happens during final validation?
- AThe skipped step is validated then
- BAll steps are re-validated
- CFinal validation is skipped
- DOnly the last step is validated
3.Why might a user be unable to proceed to the next step in a multi-step form?
- ALocal storage error
- BComponent state reset
- CIncomplete current step validation
- DIncorrect URL manipulation
4.What is a potential risk of storing passwords in localStorage during a multi-step form process?
- AImproved performance
- BPasswords are not stored
- CData persists beyond session
- DPasswords are encrypted
5.A user navigates back to a previous step. What ensures their previously entered data is retained?
- AStoring data in session storage
- BPassing 'values' as defaultValues
- CRe-entering data manually
- DUsing cookies
6.What happens if a user tries to jump forward to an incomplete step in a multi-step form?
- AError message shown
- BForm resets
- CStep is skipped
- DButton is disabled
7.How does autosaving drafts help in a multi-step form process?
- AReduces server load
- BPrevents data loss on refresh
- CEnsures data encryption
- DImproves form loading speed
8.A user believes that storing all form data in component state is sufficient. What might they overlook?
- ABack button functionality
- BForm submission
- CData validation
- DUser authentication