New 2024 Realistic C-HANADEV-18 Dumps Test Engine Exam Questions in here [Q22-Q41]

QUESTION 22
You created an HDI database role, using the SAP Web IDE for SAP HANA and deployed your project. Afterward, you made some modifications to the runtime role.
What happens when you change and re-build the design-time role? Please choose the correct answer.

The runtime modifications are kept.

The deployment of the role fails.

You need to confirm the runtime modifications

The runtime modifications are overwritten.

QUESTION 23
A Node.js module is executed for the first time in SAP HANA extended application services, advanced model (XS advanced). Which of the following activities are performed automatically? There are 2 correct answers to this question.

The source code is compiled to create an executable binary file.

A new SAP HANA Deployment Infrastructure (HDI) container is created.

The required modules are downloaded based on module dependencies.

A new service is executed on the application server.

QUESTION 24
You need to synchronize all unsynchronized changes of the remote Git branch with a local Git branch. Which operation do you use? Please choose the correct answer.

Push

Rebase

Pull

Reset

QUESTION 25
You created several database tables in a multi-target application and need to keep their names as short as possible. Which parameter of the .hdinamespace file do you set to ignore? Please choose the correct answer.

name

hdbtable

mixinTypes

subfolder

QUESTION 26
Which parameter do you adapt to change the file that is initially delivered by an HTML5 module? Please choose the correct answer.

Service_url parameter of the mta.xml file

Welcome file parameter of the xs-app.json file

Start parameter of the package.json file

Runners parameter of the projectjson file

QUESTION 27
Which activities do you perform on an application in the SAP HANA XS Advanced Cockpit? There are 2 correct answers to this question.

Monitor applications assigned to the current space.

Deploy applications to SAP Cloud Platform.

Display HDI container content.

Start, stop, and restart applications.

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

QUESTION 28
Which elements can you specify with the SAP WeblDE for SAP HANA graphical editor for Core Data Services data models? There are 3 correct answers to this question.

Entity

Synonym

Procedure

Context

Association

The SAP Web IDE for SAP HANA graphical editor for Core Data Services (CDS) data models allows you to specify the following elements12:
* Entity: An entity is a CDS artifact that defines a data structure with attributes, keys, and associations. An entity can be mapped to a database table or view, or it can be used as a source for another entity or a calculation view. You can create an entity by dragging the entity icon from the palette to the canvas, and then defining its properties and attributes in the properties panel.
* Context: A context is a CDS artifact that defines a namespace for other CDS artifacts, such as entities, views, types, or associations. A context can be used to organize and group related CDS artifacts, and to avoid name conflicts. You can create a context by dragging the context icon from the palette to the canvas, and then defining its name and description in the properties panel. You can also add other CDS artifacts to the context by dragging them from the project explorer or the palette to the context node in the canvas.
* Association: An association is a CDS artifact that defines a relationship between two entities, based on a join condition. An association can be used to navigate from one entity to another, and to filter, aggregate, or project data from the target entity. You can create an association by dragging the association icon from the palette to the canvas, and then connecting it to the source and target entities.
You can also define the cardinality, join condition, and exposed attributes of the association in the properties panel.
The other options are not correct because they are not elements that can be specified with the SAP Web IDE for SAP HANA graphical editor for CDS data models. A synonym is a database object that provides an alternative name for another database object, such as a table, view, or procedure. A synonym is not a CDS artifact, and it cannot be created or edited with the graphical editor. A procedure is a database object that contains a set of SQL statements that perform a specific task. A procedure can be created or edited with the SQL editor, but not with the graphical editor. A procedure can also be exposed as a CDS artifact, but it cannot be specified with the graphical editor. References:
* SAP HANA Platform, SAP HANA Modeling Guide for SAP HANA Web Workbench, Core Data Services
* SAP HANA Platform, SAP HANA Developer Guide for SAP HANA Web IDE, Developing Core Data Services Models, Using the Graphical Editor

QUESTION 29
A user is dropped with the “cascade” option. The user schema also contains objects owned by other users, or on which other users have privileges. What happens to the objects? There are 2 correct answers to this question.

