Does FireDAC TFDQuery apply Limit and Offset server-side or client-side?

Goal: Page through a large dataset using TFDQuery Limit and Offset while avoiding full-table downloads to the RAD Studio client.

FireDAC translates Limit and Offset into native SQL when the connected server and driver support pagination. For older servers without native OFFSET or FETCH support, the library may instead retrieve all matching rows and apply the bound locally. It is unclear whether this fallback happens silently, whether RecordCount returns the bounded count or the full unfiltered count, and which driver versions guarantee server-side execution.

Does FireDAC silently fall back to client-side pagination when native server support is missing?

Does RecordCount reflect the Limit and Offset bounds or the complete result set under client-side emulation?

Which RAD Studio and database driver combinations ensure that Limit and Offset are pushed to the server?