Mass assignment protection in Laravel - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to allow mass assignment for the 'name' attribute in a Laravel model.

Laravel

protected $fillable = ['[1]'];

Drag options to blanks, or click blank then click option'

Aemail

Bpassword

Cid

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Putting attributes not intended for mass assignment like 'password' or 'id' in $fillable.

Leaving $fillable empty and expecting mass assignment to work.

The $fillable property specifies which attributes can be mass assigned. Here, 'name' is allowed.

2fill in blank

medium

Complete the code to protect all attributes from mass assignment in a Laravel model.

Laravel

protected $guarded = ['[1]'];

Drag options to blanks, or click blank then click option'

Apassword

B*

Cemail

Dname

Attempts:

3 left

💡 Hint

Common Mistakes

Using $fillable instead of $guarded to block all attributes.

Listing specific attributes instead of '*' to block all.

Setting $guarded to ['*'] blocks mass assignment on all attributes.

3fill in blank

hard

Fix the error in the model to allow mass assignment only for 'title' and 'content'.

Laravel

protected $fillable = ['title', '[1]'];

Drag options to blanks, or click blank then click option'

Aauthor

Bdate

Ccontent

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Adding attributes not intended for mass assignment.

Leaving out 'content' from the fillable array.

Both 'title' and 'content' must be listed in $fillable to allow mass assignment.

4fill in blank

hard

Fill both blanks to define a model that blocks mass assignment on all attributes except 'email'.

Laravel

protected $guarded = ['[1]'];
protected $fillable = ['[2]'];

Drag options to blanks, or click blank then click option'

A*

Bemail

Cusername

Dpassword

Attempts:

3 left

💡 Hint

Common Mistakes

Using $fillable without $guarded to block attributes.

Not listing allowed attributes in $fillable.

Setting $guarded to ['*'] blocks all attributes, but $fillable overrides to allow 'email'.

5fill in blank

hard

Fill all three blanks to create a mass assignment safe model that allows 'name' and 'email' but blocks 'password'.

Laravel

protected $fillable = ['[1]', '[2]'];
protected $guarded = ['[3]'];

Drag options to blanks, or click blank then click option'

Aname

Bemail

Cpassword

Did

Attempts:

3 left

💡 Hint

Common Mistakes

Putting 'password' in $fillable by mistake.

Leaving $guarded empty and exposing sensitive data.

The $fillable array lists 'name' and 'email' as allowed for mass assignment. The $guarded array blocks 'password' to protect it.

Practice

1. What is the main purpose of mass assignment protection in Laravel?

easy

A. To speed up database queries automatically

B. To control which model attributes can be set in bulk

C. To encrypt user passwords before saving

D. To generate database migrations

Solution

1. Step 1: Understand mass assignment concept

   Mass assignment means setting multiple model attributes at once, often from user input.

2. Step 2: Identify protection purpose

   Mass assignment protection controls which attributes can be set this way to prevent unwanted changes.

3. Final Answer:

   To control which model attributes can be set in bulk -> Option B

4. Quick Check:

   Mass assignment protection = control allowed fields [OK]

Hint: Mass assignment protects fields from unwanted bulk changes [OK]

Common Mistakes:

• Confusing mass assignment with password encryption
• Thinking it speeds up queries
• Believing it creates migrations automatically

2. Which of the following is the correct way to allow mass assignment for the 'name' and 'email' fields in a Laravel model?

easy

A. public $fillable = ['name', 'email'];

B. protected $guarded = ['name', 'email'];

C. protected $fillable = ['name', 'email'];

D. public $guarded = ['name', 'email'];

Solution

1. Step 1: Recall correct property for allowed fields

   In Laravel, $fillable lists fields allowed for mass assignment.

2. Step 2: Check syntax and visibility

   The property should be protected and named $fillable with an array of allowed fields.

3. Final Answer:

   protected $fillable = ['name', 'email']; -> Option C

4. Quick Check:

   $fillable = allowed fields [OK]

Hint: Use $fillable to list allowed fields, not $guarded [OK]

Common Mistakes:

• Using $guarded to allow fields instead of block
• Making $fillable public instead of protected
• Confusing $fillable and $guarded names

3. Given the model below, what will happen if you try to create a user with User::create(['name' => 'Anna', 'email' => '[e-mail]', 'role' => 'admin']);?

class User extends Model {
    protected $fillable = ['name', 'email'];
}

medium

A. Error thrown because role is not fillable

B. User is created with all fields including role

C. User is created but name and email are empty

D. User is created with name and email set; role is ignored

Solution

1. Step 1: Check $fillable fields

   The model allows mass assignment only for 'name' and 'email'.

2. Step 2: Understand behavior for unfillable fields

   The 'role' field is ignored during mass assignment, no error is thrown.

3. Final Answer:

   User is created with name and email set; role is ignored -> Option D

4. Quick Check:

   Only $fillable fields set, others ignored [OK]

Hint: Only $fillable fields are set; others ignored silently [OK]

Common Mistakes:

• Expecting an error for unfillable fields
• Thinking all fields are set regardless of $fillable
• Assuming unfillable fields become null

4. You have this model:

class Post extends Model {
    protected $guarded = [];
}

You want to prevent mass assignment on the 'is_admin' field. What is the best fix?

medium

A. Add 'is_admin' to the $guarded array

B. Set $guarded = ['*'] to block all fields

C. Remove the $guarded property completely

D. Add 'is_admin' to the $fillable array

Solution

1. Step 1: Understand current $guarded setting

   Currently, $guarded is empty array, so all fields are mass assignable.

2. Step 2: Block 'is_admin' field

   To block a field, add it to $guarded array to prevent mass assignment.

3. Final Answer:

   Add 'is_admin' to the $guarded array -> Option A

4. Quick Check:

   $guarded blocks fields; add 'is_admin' there [OK]

Hint: Add fields to $guarded to block mass assignment [OK]

Common Mistakes:

• Adding blocked fields to $fillable instead
• Removing $guarded and expecting protection
• Blocking all fields unintentionally with ['*']

5. You want to allow mass assignment on all fields except 'password' and 'is_admin' in a Laravel model. Which is the best way to do this?

hard

A. protected $guarded = ['password', 'is_admin'];

B. protected $fillable = ['password', 'is_admin'];

C. protected $fillable = ['*'];

D. protected $guarded = [];

Solution

1. Step 1: Understand the goal

   Allow all fields except 'password' and 'is_admin' for mass assignment.

2. Step 2: Choose correct property

   Using $guarded to block specific fields is best for this case.

3. Step 3: Evaluate options

   Setting protected $guarded = ['password', 'is_admin']; blocks those fields and allows others.

4. Final Answer:

   protected $guarded = ['password', 'is_admin']; -> Option A

5. Quick Check:

   $guarded blocks fields; use it to exclude only some [OK]

Hint: Use $guarded to block few fields, allow all others [OK]

Common Mistakes:

• Using $fillable with only blocked fields (wrong meaning)
• Setting $fillable to ['*'] which is invalid
• Leaving $guarded empty and expecting protection