C_HANADEV_18 SAP Certified Development Associate - SAP HANA 2.0 SPS06 Questions and Answers

According to the SAP HANA Developer Guide, you use the pull operation to synchronize all unsynchronized changes of the remote Git branch with a local Git branch. The pull operation fetches the changes from the remote branch and merges them with the local branch. This way, you can update your local branch with the latest changes from the remote branch. The other options are incorrect, because:

• Push is the opposite of pull. It sends the changes from the local branch to the remote branch, not the other way around.
• Rebase is an alternative to merge. It rewrites the history of the local branch by applying the changes from the remote branch as new commits on top of the local branch. This creates a linear history, but it may cause conflicts or lose some information.
• Reset is a way to undo changes in the local branch. It moves the branch pointer to a different commit, and optionally discards the changes in the working directory or the staging area.

References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111.

The APPLY_FILTER function is a SQLScript function that applies a filter condition to a table variable and returns a new table variable with the filtered rows. The APPLY_FILTER function supports the following parameters12:

• Filter condition: A mandatory parameter that specifies the filter condition as a string literal or a string expression. The filter condition must follow the syntax of the WHERE clause in SQL, and it can use column names, literals, operators, and functions. For example, APPLY_FILTER(:table_var, ‘price > 100 and category = ‘‘A’’’).
• Table variable: A mandatory parameter that specifies the table variable to which the filter condition is applied. The table variable must be a local or input parameter of the SQLScript procedure or function that calls the APPLY_FILTER function. For example, APPLY_FILTER(:table_var, :filter_cond).

The other options are not correct because they are not parameters of the APPLY_FILTER function. A join condition is a parameter of the APPLY_FILTER_JOIN function, which applies a filter condition to two table variables and returns a new table variable with the joined and filtered rows. An entity set is a parameter of the APPLY_FILTER_ENTITY function, which applies a filter condition to an entity set and returns a new entity set with the filtered rows. These functions are part of the SAP HANA Predictive Analysis Library (PAL), and they are not part of the SQLScript language3. References:

• SAP HANA Platform, SAP HANA SQL and System Views Reference, SQLScript Guide, SQLScript Functions, APPLY_FILTER
• SAP HANA Platform, SAP HANA Developer Guide for SAP HANA Web IDE, Developing Database Modules, Developing SQLScript Procedures and Functions, Using APPLY_FILTER
• SAP HANA Platform, SAP HANA Predictive Analysis Library (PAL), Reference Guide, PAL SQLScript Functions, APPLY_FILTER_JOIN, APPLY_FILTER_ENTITY

 SAP HANA extended application services, advanced model (XS advanced) provides a comprehensive platform for the development and execution of micro-service oriented applications, taking advantage of SAP HANA’s in-memory architecture and parallel execution capabilities1. XS advanced supports several programming languages and execution environments, such as Java and Node.js, and also provides compatibility with XS classic model2. To develop native SAP HANA applications in XS advanced, you can use the following new components:

• Git repository: XS advanced integrates with Git, a distributed version control system, to manage the source code of your applications. You can use Git to clone, create, push, pull, merge, and branch your projects, and also to collaborate with other developers3.
• SAP Web IDE for SAP HANA: XS advanced provides a web-based integrated development environment (IDE) that allows you to create, edit, test, debug, and deploy your applications. SAP Web IDE for SAP HANA supports various development tools and features, such as editors, wizards, templates, code completion, syntax highlighting, code analysis, debugging, testing, and deployment3.

The other options are not correct because:

• SAP HANA repository: This is a component of XS classic model, not XS advanced. The SAP HANA repository stores the design-time artifacts of your applications, such as views, procedures, and scripts. In XS advanced, the design-time artifacts are stored in Git repositories instead4.
• SAP HANA studio: This is a desktop-based IDE that can be used to develop applications for XS classic model, but not for XS advanced. SAP HANA studio provides various perspectives and tools to access and manage the SAP HANA database, such as the administration console, the catalog, the content, and the security4.

