Sample questions
Mobile NavigationDifficulty 1
In stack-based navigation, what is a navigation stack?
- aA list of every screen ever loaded into memory, whether or not the user actually visited it
- bAn ordered collection of screens where entering a new one pushes it on top and going back pops it off✓
- cA fixed set of top-level destinations the user switches between with a single tap, none stacked on another
- dA single screen that redraws its own content depending on which button the user last pressed
Explanation:A navigation stack models screens as a last-in, first-out sequence: opening a new screen pushes it on top, and back navigation pops the top screen to reveal the one beneath. (a) describes something closer to a cache; (c) describes tab navigation, not a stack; (d) describes a single mutable view, not a stack of destinations.
Mobile NavigationDifficulty 1
What distinguishes tab-based navigation from stack-based push navigation?
- aOnly one destination can ever exist, so opening a tab replaces the previous one permanently
- bEvery destination is reached by first popping the current screen off a shared stack
- cSeveral top-level destinations sit side by side, reached directly, each keeping state✓
- dThere is no concept of going back, only moving forward to the next tab in a fixed order
Explanation:Tabs represent parallel top-level sections of an app; switching tabs jumps directly to another section rather than popping through history, and each tab typically preserves its own state while inactive. (a) and (d) misdescribe tabs as a single destination or a strict forward sequence; (b) describes stack navigation, not tabs.
Mobile NavigationDifficulty 2
In nested navigation where a tab hosts its own internal stack, what typically happens when the user pushes a screen inside one tab?
- aThat tab's own stack grows; the stacks belonging to the other tabs are unaffected✓
- bAll tabs share a single stack, so the screen is pushed visibly onto every tab at once
- cNesting means a stack can only ever contain other stacks, never an individual screen
- dNesting is purely a visual style choice with no effect on what is remembered when switching tabs
Explanation:Each tab commonly owns an independent navigation stack nested inside the top-level tab container, so pushing inside one tab only changes that tab's own history. (b) describes a shared-stack design, which is a different architecture; (c) and (d) misstate what nesting means structurally.
Mobile NavigationDifficulty 2
A user is three screens deep on a stack and presses the back button/gesture. What is the expected default behavior?
- aIt always returns the user to the app's home tab, skipping the intermediate screens
- bIt pops the current screen and reveals whatever screen was directly beneath it✓
- cIt closes the app immediately, regardless of how many screens are currently open
- dIt reloads the current screen with fresh data instead of navigating anywhere
Explanation:The standard contract for back is a single pop: remove the top of the stack and show what's now on top, one step at a time. (a) and (c) both skip or ignore the actual stack depth; (d) confuses a refresh action with a navigation action.
Mobile NavigationDifficulty 2
How does a swipe-back gesture relate to the back control's pop behavior?
- aIt permanently deletes the screen being left so it cannot be revisited later in the session
- bIt behaves like opening a brand-new destination rather than reversing the last navigation step
- cIt is only available on the very first screen of the stack and nowhere else
- dIt performs the same pop operation as the back control, typically with a partial, cancellable transition✓
Explanation:A swipe-back gesture is an alternate input for the same pop operation the back control triggers, usually rendered as a draggable transition the user can release partway to cancel and stay on the current screen. (a), (b), and (c) all describe behavior unrelated to how the gesture actually maps to navigation.
Mobile NavigationDifficulty 1
What is a deep link, at a conceptual level?
- aA link that always opens the app's home screen no matter what URL was tapped
- bA shortcut icon placed on the device's home screen that launches the app
- cA URL or identifier meant to take the user to a specific screen inside the app✓
- dA background network request the app makes periodically to refresh its data
Explanation:A deep link's purpose is to encode a target destination inside the app so opening it lands the user on that specific screen rather than a generic entry point. (a) contradicts the whole point of a deep link; (b) and (d) describe unrelated concepts (a launcher shortcut, a background sync call).