DVA-C02 Troubleshooting and Optimization Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  The function executed but threw an unhandled exception.

  Why this is correct

  A 200 status code confirms the invocation reached the function and returned a response, while FunctionError set to 'Unhandled' signals the runtime caught an exception the code did not handle. The function executed but terminated abnormally, so the handler threw an unhandled error.

• ✗

  The function returned an error in the LogResult field.

  Why it's wrong here

  FunctionError 'Unhandled' means the function's code threw an unhandled exception, not that LogResult contains an error; LogResult holds base64-encoded tail logs. It is tempting because logs often reveal the exception, but LogResult is diagnostic output, not the error signal itself.

• ✗

  The function timed out during execution.

  Why it's wrong here

  A timeout produces a `Task timed out` error message and typically a 502 status, not a 200 with `FunctionError: Unhandled`. That field signals the handler itself threw an uncaught exception. Timeout configuration is the right focus when a function exceeds its configured limit, but here the invocation completed and returned a response.

• ✗

  The function was invoked but there was a network error.

  Why it's wrong here

  A network error would surface as a CLI transport failure or timeout, not a 200 response carrying a FunctionError field; the invocation clearly reached the function and returned a payload. It is tempting because network faults do disrupt Lambda calls, but those manifest before invocation completes, whereas 'Unhandled' signals the function code itself threw an uncaught exception.

Go deeper

Related to this question