References: 2: SAP HANA Extended Application Services, Advanced Model 4: SAP HANA Extended Application Services 1: SAP HANA extended application services, advanced model 3: SAP HANA Developer Guide for SAP HANA XS Advanced Model (SAP Web IDE)

 To create a calculation view in a multi-target application, you need to use the SAP Web IDE for SAP HANA, which is a web-based development environment that supports the full development lifecycle of SAP HANA applications. The SAP Web IDE for SAP HANA provides graphical and code-based editors for creating calculation views, as well as other database artifacts, such as tables, views, procedures, functions, and more. You can also use the SAP Web IDE for SAP HANA to create and deploy multi-target applications, which are modular applications that consist of multiple components, such as database modules, Node.js modules, Java modules, HTML5 modules, etc. The other options are incorrect because the SAP HANA database explorer, the SAP HANA Web-based Development Workbench, and the SAP HANA studio do not support the creation of calculation views in a multi-target application. The SAP HANA database explorer is a web-based tool that allows you to browse, manage, and query SAP HANA databases, but not to create or edit database artifacts. The SAP HANA Web-based Development Workbench is a deprecated tool that was used to create and edit SAP HANA XS classic applications, but not multi-target applications. The SAP HANA studio is a desktop tool that was used to create and edit SAP HANA native applications, but not multi-target applications. References:

• SAP Web IDE for SAP HANA - SAP Help Portal
• Creating Calculation Views - SAP Help Portal
• Multi-Target Applications - SAP Help Portal
• SAP HANA Database Explorer - SAP Help Portal
• SAP HANA Web-based Development Workbench - SAP Help Portal
• [SAP HANA Studio] - SAP Help Portal

 To manage an exception in a SQLScript, you can use the SIGNAL and RESIGNAL features, which are SQLScript statements that allow you to raise and handle errors or warnings in your code. The SIGNAL statement allows you to raise a user-defined exception with a specified message and SQLSTATE value. The RESIGNAL statement allows you to propagate an existing exception to the calling procedure or function, or to modify the message or SQLSTATE value of the exception. You can use the SIGNAL and RESIGNAL statements in combination with the BEGIN and END blocks, and the DECLARE and EXIT HANDLER clauses, to define the scope and the action of the exception handling12.

The other options are not correct because they are not SQLScript features that can be used to manage an exception. The DECLARE EXIT HANDLER clause is a SQL feature that allows you to declare a handler for a specific condition or a generic SQLWARNING, SQLEXCEPTION, or NOT FOUND condition. The CREATE EXIT HANDLER statement is not a valid SQL or SQLScript statement at all. References:

• SAP HANA Platform, SAP HANA SQL and System Views Reference, SQL Reference Manual, SQL Statements, SIGNAL
• SAP HANA Platform, SAP HANA SQL and System Views Reference, SQL Reference Manual, SQL Statements, RESIGNAL

According to the SAP HANA Developer Guide, XSODATA supports the following HTTP commands to define the operations on the resources:

• DGET: Retrieves a single entity or a collection of entities from the data source.
• DPUT: Updates an existing entity in the data source.
• POST: Creates a new entity in the data source.
• DELETE: Deletes an existing entity from the data source.

The READ and INSERT commands are not valid HTTP commands for XSODATA. They are keywords that can be used in the service definition file (.xsodata) to specify the access mode for each entity set. References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111

In Node.js, the package.json file is used to define external module dependencies. A module is a piece of code that can be reused and shared by other applications. A dependency is a module that is required by another module to function properly. The package.json file contains a list of dependencies with their names and versions, as well as other metadata about the application, such as name, description, version, scripts, and license. The package.json file allows the Node.js application to install and manage the dependencies using the npm command-line tool. The other files are not used to define external module dependencies in Node.js. The mta.yaml file is used to define the structure and dependencies of a multi-target application. The pom.xml file is used to define the configuration and dependencies of a Maven project. The server.js file is used to define the main entry point and logic of a Node.js application. References:

• SAP HANA 2.0 SPS06 - Application Development for SAP HANA1, Section 5.2.1, p. 135-136
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.1, p. 15-16
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.2, p. 17-18
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.3, p. 19-20
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.4, p. 21-22
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.5, p. 23-24
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.6, p. 25-26
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.7, p. 27-28
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.8, p. 29-30
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.9, p. 31-32
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.10, p. 33-34
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.11, p. 35-36
• SAP HANA 2.0 SPS06 - Node.js Development2, Section 2.12, p. 37-38

 SAP HANA, express edition is a streamlined version of SAP HANA that can run on laptops and other resource-constrained hosts, such as a cloud-hosted virtual machine. SAP HANA, express edition is free to use for in-memory databases up to 32 GB of RAM. SAP HANA, express edition supports the following services:

• Text analytics: This service allows you to analyze unstructured text data, such as documents, emails, tweets, and blogs, using natural language processing techniques. You can use text analytics to extract entities, facts, sentiments, and keywords from text data, and to perform linguistic analysis, such as tokenization, lemmatization, and part-of-speech tagging.
• Multi-core and parallelization: This service allows you to leverage the multi-core architecture and parallel processing capabilities of SAP HANA to optimize the performance of data-intensive operations, such as queries, calculations, and transformations. You can use multi-core and parallelization to distribute the workload across multiple CPU cores and threads, and to execute tasks in parallel or in batches.
• Columnar OLTP and OLAP: This service allows you to store and process data in a columnar format, which enables faster data compression, aggregation, and analysis. You can use columnar OLTP and OLAP to support both transactional and analytical workloads on the same data set, without requiring data duplication or pre-aggregation.

The other options are not correct because:

• A. Dynamic tiering: This service allows you to extend the SAP HANA in-memory database with disk-based tables that can store large volumes of warm or cold data. You can use dynamic tiering to reduce the memory footprint and cost of SAP HANA, while still maintaining query access to the disk-based data. However, dynamic tiering is not supported by SAP HANA, express edition, as it requires additional hardware and software components.
• D. System replication: This service allows you to create and maintain one or more secondary SAP HANA systems that are identical copies of a primary SAP HANA system. You can use system replication to ensure high availability and disaster recovery of SAP HANA, as the secondary systems can take over the role of the primary system in case of a failure. However, system replication is not supported by SAP HANA, express edition, as it requires additional licenses and configuration.

References:

• SAP HANA, express edition, Overview
• SAP HANA, express edition, Features
• SAP HANA, express edition, FAQ

You can use APPLY_FILTER to add a dynamic WHERE clause on SELECT statements that query database tables or intermediate table variables. Database tables are persistent tables that store data in the SAP HANA database. Intermediate table variables are variables that store temporary results of SQL queries in a tabular format. You can use APPLY_FILTER to define data transformations and data flows without using imperative statements or side effects1.

The other two options, scalar variables and virtual tables, are not objects that can be applied with the filter. Scalar variables are variables that store single values of a specific data type. You cannot use APPLY_FILTER on scalar variables, as they are not tabular data sources. Virtual tables are tables that provide access to remote data sources, such as other SAP HANA databases or external systems. You cannot use APPLY_FILTER on virtual tables, as they are not supported by the function2. References: 1: APPLY_FILTER | SAP Help Portal 2: Virtual Tables | SAP Help Portal

Graphical calculation views are graphical or scripted views that can be used for complex calculations and data transformations in SAP HANA. There are three types of graphical calculation views: cube, dimension, and SQL access only. Cube and cube with star join are the only types that can handle measures, which are numeric values that can be aggregated, such as sales amount or quantity. Dimension views are used to model master data or attributes, such as product name or customer ID. SQL access only views are used to expose the data of another view without any additional logic or transformation. References:

• SAP HANA 2.0 SPS06 - Application Development for SAP HANA1, Section 4.1, p. 77-78
• SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.1, p. 7
• SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.2, p. 8-9
• SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.3, p. 10-11
• SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.4, p. 12-13
• SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.5, p. 14-15

According to the SAP HANA Developer Guide, to perform a specific task of an XS advanced application, a user needs to have directly assigned a role collection. A role collection is a set of roles that grant the user the necessary privileges and authorizations to access and use the application. A role collection can be assigned to a user either directly by an administrator, or indirectly by a workflow or a self-service. The other options are incorrect, because:

• To have directly assigned a scope is not a way to perform a specific task of an XS advanced application, but a way to limit the access of a user to a subset of resources within an application. A scope is a qualifier that can be added to a role to restrict the user’s access to a specific resource, such as a space, an organization, or a service instance. A scope does not grant any privileges or authorizations by itself, but only modifies the existing ones.
• To be assigned to an organization is not a way to perform a specific task of an XS advanced application, but a way to group users and resources in a logical unit. An organization is a container that holds spaces, users, applications, and services. An organization can have one or more spaces, which are isolated environments for developing, deploying, and running applications. A user can belong to one or more organizations, but can only perform tasks in the spaces that they are assigned to.
• To be assigned to a space is not a way to perform a specific task of an XS advanced application, but a way to access a specific environment for developing, deploying, and running applications. A space is a sub-container within an organization that holds applications and services. A space can have one or more users, who can have different roles and permissions depending on their tasks. A user can belong to one or more spaces within an organization, but can only perform tasks in the spaces that they are assigned to.

