Email verification in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a user clicks the email verification link in Laravel?

In Laravel's built-in email verification system, what is the expected behavior when a user clicks the verification link sent to their email?

A The user's email_verified_at field is updated, and they are redirected to a verified home page.

B The user is asked to enter their password again before verification completes.

C The verification link expires immediately and shows an error page.

D The user is automatically logged out and redirected to the login page.

💡 Hint

Think about what Laravel does to mark the email as verified and where it sends the user afterward.

When the user clicks the verification link, Laravel updates the email_verified_at timestamp in the database and redirects the user to a page confirming verification or the intended home page.

📝 Syntax

intermediate

Which code snippet correctly enables email verification in a Laravel User model?

Choose the correct way to enable email verification in the User model in Laravel.

A class User extends Authenticatable uses MustVerifyEmail {}

B class User extends Authenticatable extends MustVerifyEmail {}

C class User extends Authenticatable with MustVerifyEmail {}

D class User extends Authenticatable implements MustVerifyEmail {}

💡 Hint

Remember how interfaces are implemented in PHP classes.

Laravel requires the User model to implement the MustVerifyEmail interface to enable email verification.

🔧 Debug

advanced

Why does the email verification link show 'Invalid signature' error?

A user clicks the email verification link but sees an 'Invalid signature' error. Which of the following is the most likely cause?

A The user's email_verified_at field is already set.

B The verification URL was modified or expired before clicking.

C The User model does not implement MustVerifyEmail interface.

D The mail driver is not configured correctly in .env file.

💡 Hint

Think about what Laravel checks when validating the verification link.

Laravel signs the verification URL with a temporary signed route. If the URL is changed or expired, the signature becomes invalid.

❓ state_output

advanced

What is the value of $user->hasVerifiedEmail() after verification?

After a user clicks the email verification link and the process completes successfully, what will $user->hasVerifiedEmail() return?

Laravel

$user = User::find(1);
// Assume user just verified email
return $user->hasVerifiedEmail();

A true

B false

C Throws an exception

D null

💡 Hint

Check what the method hasVerifiedEmail() checks internally.

The method returns true if the email_verified_at column is not null, indicating the email is verified.

🧠 Conceptual

expert

Which middleware ensures only verified users access a route?

In Laravel, which middleware should you apply to a route to restrict access only to users who have verified their email?

A auth

B auth.verified

C verified

D verified.email

💡 Hint

Look for the middleware name Laravel uses by default for email verification.

Laravel provides the verified middleware to restrict routes to only users with verified emails.

Practice

1. What is the main purpose of email verification in Laravel?

easy

A. To reset the user's password automatically

B. To delete unverified user accounts immediately

C. To log the user out after registration

D. To confirm a user's email address for security and trust

Solution

1. Step 1: Understand email verification purpose

   Email verification ensures the user owns the email they provided.

2. Step 2: Identify security benefits

   This process improves security and trust by confirming email validity.

3. Final Answer:

   To confirm a user's email address for security and trust -> Option D

4. Quick Check:

   Email verification = Confirm email ownership [OK]

Hint: Email verification confirms user email ownership [OK]

Common Mistakes:

• Confusing email verification with password reset
• Thinking it logs out users automatically
• Assuming it deletes accounts immediately

2. Which interface must the User model implement to enable email verification in Laravel?

easy

A. Illuminate\Contracts\Auth\MustVerifyEmail

B. Illuminate\Contracts\Auth\Authenticatable

C. Illuminate\Contracts\Auth\CanResetPassword

D. Illuminate\Contracts\Auth\Access\Authorizable

Solution

1. Step 1: Identify the required interface for email verification

   Laravel requires the User model to implement MustVerifyEmail to enable verification.

2. Step 2: Confirm the correct namespace and interface

   The interface is Illuminate\Contracts\Auth\MustVerifyEmail.

3. Final Answer:

   Illuminate\Contracts\Auth\MustVerifyEmail -> Option A

4. Quick Check:

   User model implements MustVerifyEmail [OK]

Hint: Use MustVerifyEmail interface on User model [OK]

Common Mistakes:

• Using Authenticatable instead of MustVerifyEmail
• Confusing with password reset interfaces
• Missing the correct namespace

3. Given this route setup in Laravel:

Route::middleware(['auth', 'verified'])->get('/dashboard', function () {
    return 'Welcome to your dashboard!';
});

What happens if a logged-in user tries to access /dashboard without verifying their email?

medium

A. They are redirected to the email verification notice page

B. They see the dashboard content immediately

C. They get a 404 Not Found error

D. They are logged out automatically

Solution

1. Step 1: Analyze middleware effects

   The 'verified' middleware checks if the user's email is verified before allowing access.

2. Step 2: Determine behavior for unverified users

   If not verified, Laravel redirects them to the verification notice page.

3. Final Answer:

   They are redirected to the email verification notice page -> Option A

4. Quick Check:

   'verified' middleware redirects unverified users [OK]

Hint: Middleware 'verified' redirects unverified users [OK]

Common Mistakes:

• Assuming unverified users see dashboard content
• Expecting a 404 error instead of redirect
• Thinking users get logged out automatically

4. Consider this User model snippet:

class User extends Authenticatable
{
    // Missing implementation here
}

Why might email verification fail to work properly with this model?

medium

A. Because the model does not use the Notifiable trait

B. Because the model does not implement MustVerifyEmail interface

C. Because the model lacks a 'verified' attribute

D. Because the model extends Authenticatable instead of Model

Solution

1. Step 1: Check interface implementation

   Email verification requires the User model to implement MustVerifyEmail interface.

2. Step 2: Identify missing implementation

   The snippet lacks this interface, so verification won't trigger properly.

3. Final Answer:

   Because the model does not implement MustVerifyEmail interface -> Option B

4. Quick Check:

   Missing MustVerifyEmail causes verification failure [OK]

Hint: Implement MustVerifyEmail to enable verification [OK]

Common Mistakes:

• Thinking extending Authenticatable is wrong
• Assuming 'verified' attribute is required manually
• Believing Notifiable trait controls verification

5. You want to customize the email verification process to send a verification email immediately after user registration. Which Laravel feature should you use to trigger this email automatically?

hard

A. Override the User model's boot method to send the email

B. Manually call the sendEmailVerificationNotification method in the controller

C. Use the Registered event and listen to it to send the verification email

D. Add a middleware to send the email on every request

Solution

1. Step 1: Identify Laravel's event system for registration

   Laravel fires a Registered event after user registration.

2. Step 2: Use event listener to send verification email

   Listening to Registered event allows sending the verification email automatically.

3. Final Answer:

   Use the Registered event and listen to it to send the verification email -> Option C

4. Quick Check:

   Registered event triggers verification email [OK]

Hint: Listen to Registered event to send verification email [OK]

Common Mistakes:

• Calling sendEmailVerificationNotification manually in controller
• Overriding boot method unnecessarily
• Using middleware to send email on every request