Route groups in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the URL prefix for routes inside this group?

Consider this Laravel route group:

Route::prefix('admin')->group(function () {
    Route::get('/dashboard', function () {
        return 'Admin Dashboard';
    });
});

What URL path will you visit to see the 'Admin Dashboard'?

Laravel

Route::prefix('admin')->group(function () {
    Route::get('/dashboard', function () {
        return 'Admin Dashboard';
    });
});

A /admin/dashboard

B /dashboard/admin

C /admin

D /dashboard

💡 Hint

Think about how the prefix adds to the route path.

The prefix 'admin' is added before all routes inside the group, so the full URL becomes '/admin/dashboard'.

📝 Syntax

intermediate

Which option correctly applies middleware to a route group?

You want to apply the 'auth' middleware to all routes inside a group. Which code snippet is correct?

A

Route::group(['middleware' => 'auth'], function () {
    Route::get('/profile', function () {
        return 'Profile';
    });
});

B

Route::group('middleware' => 'auth', function () {
    Route::get('/profile', function () {
        return 'Profile';
    });
});

C

Route::middleware('auth')->group(function () {
    Route::get('/profile', function () {
        return 'Profile';
    });
});

D

Route::middleware(['auth'])->group(function () {
    Route::get('/profile', function () {
        return 'Profile';
    });
});

💡 Hint

Check the correct syntax for passing middleware in a group.

The correct syntax for applying middleware in a group can use either an array as the first argument to Route::group(), or the middleware() method before group().

❓ state_output

advanced

What is the output of this nested route group?

Given this Laravel route group code:

Route::prefix('api')->group(function () {
    Route::prefix('v1')->group(function () {
        Route::get('/users', function () {
            return 'Users v1';
        });
    });
});

What URL path will return 'Users v1'?

Laravel

Route::prefix('api')->group(function () {
    Route::prefix('v1')->group(function () {
        Route::get('/users', function () {
            return 'Users v1';
        });
    });
});

A /users/api/v1

B /v1/api/users

C /api/users/v1

D /api/v1/users

💡 Hint

Prefixes stack in the order they are nested.

The outer prefix 'api' and inner prefix 'v1' combine to form '/api/v1/users'.

🔧 Debug

advanced

Why does this route group cause a syntax error?

Look at this code:

Route::group(['prefix' => 'admin', 'middleware' => 'auth'], function () {
    Route::get('/dashboard', function () {
        return 'Dashboard';
    });
});

Why does this code cause a syntax error?

Laravel

Route::group(['prefix' => 'admin', 'middleware' => 'auth'], function () {
    Route::get('/dashboard', function () {
        return 'Dashboard';
    });
});

A The callback function is missing the use keyword to import variables.

B The function keyword is missing parentheses after it.

C The array syntax is correct; no syntax error here.

D The array keys should be strings without quotes.

💡 Hint

Check the array syntax and function declaration carefully.

The array syntax and function declaration are correct; this code does not cause a syntax error.

🧠 Conceptual

expert

How does the 'as' option affect route names in groups?

Consider this route group:

Route::name('admin.')->group(function () {
    Route::get('/users', function () {
        return 'Users';
    })->name('users');
});

What is the full route name for the '/users' route?

Laravel

Route::name('admin.')->group(function () {
    Route::get('/users', function () {
        return 'Users';
    })->name('users');
});

A users

B admin.users

C adminusers

D admin.users.users

💡 Hint

The 'name' prefix adds before the route's own name.

The 'name' method on the group adds 'admin.' before each route's name, so the full name is 'admin.users'.

Practice

1. What is the main purpose of using Route::group() in Laravel?

easy

A. To register routes only for API requests

B. To define a single route with multiple HTTP methods

C. To create a route that redirects to another URL

D. To apply shared settings like middleware or prefixes to multiple routes at once

Solution

1. Step 1: Understand Route Group Purpose

   Route groups allow you to bundle routes that share common attributes like middleware or URL prefixes.

2. Step 2: Compare with Other Options

   Options A, B, and C describe different routing features, not the grouping concept.

3. Final Answer:

   To apply shared settings like middleware or prefixes to multiple routes at once -> Option D

4. Quick Check:

   Route groups = shared settings [OK]

Hint: Route groups bundle routes with common settings fast [OK]

Common Mistakes:

• Thinking route groups define single routes
• Confusing route groups with route redirects
• Assuming route groups are only for API routes

2. Which of the following is the correct syntax to create a route group with a prefix admin in Laravel?

easy

A. Route::group('prefix' => 'admin', function () { /* routes */ });

B. Route::group(['prefix' => 'admin'], function () { /* routes */ });

C. Route::group(['admin' => 'prefix'], function () { /* routes */ });