References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111.

 To create a graphical representation of an individual SQL statement, you can use the Plan trace. The Plan trace is a tool that allows you to generate and visualize the execution plan of an SQL statement, with estimated or actual performance information for each operator. The Plan trace can help you understand and analyze the query optimization and execution process, and identify potential performance bottlenecks or improvement opportunities12.

The other options, Expensive statements trace, Performance trace, and SQL trace, are not tools that can create a graphical representation of an individual SQL statement. The Expensive statements trace is a tool that records the SQL statements that exceed a certain threshold of resource consumption, such as CPU time, memory, or disk reads. The Expensive statements trace can help you identify the most resource-intensive queries in the system, but it does not provide a graphical view of the execution plan3. The Performance trace is a tool that records the performance statistics of the database operations, such as SQL statements, transactions, procedures, or triggers. The Performance trace can help you measure and compare the performance of different database operations, but it does not provide a graphical view of the execution plan either. The SQL trace is a tool that captures every SQL statement that enters the database at the session layer. The SQL trace can help you monitor and troubleshoot the SQL statements that are executed in the database, but it does not provide a graphical view of the execution plan either. References: 1: Plan Trace | SAP Help Portal 2: Analyzing SQL Execution with the Plan Visualizer | SAP Help Portal 3: Expensive Statements Trace | SAP Help Portal : [Performance Trace | SAP Help Portal] : [SQL Trace | SAP Help Portal]

Dynamic SQL allows you to construct and execute SQL statements at run time, using variables and expressions that may not be supported in SQLScript. However, it also has some drawbacks, such as:

• Limited opportunities for optimization: The SQL statement is potentially recompiled every time it is executed, which may affect the performance and resource consumption. The optimizer cannot use static information, such as data types, cardinalities, or indexes, to generate an optimal execution plan. The statement may also bypass the SQL cache, which stores the results of frequently executed queries for faster retrieval.
• Additional SQL execution privileges are required: The user who executes the dynamic SQL statement must have the necessary privileges to access the objects and operations referenced in the statement. This may pose a security risk, as the user may gain access to sensitive data or perform unauthorized actions. To prevent SQL injection attacks, the dynamic SQL statement should be validated and sanitized before execution.

The other options are incorrect, because:

• It is possible to bind the result of a dynamic SQL statement to a SQLScript variable, using the INTO clause of the EXECUTE IMMEDIATE statement. For example, EXECUTE IMMEDIATE 'SELECT COUNT(*) FROM "TABLE"' INTO lv_count;
• It is possible to use SQLScript variables in a dynamic SQL statement, using the USING clause of the EXECUTE IMMEDIATE statement. For example, EXECUTE IMMEDIATE 'SELECT * FROM "TABLE" WHERE "COLUMN" = ?' USING lv_value;

References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111.

According to the SAP HANA Developer Guide, a multi join is a join that can be defined only with multi-column join in calculation views. A multi join allows you to join multiple data sources using multiple join conditions. You can specify the join type, the join cardinality, and the join columns for each pair of data sources. A multi join is useful when you need to join data sources that have complex relationships or different granularities. The other options are incorrect, because:

• A dynamic join is a join that can be defined with either single-column join or multi-column join in calculation views. A dynamic join allows you to join two data sources using a join condition that is evaluated at run time based on the user input. You can specify the join type, the join cardinality, and the join columns as parameters or variables.
• A text join is a join that can be defined with either single-column join or multi-column join in calculation views. A text join allows you to join a data source with a text table that contains language-dependent descriptions of the data. You can specify the join type, the join cardinality, and the join columns as well as the language column and the language code.
• A temporal join is a join that can be defined with either single-column join or multi-column join in calculation views. A temporal join allows you to join a data source with a history table that contains time-dependent versions of the data. You can specify the join type, the join cardinality, and the join columns as well as the validity columns and the validity period.

References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111.

According to the SAP HANA Developer Guide, the resource path of an OData service URL identifies the entity or entity set that is requested. The resource path consists of the service root URI followed by a slash (/) and the name of the entity set. For example, to view all available products in the Products entity set, the resource path is /Products. The other options are incorrect, because:

• /Products/$metadata is not a valid resource path, but a system query option that returns the metadata document of the OData service.
• /Products/’ is not a valid resource path, but a syntax error. The single quotation mark is not needed after the entity set name.
• /Products/ALL is not a valid resource path, but a filter expression that can be used as a query option. The filter expression must be preceded by a question mark (?) and the $filter system query option. For example, /Products?$filter=ALL.

References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111.

 To see the commits applied to the file in the remote Git repository without syncing the file, you need to use the git fetch command. This command downloads the latest changes from the remote repository to your local repository, but does not merge them with your local branches. This way, you can inspect the differences between your local and remote files, and decide whether to merge them later or not. You can use the SAP Web IDE for SAP HANA or the command line to execute the git fetch command. The other options are incorrect because they either sync the file or do not download the changes from the remote repository. The git stash command saves your local changes to a temporary stash and reverts your working directory to the last commit. This command is useful when you want to switch branches or pull changes without committing your local changes, but it does not download the changes from the remote repository. The git merge command combines the changes from one branch into another branch. This command is useful when you want to sync your local branch with the remote branch, but it does not allow you to see the commits applied to the file before merging. The git pull command fetches and merges the changes from the remote repository into your local branch. This command is useful when you want to update your local branch with the latest changes from the remote branch, but it does not allow you to see the commits applied to the file before merging. References:

• Git Fetch - SAP Help Portal
• Git Merge - SAP Help Portal
• Git Pull - SAP Help Portal
• Git Stash - SAP Help Portal
• HA100 - SAP HANA 2.0 SPS06 Introduction - SAP Training

According to the SAP HANA Developer Guide, the SAP HANA Deployment Infrastructure (HDI) uses so-called containers to store design-time artifacts and the corresponding deployed run-time (catalog) objects. The HDI makes a strict separation between design-time and run-time objects by introducing the following, distinct container types:

• Design-time container (DTC): A Git repository that stores the design-time artifacts, such as CDS files, SQL files, or HDB files, that define the database objects in the persistence model. The DTC is part of the database module of the multi-target application (MTA).
• Run-time container (RTC): A schema in the SAP HANA database that stores the run-time objects, such as tables, views, or procedures, that are created based on the design-time artifacts. The RTC is also known as the HDI container.
• Build container (BTC): A temporary schema in the SAP HANA database that is used to build the run-time objects from the design-time artifacts. The BTC is deleted after the build process is completed.

When you define a database object in the persistence model, you create a design-time artifact in the DTC. When you deploy the database module of the MTA, the HDI creates an RTC and a BTC, and builds the corresponding run-time object in the RTC based on the design-time artifact. The BTC is then dropped, and the RTC remains as the HDI container for the database module. References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111.

SAPUI5 is a JavaScript-based UI framework that enables the development of web applications that run on various devices and platforms. SAPUI5 has the following characteristics12:

• Provides an extensibility concept: SAPUI5 allows developers to extend or customize the standard UI components, such as controls, views, or controllers, to meet specific requirements or scenarios. SAPUI5 also supports the creation of custom UI components, which are reusable and modular UI elements that can be integrated into other SAPUI5 applications.
• Enables responsive application design: SAPUI5 supports the development of responsive applications, which are applications that adapt to different screen sizes, orientations, and resolutions, and provide a consistent and optimal user experience across different devices. SAPUI5 provides various layout options, such as grids, panels, or flexboxes, to arrange the UI elements according to the available space. SAPUI5 also provides various UI patterns, such as master-detail, split-screen, or full-screen, to organize the application content and navigation according to the device type.
• Supports customer-specific theming: SAPUI5 allows developers to apply different themes to the UI components, such as colors, fonts, icons, or backgrounds, to match the branding or style of the customer or the application. SAPUI5 provides a set of predefined themes, such as SAP Fiori, SAP Belize, or SAP Quartz, that follow the SAP design guidelines and principles. SAPUI5 also provides tools, such as the UI Theme Designer or the SAPUI5 Theme Builder, to create or modify custom themes.

The other options are not correct because they are not characteristics of SAPUI5. SAPUI5 does not render the UI on the server side, but rather on the client side, in the browser or the device that accesses the application. SAPUI5 does not provide a device-specific user experience, but rather a device-agnostic user experience, which means that the application can run on any device and platform without requiring any changes or adaptations. References:

