Error Boundaries — Concept Check
Questions on Error Boundaries. Without a boundary, one thrown error unmounts your entire application and leaves a blank white page. A boundary contains the damage to one part of the screen.
Questions in this quiz
7 questions on Error Boundaries — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A React application crashes and shows a blank white page when a null value enters a component. What is the best way to handle this?
- AIgnore the error as it won't affect the overall application.
- BPlace an error boundary around the component to catch the error.
- CRely on React's default behavior to handle the error gracefully.
- DUse try/catch blocks in every component to prevent crashes.
2.You have a component that occasionally throws an error during rendering. What should you do to prevent the entire app from crashing?
- AWrap the component with an error boundary to catch the error.
- BImplement server-side rendering to bypass the error.
- CHandle the error in a global event listener for unhandled rejections.
- DUse setTimeout to delay the rendering and avoid errors.
3.An error occurs in an event handler in your React app. Why doesn't the error boundary catch it?
- AError boundaries do not catch errors in event handlers.
- BThe error boundary is not configured to handle event errors.
- CEvent handlers automatically prevent errors from propagating.
- DThe error boundary is placed too low in the component tree.
4.Where should you place an error boundary to ensure a broken page keeps the header and navigation visible?
- AAround each individual widget on the page.
- BPer route to isolate page-specific errors.
- CAround the entire application as a last resort.
- DOnly around components that frequently fail.
5.A developer believes that placing an error boundary too high in the component tree is beneficial. What is a potential downside?
- AIt may cause the entire app to disappear on an error.
- BIt prevents any errors from being logged properly.
- CIt will catch errors in event handlers, which is unnecessary.
- DIt makes the app slower due to increased error handling.
6.Why might an error boundary fail to catch a rejected promise?
- AThe promise was handled by a query library instead.
- BPromises automatically handle their own errors.
- CThe error boundary was not defined in a class component.
- DError boundaries do not handle async code or promises.
7.What is the purpose of the componentDidCatch lifecycle method in an error boundary?
- ATo automatically reset the error state.
- BTo prevent any rendering errors from occurring.
- CTo catch errors in event handlers.
- DTo log errors and provide error information.