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.

Practice

1. What does the following Laravel route definition do?
Route::get('/home', function () { return 'Welcome Home'; });

easy

A. It redirects '/home' to another URL.

B. It creates a database entry for '/home'.

C. It responds with 'Welcome Home' when the '/home' URL is visited.

D. It deletes the '/home' route.

Solution

1. Step 1: Understand Route::get usage

   The Route::get method defines a route that listens for GET requests on a specific URL.

2. Step 2: Analyze the callback function

   The callback returns the string 'Welcome Home' when the '/home' URL is accessed.

3. Final Answer:

   It responds with 'Welcome Home' when the '/home' URL is visited. -> Option C

4. Quick Check:

   Route::get('/home', ...) returns 'Welcome Home' [OK]

Hint: Route::get defines response for a URL visit [OK]

Common Mistakes:

• Thinking it creates or deletes database entries
• Confusing route response with redirection
• Assuming it modifies URLs instead of responding

2. Which of the following is the correct syntax to define a route in Laravel that responds to a GET request at URL '/about'?

easy

A. Route::get('/about', function () { return 'About Us'; });

B. Route.get('/about', function () { return 'About Us'; });

C. Route::post('/about', function () { return 'About Us'; });

D. Route::get('/about') { return 'About Us'; };

Solution

1. Step 1: Identify correct method and syntax

   Laravel uses Route::get() with double colon and parentheses to define GET routes.

2. Step 2: Check callback function syntax

   The callback must be an anonymous function inside parentheses returning the response.

3. Final Answer:

   Route::get('/about', function () { return 'About Us'; }); -> Option A

4. Quick Check:

   Correct Laravel route syntax uses Route::get(...) [OK]

Hint: Use Route::get() with function callback for GET routes [OK]

Common Mistakes:

• Using dot instead of double colon
• Using Route::post for GET requests
• Missing parentheses around function

3. What will be the output when visiting the URL '/greet' given this route?

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

medium

A. Hello, Laravel!

B. 404 Not Found error

C. Syntax error

D. Redirect to homepage

Solution

1. Step 1: Check route URL and method

   The route listens for GET requests at '/greet'. Visiting '/greet' triggers this route.

2. Step 2: Analyze the returned response

   The callback returns the string 'Hello, Laravel!' which will be shown in the browser.

3. Final Answer:

   Hello, Laravel! -> Option A

4. Quick Check:

   Route returns string response on GET request [OK]

Hint: Route::get returns callback output on URL visit [OK]

Common Mistakes:

• Expecting a 404 error if route is defined
• Confusing output with redirect or error
• Assuming syntax error without checking code

4. Identify the error in this Laravel route definition:

Route::get('/contact', function { return 'Contact Page'; });

medium

A. Route URL should not start with '/'

B. Missing parentheses after function keyword

C. Return statement is not allowed in routes

D. Route::get should be Route::post

Solution

1. Step 1: Check function syntax in route callback

   Anonymous functions require parentheses after the function keyword even if no parameters are used.

2. Step 2: Verify other parts of the route

   The URL starting with '/' is correct, return statements are allowed, and Route::get is valid for GET requests.

3. Final Answer:

   Missing parentheses after function keyword -> Option B

4. Quick Check:

   Anonymous functions need () after function [OK]

Hint: Always add () after function keyword in callbacks [OK]

Common Mistakes:

• Omitting parentheses after function
• Thinking URL cannot start with '/'
• Confusing GET and POST methods

5. You want to create a route that returns a JSON response with a message 'Success' when visiting '/api/status'. Which is the correct Laravel route definition?

hard

A. Route::get('/api/status', function () { echo json_encode(['message' => 'Success']); });

B. Route::get('/api/status', function () { return 'Success'; });

C. Route::post('/api/status', function () { return response()->json(['message' => 'Success']); });

D. Route::get('/api/status', function () { return response()->json(['message' => 'Success']); });

Solution

1. Step 1: Choose correct HTTP method and URL

   The route should respond to GET requests at '/api/status'.

2. Step 2: Return JSON response properly

   Laravel's response()->json() helper returns a JSON response correctly formatted with headers.

3. Step 3: Check other options for correctness

   Route::get('/api/status', function () { return 'Success'; }); returns plain text, Route::post('/api/status', function () { return response()->json(['message' => 'Success']); }); uses POST instead of GET, Route::get('/api/status', function () { echo json_encode(['message' => 'Success']); }); uses echo which is not recommended in routes.

4. Final Answer:

   Route::get('/api/status', function () { return response()->json(['message' => 'Success']); }); -> Option D

5. Quick Check:

   Use response()->json() for JSON output in routes [OK]

Hint: Use response()->json() to return JSON in routes [OK]

Common Mistakes:

• Using wrong HTTP method (POST instead of GET)
• Returning plain string instead of JSON
• Using echo instead of return in route