Route parameters in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Laravel route with parameter?

Consider this Laravel route definition:

Route::get('/user/{id}', function ($id) { return "User ID: $id"; });

What will be the output when visiting URL /user/42?

Laravel

Route::get('/user/{id}', function ($id) { return "User ID: $id"; });

A User ID: 42

B User ID: {id}

C User ID: $id

D 404 Not Found

💡 Hint

Route parameters are passed as variables to the callback function.

The {id} in the route URL is captured and passed as the $id argument to the closure. So visiting /user/42 sets $id to 42, which is returned in the string.

📝 Syntax

intermediate

Which route definition correctly uses an optional parameter?

In Laravel, how do you define a route with an optional parameter named page?

A Route::get('/posts/{page}', function ($page = 1) { return $page; });

B Route::get('/posts/{page?}', function ($page = 1) { return $page; });

C Route::get('/posts/{page?}', function ($page) { return $page; });

D Route::get('/posts/{page?}', function () { return $page; });

💡 Hint

Optional parameters use a question mark and default value in the function.

The question mark after {page} makes it optional. The function must provide a default value for $page to avoid errors when the parameter is missing.

🔧 Debug

advanced

Why does this route cause an error?

Given this route:

Route::get('/product/{id}', function () { return "Product ID: $id"; });

What error will occur when visiting /product/5?

Laravel

Route::get('/product/{id}', function () { return "Product ID: $id"; });

A Syntax error due to missing parameter

B 404 Not Found error

C Undefined variable $id error

D No error, outputs 'Product ID: 5'

💡 Hint

Check if the route parameter is passed to the function.

The route expects a parameter {id}, but the closure does not accept any arguments. So $id is undefined inside the function, causing an error.

🧠 Conceptual

advanced

What happens if two routes conflict with parameters?

Consider these two routes:

Route::get('/user/{name}', function ($name) { return "User: $name"; });
Route::get('/user/profile', function () { return "Profile page"; });

What will happen when visiting /user/profile?

A Laravel throws a route conflict error

B The second route matches and outputs 'Profile page'

C 404 Not Found error

D The first route matches and outputs 'User: profile'

💡 Hint

Routes are matched in the order they are defined.

The first route with {name} matches any string after /user/, including 'profile'. So it captures 'profile' as $name and returns 'User: profile'. The second route is never reached.

❓ state_output

expert

What is the output of this route with multiple parameters and constraints?

Given this route:

Route::get('/order/{id}/{status}', function ($id, $status) { return "Order $id is $status"; })->where(['id' => '[0-9]+', 'status' => 'pending|shipped']);

What is the output when visiting /order/123/shipped and /order/abc/pending respectively?

Laravel

Route::get('/order/{id}/{status}', function ($id, $status) { return "Order $id is $status"; })->where(['id' => '[0-9]+', 'status' => 'pending|shipped']);

A First URL: 'Order 123 is shipped', Second URL: 404 Not Found

B First URL: 404 Not Found, Second URL: 'Order abc is pending'

C Both URLs output the order status string

D Both URLs return 404 Not Found

💡 Hint

Route constraints limit which URLs match the route.

The 'id' must be digits only, so '123' matches but 'abc' does not. The 'status' must be 'pending' or 'shipped'. So the first URL matches and returns the string. The second URL does not match the constraints and returns 404.