How can you handle a "Not Found" route without specifying a specific path?Review LaterBy using the component provided by React Router.By defining a route with a path of "/" as the last route in the configuration.By using the history.notfound() method when a route match fails.By using the RouteNotFound attribute within the configuration.

Which route is not valid for this React Router component? <Routes> <Route path='/' element={<Home />} /> <Route path='/user/:id' element={<User />} /> <Route path='/user/:id/edit' element={<UserEdit />} /> <Route path='/post/:id' element={<Post />} /> <Route path='/posts' element={<Posts />} /></Routes>  Pick ONE option/user/1/edit/post/10/post/profile/12

Consider the base Url as http://reactjs.com and choose the updated Url when the below route is encountered:<Route path = "/about"  element= {<AboutUs/>} /> http://reactjs.com/about/http://reactjs.com//abouthttp://reactjs.com/abouthttp://reactjs.com/AboutUs

Error HandlingThe error.js file convention allows you to gracefully handle unexpected runtime errors in nested routes.Automatically wrap a route segment and its nested children in a React Error Boundary.Create error UI tailored to specific segments using the file-system hierarchy to adjust granularity.Isolate errors to affected segments while keeping the rest of the application functional.Add functionality to attempt to recover from an error without a full page reload.Create error UI by adding an error.js file inside a route segment and exporting a React component:

Routing is provided by default in ____ but not provided in ____?(1 Point)Node.js and react.jsExpress.js and node.jsAll of the aboveNode.js and express.js

Q1 of 4outlined_flagWhich react router property is used to specify, the component to be rendered when a route is encountered?elementcomponentpathto