Basic route definition in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Laravel route?

Consider this Laravel route definition:

Route::get('/welcome', function () { return 'Hello, Laravel!'; });

What will a user see when they visit /welcome in their browser?

Laravel

Route::get('/welcome', function () { return 'Hello, Laravel!'; });

A A 404 Not Found error page

B A blank page with no content

C A JSON response with {"message": "Hello, Laravel!"}

D The text 'Hello, Laravel!' displayed in the browser

💡 Hint

Think about what the route returns directly to the browser.

The route returns a simple string 'Hello, Laravel!' which Laravel sends as the HTTP response body. So the browser displays that text.

📝 Syntax

intermediate

Which route definition is syntactically correct?

Which of the following Laravel route definitions is valid and will not cause a syntax error?

A Route::get('/home', function() { return 'Home'; });

B Route::get('/home' function() { return 'Home'; });

C Route::get('/home', function() { return 'Home' });

D Route::get('/home', function() { return 'Home'; )

💡 Hint

Look carefully at commas, parentheses, and semicolons.

Option A has correct syntax with comma separating parameters, proper braces, and semicolon. Others miss commas, semicolons, or have mismatched parentheses.

❓ state_output

advanced

What is the output when visiting /user/42?

Given this Laravel route:

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

What will the browser display when visiting /user/42?

Laravel

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

A 404 Not Found error

B User ID: {id}

C User ID: 42

D User ID: $id

💡 Hint

The {id} part is a route parameter passed to the function.

Laravel passes the URL segment 42 as $id to the function, so it returns 'User ID: 42'.

🔧 Debug

advanced

Why does this route cause an error?

Look at this Laravel route:

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

Why will this cause an error when visiting /post/10?

Laravel

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

A Because the function must return a view, not a string

B Because $id is not passed as a parameter to the function

C Because the route method get() is not valid

D Because the route URL is missing a leading slash

💡 Hint

Check if the function receives the route parameter.

The function does not accept $id as a parameter, so $id is undefined inside it, causing an error.

🧠 Conceptual

expert

How many routes are defined after this code runs?

Consider this Laravel code:

Route::get('/page', fn() => 'Page');
Route::post('/page', fn() => 'Page POST');
Route::match(['get', 'post'], '/page', fn() => 'Page Match');

How many distinct routes are registered in Laravel's router after this code executes?

Laravel

Route::get('/page', fn() => 'Page');
Route::post('/page', fn() => 'Page POST');
Route::match(['get', 'post'], '/page', fn() => 'Page Match');

A 2

B 1

C 4

D 3

💡 Hint

Think about how Laravel handles routes with same URL but different methods.

Laravel registers routes for unique HTTP method and URI combinations, with later registrations overwriting earlier ones for the same method+URI. The first registers GET /page, the second POST /page. Route::match(['get', 'post']) registers GET /page (overwriting) and POST /page (overwriting). Thus, 2 distinct routes: GET /page and POST /page.