SAP C_HANADEV_18 SAP Certified Development Associate - SAP HANA 2.0 SPS06 Exam Practice Test

Answer : C

An OData V2 service is a web service that exposes data from a data source, such as a SAP HANA database, in a standardized and interoperable format based on the OData protocol version 2.0. An OData V2 service consists of one or more entity sets, which are collections of entities of the same type. An entity is a data object that has properties and a unique key. An OData V2 service can also define associations between entity sets, which are relationships that specify how entities are related to each other. An OData V2 service can also define function imports, which are operations that can be invoked by the client to perform specific tasks.

An OData V2 service exposes a data model that describes the structure and semantics of the data and the operations that are supported by the service. The data model is represented in an XML document that conforms to the OData Metadata XML Schema. The data model contains information such as the entity types, the entity sets, the associations, the function imports, the namespaces, the annotations, and the service document.

To view the data model exposed by an OData V2 service, you need to append the $metadata system query option to the service URL. The $metadata system query option requests the metadata document of the service. For example, if the service URL is http://services.odata.org/V2/Northwind/Northwind.svc, then the metadata document URL is http://services.odata.org/V2/Northwind/Northwind.svc/$metadata. The metadata document URL can be accessed by any HTTP client, such as a web browser, and it returns the XML representation of the data model.

The other options are incorrect because they are not system query options that can be used to view the data model exposed by an OData V2 service. $schema is not a valid system query option in OData V2. $service definition is a system query option in OData V4, not OData V2, and it requests the service definition document, which is a JSON document that describes the capabilities and annotations of the service. $format is a system query option that can be used to specify the desired format of the response, such as XML or JSON, but it does not request the data model of the service.Reference:

SAP HANA Platform 2.0 SPS06: OData V2 Developer Guide, Section 1.1

SAP HANA Platform 2.0 SPS06: OData V2 Developer Guide, Section 2.1

SAP HANA Platform 2.0 SPS06: OData V2 Developer Guide, Section 2.6

OData Version 2.0: Part 1 - Protocol, Section 2.2.6

OData Version 2.0: Part 3 - CSDL, Section 1

Answer : C

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

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

Answer : B

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.Reference:1:Synonyms | SAP Help Portal2:Synonym Definition | SAP Help Portal3:Views | SAP Help Portal4:Import | SAP Help Portal5:Procedure Definition | SAP Help Portal

Answer : C, D, E

Calculation views are a type of virtual data models that allow you to define complex calculations and aggregations on data from various sources, such as tables, views, or other calculation views. Calculation views are executed by different SAP HANA engines, depending on the type and complexity of the calculation view and the query that is submitted to it. The main SAP HANA engines responsible for executing calculation views are:

OLAP Engine: This engine is responsible for executing analytical queries on calculation views that are based on the star schema, which consists of a central fact table and multiple dimension tables. The OLAP engine supports multidimensional analysis, such as slicing, dicing, filtering, sorting, ranking, and drill-down operations. The OLAP engine also optimizes the query execution by applying techniques such as push-down, pruning, and caching.

Calculation Engine: This engine is responsible for executing complex calculations and transformations on calculation views that are based on the graph model, which consists of nodes and edges that represent data sources and operations. The calculation engine supports advanced features, such as hierarchies, unions, projections, aggregations, joins, and scripting. The calculation engine also leverages the parallel processing capabilities of SAP HANA to optimize the performance of data-intensive operations.

Join Engine: This engine is responsible for executing join operations on calculation views that involve multiple data sources. The join engine supports different types of joins, such as inner join, left outer join, right outer join, full outer join, referential join, and text join. The join engine also applies various join algorithms, such as hash join, nested loop join, and merge join, depending on the characteristics of the data sources and the join conditions.

The other options are not correct because:

A) Java Engine: This engine is not responsible for executing calculation views, but for executing Java applications that run on the SAP HANA XS Advanced Model. The Java engine provides the core services and libraries for building and running Java applications, such as data access, authentication, authorization, localization, logging, and testing.

B) XS Engine: This engine is not responsible for executing calculation views, but for executing XSJS and XSODATA applications that run on the SAP HANA XS Classic Model. The XS engine provides the runtime environment and the web server for executing XSJS and XSODATA applications, which can access SAP HANA database features using JavaScript syntax.

SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 6, Section 6.1

SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 6, Section 6.2

SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 6, Section 6.3

SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 6, Section 6.4

Answer : A

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

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

Answer : C, D

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

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

Answer : A, B

The index.html file is the entry point of the UI5 application. It contains the following elements:

Framework Reference: This element specifies the location of the UI5 resources, such as libraries, themes, and controls. It can be done by using the data-sap-ui-resourceroots attribute or the sap.ui.localResources() function.

Bootstrap: This element initializes the UI5 framework and loads the required libraries and components. It can be done by using the script tag with the src attribute pointing to the sap-ui-core.js file and the data-sap-ui-xx attributes to configure the bootstrap parameters.

Backend Connection: This element is optional and depends on the application logic. It can be used to establish a connection to the backend system, such as an OData service, by using the data-sap-ui-bindingSyntax attribute or the sap.ui.model.odata.v2.ODataModel() constructor.

UI-Area: This element defines the HTML element where the UI5 content will be rendered. It can be done by using the data-sap-ui-oninit attribute or the sap.ui.getCore().attachInit() function to register a callback function that creates and places the UI5 root component or view.

SAP HANA 2.0 SPS06 - Application Development for SAP HANA1, Section 5.1.1, p. 131-132

SAP HANA 2.0 SPS06 - Developing Web Apps with SAPUI52, Section 2.1, p. 17-20

SAP HANA 2.0 SPS06 - Developing Web Apps with SAPUI52, Section 3.1, p. 37-40

SAP HANA 2.0 SPS06 - Developing Web Apps with SAPUI52, Section 4.1, p. 59-62

SAP HANA 2.0 SPS06 - Developing Web Apps with SAPUI52, Section 5.1, p. 81-84