SAP HANA Certification Exam Prep Test

During delta merge operations, the additional disk space factor required is 1.2. This means that when merging the changes made to the data since the last full merge, the system needs 1.2 times the size of the changed data to perform the merge operation. This factor takes into account any new or modified data that needs to be merged, as well as any overhead or temporary storage required during the process.

During the Database Migration Option (DMO) procedure using the in-place migration, the R3load processes are located on the Primary Application Server (PAS) host. This means that the R3load processes responsible for migrating the database are running on the PAS host, where the primary application server is located.

The SAP HANA cockpit automatically assigns the Test, Development, and Production usage types to tiles in the system. These usage types represent different environments in which the SAP HANA database system can be used. The Test environment is used for testing purposes, the Development environment is used for developing and modifying applications, and the Production environment is used for running live applications.

The system schema _SYS_STATISTICS provides performance data and system alerts details that can be reviewed in SAP HANA MiniChecks.

The status "Syncing" indicates a temporary connection loss of the secondary system. This means that the secondary system is currently catching up with the changes made on the primary system and is in the process of synchronizing the data. Once the synchronization is complete, the status will change to "Synced" indicating that the secondary system is fully up to date with the primary system.

The prerequisite when installing the SAP Landscape Management tool is the SAP NetWeaver Application Server Java. This means that before installing the tool, the user must ensure that the SAP NetWeaver Application Server Java is already installed on their system.

During the delta merge process, data is inserted into both Main 2 and Delta 2 memory areas. The delta merge process involves merging the changes made in the delta memory areas (Delta 1 and Delta 2) into the main memory areas (Main 1 and Main 2). Therefore, data is inserted into both the current main memory area (Main 2) and the delta memory area that contains the latest changes (Delta 2).

Restricted users typically have limited access to resources and privileges on a system. In order to enable these users to connect to databases, explicit permissions need to be granted. ODBC (Open Database Connectivity) and JDBC (Java Database Connectivity) are both connection technologies that allow applications to connect to databases. By enabling ODBC and JDBC connections explicitly, restricted users will have the necessary access to connect to and interact with databases. Therefore, ODBC and JDBC are the correct answers for this question.

SAP expert sizing is needed in scenarios where customers want to consolidate multiple ERP source systems into one ERP system on SAP HANA, as well as when they want to carve out ERP functionality from the source system to the ERP on SAP HANA system. This process requires expert sizing to determine the appropriate hardware and infrastructure requirements for the migration and consolidation.

Before starting the Database Migration Option (DMO) procedure, two preparation tasks that need to be performed are checking if the latest SPAM/SAINT update is applied and updating the SAP Host Agent to the latest version. These tasks ensure that the system is up to date and compatible with the migration process.

The SAP HANA database system running in log mode "normal" automatically executes a regular log backup when the time threshold is exceeded. This means that after a certain amount of time has passed since the last log backup, the system will initiate a new backup to ensure data consistency and recovery options. Additionally, the system also triggers a regular log backup when the log segment is full. This occurs when the current segment used to store transaction logs reaches its maximum capacity, prompting the system to create a new segment and backup the filled segment to free up space for new logs.

In the Manage Users app in SAP HANA cockpit, you can directly assign privileges and roles to a user. Privileges are specific authorizations that determine what actions a user can perform, while roles are a collection of privileges and authorizations grouped together for easier management. By assigning privileges and roles, you can control the access and permissions of a user within the SAP HANA system.

To perform a complete backup of an SAP HANA database system, it is necessary to back up the system database and all tenant databases individually. This means that each database within the system needs to be backed up separately to ensure that all data is properly preserved. Backing up the complete storage system or the complete database system may not be sufficient as it may not capture all the necessary data from each individual database. Therefore, the correct approach is to perform individual backups for each database within the system.

The correct sequence for the restart of the SAP HANA database system is as follows: first, row tables are loaded into memory. Then, open transactions are recovered. After that, aborted transactions are rolled back. Finally, column tables are loaded. This sequence ensures that the necessary data is loaded into memory and any incomplete or failed transactions are properly handled before loading the column tables.

