Most Recent SAP C_HANADEV_18 Exam Questions & Answers

To exclusively use declarative logic in an SQL Script procedure, you can use TABLE variables and MAP_REDUCE functions. TABLE variables are variables that store intermediate results of SQL queries in a tabular format.You can use TABLE variables to define data transformations and data flows without using imperative statements or side effects1. MAP_REDUCE functions are functions that apply a map function to each row of a table and then aggregate the results using a reduce function.You can use MAP_REDUCE functions to implement complex algorithms and calculations in a declarative way2.

The other two options, COMMIT statement and IF condition, are not operators that can be used to exclusively use declarative logic in an SQL Script procedure. COMMIT statement is a statement that ends a transaction and makes all changes permanent in the database.You cannot use COMMIT statement in a declarative logic, as it is an imperative statement that has a side effect3. IF condition is a condition that executes a block of code based on a boolean expression.You cannot use IF condition in a declarative logic, as it is an imperative construct that introduces control flow4.Reference:1:TABLE Variables | SAP Help Portal2:MAP_REDUCE Function | SAP Help Portal3:COMMIT Statement | SAP Help Portal4:IF Statement | SAP Help Portal

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

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

Join optimization (pruning) is a technique that allows you to omit join fields from the aggregation if they are not requested by the query and they do not affect the result set. Join optimization (pruning) can improve the query performance by reducing the data volume and the number of join operations. However, join optimization (pruning) is only supported for certain types of joins, such as outer join, text join, and referential join. These types of joins preserve the number of records from one of the join partners, regardless of the join condition.Therefore, the join execution does not influence the result set, and the join fields can be safely omitted12.

Inner join is not a type of join that is supported by join optimization (pruning). Inner join is a type of join that only returns the records that have a matching partner in both join partners, based on the join condition. Inner join can add or delete records from the result set, depending on the data and the join condition.Therefore, the join execution does influence the result set, and the join fields cannot be omitted without changing the query semantics12.Reference:1:Optimize Join Execution | SAP Help Portal2:Prerequisites for Pruning Join Columns | SAP Help Portal

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.

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

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