C-DBADM-2404 SAP Certified Technology Associate Database Administrator Practice Questions

BACKINT for SAP HANA is the official, certified API that enables third-party backup tools to directly back up and restore an SAP HANA database. The third-party tool provides a BACKINT agent that integrates with SAP HANA. When a backup is initiated, SAP HANA streams the data through this interface to the external backup management solution instead of writing to the local file system.

This solution correctly addresses both problems. SAP HANA Native Storage Extension (NSE) is the standard feature for managing 'warm' data, allowing less frequently accessed data to be stored on disk while remaining accessible via SQL, which directly resolves the memory pressure issue. For security, the standard procedure is to acquire and import a trusted TLS/SSL certificate (using a self-signed one is possible for non-production, but the principle is correct) and then enable SSL communication via configuration parameters. Both tasks are manageable with standard SAP tools like SAP HANA Cockpit.

The log_backup_timeout_s parameter, located in the persistence section of the global.ini file, defines the interval in seconds after which an automatic log backup is triggered if one has not already occurred. The default value is 900 seconds (15 minutes). Reducing this value will cause log backups to run more frequently, helping to prevent 'log full' situations.

This statement is false. Storing keys with the data they encrypt would defeat the purpose of encryption. In SAP HANA, the root keys used for data and log volume encryption are securely stored in a separate location called the Secure Store in the File System (SSFS). This separation ensures that even if an attacker gains access to the physical data volumes, they cannot decrypt the data without also compromising the SSFS.

The password_lock_time parameter specifies the number of minutes a user account remains locked after reaching the maximum_invalid_connect_attempts. Setting this parameter to a value greater than 0 enables the automatic unlock feature. A value of 0 means the account remains locked until an administrator manually unlocks it.

The M_EXPENSIVE_STATEMENTS system view is the primary tool for identifying poorly performing SQL statements. It can be configured to trace statements that exceed thresholds for duration, CPU time, or memory usage. By querying this view and filtering on the MEMORY_SIZE column, an administrator can pinpoint the exact statements that consumed excessive memory.

The core concept is that scale-up (or vertical scaling) involves making a single machine more powerful by adding resources like CPU and RAM. In contrast, scale-out (or horizontal scaling) involves distributing the workload across multiple, often commodity, servers that work together in a cluster. The diagram correctly illustrates this distinction.

To achieve an RPO of zero, the replication mode must be synchronous ('sync' or 'syncmem'). The 'sync' mode ensures that the primary system commits a transaction only after receiving confirmation that the logs have been persisted on the secondary site. To allow read access on the secondary system, the operation mode must be 'logreplay_readaccess'. This combination meets both requirements. 'async' mode does not guarantee RPO=0. 'delta_datashipping' is an older mode and does not allow read access. 'logreplay' alone does not enable read access for reporting.

SAP HANA supports enabling both log and data volume encryption online. Log volume encryption can be enabled and takes effect immediately for new log segments. Data volume encryption can also be enabled while the system is online. Once enabled, all pages written to the data volume during subsequent savepoints will be encrypted. Over time, the entire data volume becomes encrypted without requiring a full database outage or a backup/restore cycle, thus minimizing disruption.

The recoverSys.py script is the specific tool provided by SAP for recovering the SYSTEMDB of a multi-tenant system from the command line. It is crucial to remember that this script CANNOT be used to recover tenant databases; tenant recovery must be initiated via SQL commands or graphical tools like SAP HANA Cockpit.