Question: Upon receiving a Floor Request message, what action is taken by the floor control interface towards the MCPTT client if the `<Queueing Capability>` value in the Track Info field is set to `'0'` (indicating no queueing support)?
Option 1: Send a Floor Queue Position Info message with an updated queue position.
Option 2: Grant the floor immediately, bypassing the queue due to lack of queueing capability.
Option 3: Send a Floor Deny message with a `<Reject Cause>` value indicating 'Another MCPTT client has permission'.
Option 4: Place the request in a special handling queue for non-queueing capable clients.
Explanation: When the `<Queueing Capability>` is set to `'0'`, indicating the floor participant in the MCPTT client does not support queueing, the interface responds by denying the floor request. This denial is communicated via a Floor Deny message, which includes a specific `<Reject Cause>` value to inform the requesting client of the reason for the denial, ensuring orderly floor control in various call scenarios.