Route prefixes in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What URL does this route respond to?

Given the following Laravel route group with a prefix, what is the full URL path for the named route dashboard.home?

Laravel

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

A /dashboard

B /dashboard/admin

C /admin

D /admin/dashboard

💡 Hint

Remember that the prefix adds before the route path inside the group.

The prefix 'admin' is added before the route path '/dashboard', so the full URL path is '/admin/dashboard'.

📝 Syntax

intermediate

Identify the syntax error in this route prefix usage

Which option contains a syntax error in defining a route group with a prefix in Laravel?

Laravel

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

A

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

B

Route::prefix('api') {
    Route::get('/users', function () {
        return 'User list';
    });
};

C

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

D

;)}
;)}    
;'tsil resU' nruter        
{ )( noitcnuf ,'sresu/'(teg::etuoR    
{ )( noitcnuf(puorg>-)'ipa'(xiferp::etuoR

💡 Hint

Check the syntax for calling the group method with a closure.

Option B is invalid because it uses braces directly after prefix() without calling group() and uses a semicolon incorrectly. The correct syntax requires calling group() with a closure.

❓ state_output

advanced

What is the output of this nested route prefix example?

Consider this Laravel route definition with nested prefixes. What URL path will respond to the route named profile.show?

Laravel

Route::prefix('user')->group(function () {
    Route::prefix('account')->group(function () {
        Route::get('/profile', function () {
            return 'User Profile';
        })->name('profile.show');
    });
});

A /user/profile/account

B /account/user/profile

C /user/account/profile

D /profile/user/account

💡 Hint

Prefixes stack in the order they are nested.

The outer prefix 'user' is added first, then the inner prefix 'account', then the route path '/profile', resulting in '/user/account/profile'.

🔧 Debug

advanced

Why does this route prefix not work as expected?

This Laravel code intends to prefix routes with 'api/v1', but the routes respond at '/v1/users' instead of '/api/v1/users'. What is the cause?

Laravel

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

A The route path '/users' should not start with a slash inside prefix groups.

B The route group closures are missing the 'use' keyword to inherit variables.

C The prefixes are concatenated correctly; the problem is in the web server configuration.

D The prefix 'api' is overwritten by the inner prefix 'v1' instead of concatenated.

💡 Hint

Check how leading slashes affect route paths inside prefix groups.

In Laravel, route paths inside prefix groups should not start with a slash because it resets the path instead of appending. The leading slash causes the inner prefix to override the outer prefix.

🧠 Conceptual

expert

How does Laravel handle route prefixes with trailing slashes?

If you define a route prefix with a trailing slash like Route::prefix('admin/')->group(...), what is the effect on the generated route URLs?

A Laravel automatically removes the trailing slash from the prefix, so URLs are normal without double slashes.

B Laravel keeps the trailing slash, causing double slashes in URLs if route paths start with a slash.

C Laravel throws a runtime error because prefixes cannot have trailing slashes.

D Laravel ignores the prefix entirely if it ends with a slash.

💡 Hint

Think about how Laravel normalizes URL paths internally.

Laravel normalizes prefixes by trimming trailing slashes to avoid double slashes in URLs, so the trailing slash in the prefix does not cause issues.