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

An HTML5 module is a module that contains static web content, such as HTML, CSS, JavaScript, or images, that are delivered by a web server. An HTML5 module can be part of a multi-target application (MTA) project, which is a single application that consists of multiple modules that are developed using different technologies and designed to run on different target runtime environments. An HTML5 module can be deployed to the XS Advanced runtime environment, which is a platform that supports the development and execution of cloud-native applications on SAP HANA.

To change the file that is initially delivered by an HTML5 module, you need to adapt the welcome file parameter of the xs-app.json file. The xs-app.json file is a configuration file that defines the routing rules and authentication settings for the HTML5 module. The welcome file parameter specifies the name of the file that is served as the default document when the root path of the HTML5 module is requested. For example, if the welcome file parameter is set to “index.html”, then the file index.html in the HTML5 module will be delivered when the user accesses the URL of the HTML5 module without any additional path. The welcome file parameter can be changed to any valid file name that exists in the HTML5 module.

The other options are incorrect because they are not parameters that can be used to change the file that is initially delivered by an HTML5 module. The service_url parameter of the mta.xml file is a parameter that defines the URL of a service that is required by a module or provided by a resource in an MTA project. The start parameter of the package.json file is a parameter that defines the script that is executed when the npm start command is run in a Node.js module. The runners parameter of the project.json file is a parameter that defines the configuration of the runners that are used to execute the code in a Cloud Foundry module. References:

• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 1.1
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 1.3
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 2.1
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 2.2
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 2.3
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 2.4
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 2.5
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 2.6
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 2.7
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 2.8
• SAP HANA Platform 2.0 SPS06: Developing Multitarget Applications, Section 2.9

To complete the navigation definition from the customer entity set to the corresponding sales orders, you need to insert an association statement between the two entity sets. An association defines a relationship between two entity sets based on a referential constraint, which specifies the foreign key and the principal key properties that link the entity sets. An association also defines the cardinality and the role names of the entity sets involved in the relationship1. In this case, the association statement should look something like this:

association Customer_Orders with referential constraint principal customer key CustomerID dependent Orders key CustomerID multiplicity “1” to “*”;

This statement defines an association named Customer_Orders that relates the customer entity set with the Orders entity set based on the CustomerID property. The principal role is assigned to the customer entity set, which means that each customer entity can have zero or more related Orders entities. The dependent role is assigned to the Orders entity set, which means that each Orders entity must have exactly one related customer entity2.

The other options are not correct because:

• Aggregation: This is a feature of calculation views that allows you to define measures and attributes for analytical queries. It is not related to OData service definitions3.
• Key specification: This is a clause that you use to define the key properties of an entity type in an OData service definition. It is not used to define navigation between entity sets1.
• Join condition: This is a clause that you use to specify how to join two tables or views in a SQL statement. It is not used to define navigation between entity sets4.

References: 1: OData Service Definition Language Syntax (XS Advanced) 2: OData Service-Definition Examples 3: Creating Calculation Views 4: SQL Reference Manual

According to the SAP Web IDE for SAP HANA Developer Guide, the Node.js environment is characterized by the following features:

• It is single-threaded: Node.js uses a single thread to handle multiple concurrent requests, instead of creating a new thread for each request. This reduces the memory and CPU overhead, and enables high scalability and performance. However, it also means that any blocking or long-running operation can affect the responsiveness of the entire application. Therefore, Node.js relies on asynchronous and non-blocking I/O operations, callbacks, promises, and events to handle concurrency and avoid blocking the main thread.
• It is built on Google’s V8 JavaScript engine: Node.js uses the V8 engine to execute JavaScript code. The V8 engine is a fast and powerful engine that compiles JavaScript code into native machine code, and supports the latest ECMAScript standards and features. The V8 engine also provides access to low-level system resources, such as files, network, and processes, through the Node.js API.

The other options are incorrect, because:

• Node.js does not use a synchronous programming model, but an asynchronous and event-driven programming model. A synchronous programming model means that each operation blocks the execution until it is completed, and the next operation can only start after the previous one is finished. An asynchronous programming model means that each operation can start without waiting for the previous one to finish, and the execution can continue with other tasks while the operation is in progress. An event-driven programming model means that each operation can trigger an event when it is completed, and the event can invoke a callback function that handles the result or the error of the operation.
• Node.js is not a client-side design-time environment for JavaScript, but a server-side run-time environment for JavaScript. A client-side design-time environment for JavaScript means that the JavaScript code is written and executed in the browser, and it can manipulate the HTML document and interact with the user interface. A server-side run-time environment for JavaScript means that the JavaScript code is written and executed on the server, and it can handle HTTP requests and responses, communicate with databases, and perform business logic.

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

To develop a Node.js application for the SAP HANA platform that executes a SQL statement in the SAP HANA database, you need to use the following modules:

• @sap/xsenv: This module provides functions to load service configuration and credentials from the environment variables of the SAP Cloud Platform or the SAP HANA XS Advanced Model. You can use this module to access the SAP HANA database service information, such as host, port, user, password, and schema.
• @sap/hdbext: This module provides a wrapper for the SAP HANA client for Node.js, which enables you to connect to the SAP HANA database and execute SQL statements. You can use this module to create a database connection pool, execute queries, fetch results, and handle errors.

The other options are not correct because:

• A. @sap/instance-manager: This module provides functions to manage the lifecycle of Node.js applications running on the SAP Cloud Platform or the SAP HANA XS Advanced Model. You can use this module to start, stop, restart, scale, and monitor your applications, but not to execute SQL statements in the SAP HANA database.
• D. @sap/node-vsi: This module provides functions to interact with the SAP HANA Virtual Schema Integrator (VSI), which enables you to access data from remote sources using virtual tables. You can use this module to create, update, delete, and query virtual tables, but not to execute SQL statements in the SAP HANA database.

References:

• SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.2
• SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.3
• SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.4
• SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.5

The package.json file is the main configuration file for a Node.js module. It contains various metadata about the module, such as its name, version, dependencies, scripts, and main entry point. The main entry point is the program that is executed when the module is run or required by another module. By default, the main entry point is index.js, but it can be changed by specifying the main property in the package.json file12. For example, if the main property is set to “server.js”, then the server.js file will be executed upon start up when the module is run.

The other options are not correct because:

• project.json: This is not a standard configuration file for Node.js modules. It may be used by some frameworks or tools, but it is not recognized by Node.js itself3.
• server.js: This is a common name for a file that contains the server logic for a Node.js module, but it is not a configuration file. It may be the main entry point for the module, but only if it is specified in the package.json file4.
• mta.yaml: This is a configuration file for multi-target applications (MTAs) in SAP HANA XS advanced model. It defines the modules, resources, and dependencies of an MTA, but it is not specific to Node.js modules5.

References: 1: package.json | Node.js v17.0.1 Documentation 2: Debugging in Visual Studio Code 3: How to run Node.js module initialization properly - Stack Overflow 4: Running Node.js Apps with PM2 (Complete Guide) - Better Stack 5: SAP HANA Developer Guide for SAP HANA XS Advanced Model (SAP Web IDE)

The mta.xml file is the main descriptor file for a multi-target application (MTA). It defines the application global elements, such as ID, version, provider, and schema version. It also defines the modules, which are the components of the application that provide specific functionality, such as a database module, a Node.js module, or an HTML5 module. Each module has a name, a type, a path, and a list of required dependencies. The mta.xml file also defines the resources, which are the shared services or configurations that the modules can consume, such as a user-provided service, an SAP HANA database, or an SAP HANA HDI container. Each resource has a name, a type, and optional parameters. The mta.xml file also defines the properties and parameters, which are the key-value pairs that can be used to configure the modules and resources, such as the host, port, or credentials. The properties and parameters can be defined globally, per module, or per resource12.

The other options are not correct because they are not part of the mta.xml file, but rather of other files or components of the MTA. The plugin name and version for every supported file suffix are defined in the .che file, which is the configuration file for the SAP Web IDE3. The application router description with the authentication methods and access routes are defined in the xs-app.json file, which is the configuration file for the application router, a Node.js module that provides a single entry point and routing mechanism for the MTA. The Node.js package definition with dependencies and initial run configurations are defined in the package.json file, which is the configuration file for the Node.js module that contains the application logic and business services. References:

• SAP HANA Platform, Developing Applications with SAP HANA Cloud Platform, Developing Multi-Target Applications
• SAP HANA Platform, SAP HANA Extended Application Services, Advanced Model, Developing and Deploying Applications, Descriptor Files, mta.xml
• SAP HANA Platform, Developing Applications with SAP HANA Cloud Platform, Developing Multi-Target Applications, Descriptor Files, .che
• [SAP HANA Platform], SAP HANA Extended Application Services, Advanced Model, Developing and Deploying Applications, Descriptor Files, xs-app.json
• [SAP HANA Platform], SAP HANA Extended Application Services, Advanced Model, Developing and Deploying Applications, Descriptor Files, package.json

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

OData associations are used to define the relationships between two or more entity types in an OData service. Associations can be simple or complex, depending on whether the relationship information is stored in one of the participating entities or in a separate association table. Associations are composed of two ends, each of which has a role name, a multiplicity, and a set of properties that form the referential constraint. The keywords that are used to define an OData association are:

• DEPENDENT: This keyword is used to specify the role name of the dependent end of the association, which is the entity type that contains the foreign key properties that refer to the principal entity type. For example, in the association Customer_Orders, the entity type Orders is the dependent end, as it contains the property CustomerID that refers to the entity type Customers.
• MULTIPLICITY: This keyword is used to specify the cardinality of each end of the association, which indicates how many instances of one entity type can be related to one instance of another entity type. The possible values for multiplicity are: 0…1 (zero or one), 1 (exactly one), or * (many). For example, in the association Customer_Orders, the multiplicity of the principal end Customers is 1, meaning that each customer can have only one instance, and the multiplicity of the dependent end Orders is *, meaning that each customer can have many orders.
• PRINCIPAL: This keyword is used to specify the role name of the principal end of the association, which is the entity type that is referenced by the foreign key properties of the dependent entity type. For example, in the association Customer_Orders, the entity type Customers is the principal end, as it is referenced by the property CustomerID of the entity type Orders.

The following keywords are not used to define an OData association, but for other purposes:

• JOIN: This keyword is used to specify the join condition between two entity sets in a query expression, which is used to retrieve data from multiple sources. For example, the query expression Customers?$expand=Orders($filter=Status eq ‘Open’) uses a join condition to filter the orders that have the status ‘Open’ for each customer.
• UNION: This keyword is used to specify the union operation between two query expressions, which is used to combine the results of both queries into one result set. For example, the query expression Customers?$filter=Country eq ‘US’ union Customers?$filter=Country eq ‘CA’ uses a union operation to get the customers that are from either the US or Canada.

A role template is a JSON file that defines the permissions and scopes for a specific role in a multi-target application. A scope is a string that represents a specific access right or privilege for a resource or service. For example, a scope can be used to grant read or write access to a database table or an OData service. A role template references the scopes that are required for the role to function properly. A role collection is a group of roles that can be assigned to a user or a group. A role is a collection of permissions and scopes that define what a user can do in an application. A route is a mapping between a URL path and a destination service in a multi-target application. A route is not related to a role template. References:

• SAP HANA 2.0 SPS06 - Application Development for SAP HANA1, Section 6.1.1, p. 147-148
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.1, p. 25-26
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.2, p. 27-28
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.3, p. 29-30
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.4, p. 31-32
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.5, p. 33-34
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.6, p. 35-36
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.7, p. 37-38
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.8, p. 39-40
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.9, p. 41-42
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.10, p. 43-44
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.11, p. 45-46
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.12, p. 47-48
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.13, p. 49-50
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.14, p. 51-52
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.15, p. 53-54
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.16, p. 55-56
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.17, p. 57-58
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.18, p. 59-60
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.19, p. 61-62
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.20, p. 63-64
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.21, p. 65-66
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.22, p. 67-68
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.23, p. 69-70
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.24, p. 71-72
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.25, p. 73-74
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.26, p. 75-76
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.27, p. 77-78
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.28, p. 79-80
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.29, p. 81-82
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.30, p. 83-84
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.31, p. 85-86
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.32, p. 87-88
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.33, p. 89-90
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.34, p. 91-92
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.35, p. 93-94
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.36, p. 95-96
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.37, p. 97-98
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.38, p. 99-100
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.39, p. 101-102
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.40, p. 103-104
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.41, p. 105-106
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.42, p. 107-108
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.43, p. 109-110
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.44, p. 111-112
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.45, p. 113-114
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.46, p. 115-116
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.47, p. 117-118
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.48, p. 119-120
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.49, p. 121-122
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.50, p. 123-124
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.51, p. 125-126
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment2, Section 3.1.52, p. 127-128
• SAP HANA 2.0 SPS06 - Cloud Foundry Environment

 According to the SAP HANA SQLScript Reference, the following statements can be used when implementing transaction management logic in SQLScript using savepoints:

• Savepoint: Creates a savepoint with a specified name within the current transaction. A savepoint marks a point in the transaction that can be rolled back to without affecting the rest of the transaction. For example, SAVEPOINT sp1;
• Rollback to savepoint: Rolls back the current transaction to the specified savepoint. All changes made after the savepoint are undone, but the transaction remains active. For example, ROLLBACK TO SAVEPOINT sp1;
• Release savepoint: Releases the specified savepoint and all subsequent savepoints. The released savepoints are no longer valid and cannot be rolled back to. For example, RELEASE SAVEPOINT sp1;

The other options are incorrect, because:

• Reverse savepoint is not a valid statement in SQLScript. There is no such statement in the SAP HANA SQLScript Reference.
• Alter system savepoint is not a statement that can be used in SQLScript, but a statement that can be used in SQL. It triggers a savepoint operation for the entire database system, not for a specific transaction. It is used for administrative purposes, such as backup and recovery, not for transaction management logic.

References: SAP HANA SQLScript Reference, Chapter 6, Section 6.4.2, page 2111.

Property projection is an OData capability that allows you to restrict the number or selection of exposed columns in an OData service. Property projection is achieved by using the $select query option, which specifies a subset of properties to be included in the response. The $select query option can be applied to a single entity, a collection of entities, or a complex type. Property projection can be used to reduce the payload size and improve the performance of the OData service.

For example, suppose you have an OData service that exposes a Products entity set with the following properties: ID, Name, Category, Price, and Description. If you want to restrict the number or selection of exposed columns to only ID and Name, you can use the $select query option as follows:

GET /Products?$select=ID,Name

The result is:

{ “@odata.context”: “$metadata#Products(ID,Name)”, “value”: [ { “ID”: 1, “Name”: “Laptop” }, { “ID”: 2, “Name”: “Mouse” }, { “ID”: 3, “Name”: “Keyboard” } ] }

The following OData capabilities are not used to restrict the number or selection of exposed columns, but for other purposes:

• Parameter entity sets: Parameter entity sets are a way to define entity sets that require one or more parameters to be specified in the request. Parameter entity sets can be used to implement function imports or actions that return a collection of entities. Parameter entity sets can also be used to filter or sort the results based on the parameters.
• Aggregation: Aggregation is a way to apply aggregate functions, such as sum, count, min, max, or average, to the properties of an entity set or a complex type. Aggregation can be used to perform calculations or analysis on the data. Aggregation is achieved by using the $apply query option, which specifies a transformation pipeline with various operators, such as groupby, aggregate, filter, or order by.
• Key specification: Key specification is a way to define the key properties of an entity type, which uniquely identify an entity instance within an entity set. Key specification is part of the entity type definition in the metadata document of the OData service. Key specification can be used to retrieve a single entity by its key values.

References:

• [OData Version 4.0 Part 2: URL Conventions], Section 5.1.1: System Query Option $select, pp. 10-11.
• [OData Version 4.0 Part 3: Common Schema Definition Language (CSDL)], Section 13: Entity Model, Subsection 13.2: Entity Sets, pp. 88-89.

The SAP Web IDE for SAP HANA is a web-based development tool that allows you to create and manage multi-target applications (MTAs) that use the SAP HANA Deployment Infrastructure (HDI). HDI is a service layer that enables you to deploy database development artifacts to HDI containers, which are isolated schemas that represent runtime objects. Some of the operations that you can perform in the SAP Web IDE for SAP HANA are:

• Deploy HTML5 modules to the SAP HANA database: HTML5 modules are web applications that run on the XS advanced runtime and can access HDI containers via service bindings. You can create, edit, test, and deploy HTML5 modules from the SAP Web IDE for SAP HANA using the MTA development perspective and the build and run commands. You can also use the HTML5 module template wizard to generate a basic HTML5 module with the required configuration files and dependencies.
• Configure the artifact namespaces: Artifact namespaces are prefixes that are added to the names of the database artifacts that are deployed to the HDI containers. They help to avoid name conflicts and to organize the artifacts in a logical way. You can configure the artifact namespaces in the SAP Web IDE for SAP HANA by editing the .hdiconfig file in the db module of your MTA project. You can also use the namespace template wizard to generate a .hdiconfig file with a default namespace.

The following operations are not possible or not recommended in the SAP Web IDE for SAP HANA:

• Create objects in the SAP HANA repository: The SAP HANA repository is a legacy feature that was used to store and manage design-time artifacts in SAP HANA 1.0. It has been deprecated since SAP HANA 2.0 SPS 02 and replaced by HDI. Therefore, you should not create objects in the SAP HANA repository, but rather use HDI containers and the SAP Web IDE for SAP HANA to develop and deploy database artifacts.
• Choose the supported SAP HANA versions: The SAP Web IDE for SAP HANA does not allow you to choose the supported SAP HANA versions for your MTA project. The supported SAP HANA versions depend on the HDI version and the SAP HANA Cloud Platform, which are determined by the target environment where you deploy your MTA project. You can check the compatibility of the HDI version and the SAP HANA Cloud Platform in the SAP HANA Deployment Infrastructure Reference.

References:

• [SAP HANA Deployment Infrastructure Reference], Chapter 5: HDI with XS Advanced, Section 5.1: Developing with the SAP Web IDE for SAP HANA, pp. 101-106.
• [SAP HANA Platform Documentation], SAP HANA Developer Guide for SAP HANA XS Advanced Model, Chapter 4: Developing HTML5 Applications, Section 4.1: Developing HTML5 Applications Using SAP Web IDE for SAP HANA, pp. 77-82.

 When you create a multi-target application in SAP Web IDE for SAP HANA, you use a Git-based repository as the source code management option. A Git-based repository allows you to store, manage, and synchronize your code across multiple branches and versions. You can also collaborate with other developers and integrate your changes with the SAP HANA Deployment Infrastructure (HDI). A Git-based repository is the recommended option for developing multi-target applications in SAP Web IDE for SAP HANA. References: Developing Multi-Target Applications, Git Integration, SAP HANA Deployment Infrastructure.

 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

You can specify the language and the default schema as metadata declarations in a SQL Script procedure when you use the SAP HANA Deployment Infrastructure (HDI). The language declaration defines the language mode of the procedure, which can be SQLSCRIPT or SQL. The default schema declaration defines the schema that is used to resolve unqualified object names in the procedure body. These declarations are optional and can be specified after the procedure name and before the parameter list. For example:

CREATE PROCEDURE MY_PROCEDURE LANGUAGE SQLSCRIPT DEFAULT SCHEMA MY_SCHEMA ( … )

The other options are incorrect because security and authorization are not valid metadata declarations for SQL Script procedures. Security and authorization are handled by the HDI framework, which automatically grants the necessary privileges to the technical users and roles that access the HDI container objects. You do not need to specify any security or authorization clauses in the SQL Script procedure definition. References:

• Procedure Metadata - SAP Help Portal
• CREATE PROCEDURE Statement (Procedural) - SAP Help Portal
• SAP HANA Deployment Infrastructure - SAP Help Portal
• HA150 - SAP HANA 2.0 SPS06 SQLScript for SAP HANA - SAP Training

The correct action is to define a User Details view using select on the user entity and using the association to read the address information. This way, you can leverage the power of CDS associations to create a join between the user and address entities without explicitly specifying the join condition. You can also use the association path to access the address fields in the view definition. This approach simplifies the data model and avoids redundancy. Option A is incorrect because it selects from the address entity instead of the user entity, which is not the desired output. Option B is incorrect because it extends the user entity with address columns, which is unnecessary and violates the normalization principle. Option D is incorrect because it creates a calculation view instead of a CDS view, which is not the requirement. Calculation views are graphical or scripted views that can be used for complex calculations and data transformations, but they are not CDS artifacts. References:

• SAP HANA 2.0 SPS06 - Application Development for SAP HANA1, Section 2.2.2, p. 32-33
• SAP HANA 2.0 SPS06 - Core Data Services for SAP HANA2, Section 2.3, p. 25-26
• SAP HANA 2.0 SPS06 - Calculation View Modeling3, Section 1.1, p. 7

 According to the SAP HANA SQLScript Reference1, database procedures are subroutines that can be called from SQL statements or other database procedures. Database procedures can have the following characteristics:

• Database procedures can have both input and output parameters; however, a parameter CANNOT be both input and output. Input parameters are used to pass values to the procedure, while output parameters are used to return values from the procedure. A parameter can be either scalar or table type, depending on the data type and cardinality. A parameter cannot be both input and output, because this would create ambiguity and inconsistency in the parameter passing mechanism. For example, you cannot declare a parameter as IN OUT, or assign a value to an input parameter, or read a value from an output parameter. For more information on database procedure parameters, see [Parameters of Database Procedures]2.
• Database procedures can have several output parameters, and a mix of both scalar and table types is possible. Output parameters are used to return values from the procedure to the caller. A procedure can have zero or more output parameters, depending on the purpose and logic of the procedure. Output parameters can be either scalar or table type, depending on the data type and cardinality. A procedure can have a mix of both scalar and table output parameters, as long as they are compatible with the caller’s expectations and syntax. For example, you can use a SELECT statement with INTO clause to assign values to scalar output parameters, or use a SELECT statement with RESULT clause to return a table output parameter. For more information on database procedure output parameters, see [Output Parameters of Database Procedures]3.
• If, in the database procedure header, you use the READS SQL DATA option, then INSERT statements are prohibited; however, dynamic SQL is allowed. The READS SQL DATA option is used to indicate that the procedure only reads data from the database, and does not modify or write any data. This option is useful for performance optimization and security enforcement, as it allows the database to apply certain optimizations and checks to the procedure. However, this option also imposes some restrictions on the procedure, such as prohibiting any INSERT, UPDATE, DELETE, or MERGE statements, or any other statements that modify the database state. Dynamic SQL, which is SQL code that is constructed and executed at run time, is still allowed, as long as it does not violate the READS SQL DATA option. For more information on the READS SQL DATA option, see [Procedure Header Options]4.
• If, in the database procedure header, you use the SQL SECURITY INVOKER option, then only the owner of the procedure can start it. The SQL SECURITY INVOKER option is used to indicate that the procedure is executed with the privileges of the user who invokes the procedure, rather than the privileges of the user who created the procedure. This option is useful for security enforcement and access control, as it allows the database to apply the appropriate authorization checks and restrictions to the procedure. However, this option does not affect who can start the procedure, as this is determined by the GRANT EXECUTE statement, which grants the execute privilege on the procedure to a specific user or role. The SQL SECURITY INVOKER option only affects how the procedure is executed, not who can execute it. For more information on the SQL SECURITY INVOKER option, see [Procedure Header Options]4.

References: 1: SAP HANA SQLScript Reference 2: Parameters of Database Procedures 3: Output Parameters of Database Procedures 4: Procedure Header Options

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

 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

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

 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

To initially load data from a .csv file into a Core Data Services (CDS) table in SAP HANA extended application services, advanced model (XS advanced), you need to create a file with extension .hdbti, which stands for HDB Table Import. This file defines the configuration and mapping for importing data from a local or remote file into a table in the HDI container. You can specify the source file name, location, format, delimiter, header, encoding, etc., as well as the target table name, schema, and column mapping. You can also specify whether to truncate the target table before importing, or to append the data to the existing table. You can use the SAP Web IDE for SAP HANA to create and deploy the .hdbti file, or use the HDI deployer CLI tool. The other options are incorrect because they are not the correct file types for importing data into a CDS table. A file with extension .hdbtabledata is a file that contains the data for a table in a JSON format, but it is not used for importing data from a .csv file. A file with extension .hdbtable is a file that defines the structure and properties of a table, but it does not contain any data. A file with extension .hdbdd is a file that defines the CDS entities, such as contexts, types, views, associations, etc., but it does not import any data. References:

• Importing Data into Tables - SAP Help Portal
• Creating Table Import Configuration Files - SAP Help Portal
• HDI Deployer CLI Tool - SAP Help Portal
• [HA300 - SAP HANA 2.0 SPS06 Modeling] - SAP Training

The SAP HANA XS Advanced Cockpit is a web-based administration tool that allows you to manage the XS Advanced runtime environment, such as organizations, spaces, applications, services, and users. The XS Advanced Cockpit provides a graphical user interface that is similar to the SAP Cloud Platform Cockpit, to provide a consistent user experience in cloud and on-premise. The XS Advanced Cockpit is available for SAP HANA 2.0 SPS03 and later releases, and it replaces the deprecated XS Advanced Administration Tools.

One of the activities that you can perform on an application in the XS Advanced Cockpit is to monitor the applications assigned to the current space. A space is a logical grouping of applications and services that share a common development and runtime environment. Each space belongs to an organization, which is a collection of users and spaces that share a common quota of resources. You can use the XS Advanced Cockpit to view the list of applications deployed in a particular space, and see their status, instances, memory usage, disk usage, and bound services. You can also filter, sort, and search the applications by name, status, or type. You can also drill down into the details of each application, such as logs, events, environment variables, routes, and service bindings.

Another activity that you can perform on an application in the XS Advanced Cockpit is to start, stop, and restart the applications. You can use the XS Advanced Cockpit to control the lifecycle of the applications deployed in a space, such as starting an application that is stopped, stopping an application that is running, or restarting an application that is experiencing issues. You can also scale the applications by changing the number of instances or the memory and disk quota allocated to each instance. You can also delete the applications that are no longer needed.

The other options are incorrect because they are not activities that you can perform on an application in the XS Advanced Cockpit. You cannot deploy applications to SAP Cloud Platform from the XS Advanced Cockpit, as the XS Advanced Cockpit is only for managing the XS Advanced runtime environment on SAP HANA. To deploy applications to SAP Cloud Platform, you need to use the SAP Cloud Platform Cockpit or the Cloud Foundry Command Line Interface (CF CLI). You also cannot display the HDI container content from the XS Advanced Cockpit, as the HDI container is a database object that is not directly related to the application. To display the HDI container content, you need to use the SAP HANA Database Explorer or the SAP Web IDE for SAP HANA. References:

• SAP HANA Platform 2.0 SPS06: SAP HANA XS Advanced Cockpit, Section 1
• SAP HANA Platform 2.0 SPS06: SAP HANA XS Advanced Cockpit, Section 2
• SAP HANA Platform 2.0 SPS06: SAP HANA XS Advanced Cockpit, Section 3
• SAP HANA Platform 2.0 SPS06: SAP HANA XS Advanced Cockpit, Section 4
• SAP HANA Platform 2.0 SPS06: SAP HANA XS Advanced Cockpit, Section 5

When a Node.js module is executed for the first time in SAP HANA extended application services, advanced model (XS advanced), the following activities are performed automatically12:

• A new SAP HANA Deployment Infrastructure (HDI) container is created: An HDI container is a logical database schema that contains the database objects and data that are required by the Node.js module. An HDI container is created based on the configuration and definition files of the Node.js module, such as the package.json, the mta.yaml, and the hdi-config.json. The HDI container is bound to the Node.js module as a service, and it can be accessed using the HDI client library or the SQL client library.
• The required modules are downloaded based on module dependencies: The Node.js module may depend on other modules or libraries that provide additional functionality or services, such as express, hdb, or passport. These dependencies are specified in the package.json file of the Node.js module, and they are downloaded and installed automatically from the npm registry or the SAP npm registry when the Node.js module is executed for the first time.

The other options are not correct because they are not activities that are performed automatically when a Node.js module is executed for the first time in XS advanced. The source code is not compiled to create an executable binary file, but rather interpreted and executed by the Node.js runtime environment. A new service is not executed on the application server, but rather the existing Node.js module is executed as a service on the application server. References:

• SAP HANA Platform, Developing Applications with SAP HANA Cloud Platform, Developing Multi-Target Applications, Developing Node.js Modules
• SAP HANA Platform, SAP HANA Extended Application Services, Advanced Model, Developing and Deploying Applications, Developing Node.js Applications

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