The objects on which other users have privileges are NOT dropped.

The objects on which other users have privileges are dropped.

The objects owned by other users are NOT dropped.

The objects owned by other users are dropped.

QUESTION 30
What key words are contained in the application descriptor file (xs-app.json)? There are 2 correct answers to this question.

routes

role-templates

tenant-mode

authentication Method

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.

QUESTION 31
Which OData capacity do you use when you need to restrict the number or selection of exposed columns?
Please choose the correct answer.

Parameter entity sets

Aggregation

Key specification

Property projection

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.

QUESTION 32
You need to install SAP HANA 2.0, express edition to develop a native SAP HANA application. Which of the following deployment options do you have?
There are 2 correct answers to this question.

Installation on Windows Server

Installation on Mac OS

Installation on Linux OS

Usage of virtual machine on Microsoft Windows

QUESTION 33
What are the nodes where filter expressions can be used in a calculation view? There are 2 correct answers to this question.

Aggregation

Star join

Union

Rank

QUESTION 34
What are the issue categories that SQL Script Code Analyser scans for? There are 3 correct answers to this question.

Performance

Privileges

Security

Business logic

Consistency

QUESTION 35
Which of the following elements can be part of the UI5 application’s index.html file? There are 2 correct answers to this question

Framework Reference

Bootstrap

Backend Connection

UI-Area

QUESTION 36
Which configuration file indicates the program that is executed upon start up when you run the Node.js module? Please choose the correct answer.

package.json

project.json

server.js

mta.yaml

QUESTION 37
Which keywords do you use to define an OData association? There are 3 correct answers to this question.

JOIN

DEPENDENT

UNION

MULTIPLICITY

PRINCIPAL

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.

QUESTION 38
What do you reference in a role template? Please choose the correct answer.

Role Collections

Roles

Routes

Scopes

QUESTION 39
An OData service contains an entity set called Products. Which resource path do you add to the OData service URL to view all available products?
Please choose the correct answer.

/Products/$metadata

/Products/’

/Products

/Products/ALL

QUESTION 40
What are the nodes where filter expressions can be used in a calculation view? There are 2 correct answers to this question.

Aggregation

Star join

Union

Rank

Filter expressions can be used in a calculation view to restrict or modify the data that is displayed or processed by the view. Filter expressions can be used in the following nodes of a calculation view12:
* Aggregation: An aggregation node is a node that applies aggregation functions, such as sum, count, or average, to the data that is passed from the previous node. Filter expressions can be used in an aggregation node to filter the data before or after the aggregation, or to define the aggregation level or the measure attributes. For example, you can use a filter expression to show only the sales data for a specific region or product category, or to calculate the average revenue per customer.
* Union: A union node is a node that combines the data from two or more nodes that have the same structure and data types. Filter expressions can be used in a union node to filter the data from each input node, or to filter the data from the output node. For example, you can use a filter expression to exclude the duplicate rows from the union result, or to show only the data that matches a certain condition from each input node.
The other options are not correct because filter expressions cannot be used in these nodes of a calculation view. A star join node is a node that joins a fact table with one or more dimension tables, based on the common key attributes. A star join node does not support filter expressions, but it supports input parameters, which are variables that can be used to filter the data at runtime. A rank node is a node that ranks the data according to a specified order and criteria. A rank node does not support filter expressions, but it supports rank filters, which are conditions that can be used to limit the number or percentage of rows in the rank result.
References:
* SAP HANA Platform, SAP HANA Modeling Guide for SAP HANA Web Workbench, Calculation Views
* SAP HANA Platform, SAP HANA Developer Guide for SAP HANA Web IDE, Developing Database Modules, Developing Calculation Views, Using Filter Expressions

QUESTION 41
What characterizes the Node.js environment? There are 2 correct answers to this question.

It uses a synchronous programming model.

It is a client-side design-time environment for JavaScript.

It is single-threaded.

It is built on Google’s V8 JavaScript engine.

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.