During the initial run of the configuration phase when performing the Database Migration Option (DMO) procedure to an SAP HANA 2.0 database tenant, the following user credentials are requested:

1. The DBACOCKPIT user of the tenant database is required to access and configure the specific tenant database.
2. The SYSTEM user of the system database is needed to perform administrative tasks and manage the overall system.
3. The DDIC user in client 000 of the ABAP system is necessary for executing the migration process and accessing the ABAP system.

These user credentials are essential for ensuring a smooth and successful migration to the SAP HANA 2.0 database tenant.

The SAP DBA Cockpit uses SAP Business Intelligence to store the performance indicators. SAP Business Intelligence is a technology that provides a comprehensive platform for data analysis, reporting, and visualization. It allows users to gather, analyze, and interpret business data, including performance indicators, to make informed decisions and monitor the performance of SAP systems.

After creating a new tenant in an SAP HANA system replication configuration, it is necessary to perform the additional action of backing up the tenant database. This is important to ensure the data integrity and availability of the newly created tenant. By backing up the tenant database, any potential data loss or system failure can be mitigated, allowing for easy recovery and restoration of the tenant's data if needed.

The container-specific technical user owns an SAP HANA Deployment Infrastructure (HDI) role.

The Kernel profiler trace must be activated to analyze performance issues with systems where third-party software cannot be installed. This trace allows for monitoring and analyzing the performance of the SAP HANA kernel, which is the core component of the SAP HANA system. By enabling the Kernel profiler trace, administrators can gather detailed information about the system's performance, including CPU usage, memory usage, and database access times, which can help identify and resolve performance issues.

The Compile server and Preprocessor are the two SAP HANA database services that can be stopped from the system database. Stopping these services can help in optimizing the performance of the system and managing the resources effectively. By stopping the Compile server, the system can be relieved from the task of compiling SQLScript procedures and functions. Similarly, stopping the Preprocessor can help in reducing the load on the system by disabling the preprocessing of SQLScript code.

The table that provides a customizing interface for the dynamic management of partitions and locations is TABLE_PLACEMENT. This table allows for the customization and management of how data is partitioned and stored in different locations within a database. It provides a flexible and dynamic approach to managing data placement, allowing for efficient storage and retrieval of data based on specific requirements and criteria.

In a SAP HANA scale-out system, the GLOBAL_ALLOCATION_LIMIT parameter determines the maximum amount of memory that can be allocated by a single node. Since there are four 1TB nodes in the system, the total available memory is 4TB. However, since the customer has purchased a 1.5TB license, the maximum memory that can be allocated is limited to the license size. Therefore, the GLOBAL_ALLOCATION_LIMIT parameter should be set to 512 GB, which is the closest value to the license size.

SYNC and SYNCMEM replication modes keep the primary system waiting until a timeout is exceeded when the secondary system is not available. These replication modes ensure that the primary system does not proceed with any further operations until it receives confirmation from the secondary system. This helps maintain data consistency and integrity between the primary and secondary systems.

The correct answer is "INIFILE ADMIN". This privilege is required to manage blacklisted parameters in SAP HANA cockpit. The INIFILE ADMIN privilege allows the user to modify and manage the INI files, which are used to configure various settings and parameters in SAP HANA. By having this privilege, the user can effectively manage and control the blacklisted parameters in the system.

The SAP HANA system processes trigger two merge methods: AUTO and CRITICAL. The AUTO merge method is automatically triggered by the system to merge delta storage with main storage when certain conditions are met. On the other hand, the CRITICAL merge method is triggered when the system detects that the delta storage is reaching its maximum capacity and needs to be merged with the main storage immediately to prevent data loss or performance issues.

Savepoints are triggered by a database soft shutdown and by performing a database backup. A savepoint is a point in a transaction where you can roll back to if necessary. When a database undergoes a soft shutdown or a backup is performed, it triggers a savepoint to ensure that the transaction can be rolled back to a specific point in case of any issues or errors.

