Why global state avoids prop drilling in React Native - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to access the global state using React Context.

React Native

const value = useContext([1]);

Drag options to blanks, or click blank then click option'

AMyContext

BuseState

Cprops

DsetState

Attempts:

3 left

💡 Hint

Common Mistakes

Using useState instead of the context object.

Trying to access props directly for global state.

We use useContext with the context object (e.g., MyContext) to access global state.

2fill in blank

medium

Complete the code to provide global state to child components.

React Native

<MyContext.Provider value=[1]>
  {children}
</MyContext.Provider>

Drag options to blanks, or click blank then click option'

AuseEffect

Bprops

CsetState

Dstate

Attempts:

3 left

💡 Hint

Common Mistakes

Passing props instead of state.

Passing setState function instead of state.

The value prop of the provider should be the global state to share it with children.

3fill in blank

hard

Fix the error in the component to avoid prop drilling by using global state.

React Native

function ChildComponent({ data }) {
  const globalData = useContext([1]);
  return <Text>{globalData}</Text>;
}

Drag options to blanks, or click blank then click option'

ADataContext

Bprops

CuseState

DsetData

Attempts:

3 left

💡 Hint

Common Mistakes

Using props instead of context.

Trying to use useState inside the child without context.

Using useContext(DataContext) accesses global state directly, avoiding passing data through props.

4fill in blank

hard

Fill both blanks to create a global state and provide it to the app.

React Native

const [[1], setData] = useState('Hello');

<MyContext.Provider value=[2]>
  <App />
</MyContext.Provider>

Drag options to blanks, or click blank then click option'

Adata

Bstate

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for state and provider value.

Passing setData instead of data to provider.

The state variable is named data and the provider value should be data to share it globally.

5fill in blank

hard

Fill all three blanks to consume and update global state in a component.

React Native

const { [1], [2] } = useContext(MyContext);

function update() {
  [2]('New Value');
}

return <Button onPress={update} title=[1] />;

Drag options to blanks, or click blank then click option'

Adata

BsetData

Dstate

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up data and setData names.

Using props instead of context.

We destructure data and setData from context. The button title shows data.

Practice

1. Why is using global state preferred over prop drilling in React Native apps?

easy

A. Because global state requires more code to pass data

B. Because prop drilling improves performance by passing props deeply

C. Because prop drilling avoids using any state management

D. Because global state allows direct data sharing without passing props through many components

Solution

1. Step 1: Understand prop drilling

   Prop drilling means passing data through many layers of components even if intermediate ones don't need it.

2. Step 2: Understand global state benefits

   Global state shares data directly with any component that needs it, avoiding unnecessary prop passing.

3. Final Answer:

   Because global state allows direct data sharing without passing props through many components -> Option D

4. Quick Check:

   Global state avoids prop drilling = C [OK]

Hint: Global state shares data directly, skipping intermediate props [OK]

Common Mistakes:

• Thinking prop drilling improves performance
• Believing global state requires more code
• Confusing prop drilling with avoiding state

2. Which of the following is the correct way to access global state using React Context in React Native?

easy

A. const value = useReducer(MyContext);

B. const value = useState(MyContext);

C. const value = useContext(MyContext);

D. const value = useEffect(MyContext);

Solution

1. Step 1: Recall React Context usage

   To access global state via React Context, useContext hook is used with the context object.

2. Step 2: Identify correct hook

   useState manages local state, useEffect manages side effects, useReducer manages complex state logic, but none access context directly.

3. Final Answer:

   const value = useContext(MyContext); -> Option C

4. Quick Check:

   Access context with useContext = D [OK]

Hint: Use useContext to read global state from context [OK]

Common Mistakes:

• Using useState instead of useContext for context
• Confusing useEffect with state access
• Trying to use useReducer directly for context

3. Given this React Native code snippet using global state, what will be the output when the button is pressed?

const CountContext = React.createContext(0);

function Display() {
  const count = React.useContext(CountContext);
  return {count};
}

function App() {
  const [count, setCount] = React.useState(0);
  return (
    
      
       setCount(count + 1)} />
    
  );
}

medium

A. The displayed number stays 0 always

B. The displayed number increases by 1 each button press

C. The app crashes due to missing context

D. The button does not respond to presses

Solution

1. Step 1: Understand context and state connection

   The count state is provided via CountContext.Provider and updated on button press.

2. Step 2: Trace button press effect

   Pressing the button calls setCount(count + 1), updating count and re-rendering Display with new value.

3. Final Answer:

   The displayed number increases by 1 each button press -> Option B

4. Quick Check:

   Context updates with state changes = B [OK]

Hint: State update triggers context value change and re-render [OK]

Common Mistakes:

• Assuming context value never changes
• Thinking button does not update state
• Believing app crashes without provider

4. Identify the bug in this React Native code that tries to use global state but still requires prop drilling:

const UserContext = React.createContext();

function Profile({ user }) {
  return {user.name};
}

function App() {
  const user = { name: 'Anna' };
  return (
    
      
    
  );
}

medium

A. Profile component should use useContext(UserContext) instead of props

B. UserContext.Provider is missing a value prop

C. User object is not defined

D. Profile component should be a class component

Solution

1. Step 1: Check how Profile receives data

   Profile expects a user prop but is rendered without props, causing undefined user.

2. Step 2: Use context to avoid prop drilling

   Profile should use useContext(UserContext) to get user directly from global state.

3. Final Answer:

   Profile component should use useContext(UserContext) instead of props -> Option A

4. Quick Check:

   Use context hook to avoid prop drilling = A [OK]

Hint: Use useContext inside components to get global state [OK]

Common Mistakes:

• Forgetting to use useContext in child components
• Assuming Provider needs no value prop
• Thinking class components are required

5. You have a React Native app with deeply nested components needing the same user data. Which approach best avoids prop drilling and keeps code clean?

hard

A. Use React Context to create a global user state and access it with useContext in any component

B. Pass user data as props through every nested component manually

C. Store user data in local component state of the top-level component only

D. Use multiple useState hooks in each nested component to hold user data

Solution

1. Step 1: Understand prop drilling problem

   Passing props through many nested components is tedious and error-prone.

2. Step 2: Use global state with React Context

   React Context allows sharing user data globally, so any component can access it directly without prop passing.

3. Final Answer:

   Use React Context to create a global user state and access it with useContext in any component -> Option A

4. Quick Check:

   Global state with context avoids prop drilling = A [OK]

Hint: React Context shares data globally, no prop passing needed [OK]

Common Mistakes:

• Passing props through every nested component
• Using local state only at top level
• Duplicating state in nested components