• SAP HANA Platform, Developing Applications with SAP HANA Cloud Platform, Developing Multi-Target Applications, Developing HTML5 Modules, Developing SAPUI5 Applications
• SAP HANA Platform, SAP HANA Extended Application Services, Advanced Model, Developing and Deploying Applications, Developing SAP Fiori Applications, Developing SAPUI5 Applications

The Technical Configuration section of a Core Data Services (CDS) entity allows you to define properties that affect the physical storage and performance of the entity in the database. You can define the following properties inside the Technical Configuration section1:

• Index: You can create one or more indexes on the entity to improve the query performance. You can specify the index name, the columns to be indexed, and the index type (such as unique, full-text, or spatial)2.
• Storage Type: You can specify the storage type of the entity, such as column store or row store, to optimize the data access and compression. You can also specify the partitioning mode and criteria for the entity, such as hash, range, or round-robin3.

The other two options, Import and Association, are not properties that can be defined inside the Technical Configuration section. Import is a keyword that allows you to import another CDS entity or a database table into the current CDS entity, and use its columns as part of the projection list4. Association is a keyword that allows you to create a relationship between two CDS entities, and use the associated entity’s columns as part of the projection list or the join condition. References: 1: Technical Configuration | SAP Help Portal 2: Index Definition | SAP Help Portal 3: Storage Type | SAP Help Portal 4: Import | SAP Help Portal : [Association | SAP Help Portal]

 You can use declare exit handlers in a SQL Script procedure to handle generic SQL exceptions or specific SQL error codes. An exit handler is a custom handler that defines a block of code to be executed when an exception occurs in the procedure. You can declare an exit handler for a generic SQL exception, which is any error that is raised by the database system, such as syntax errors, constraint violations, or division by zero. You can also declare an exit handler for a specific SQL error code, which is a numeric code that identifies the type and severity of the error, such as 301 for unique constraint violation, or 1299 for no data found12.

The other two options, generic SQL conditions and specific SQL conditions, are not valid arguments for declare exit handlers. A condition is a named exception that can be declared by using a condition variable and optionally associated with an SQL error code. A condition can be used to signal or resignal an exception in the procedure, or to register a continue handler, which is a custom handler that defines a block of code to be executed when an exception occurs, but does not exit the procedure. However, a condition cannot be used to register an exit handler, as the syntax requires an SQL error code or a generic SQL exception12. References: 1: Exception Handling | SAP Help Portal 2: Exception Handling Examples | SAP Help Portal

To access a remote database table object within your HDB module in a Multi-target application project, you need to perform the following activities:

• Create/update the .hdbgrants file providing authorizations for the remote schema. This file defines the privileges that are granted to the HDI container technical users for accessing the remote schema. You need to specify the user-provided service name, the schema name, and the privileges, such as SELECT, INSERT, UPDATE, DELETE, EXECUTE, etc. You can also use the wildcard character (*) to grant privileges on all objects in the remote schema.
• Create a synonym for the remote table object. A synonym is a database object that provides an alternative name for another database object, such as a table, view, or procedure. You can use synonyms to simplify the access to remote objects by avoiding the need to specify the full qualified name. You can create a synonym in your HDB module by using the .hdbsynonym file, where you specify the target object name, the target object schema, and the user-provided service name.
• Create a view that refers to the table. A view is a database object that defines a logical table based on the result set of a SQL query. You can use views to access data from one or more tables, including remote tables, by applying filters, joins, aggregations, calculations, etc. You can create a view in your HDB module by using the .hdbview file, where you specify the SQL query that references the synonym of the remote table object.

The other options are incorrect because you do not need to create a view that refers to a synonym, nor create a synonym that refers to a view. These are redundant steps that do not add any value to the access of the remote table object. References:

• Accessing Remote Data - SAP Help Portal
• Granting Privileges on Remote Schemas - SAP Help Portal
• Creating Synonyms - SAP Help Portal
• Creating Views - SAP Help Portal

To check user input data in your OData request, you need to use the Validation exit type. The Validation exit type is a custom exit that allows you to perform validation of input data and data consistency checks before, after, or during the change operation, or before or after the commit operation. You can specify a maximum of four validation exits per change operation; the exit is registered for the corresponding event with the respective keyword: “before”, “after”, “precommit” or “postcommit”. The validation exit is executed as an SQLScript procedure with a specific signature, and it can raise an error if the input data does not meet the validation criteria1.