The correct answers for installing an SAP HANA multi-host system are "/hana/log/" and "/hana/shared". These file system locations are suggested because "/hana/log/" is used for storing log files specific to each SAP HANA system, and "/hana/shared" is used for storing shared data and configuration files that are common to all SAP HANA systems in the multi-host setup.

The SAP HANA database lifecycle manager (HDBLCM) on installation media allows you to update SAP HANA and its components, as well as extract components. This means that you can use HDBLCM to apply updates and patches to the SAP HANA database system, ensuring that it remains up to date with the latest features and bug fixes. Additionally, you can extract components from the installation media, which can be useful for various purposes such as troubleshooting or creating backups.

To redistribute tables across the hosts in a scale-out system, you need the RESOURCE ADMIN system privilege. This privilege allows you to manage system resources, including redistributing tables to balance the workload and optimize performance. The RESOURCE ADMIN privilege gives you the authority to make changes and adjustments to the system's resource allocation, ensuring efficient distribution of tables across the hosts in the scale-out system.

To add hosts to an SAP HANA scale-out system, two prerequisites must be considered. Firstly, the SAP HANA system installation should be on a shared file system. This ensures that all hosts in the system have access to the necessary installation files and can operate seamlessly. Secondly, the host being added must have access to the installation directories. This ensures that the new host can retrieve the required files and configurations to join the scale-out system successfully. The other two options, shutting down the SAP HANA database server and placing the additional host in a different data center, are not prerequisites for adding hosts to the system.

The correct minimum requirement for the log volume and /hana/shared/ file system for an SAP HANA database system is as follows: For a 256 GB system, the log volume should be 128 GB and the /hana/shared/ file system should be 256 GB. This means that for every 256 GB system, the log volume should be half the size at 128 GB, while the /hana/shared/ file system should remain the same at 256 GB.

The prerequisites necessary for productively using SAP HANA cockpit 2.0 are an IBM Power System with operating system SUSE Linux Enterprise Server (SLES) and 16 GB RAM on a dedicated server. These requirements indicate that the system needs to be running on an IBM Power System with SLES as the operating system. Additionally, it needs to have a minimum of 16 GB RAM allocated to it on a dedicated server.

The hdblcm tool in batch mode requires the password of the user sapadm and the SAP HANA System ID (SID) to be provided as mandatory parameters. These parameters are necessary for the tool to authenticate the user and identify the specific SAP HANA system for installation or configuration. The data and log path, as well as the installation path, are not mentioned as mandatory parameters in this context.

The Secure User Store (hdbuserstore) can be used to configure failover supporting a 3-tier scenario by storing the connection information on the SAP HANA database client. This allows for seamless switching between different database instances in case of a failure. Additionally, it can also be used to store connection information on the SAP HANA XS Advanced engine, enabling secure and efficient access to the database.

The correct answer for this question is SAP Solution Manager and SAP HANA cockpit. These two products are used for SAP HANA administration. SAP Solution Manager is a centralized tool that helps in managing and monitoring SAP systems, including SAP HANA. It provides functionalities such as system landscape management, incident management, and change control. On the other hand, SAP HANA cockpit is a web-based tool that allows administrators to monitor and manage SAP HANA databases. It provides features such as performance monitoring, configuration management, and user management. Both of these products are essential for efficient SAP HANA administration.

To rename a tenant database in the SAP HANA cockpit, there are two prerequisites to consider. Firstly, the tenant database must be stopped. This ensures that there are no active processes or connections to the database during the renaming process. Secondly, the database should not be in a move operation, meaning there should be no ongoing data migration or relocation processes happening with the database. These prerequisites ensure a stable and consistent state for the renaming operation to avoid any potential conflicts or data loss.

You can resume the incomplete recovery in the cases of an aborted recovery of a delta data backup and an aborted recovery of a log backup.

