Final answer:
The correct solution to prevent SAML token replay is by Implementing SAML Token Time-to-Live Policies, which ensures tokens are only valid for a limited duration. Database solutions are not relevant to this specific issue.
Step-by-step explanation:
The question posed focuses on preventing SAML token replay attacks. The correct solution for preventing SAML token replay is not inherently tied to database technologies such as SQL Server Always On Availability Groups, MySQL Replication with SSL, or Oracle Data Guard. Instead, it involves implementing security measures related to the SAML protocol itself.
Implementing SAML Token Time-to-Live (TTL) Policies is the appropriate option among those listed. By setting a Time-to-Live on SAML tokens, you ensure that these tokens are valid only for a limited period, thereby reducing the window for potential replay attacks. This method discourages attackers because, by the time they attempt to reuse a token, it may have already expired.
In addition to TTL policies, other SAML best practices include using one-time use assertions and having an accurate clock synchronization across all systems involved in the SAML authentication process to enforce the validity period accurately.