C_HANADEV_18 Practice Exam Questions with Answers SAP Certified Development Associate - SAP HANA 2.0 SPS06 Certification

According to the SAP HANA Developer Guide, declarative logic in SQL Script is a way of expressing complex data transformations by means of classical relational operators, such as selection, projection, join, aggregation, etc. Declarative logic does not specify how data is processed, but rather what the desired result is. The SAP HANA database has the freedom to optimize the data flow and execution plan, which may result in better performance. Declarative logic is free of side effects, meaning that it does not modify any data or state outside the scope of the statement. Declarative logic declares the flow of data, meaning that it binds new variables that are referenced elsewhere in the body of the procedure or function. The other options are incorrect, because:

• Declarative logic does not support the full set of SQL Script, but only a subset of SQL features that are side-effect free and deterministic. For example, declarative logic does not support imperative constructs, such as loops, conditions, exceptions, etc.
• Declarative logic does not define how data is processed, but rather what the desired result is. How data is processed is determined by the SAP HANA database optimizer, which may choose different execution plans depending on the data characteristics, system resources, and other factors.

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

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

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

To set up unit testing for your SQL Script procedure, you use a library with language SQLSCRIPT TEST. A library with language SQLSCRIPT TEST is a special type of library that contains SQL Script test cases for testing the behavior and performance of SQL Script procedures. A SQL Script test case is a SQL Script procedure that has the prefix TEST_ and that uses the ASSERT and EXPECT statements to verify the expected results and outputs of the procedure under test. A library with language SQLSCRIPT TEST can be created in the SAP Web IDE for SAP HANA or in the SAP HANA Studio, and can be executed by using the SQL Script Test Framework, which is a tool that runs the test cases and generates a test report.

The following options are not used to set up unit testing for your SQL Script procedure, but for other purposes:

• SQL Script logging procedures: SQL Script logging procedures are procedures that use the APPLY_FILTER and APPLY_AGGREGATION statements to perform logging operations on table variables or cursors. SQL Script logging procedures can be used to monitor and analyze the execution of SQL Script procedures, but not to test their correctness or functionality.
• The SQL Script debugger: The SQL Script debugger is a tool that allows you to debug SQL Script procedures by setting breakpoints, inspecting variables, and stepping through the code. The SQL Script debugger can be used to identify and fix errors or bugs in SQL Script procedures, but not to verify their expected results or outputs.
• The SQL Script Code Analyzer: The SQL Script Code Analyzer is a tool that analyzes SQL Script code and provides suggestions and recommendations for improving its quality, performance, and maintainability. The SQL Script Code Analyzer can be used to optimize and refactor SQL Script code, but not to test its behavior or functionality.

References:

• [SAP HANA Platform Documentation], SAP HANA SQLScript Reference, Chapter 6: SQLScript Test Framework, pp. 153-158.
• [SAP HANA Platform Documentation], SAP HANA Developer Guide for SAP HANA XS Advanced Model, Chapter 7: Developing SQLScript Procedures, Section 7.4: Testing SQLScript Procedures, pp. 137-140.

 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

To create a native SAP HANA application that fully leverages the SAP HANA platform, you should implement data-intensive calculations on the database layer, using SQLScript or calculation views. SQLScript is a scripting language that allows you to write stored procedures, functions, and triggers that perform complex calculations and data transformations on the SAP HANA database. Calculation views are graphical or scripted views that define data models based on tables, views, or other calculation views, and apply filters, joins, aggregations, and other operations on the data. By pushing the calculations onto the database layer, you can take advantage of the in-memory processing, parallelization, and optimization capabilities of SAP HANA, and reduce the data transfer and network latency between the application layer and the database layer123.

The other options are not correct because they do not fully leverage the SAP HANA platform, and they may result in poor performance, high resource consumption, and increased complexity. Pushing the calculations onto the application layer means that you use a programming language, such as Java or Node.js, to perform the calculations on the application server, which may not be as efficient or scalable as the database server. Pushing the calculations onto the presentation layer means that you use a UI framework, such as SAPUI5 or SAP Fiori, to perform the calculations on the client device, such as a browser or a mobile device, which may not have enough processing power or memory to handle large or complex data sets. Distributing the calculations between the application layer and the presentation layer means that you split the calculations into different parts and execute them on different layers, which may introduce inconsistency, redundancy, and dependency issues. References:

• SAP HANA Platform, SAP HANA SQL and System Views Reference, SQLScript Guide
• SAP HANA Platform, SAP HANA Modeling Guide for SAP HANA Web Workbench, Calculation Views
• SAP HANA Platform, Developing Applications with SAP HANA Cloud Platform, Developing Multi-Target Applications, Developing Database Modules

To access objects in an external SAP HANA Deployment Infrastructure (HDI) container, you need to define synonyms in the persistence model. Synonyms are design-time artifacts that provide a logical name and a reference to an object in another schema or HDI container. Synonyms allow you to access the data and functionality of the external objects without granting direct privileges or using fully qualified names1. Synonyms can be created for tables, views, procedures, functions, and other database objects2.

