Question: How should a Network Function (NF) Service Producer handle an HTTP GET request with one or more unsupported query parameters, assuming no specific handling is defined for the API?
Option 1: Reject the request with a 404 Not Found error, indicating the absence of a required parameter.
Option 2: Ignore the unsupported query parameters and respond based on the rest of the supported query parameters in the request.
Option 3: Respond with a 500 Internal Server Error, signaling an inability to process the request due to unsupported parameters.
Option 4: Redirect the request to a default API endpoint, omitting all provided query parameters.
Explanation: For safe HTTP methods like GET, ignoring unsupported query parameters and processing the request based on supported parameters ensures minimal disruption to service while maintaining the integrity of the request-response cycle. This approach aligns with the principle of graceful degradation in network interactions, where possible.