Tag new C_HANADEV_18 exam questions fee

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.

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

The application descriptor file (xs-app.json) is a JSON file that defines the routing and authentication configuration for an HTML5 module in a multi-target application (MTA) project. It is located in the root folder of the HTML5 module and is used by the managed application router to dispatch requests to the appropriate destinations and to authenticate users. Some of the key words that are contained in the xs-app.json file are:
* routes: This is an array of objects that specify the rules for forwarding requests to the back-end microservices or destinations. Each route object has a source property that defines a regular expression to match the request path, and a destination property that defines the name of the destination to which the request should be forwarded. Optionally, a route object can also have other properties, such as authentication, csrfProtection, service, or scope, to further configure the routing behavior.
* authenticationMethod: This is a property that defines the authentication method to be used for the HTML5 module. It can have one of the following values: route, which means that the authentication method is defined by the route configuration; none, which means that no authentication is required; or approuter, which means that the authentication is delegated to the approuter service. The authenticationMethod property can be set at the global level for the entire HTML5 module, or at the route level for a specific route.
The following key words are not contained in the xs-app.json file, but in other files related to the MTA project:
* role-templates: This is an array of objects that define the roles and their corresponding scopes and attributes for the application. The role-templates are defined in the xs-security.json file, which is the application security descriptor file that specifies the security configuration for the application. The xs-security.json file is located in the root folder of the db module and is used by the User Account and Authentication (UAA) service to manage the authorization and trust management for the application.
* tenant-mode: This is a property that defines the tenant mode for the application. It can have one of the following values: dedicated, which means that the application runs in a dedicated schema for each tenant; shared, which means that the application runs in a shared schema for all tenants; or mixed, which means that the application runs in a mixed mode depending on the tenant context. The tenant-mode property is defined in the mta.yaml file, which is the deployment descriptor file that specifies the metadata and dependencies for the MTA project. The mta.yaml file is located in the root folder of the MTA project and is used by the Cloud Foundry environment to deploy the application.
References:
* [SAP HANA Deployment Infrastructure Reference], Chapter 5: HDI with XS Advanced, Section 5.1:
Developing with the SAP Web IDE for SAP HANA, Subsection 5.1.2: Configure Application Routing (xs-app.json), pp. 101-104.
* [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, Subsection 4.1.3: Configure Application Routing (xs-app.json), pp. 77-80.

To specify the target currency for currency conversion in calculation views, you can use one of the following methods:
* In a column: You can associate the measure with an attribute column that contains the target currency code. For example, if you have a table that stores the sales amount and the currency code for each transaction, you can use the currency code column as the target currency for the sales amount measure.
* With an input parameter: You can create an input parameter that allows the user to select or enter the target currency code at runtime. For example, if you want to display the sales amount in different currencies based on the user’s preference, you can use an input parameter as the target currency for the sales amount measure.
* With a fixed value: You can associate the measure with a fixed currency code that is available in the currency table. For example, if you want to display the sales amount in a single currency, such as USD, you can use a fixed value as the target currency for the sales amount measure. References: Associate Measures with Currency, How to perform Currency Conversion in SAP HANA, Implementing Currency Conversion.

The SAP HANA system views that contain information about the object ownership are SCHEMAS and ROLES. The SCHEMAS view provides information about the schemas in the database, including the owner of each schema1. The ROLES view provides information about the roles in the database, including the owner of each role2. The object ownership indicates who has the right to grant or revoke privileges on the object, or to alter or drop the object3.
The other two options, TABLES and OBJECTS, do not contain information about the object ownership. The TABLES view provides information about the tables in the database, but not the owner of each table4. The OBJECTS view provides information about the objects in the database, such as views, procedures, functions, etc., but not the owner of each object5. References: 1: SCHEMAS System View | SAP Help Portal 2: ROLES System View | SAP Help Portal 3: Object Ownership | SAP Help Portal 4: TABLES System View | SAP Help Portal 5: OBJECTS System View | SAP Help Portal

SAP HANA supports two types of user-defined functions: table and scalar. User-defined functions are functions that are created by users to perform specific tasks or calculations on data. User-defined functions can be used in SQL expressions, such as in the SELECT, WHERE, or GROUP BY clauses of SQL statements.
User-defined functions can also be used in SQLScript, which is a scripting language for SAP HANA that extends SQL with procedural and analytical features.
Table functions are user-defined functions that return a table as the output. Table functions can be used to implement complex logic or transformations on data, such as pivoting, unpivoting, aggregation, or ranking.
Table functions can also be used to create calculation views, which are virtual data models that expose data from SAP HANA tables or views. Table functions are created by using the CREATE FUNCTION statement with the RETURNS <return_table_type> clause, where <return_table_type> specifies the table type of the output. Table functions can be called in the FROM clause of SQL statements, or in the node expression of calculation views.
Scalar functions are user-defined functions that return a scalar value as the output. Scalar functions can be used to perform simple calculations or validations on data, such as converting units, checking conditions, or generating IDs. Scalar functions are created by using the CREATE FUNCTION statement with the RETURNS
<return_parameter_list> clause, where <return_parameter_list> specifies the scalar type of the output. Scalar functions can be called in the SELECT or WHERE clauses of SQL statements, or in the expression of calculated columns.
The following types of functions are not supported by SAP HANA as user-defined functions, but as built-in functions or features:
* Aggregate functions: Aggregate functions are functions that perform calculations on a set of values and return a single value. For example, SUM, COUNT, MIN, MAX, or AVG are aggregate functions.
Aggregate functions are built-in functions that are provided by SAP HANA and can be used in SQL expressions, such as in the SELECT or GROUP BY clauses of SQL statements, or in the expression of aggregated columns. Aggregate functions cannot be created by users as user-defined functions.
* Hierarchy functions: Hierarchy functions are functions that operate on hierarchical data, such as parent-child or level-based hierarchies. For example, HIERARCHY_ANCESTORS, HIERARCHY_DESCENDANTS, or HIERARCHY_LEVEL are hierarchy functions. Hierarchy functions are built-in functions that are provided by SAP HANA and can be used in SQL expressions, such as in the SELECT or WHERE clauses of SQL statements, or in the expression of hierarchy columns. Hierarchy functions cannot be created by users as user-defined functions.
References:
* [SAP HANA Platform Documentation], SAP HANA SQL and System Views Reference, Chapter 3:
SQL Expressions, Section 3.5: Function Expressions, pp. 59-60.
* [SAP HANA Platform Documentation], SAP HANA SQLScript Reference, Chapter 6: SQLScript Test Framework, Section 6.1: User-Defined Functions, pp. 153-154.

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