The other options, views, imports, and procedures, are not artifacts that can be defined in the persistence model to access objects in an external HDI container. Views are artifacts that define a logical data model based on one or more tables or other views. Views can be used to query data from different sources, but they do not provide a reference to an external object3. Imports are artifacts that allow you to import another CDS entity or a database table into the current CDS entity, and use its columns as part of the projection list. Imports can be used to reuse data definitions, but they do not provide a reference to an external object either4. Procedures are artifacts that define a set of SQL statements that can be executed as a unit. Procedures can be used to implement complex logic and calculations, but they do not provide a reference to an external object either5. References: 1: Synonyms | SAP Help Portal 2: Synonym Definition | SAP Help Portal 3: Views | SAP Help Portal 4: Import | SAP Help Portal 5: Procedure Definition | 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

 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.

The package descriptor package.json is a JSON file that defines the build, deployment, and runtime dependencies of a JavaScript application in SAP HANA XS Advanced. The package.json file is mandatory for JavaScript applications and it is located in the general section of the project. As well as the application name and version, dependencies to other Node.js modules, the Node.js version, run scripts, and the main program are configured. The package descriptor package.json is used for the following purposes:

• To list the package dependencies: The package.json file contains a dependencies property that lists the names and versions of the Node.js modules that the application depends on. These modules are installed by the npm install command during the build process and are available in the node_modules folder of the application. The dependencies property can also specify the scope and type of the dependencies, such as devDependencies for development-only modules, or peerDependencies for modules that are required by other modules.
• To define the routes: The package.json file contains a sap.cloud.service property that defines the name of the service that the application provides or consumes. This name is used to generate the routes for the application in the XS advanced environment. The routes are defined in the xs-app.json file, which is located in the same folder as the package.json file. The routes specify the rules for forwarding requests to the back-end microservices or destinations.

The following purposes are not achieved by the package descriptor package.json, but by other files or tools:

• To define back-end destinations: The back-end destinations are defined in the mta.yaml file, which is the deployment descriptor file that specifies the metadata and dependencies for the multi-target application (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. The back-end destinations are declared as resources of type org.cloudfoundry.existing-service or org.cloudfoundry.managed-service, and are bound to the application modules by the requires property.
• To set the router version: The router version is set by the @sap/approuter module, which is a Node.js module that provides the application router service for the XS advanced environment. The application router service is responsible for routing requests to the appropriate destinations and for authenticating users. The @sap/approuter module is installed by the npm install command during the build process and is available in the node_modules folder of the application. The version of the @sap/approuter module is specified in the dependencies property of the package.json file.

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 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]

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. References: 1: TABLE Variables | SAP Help Portal 2: MAP_REDUCE Function | SAP Help Portal 3: COMMIT Statement | SAP Help Portal 4: IF Statement | SAP Help Portal

The SQL Script Code Analyser is a tool that scans SQL Script code for potential issues and provides suggestions for improvement. The tool can be accessed from the SAP Web IDE for SAP HANA or from the SAP HANA database explorer. The tool scans for issues in the following categories:

• Performance: This category covers issues that may affect the execution time or resource consumption of the SQL Script code, such as inefficient joins, missing indexes, unnecessary data transfers, etc. The tool provides recommendations for optimizing the code, such as using parallel processing, avoiding nested loops, using table variables, etc.
• Security: This category covers issues that may expose the SQL Script code to security risks, such as SQL injection, privilege escalation, data leakage, etc. The tool provides recommendations for securing the code, such as using parameterized queries, escaping literals, applying proper authorization checks, etc.
• Consistency: This category covers issues that may affect the readability, maintainability, or portability of the SQL Script code, such as coding style, naming conventions, documentation, compatibility, etc. The tool provides recommendations for improving the code quality, such as using consistent indentation, avoiding hard-coded values, adding comments, following best practices, etc.

The other options are incorrect because privileges and business logic are not issue categories that the SQL Script Code Analyser scans for. Privileges are handled by the SAP HANA Deployment Infrastructure framework, which automatically grants the necessary privileges to the technical users and roles that access the HDI container objects. Business logic is the domain-specific logic that defines the functionality and behavior of the SQL Script code, and it is not within the scope of the tool to verify or validate it. References:

• SQL Script Code Analyzer - SAP Help Portal
• SQL Script Code Analyzer in SAP Web IDE for SAP HANA - SAP Help Portal
• SQL Script Code Analyzer in SAP HANA Database Explorer - SAP Help Portal
• HA150 - SAP HANA 2.0 SPS06 SQLScript for SAP HANA - SAP Training

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

 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

 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

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

 A calculation view of type “SQL Access Only” is a calculation view that is not visible to the reporting tools and does not support multidimensional reporting. However, it can be directly accessed via SQL and used as a modelled data source for another view. This type of calculation view is useful for scenarios where you want to perform complex calculations or transformations on the data, but do not need to expose the result to the end users or analytical applications. You can use the SQL Access Only calculation view as an intermediate step in your data modelling process, and then use another calculation view with data category Cube or Dimension to provide the final output for reporting or analysis. The other options are incorrect because a calculation view of type “SQL Access Only” cannot be directly exposed to all client tools or used for multidimensional analysis. These features are only available for calculation views with data category Cube or Dimension. References:

• Supported Data Categories for Calculation Views - SAP Help Portal
• Quick Reference: Calculation View Properties - SAP Help Portal
• SAP HANA Modeling Guide for SAP HANA Studio - SAP Help Portal
• New Hierarchy SQL enablement with Calculation Views in SAP HANA 1.0 SPS 10 - SAP Blogs
• HA300 - SAP HANA 2.0 SPS06 Modeling - SAP Training

To run an SQL statement against the SAP HANA database from a Node.js application, you need to use the @sap/hdbext module. 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/hdi: This module provides functions to interact with the SAP HANA Deployment Infrastructure (HDI), which enables you to create and manage database artifacts, such as tables, views, procedures, and functions, using the HDI container service. You can use this module to deploy, undeploy, and access HDI containers, but not to run SQL statements against the SAP HANA database.
• B. @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, but not to run SQL statements against the SAP HANA database.
• C. @sap/xssec: This module provides functions to handle authentication and authorization for Node.js applications using the User Account and Authentication (UAA) service and the XSUAA service. You can use this module to verify JWT tokens, check scopes, and obtain user information, but not to run SQL statements against the SAP HANA database.

References:

• 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
• SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.6

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.

 According to the SAP Web IDE for SAP HANA Developer Guide, you can debug a Node.js module in SAP Web IDE for SAP HANA by attaching the debugger to the application in the SAP Web IDE for SAP HANA. To do this, you need to open the debugger panel, attach your application, and choose your multi-target application and select a debug target. Then, you can perform the regular debugging tasks, such as setting breakpoints, stepping through the code, examining the variables, and so on. The other options are incorrect, because:

• Setting the enabled parameter to true in the section debugger of the xsengine.ini file is not a way to debug a Node.js module in SAP Web IDE for SAP HANA, but a way to enable the XS JavaScript debugger for XSJS applications. This is not relevant for Node.js modules, which use a different runtime and debugger.
• Adding the sap.hana.xs.debugger::Debugger role to the HDI Container’s #RT User is not a way to debug a Node.js module in SAP Web IDE for SAP HANA, but a way to grant the XS JavaScript debugger privileges to the runtime user of the HDI container. This is not relevant for Node.js modules, which use a different runtime and debugger.
• Starting the debugger from the XS command line interface and running the program in SAP Web IDE for SAP HANA is not a way to debug a Node.js module in SAP Web IDE for SAP HANA, but a way to debug a Node.js module using command-line tools. This is an alternative option for debugging Node.js modules, but it does not use the SAP Web IDE for SAP HANA.

References: SAP Web IDE for 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.

When you create a new project in SAP Web IDE for SAP HANA, you must specify the project name and the template. The project name is a unique identifier for your project that is used to create the folder structure and the deployment descriptor file (mta.yaml) for your project. The template is a predefined set of files and configurations that provide the basic structure and functionality for your project. You can choose from various templates, such as SAP HANA Database Project, SAP Cloud Platform Business Application, SAP Fiori Freestyle Project, and more, depending on your development scenario and requirements.

The following information is not required or not applicable when you create a new project in SAP Web IDE for SAP HANA:

• SAP HANA database version: This information is not required when you create a new project in SAP Web IDE for SAP HANA, as the SAP HANA database version is determined by the target environment where you deploy your project. The SAP Web IDE for SAP HANA supports multiple SAP HANA versions, such as SAP HANA 2.0 SPS 04, SAP HANA 2.0 SPS 05, and SAP HANA Cloud. You can check the compatibility of the SAP Web IDE for SAP HANA and the SAP HANA database versions in the SAP HANA Deployment Infrastructure Reference.
• Namespace: This information is not applicable when you create a new project in SAP Web IDE for SAP HANA, as the namespace is a concept that is used to organize the design-time artifacts in the SAP HANA repository, which is a legacy feature that has been deprecated since SAP HANA 2.0 SPS 02. Instead of using the SAP HANA repository, you should use the SAP HANA Deployment Infrastructure (HDI) to deploy your database artifacts to HDI containers, which are isolated schemas that represent runtime objects. You can configure the artifact namespaces for your HDI containers by editing the .hdiconfig file in the db module of your project.

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.1: Create a Project, pp. 101-102.
• [SAP HANA Platform Documentation], SAP HANA Developer Guide for SAP HANA XS Advanced Model, Chapter 2: Getting Started with SAP Web IDE for SAP HANA, Section 2.1: Creating a Project, pp. 17-19.