Bird
Raised Fist0
Laravelframework~30 mins

Route groups in Laravel - Mini Project: Build & Apply

Choose your learning style10 modes available
Organizing Routes with Route Groups in Laravel
📖 Scenario: You are building a simple web application with Laravel. You want to organize your routes by grouping them under a common URL prefix and middleware for better structure and security.
🎯 Goal: Create a route group in Laravel that applies a URL prefix /admin and middleware auth to three routes: /dashboard, /users, and /settings.
📋 What You'll Learn
Create a route group with prefix admin
Apply middleware auth to the route group
Define three GET routes inside the group: /dashboard, /users, and /settings
Each route should return a simple string response indicating the page name
💡 Why This Matters
🌍 Real World
Route groups help keep Laravel routes organized and secure by applying common settings to many routes at once.
💼 Career
Understanding route groups is essential for Laravel developers to build scalable and maintainable web applications.
Progress0 / 4 steps
1
Set up the initial routes without grouping
Create three GET routes in routes/web.php for /admin/dashboard, /admin/users, and /admin/settings. Each route should return a string: "Dashboard Page", "Users Page", and "Settings Page" respectively.
Laravel
Hint

Use Route::get() for each URL with a closure returning the page name string.

2
Create a route group with prefix and middleware
Create a route group using Route::prefix('admin')->middleware('auth')->group() and place the three routes inside this group. Remove the /admin prefix from individual routes inside the group.
Laravel
Hint

Use Route::prefix('admin')->middleware('auth')->group(function () { ... }); and put the routes inside the function.

3
Add a name prefix to the route group
Add a name prefix admin. to the route group by chaining ->name('admin.') to the group definition. This will prefix route names inside the group.
Laravel
Hint

Chain ->name('admin.') before ->group() to add the name prefix.

4
Name each route inside the group
Add route names to each route inside the group using ->name() with these exact names: dashboard, users, and settings.
Laravel
Hint

Use ->name('dashboard'), ->name('users'), and ->name('settings') after each route definition.

Practice

(1/5)
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
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard