Question: Upon receiving a Floor Release message from an associated floor participant, where the MCPTT client has negotiated support for queueing of floor requests, what action does the IWF floor control server take regarding the MCPTT client's position in the active floor request queue?
Option 1: The IWF floor control server adds the MCPTT client to the beginning of the active floor request queue.
Option 2: The IWF floor control server keeps the MCPTT client's position unchanged in the active floor request queue.
Option 3: The IWF floor control server moves the MCPTT client to the end of the active floor request queue.
Option 4: The IWF floor control server removes the MCPTT client from the active floor request queue, if they were in it.
Explanation: When an MCPTT client has negotiated support for queueing of floor requests and a Floor Release message is received, the IWF floor control server's response includes removing the MCPTT client from the active floor request queue (if they were in it), as this indicates the client no longer needs to hold or wait for the floor. This action aligns with efficiently managing floor requests in queued scenarios.