Question: Upon successful modification of an existing individual EAS Deployment Information resource via an HTTP PUT request, what is the expected response from the Network Exposure Function (NEF) to the Application Function (AF), assuming the Unified Data Repository (UDR) confirms the update?
Option 1: HTTP response with '404 Not Found' status code and no EasDeployInfo data structure.
Option 2: HTTP response with '500 Internal Server Error' status code and a ProblemDetails data structure.
Option 3: HTTP response with '201 Created' status code and the updated EasDeployInfo data structure.
Option 4: HTTP response including either '200 OK' status code with the updated EasDeployInfo data structure or '204 No Content' status code.
Explanation: According to standard practices for RESTful APIs, upon successfully updating a resource, the server typically responds with either a '200 OK' status code if there's content to return (the updated EasDeployInfo data structure) or a '204 No Content' status code if there's no content to return after the update, aligning with the described NEF behavior upon successful modification and UDR confirmation.