Take Test: Symfony 7 – PHP – Exception and Error Handling

Question 1: What is the purpose of exceptions in PHP?

To replace syntax errors.

To stop PHP from executing functions.

To handle runtime errors in a structured and recoverable way.

To speed up performance.

Question 2: What base interface do all exceptions and errors implement in PHP 7+?

Throwable

ExceptionInterface

RuntimeError

ErrorHandler

Question 3: What happens when an exception is not caught?

The exception is silently ignored.

It is automatically logged but execution continues.

PHP stops execution and reports an uncaught exception fatal error.

It converts to a notice.

Question 4: Which keyword is used to handle exceptions?

handle

recover

guard

catch

Question 5: Which block always executes, whether an exception is thrown or not?

after

always

finally

last

Question 6: Which class is the base of all user-defined exceptions?

Exception

Throwable

Error

RuntimeException

Question 7: What does this code print?\ntry { throw new Exception("Oops"); } catch (Exception $e) { echo $e->getMessage(); }

Nothing

Oops

Exception

Fatal error

Question 8: What does "Error" represent in PHP 7+?

A syntax issue detected at compile time.

A warning that never stops execution.

A class used for logging.

A catchable object representing fatal PHP engine errors.

Question 9: Can you catch both Exception and Error together?

No, they must be caught separately.

Yes, but only with try/finally.

Yes, if both extend RuntimeException.

Yes, by catching Throwable.

Question 10: What happens if you throw something that is not a Throwable?

It is automatically converted to Exception.

PHP throws a TypeError.

It is ignored silently.

It triggers a warning.

Question 11: What is the correct order of try/catch/finally blocks?

try → catch → finally

try → finally → catch

catch → try → finally

try → handle → exit

Question 12: Which method retrieves the error message from an Exception object?

message()

error()

getMessage()

toString()

Question 13: What is the effect of rethrowing an exception inside a catch block?

It creates a new exception instance.

It stops all exception handling.

It propagates the same exception to the outer scope.

It clears the stack trace.

Question 14: What’s the purpose of the ErrorException class?

To convert PHP errors into catchable exceptions.

To log exceptions automatically.

To recover memory from fatal errors.

To filter exceptions by type.

Question 15: What function allows setting a global handler for uncaught exceptions?

register_shutdown_function()

set_exception_handler()

set_error_handler()

handle_uncaught()

Question 16: What’s the main difference between Exception and Error in PHP 7+?

Errors can be caught; exceptions cannot.

Exceptions terminate the script immediately.

Exceptions are for program logic errors; Errors are for engine-level problems.

They behave identically.

Question 17: What happens if a finally block has a return statement?

It overrides any previous return or exception.

It is ignored at runtime.

It executes after the script ends.

It triggers a parse error.

Question 18: How can PHP errors like E_WARNING be converted into exceptions?

By enabling display_errors.

By using ini_set("error_mode","exception").

By using finally instead of catch.

By using set_error_handler() and throwing an ErrorException.

Question 19: Which statement is true about multiple catch blocks?

All catch blocks are executed sequentially.

The first matching catch block handles the exception.

Only the last catch block is valid.

Multiple catch blocks are not supported.

Question 20: What’s the best practice when catching exceptions broadly (Throwable)?

Silently ignore it.

Log it and either rethrow or exit gracefully.

Convert it into a string and echo.

Suppress it with @ operator.