Model creation in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the default table name for this Laravel model?

Given this Laravel model class, what table will Eloquent use by default?

Laravel

namespace App\Models;

use Illuminate\Database\Eloquent\Model;

class ProductCategory extends Model
{
    // No table property defined
}

A "productcategory"

B "product_categories"

C "product_category"

D "productcategories"

💡 Hint

Laravel converts the model class name to snake_case and pluralizes it.

Laravel automatically converts the model class name from PascalCase to snake_case and pluralizes it to determine the table name. So ProductCategory becomes product_categories.

📝 Syntax

intermediate

Which option correctly defines a guarded property to protect 'id' and 'created_at' fields?

Choose the correct syntax to protect 'id' and 'created_at' from mass assignment in a Laravel model.

Laravel

class UserProfile extends Model
{
    // Define guarded property here
}

A public $guarded = ['id', 'created_at'];

B protected $guarded = 'id', 'created_at';

C protected $guarded = ['id', 'created_at'];

D protected $guarded = array('id', 'created_at');

💡 Hint

The guarded property must be protected and assigned an array.

The guarded property must be declared as protected and assigned an array of field names to protect them from mass assignment.

❓ state_output

advanced

What is the value of $model->timestamps after this model is instantiated?

Consider this Laravel model. What is the value of the public property $timestamps after creating a new instance?

Laravel

class Order extends Model
{
    public $timestamps = false;
}

$model = new Order();
$value = $model->timestamps;

A false

B true

C null

D undefined property error

💡 Hint

The model property $timestamps controls if timestamps are managed automatically.

Since the model explicitly sets public $timestamps = false, the property value is false after instantiation.

🔧 Debug

advanced

Why does this model fail to save data to the database?

This Laravel model does not save data when calling save(). What is the likely cause?

Laravel

class Customer extends Model
{
    protected $table = 'customers';
    protected $fillable = ['name', 'email'];

    public function save(array $options = [])
    {
        // Forgot to call parent save
    }
}

$customer = new Customer();
$customer->name = 'Alice';
$customer->email = '[e-mail]';
$customer->save();

A The save method overrides parent but does not call parent::save(), so data is not saved.

B The $fillable array is missing 'id', so save fails.

C The protected $table property is incorrect and causes failure.

D The model class must be abstract to save data.

💡 Hint

Overriding save requires calling the parent's save method.

Overriding the save method without calling parent::save() prevents the actual saving process, so no data is saved.

🧠 Conceptual

expert

Which statement about Laravel model events is true?

Select the correct statement about Laravel model events during model creation.

A The saved event fires before the creating event.

B The created event fires before the model is saved to the database.

C The saving event fires only after the model is saved to the database.

D The creating event fires before the model is saved to the database.

💡 Hint

Think about the order of events when a model is saved.

The creating event fires before the model is saved, allowing you to modify data before insertion. The created event fires after saving.