Question: Upon receiving a Floor Queue Position Request message from an MCPTT (Mission Critical Push To Talk) client, what actions does the floor participant interface toward the MCPTT client undertake?
Option 1: It grants immediate permission and sends a confirmation to the MCPTT client.
Option 2: It ignores the request if in the 'P: has no permission' state and doesn't forward it.
Option 3: It changes its state to 'P: has permission' before sending the request to the floor control server interface.
Option 4: It sends the Floor Queue Position Request message to the floor control server interface and remains in the 'P: has no permission' state.
Explanation: This is correct because, according to the specified behavior, upon receiving such a request from an MCPTT client, the interface not only forwards the request to the floor control server for processing but also maintains its current state of 'P: has no permission', ensuring that permission management is centrally controlled by the floor control server. This approach ensures seamless integration with LMR systems while maintaining the integrity of the MCPTT service's permission framework.