API resource controllers in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Laravel API resource controller method?

Consider a Laravel API resource controller with this method:

public function show($id) {
    return response()->json(['id' => $id, 'name' => 'Item '.$id]);
}

What JSON response will be returned when calling show(5)?

Laravel

public function show($id) {
    return response()->json(['id' => $id, 'name' => 'Item '.$id]);
}

A {"id":5,"name":"Item"}

B {"id":5,"name":"Item 6"}

C {"id":5,"name":"Item 5"}

D }"5 metI":"eman",5:"di"{

💡 Hint

Look at how the string concatenation works with the $id variable.

The method returns a JSON response with the id as an integer 5 and the name as 'Item 5'. Route parameters are strings by default but Laravel casts numeric route parameters to integers when passed to controller methods.

📝 Syntax

intermediate

Which option correctly defines a Laravel API resource controller route?

You want to register a resource controller named ProductController for API routes in routes/api.php. Which route definition is correct?

A Route::resource('products', 'ProductController');

B Route::apiResource('products', ProductController);

C Route::resource('products', ProductController::class);

D Route::apiResource('products', ProductController::class);

💡 Hint

API resource routes exclude create/edit routes and require the controller class reference.

The correct syntax for API resource routes uses Route::apiResource with the controller class reference using ::class.

❓ state_output

advanced

What is the HTTP status code returned by this API resource controller method?

Given this method in a Laravel API resource controller:

public function store(Request $request) {
    $data = $request->validate(['name' => 'required']);
    $item = Item::create($data);
    return response()->json($item, 201);
}

What HTTP status code will the client receive after a successful POST request?

Laravel

public function store(Request $request) {
    $data = $request->validate(['name' => 'required']);
    $item = Item::create($data);
    return response()->json($item, 201);
}

A 201

B 400

C 500

D 200

💡 Hint

201 means resource created successfully.

The method explicitly returns a JSON response with status code 201, which means 'Created'.

🔧 Debug

advanced

Why does this Laravel API resource controller method cause a runtime error?

Examine this method:

public function update(Request $request, $id) {
    $item = Item::findOrFail($id);
    $item->update($request->all);
    return response()->json($item);
}

What causes the error when calling this method?

Laravel

public function update(Request $request, $id) {
    $item = Item::findOrFail($id);
    $item->update($request->all);
    return response()->json($item);
}

A Using $request->all without parentheses causes a runtime error.

B findOrFail does not exist on the Item model.

C update method requires a second argument for validation.

D response()->json cannot return model instances.

💡 Hint

Check how methods are called on the Request object.

The error is caused because $request->all is a method and must be called with parentheses: $request->all().

🧠 Conceptual

expert

Which statement best describes the difference between Route::resource and Route::apiResource in Laravel?

Choose the most accurate explanation about these two routing methods:

A Route::apiResource creates routes only for GET requests, Route::resource creates routes for all HTTP verbs.

B Route::resource creates all RESTful routes including web views, while Route::apiResource excludes routes for create and edit views.

C Route::resource is deprecated and replaced by Route::apiResource in Laravel 9+.

D Route::apiResource automatically applies authentication middleware, Route::resource does not.

💡 Hint

Think about which routes are included or excluded for API-only controllers.

Route::resource creates all RESTful routes including those for HTML views like create and edit, while Route::apiResource excludes these since APIs usually don't serve HTML forms.