Which trace do you use to create a graphical representation of an individual SQL Statement? Please choose the correct answer.
Correct Answer: C
Question 22
What is the package descriptor package.json used for? There are 2 correct answers to this question.
Correct Answer: C,D
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.
Question 23
You need to consume a Node.js service in an SAPUI5 application. In which section of the mta.xml file do you define the variable for the exposed service? Please choose the correct answer.
Correct Answer: D
Question 24
You are working on an entity using Core Data Services. Which properties can you define inside the Technical Configuration section? There are 2 correct answers to this question.
Correct Answer: A,C
The Technical Configuration section of a Core Data Services (CDS) entity allows you to define properties that affect the physical storage and performance of the entity in the database. You can define the following properties inside the Technical Configuration section1: * Index: You can create one or more indexes on the entity to improve the query performance. You can specify the index name, the columns to be indexed, and the index type (such as unique, full-text, or spatial)2. * Storage Type: You can specify the storage type of the entity, such as column store or row store, to optimize the data access and compression. You can also specify the partitioning mode and criteria for the entity, such as hash, range, or round-robin3. The other two options, Import and Association, are not properties that can be defined inside the Technical Configuration section. Import is a keyword that allows you to import another CDS entity or a database table into the current CDS entity, and use its columns as part of the projection list4. Association is a keyword that allows you to create a relationship between two CDS entities, and use the associated entity's columns as part of the projection list or the join condition. References: 1: Technical Configuration | SAP Help Portal 2: Index Definition | SAP Help Portal 3: Storage Type | SAP Help Portal 4: Import | SAP Help Portal : [Association | SAP Help Portal]
Question 25
How do you specify the target currency for currency conversion in calculation views? There are 3 correct answers to this question.
Correct Answer: A,C,D
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.