D. Route::group(function () { prefix('admin'); /* routes */ });

Solution

1. Step 1: Recall Route Group Syntax

   Route groups use an array of attributes as the first argument, e.g., ['prefix' => 'admin'].

2. Step 2: Identify Correct Array Syntax

   Route::group(['prefix' => 'admin'], function () { /* routes */ }); correctly uses the array with 'prefix' key and a closure function.

3. Final Answer:

   Route::group(['prefix' => 'admin'], function () { /* routes */ }); -> Option B

4. Quick Check:

   Array with 'prefix' key = correct syntax [OK]

Hint: Use array with 'prefix' key inside Route::group [OK]

Common Mistakes:

• Missing array brackets around attributes
• Swapping key and value in array
• Trying to call prefix() inside the closure

3. Given the following route group code, what URL will respond to the Route::get('dashboard', ...) route?

Route::group(['prefix' => 'admin'], function () {
    Route::get('dashboard', function () {
        return 'Admin Dashboard';
    });
});

medium

A. /admin/dashboard

B. /admin

C. /dashboard

D. /dashboard/admin

Solution

1. Step 1: Understand Prefix Effect

   The 'prefix' => 'admin' adds '/admin' before all routes inside the group.

2. Step 2: Combine Prefix and Route URI

   The route URI is 'dashboard', so combined URL is '/admin/dashboard'.

3. Final Answer:

   /admin/dashboard -> Option A

4. Quick Check:

   Prefix + route URI = /admin/dashboard [OK]

Hint: Prefix adds before route URI in URL [OK]

Common Mistakes:

• Ignoring the prefix and using only route URI
• Appending prefix after route URI
• Confusing route name with URL

4. Identify the error in this route group code:

Route::group(['middleware' => 'auth'], function {
    Route::get('profile', function () {
        return 'User Profile';
    });
});

medium

A. Missing parentheses after function keyword

B. Middleware should be an array, not a string

C. Route::group cannot use middleware

D. Route URI 'profile' is invalid

Solution

1. Step 1: Check Closure Syntax

   The anonymous function must have parentheses: function() { ... }.

2. Step 2: Validate Middleware Usage

   Middleware can be a string or array, so that is correct here.

3. Final Answer:

   Missing parentheses after function keyword -> Option A

4. Quick Check:

   Anonymous function needs () after function [OK]

Hint: Always add () after function keyword for closures [OK]

Common Mistakes:

• Omitting parentheses in anonymous functions
• Thinking middleware must be array always
• Assuming route URI 'profile' is invalid

5. You want to create a route group with prefix api and middleware auth:api. Inside it, you define a route GET /users that returns a JSON list of users. Which is the correct way to write this in Laravel?

hard

A. Route::middleware('auth:api')->group(['prefix' => 'api'], function () {
Route::get('users', function () {
return response()->json(['users' => []]);
});
});

B. Route::group(['prefix' => 'api'], function () {
Route::middleware('auth:api')->get('users', function () {
return ['users' => []];
});
});

C. Route::group(['prefix' => 'api', 'middleware' => 'auth:api'], function () {
Route::get('users', function () {
return response()->json(['users' => []]);
});
});

D. Route::group(['middleware' => 'auth:api'], function () {
Route::prefix('api')->get('users', function () {
return response()->json(['users' => []]);
});
});

Solution

1. Step 1: Combine Prefix and Middleware in One Group

   Route::group(['prefix' => 'api', 'middleware' => 'auth:api'], function () { Route::get('users', function () { return response()->json(['users' => []]); }); }); correctly passes both 'prefix' and 'middleware' as keys in the attributes array.

2. Step 2: Check Route Definition Inside Group

   The route uses Route::get with URI 'users' and returns JSON response properly.

3. Step 3: Verify Other Options

   Route::group(['prefix' => 'api'], function () { Route::middleware('auth:api')->get('users', function () { return ['users' => []]; }); }); applies middleware only to the route, not the group prefix. Route::middleware('auth:api')->group(['prefix' => 'api'], function () { Route::get('users', function () { return response()->json(['users' => []]); }); }); has wrong group syntax. Route::group(['middleware' => 'auth:api'], function () { Route::prefix('api')->get('users', function () { return response()->json(['users' => []]); }); }); misuses prefix inside the route.

4. Final Answer:

   Route::group(['prefix' => 'api', 'middleware' => 'auth:api'], function () { Route::get('users', function () { return response()->json(['users' => []]); }); }); -> Option C

5. Quick Check:

   Group attributes array with prefix and middleware [OK]

Hint: Put prefix and middleware together in group attributes array [OK]

Common Mistakes:

• Splitting prefix and middleware into separate calls incorrectly
• Misplacing prefix() inside route closure
• Using middleware() outside group incorrectly