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.Reference:

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 produce sales value for the month using sales order line items (sales price per item x quantity sold), you can use a calculated column of a calculation view that performs the multiplication of the two columns and applies a transparent filter and a non-equijoin to restrict the data to the desired month. A transparent filter is a filter condition that is applied to the data source of a view node and is propagated to the subsequent nodes. A non-equijoin is a join condition that uses operators other than equality, such as greater than, less than, or between. For example, you can use a transparent filter to filter the sales order line items by the month of the order date, and then use a non-equijoin to join the sales order line items with the sales price table by the order date and the valid from and valid to dates of the sales price.Reference:Transparent Filters,Non-Equijoins,Create Calculated Columns.

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.Reference:

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

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.Reference:

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

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.