By default, the audit trail target used in the SAP HANA Cloud, SAP HANA database, is a Database table. This setup is chosen for better integration with existing database management and security tools, allowing for complex queries and reports on audit data, and leveraging the database's built-in security features to protect audit data.References= SAP HANA Cloud administration and security guides which explain the setup and management of audit trails within the database system.
Database Security

Savepoints in SAP HANA are triggered by:B. By issuing a transactional commit, which initiates a savepoint to ensure that all committed transactions are durably written to the disk.C. By a database soft shutdown, during which SAP HANA ensures that all changes are safely written to the disk in the form of a final savepoint to prevent any data loss.Savepoints are not directly triggered by performing a delta merge or a database backup; these processes may coincide with savepoints for consistency but do not inherently cause them.References= SAP HANA administration guide detailing how transactional data management is handled, including the automatic triggering of savepoints at specific operations like shutdowns and commits.
SAP HANA Architecture

To view the audit trail in the SAP HANA Cloud, you can use:B. The Auditing card in the SAP HANA cockpit, which provides a user interface to access and analyze audit logs directly from the cockpit dashboard.C. The SQL Console in the SAP HANA database explorer, which allows running SQL queries to directly fetch audit data from the audit tables.This dual approach helps in effectively monitoring and ensuring compliance with data access and changes, thereby enhancing the security posture of the organization.References= SAP HANA Cloud documentation and best practices on security monitoring and compliance.
Database Security