The other options, Consistency, Modification, and Verification, are not exit types that you can use to check user input data in your OData request. Consistency is not an exit type, but a property that you can set in the OData service definition to enable or disable the consistency check for the change operations. The consistency check ensures that the data in the database is consistent with the data in the request payload2. Modification is an exit type that allows you to define custom logic to create, update, or delete an entry in an entity set. If a modification exit is specified, it is executed instead of the generic actions provided by the OData infrastructure1. Verification is not an exit type, but a process that you can perform to ensure that the OData service definition is valid and can be activated without errors3. References: 1: Custom Exits for OData Write Requests | SAP Help Portal 2: Consistency Check | SAP Help Portal 3: Verifying the OData Service Definition | SAP Help Portal

SAP HANA 2.0, express edition is a streamlined version of SAP HANA that can run on laptops and other resource-constrained hosts. It supports native SAP HANA application development and can be installed on Linux OS or used as a virtual machine on Microsoft Windows. Installation on Windows Server or Mac OS is not supported by SAP HANA 2.0, express edition. References:

• SAP HANA 2.0 SPS06 - Application Development for SAP HANA1, Section 1.1, p. 5
• SAP HANA, express edition - Installation Guide, Section 1.1, p. 7
• SAP HANA, express edition - FAQ, Question 1

 Filter expressions can be used in a calculation view to restrict or modify the data that is displayed or processed by the view. Filter expressions can be used in the following nodes of a calculation view12:

• Aggregation: An aggregation node is a node that applies aggregation functions, such as sum, count, or average, to the data that is passed from the previous node. Filter expressions can be used in an aggregation node to filter the data before or after the aggregation, or to define the aggregation level or the measure attributes. For example, you can use a filter expression to show only the sales data for a specific region or product category, or to calculate the average revenue per customer.
• Union: A union node is a node that combines the data from two or more nodes that have the same structure and data types. Filter expressions can be used in a union node to filter the data from each input node, or to filter the data from the output node. For example, you can use a filter expression to exclude the duplicate rows from the union result, or to show only the data that matches a certain condition from each input node.

The other options are not correct because filter expressions cannot be used in these nodes of a calculation view. A star join node is a node that joins a fact table with one or more dimension tables, based on the common key attributes. A star join node does not support filter expressions, but it supports input parameters, which are variables that can be used to filter the data at runtime. A rank node is a node that ranks the data according to a specified order and criteria. A rank node does not support filter expressions, but it supports rank filters, which are conditions that can be used to limit the number or percentage of rows in the rank result. References:

• SAP HANA Platform, SAP HANA Modeling Guide for SAP HANA Web Workbench, Calculation Views
• SAP HANA Platform, SAP HANA Developer Guide for SAP HANA Web IDE, Developing Database Modules, Developing Calculation Views, Using Filter Expressions

A multi-target application (MTA) is a single application that consists of multiple modules that are developed using different technologies and designed to run on different target runtime environments. A database module is a module that contains database artifacts, such as tables, views, procedures, or functions, that are deployed to a SAP HANA database. A HANA Deployment Infrastructure (HDI) container is a logical grouping of database objects that are isolated from other containers and schemas in the same database. An HDI container has its own technical user, roles, and privileges, and can be accessed only through a service binding. When a database module is built, the SAP Web IDE for SAP HANA or the SAP Business Application Studio automatically creates an HDI container and binds it as a resource to the database module. It also creates the runtime objects, such as physical tables or views, in the schema associated with the HDI container. Therefore, the runtime objects of a database module are created in the HDI container, which is the correct answer. The other options are incorrect because they are not the environments where the runtime objects of a database module are created. The Java Runtime Environment (JRE) is a software environment that provides the minimum requirements for executing a Java application. The SAP HANA Runtime Tools (HRTT) are a set of tools that enable developers to create, run, and debug SAP HANA native applications in Eclipse. The SAP Web IDE for SAP HANA is a web-based development environment that supports the development of MTA projects and modules. References:

• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 1.1
• SAP HANA Platform 2.0 SPS06: SAP HANA Deployment Infrastructure, Section 1
• SAP HANA Platform 2.0 SPS06: SAP HANA Database Application Development, Section 2.1
• SAP HANA Platform 2.0 SPS06: SAP HANA Database Application Development, Section 2.2
• SAP HANA Platform 2.0 SPS06: SAP HANA Database Application Development, Section 2.3
• SAP Business Application Studio Multitarget Application (MTA) development toolkit, Section 2