C-DBADM-2404 Sample Questions & Answers

This statement is false. Since SAP HANA 2.0, Multi-tenant Database Containers (MDC) is the default and only operational mode. A standard installation will always create a SYSTEMDB and a default tenant database. The previous single-container mode is no longer available.

Object privileges are used to grant access to specific database objects like schemas, tables, views, or procedures. To grant read-only access (SELECT) to all tables within the SALES_DATA schema, the administrator should grant the SELECT object privilege on the SALES_DATA schema to the REPORT_USER_ROLE. This is the most direct and appropriate method. System privileges are for administrative actions, Analytic privileges are for controlling access to data within modeling views, and Package privileges are for repository packages.

The default interval for automatic savepoints in SAP HANA is 300 seconds, which is equivalent to 5 minutes. This is a critical parameter for database consistency and recovery performance. The 900 seconds (15 minutes) value is the default for the log backup interval, not the savepoint interval.

Column-store databases store data in columns rather than rows. This layout is highly advantageous for analytical queries (OLAP) because only the required columns for a query need to be read from memory/disk. Furthermore, since all data in a single column is of the same type, it allows for extremely high compression ratios. Row-store is generally faster for OLTP workloads that affect single, entire rows.

The SAP HANA Database Lifecycle Manager (hdblcm) is the standard command-line tool for all lifecycle management tasks. This includes initial installation, applying support packages and patches (updates), adding or removing components, and reconfiguring the system. hdbsql is for database queries, and hdbnsutil is a lower-level tool for name server administration.

In SAP HANA Cockpit's Performance Monitor, the 'CPU Usage' view provides a direct visualization of CPU consumption over time, broken down by host and service (e.g., indexserver, nameserver). This is the primary starting point. The 'Threads' view is the next logical step, as it allows the administrator to see the details of active threads, filter by high CPU time, and identify the specific operations or SQL statements responsible for the high load.

The AUDITOR standard role is specifically designed for security administrators and auditors. It grants read-only access to all system views related to security, such as audit policies, users, roles, and privileges, without granting access to application data or the ability to modify system settings. The MONITORING role is for performance monitoring, and PUBLIC is a default role with minimal privileges granted to all users.

In a scale-out landscape, the master name server holds the authoritative information about the system's topology. This includes which hosts are part of the system, which services are running on which hosts, and how data is distributed across the index servers on different nodes. Client connections first query the name server to locate the correct index server for their request. SQL execution is the role of the index server.

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.