Deleting files in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when you delete a file using Laravel's Storage facade?

Consider this Laravel code snippet:

use Illuminate\Support\Facades\Storage;

Storage::delete('documents/report.pdf');

What is the result of running this code if the file exists?

Laravel

use Illuminate\Support\Facades\Storage;

Storage::delete('documents/report.pdf');

A The file 'documents/report.pdf' is removed from the storage disk and returns true.

B The file is moved to a trash folder for recovery later.

C The file remains unchanged and the method returns false.

D An exception is thrown if the file exists.

💡 Hint

Think about what the Storage facade's delete method does when the file exists.

Laravel's Storage::delete method removes the specified file from the disk and returns true if successful. It does not move files to trash or throw exceptions if the file exists.

📝 Syntax

intermediate

Which Laravel code correctly deletes multiple files at once?

You want to delete these files: 'a.txt', 'b.txt', and 'c.txt' from storage. Which code snippet does this correctly?

A Storage::deleteAll(['a.txt', 'b.txt', 'c.txt']);

B Storage::delete('a.txt', 'b.txt', 'c.txt');

C Storage::delete(['a.txt', 'b.txt', 'c.txt']);

D Storage::delete(['a.txt' => true, 'b.txt' => true, 'c.txt' => true]);

💡 Hint

Check the method signature for deleting multiple files in Laravel Storage.

Storage::delete accepts an array of file paths to delete multiple files at once. Passing multiple string arguments or associative arrays is invalid.

🔧 Debug

advanced

Why does this Laravel code fail to delete the file?

Look at this code:

use Illuminate\Support\Facades\Storage;

$file = 'uploads/image.png';
Storage::delete($file);

The file exists but is not deleted. What is the most likely cause?

Laravel

use Illuminate\Support\Facades\Storage;

$file = 'uploads/image.png';
Storage::delete($file);

A The default storage disk is not set to the disk where the file exists.

B The file path is missing a leading slash.

C Storage::delete requires the full URL, not relative path.

D The file is locked by another process and cannot be deleted.

💡 Hint

Think about where Laravel looks for files when deleting.

Storage::delete deletes files from the default disk configured in filesystems.php. If the file is on another disk, you must specify it. A missing leading slash or URL instead of path is not the issue.

❓ state_output

advanced

What is the return value of Storage::delete when deleting multiple files?

Given this code:

use Illuminate\Support\Facades\Storage;

$result = Storage::delete(['file1.txt', 'file2.txt', 'file3.txt']);

Assuming 'file1.txt' and 'file3.txt' exist and are deleted, but 'file2.txt' does not exist, what is the value of $result?

Laravel

use Illuminate\Support\Facades\Storage;

$result = Storage::delete(['file1.txt', 'file2.txt', 'file3.txt']);

A The number of files successfully deleted

B false

C An array of booleans indicating each file's deletion success

D true

💡 Hint

Check Laravel's documentation on Storage::delete return values.

Storage::delete returns true if all files were deleted or did not exist. It returns false only if any file could not be deleted due to an error.

🧠 Conceptual

expert

Which Laravel method should you use to delete a file and handle failure gracefully?

You want to delete a file and log a message if deletion fails without throwing an exception. Which approach is best?

A Use Storage::deleteOrFail which throws exceptions on failure.

B Use Storage::delete and check its boolean return value to log failure.

C Use unlink() PHP function directly and catch exceptions.

D Use Storage::remove which returns detailed error messages.

💡 Hint

Consider Laravel's Storage methods and their behavior on failure.

Storage::delete returns true or false without throwing exceptions, allowing you to handle failure gracefully. unlink() is a PHP function but does not integrate with Laravel's storage disks. deleteOrFail throws exceptions. Storage::remove does not exist.