The tools hdbcons and Sapcontrol can be used to investigate an SAP HANA system that is started but cannot be reached using SQL. Hdbcons is a command-line tool that allows you to connect to the HANA database system and perform various diagnostic and troubleshooting tasks. Sapcontrol is a central control and monitoring tool for SAP systems, which can be used to check the status of various components and services of the SAP HANA system. Both tools provide different functionalities to investigate and resolve issues with the SAP HANA system.

Before activating SAP HANA system replication with secondary time travel, it is mandatory for both the primary and secondary systems to have the same SAP HANA version. Additionally, the CPU architecture of both systems must be identical.

LDAP servers can perform the tasks of role assignment and user creation. Role assignment involves assigning specific roles or permissions to users within an organization's directory. User creation refers to the process of creating new user accounts within the directory.

In SAP HANA cockpit, you can configure the following alert configuration properties:
1. Email alert notification: This allows you to set up email notifications for alerts, so that you can be informed about any critical issues or events.
2. Alert threshold values: You can define the threshold values for different alerts, specifying the conditions under which an alert should be triggered.
3. Alert checker category: This allows you to categorize different types of alerts based on their severity or importance, making it easier to prioritize and manage them effectively.

When you create a technical user during the register resource procedure in SAP HANA cockpit, the user is automatically assigned the privileges of SELECT on the _SYS_STATISTICS scheme and CATALOG READ. These privileges allow the user to access and retrieve statistical information from the _SYS_STATISTICS scheme and read the catalog information.

The prerequisites necessary for using the SAP HANA database lifecycle manager (HDBLCM) Web user interface are having communication port 1129 open and having the SAP Host Agent installed on the SAP HANA host. These requirements allow for the proper communication and management of the SAP HANA database through the HDBLCM Web user interface. The other options, such as having the SAP HANA database system in any version or having the SAP HANA Client software locally installed, are not necessary for using the HDBLCM Web user interface.

In a Multiple Database Container (MDC) system, the privilege needed to perform database-specific backups on all tenant databases is DATABASE ADMIN. This privilege grants the user the authority to perform administrative tasks specific to a database, including performing backups.

The correct answers for this question are MONITOR ADMIN and DATABASE ADMIN. When connected to the system database, MONITOR ADMIN privileges are required to monitor the system and tenant databases. DATABASE ADMIN privileges are required to administer the tenant databases, including tasks such as creating, modifying, and deleting databases. BACKUP ADMIN and DATA ADMIN privileges are not specifically required for administrating tenant databases when connected to the system database.

Page Management and logger are the two features of the storage engine in the SAP HANA index server that enable data consistency and maintain durable changes. Page Management ensures efficient allocation and management of data pages in memory and on disk, while the logger records all changes made to the database in a persistent and sequential log. These features work together to ensure that data is stored and updated consistently and that changes are durable and recoverable in case of system failures.

Workload classes and admission control are two SAP HANA features that can be used to manage the database peak load. Workload classes allow for the classification and prioritization of different types of workloads, allowing the system to allocate resources accordingly. Admission control helps in managing the system resources by controlling the number of concurrent sessions or requests, ensuring that the system does not get overloaded during peak load periods. These features help optimize performance and ensure efficient resource allocation during high demand periods.

You can load and unload individual tables and table columns manually in an SAP HANA tenant database when you need to measure total memory and when you need to actively free up memory.

The Manage Full System Information Dumps app in SAP HANA cockpit provides the features of Diagnosis information and Runtime environment. This means that the app allows users to gather diagnostic information about the system and its components, as well as information about the current runtime environment. These features are important for troubleshooting and monitoring the system's performance and health.

If a user has the ALL PRIVILEGES activity, they can manipulate views and tables in the database. Views are virtual tables that display the result of a query, and users with ALL PRIVILEGES can modify, create, or delete views. Tables are the main objects in a database that store data, and users with ALL PRIVILEGES can perform various operations on tables such as inserting, updating, deleting, or altering the structure of tables. However, procedures and sequences are not directly related to the manipulation of database objects, so they are not included in the correct answer.