Query optimization in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

Understanding Eager Loading Impact

Consider a Laravel application with Post and Comment models where each post has many comments.

What will be the main difference in database queries between these two code snippets?

1. $posts = Post::all(); foreach ($posts as $post) { echo $post->comments->count(); }
2. $posts = Post::with('comments')->get(); foreach ($posts as $post) { echo $post->comments->count(); }

A The first code runs one query for posts and one query per post for comments; the second runs two queries total using eager loading.

B Both codes run the same number of queries because Laravel caches comments automatically.

C The first code runs a single query joining posts and comments; the second runs multiple queries.

D The second code runs one query per comment, while the first runs only one query.

💡 Hint

Think about how Laravel loads related data lazily vs eagerly.

The first code triggers the N+1 query problem: one query for posts plus one query per post to get comments. The second code uses eager loading, running only two queries: one for posts and one for all related comments.

📝 Syntax

intermediate

Correct Use of Query Builder for Optimization

Which of the following Laravel query builder snippets correctly limits the selected columns to optimize the query?

A $users = DB::table('users')->get(['id', 'name']);

B $users = DB::table('users')->select('id', 'name')->get();

C $users = DB::table('users')->columns('id', 'name')->get();

D $users = DB::table('users')->only('id', 'name')->get();

💡 Hint

Check the Laravel documentation for selecting specific columns.

The select() method specifies which columns to retrieve. The get() method does not accept column names as parameters. Methods columns() and only() do not exist in Laravel's query builder.

🔧 Debug

advanced

Identifying Cause of Slow Query

A Laravel query is running very slowly:

$orders = Order::where('status', 'pending')->get(); foreach ($orders as $order) { echo $order->user->name; }

What is the most likely cause of the slow performance?

A The query is missing eager loading for the related user, causing N+1 queries.

B The <code>where</code> clause is invalid and causes a full table scan.

C The <code>get()</code> method is not fetching any data, causing errors.

D The <code>user</code> relation is not defined, causing a syntax error.

💡 Hint

Think about how Laravel loads related models when accessed inside a loop.

Accessing $order->user inside the loop without eager loading triggers a separate query for each order, causing the N+1 query problem and slow performance.

🧠 Conceptual

advanced

Effect of Using Chunking on Large Datasets

What is the main advantage of using Laravel's chunk() method when processing large datasets?

A It combines multiple queries into a single complex query for faster execution.

B It automatically caches all records to speed up repeated queries.

C It reduces memory usage by processing records in smaller batches instead of loading all at once.

D It disables eager loading to improve query speed.

💡 Hint

Think about how loading many records at once affects memory.

The chunk() method processes records in small groups, preventing high memory usage that occurs when loading large datasets all at once.

❓ state_output

expert

Output of Complex Query with Subquery Optimization

Given the following Laravel query, what will be the output?

$latestPosts = Post::select('id', 'title')
    ->whereIn('id', function ($query) {
        $query->selectRaw('MAX(id)')
              ->from('posts')
              ->groupBy('user_id');
    })->get();

foreach ($latestPosts as $post) {
    echo $post->title . ', ';
}

Assuming the posts table has multiple posts per user, what does this query return?

A Titles of posts with the lowest id for each user.

B All post titles from the posts table, separated by commas.

C An empty collection because the subquery is invalid.

D Titles of the latest post (highest id) for each user, separated by commas.

💡 Hint

Focus on what the subquery selects and how it filters the main query.

The subquery selects the maximum post id per user. The main query selects posts whose id is in that list, effectively fetching the latest post per user.