あなたを余裕でC-HANADEV-18試験合格させます！100%試験高合格率保証 [2024]
C-HANADEV-18問題集本日限定！無料アクセスが可能に！fromJPNTest
SAP C_HANADEV_18試験は、SAP HANAプラットフォームでの開発スキルを検証しようとする個人向けに設計されています。この試験は、SAP HANA開発、SAP HANA展開、SAP HANAモデリングの分野で知識とスキルをテストすることを目的としています。この認定は世界的に認識されており、SAPエコシステムでのキャリアを前進させようとする専門家にとって貴重な資産です。
質問 # 38
You develop a Node.js application for the SAP HANA platform that executes a SQL statement in the SAP HANA database. Which modules do you use?
There are 2 correct answers to this question.
- A. @sap/hdbext
- B. @sap/node-vsi
- C. @sap/instance-manager
- D. @sap/xsenv
正解：A、D
解説：
To develop a Node.js application for the SAP HANA platform that executes a SQL statement in the SAP HANA database, you need to use the following modules:
* @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.
* @sap/hdbext: 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/instance-manager: This module provides functions to manage the lifecycle of Node.js applications running on the SAP Cloud Platform or the SAP HANA XS Advanced Model. You can use this module to start, stop, restart, scale, and monitor your applications, but not to execute SQL statements in the SAP HANA database.
* D. @sap/node-vsi: This module provides functions to interact with the SAP HANA Virtual Schema Integrator (VSI), which enables you to access data from remote sources using virtual tables. You can use this module to create, update, delete, and query virtual tables, but not to execute SQL statements in the SAP HANA database.
References:
* SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.2
* 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
質問 # 39
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.
- A. Reset
- B. Push
- C. Pull
- D. Rebase
正解：C
解説：
According to the SAP HANA Developer Guide, you use the pull operation to synchronize all unsynchronized changes of the remote Git branch with a local Git branch. The pull operation fetches the changes from the remote branch and merges them with the local branch. This way, you can update your local branch with the latest changes from the remote branch. The other options are incorrect, because:
* Push is the opposite of pull. It sends the changes from the local branch to the remote branch, not the other way around.
* Rebase is an alternative to merge. It rewrites the history of the local branch by applying the changes from the remote branch as new commits on top of the local branch. This creates a linear history, but it may cause conflicts or lose some information.
* Reset is a way to undo changes in the local branch. It moves the branch pointer to a different commit, and optionally discards the changes in the working directory or the staging area.
References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111.
質問 # 40
Which Git command do you use to consolidate all changes from one branch with another branch using a single commit? Please choose the correct answer.
- A. Push
- B. Merge
- C. Rebase
- D. Commit
正解：B
質問 # 41
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.
- A. Context
- B. Association
- C. Synonym
- D. Procedure
- E. Entity
正解：A、B、E
解説：
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
質問 # 42
You work on a multi-target application that uses the SAP HANA Deployment Infrastructure (HDI). Which operations can you perform in the SAP Web IDE for SAP HANA?
There are 2 correct answers to this question.
- A. Deploy HTML5 modules to the SAP HANA database.
- B. Create objects in the SAP HANA repository.
- C. Choose the supported SAP HANA versions.
- D. Configure the artifact namespaces.
正解：A、D
解説：
The SAP Web IDE for SAP HANA is a web-based development tool that allows you to create and manage multi-target applications (MTAs) that use the SAP HANA Deployment Infrastructure (HDI). HDI is a service layer that enables you to deploy database development artifacts to HDI containers, which are isolated schemas that represent runtime objects. Some of the operations that you can perform in the SAP Web IDE for SAP HANA are:
* Deploy HTML5 modules to the SAP HANA database: HTML5 modules are web applications that run on the XS advanced runtime and can access HDI containers via service bindings. You can create, edit,
* test, and deploy HTML5 modules from the SAP Web IDE for SAP HANA using the MTA development perspective and the build and run commands. You can also use the HTML5 module template wizard to generate a basic HTML5 module with the required configuration files and dependencies.
* Configure the artifact namespaces: Artifact namespaces are prefixes that are added to the names of the database artifacts that are deployed to the HDI containers. They help to avoid name conflicts and to organize the artifacts in a logical way. You can configure the artifact namespaces in the SAP Web IDE for SAP HANA by editing the .hdiconfig file in the db module of your MTA project. You can also use the namespace template wizard to generate a .hdiconfig file with a default namespace.
The following operations are not possible or not recommended in the SAP Web IDE for SAP HANA:
* Create objects in the SAP HANA repository: The SAP HANA repository is a legacy feature that was used to store and manage design-time artifacts in SAP HANA 1.0. It has been deprecated since SAP HANA 2.0 SPS 02 and replaced by HDI. Therefore, you should not create objects in the SAP HANA repository, but rather use HDI containers and the SAP Web IDE for SAP HANA to develop and deploy database artifacts.
* Choose the supported SAP HANA versions: The SAP Web IDE for SAP HANA does not allow you to choose the supported SAP HANA versions for your MTA project. The supported SAP HANA versions depend on the HDI version and the SAP HANA Cloud Platform, which are determined by the target environment where you deploy your MTA project. You can check the compatibility of the HDI version and the SAP HANA Cloud Platform in the SAP HANA Deployment Infrastructure Reference.
References:
* [SAP HANA Deployment Infrastructure Reference], Chapter 5: HDI with XS Advanced, Section 5.1:
Developing with the SAP Web IDE for SAP HANA, pp. 101-106.
* [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, pp. 77-82.
質問 # 43
What key words are contained in the application descriptor file (xs-app.json)? There are 2 correct answers to this question.
- A. tenant-mode
- B. role-templates
- C. routes
- D. authentication Method
正解：C、D
解説：
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.
質問 # 44
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.
- A. name
- B. mixinTypes
- C. hdbtable
- D. subfolder
正解：D
質問 # 45
Your multi-target application will use XSJS. Which module type do you create in your application project?
Please choose the correct answer.
- A. SAP HANA database
- B. Java
- C. Node.js
- D. HTML5
正解：C
解説：
To create a multi-target application that will use XSJS, you need to create a Node.js module type in your application project. XSJS is a scripting language that allows you to implement server-side logic and access SAP HANA database features using JavaScript syntax. XSJS is supported by the Node.js runtime of the SAP HANA XS Advanced Model, which provides the necessary libraries and services to execute XSJS code. You can use the SAP Web IDE for SAP HANA to create a Node.js module and add XSJS files to it. The other options are not correct because:
* A. Java is not the module type you need to create for XSJS, as XSJS is not a Java-based language. Java is a module type that allows you to implement Java applications using the Java runtime of the SAP HANA XS Advanced Model.
* B. SAP HANA database is not the module type you need to create for XSJS, as XSJS is not a database object. SAP HANA database is a module type that allows you to create database artifacts, such as tables, views, procedures, and functions, using the SAP HANA deployment infrastructure (HDI).
* D. HTML5 is not the module type you need to create for XSJS, as XSJS is not a web page. HTML5 is a module type that allows you to create static web content, such as HTML, CSS, and JavaScript files, using the HTML5 application repository service.
References:
* SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.6
* SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.7
* SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.8
* SAP HANA Developer Guide for SAP HANA Web IDE, Chapter 5, Section 5.9
質問 # 46
What are the disadvantages when deploying Dynamic SQL? There are 2 correct answers to this question.
- A. No possibility to bind the result to a SQL Script variable
- B. Limited opportunities for optimization
- C. Additional SQL execution privileges are required
- D. No possibility to use SQL Script variables
正解：A、B
質問 # 47
What are the issue categories that SQL Script Code Analyser scans for? There are 3 correct answers to this question.
- A. Consistency
- B. Business logic
- C. Privileges
- D. Performance
- E. Security
正解：A、D、E
解説：
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
質問 # 48
What statement must you insert to the following OData service to complete the navigation definition from the customer entity set to the corresponding sales orders? Please choose the correct answer.
service{ "sample.odata::customer" as customer" navigates ("Customer_Orders* as "toOrders); "sample.odata::salesorder" as "Orders";)
- A. Aggregation
- B. Association
- C. Join condition
- D. Key specification
正解：B
質問 # 49
Which of the following are characteristics of SAPUI5? There are 3 correct answers to this question.
- A. Enables responsive application design
- B. Provides an extensibility concept
- C. Provides a device-specific user experience
- D. Supports customer-specific theming
- E. Renders the UI on the server side
正解：A、B、D
解説：
SAPUI5 is a JavaScript-based UI framework that enables the development of web applications that run on various devices and platforms. SAPUI5 has the following characteristics12:
* Provides an extensibility concept: SAPUI5 allows developers to extend or customize the standard UI components, such as controls, views, or controllers, to meet specific requirements or scenarios. SAPUI5 also supports the creation of custom UI components, which are reusable and modular UI elements that can be integrated into other SAPUI5 applications.
* Enables responsive application design: SAPUI5 supports the development of responsive applications, which are applications that adapt to different screen sizes, orientations, and resolutions, and provide a consistent and optimal user experience across different devices. SAPUI5 provides various layout options, such as grids, panels, or flexboxes, to arrange the UI elements according to the available space.
SAPUI5 also provides various UI patterns, such as master-detail, split-screen, or full-screen, to organize the application content and navigation according to the device type.
* Supports customer-specific theming: SAPUI5 allows developers to apply different themes to the UI components, such as colors, fonts, icons, or backgrounds, to match the branding or style of the customer or the application. SAPUI5 provides a set of predefined themes, such as SAP Fiori, SAP Belize, or SAP Quartz, that follow the SAP design guidelines and principles. SAPUI5 also provides tools, such as the UI Theme Designer or the SAPUI5 Theme Builder, to create or modify custom themes.
The other options are not correct because they are not characteristics of SAPUI5. SAPUI5 does not render the UI on the server side, but rather on the client side, in the browser or the device that accesses the application.
SAPUI5 does not provide a device-specific user experience, but rather a device-agnostic user experience, which means that the application can run on any device and platform without requiring any changes or adaptations. References:
* SAP HANA Platform, Developing Applications with SAP HANA Cloud Platform, Developing Multi-Target Applications, Developing HTML5 Modules, Developing SAPUI5 Applications
* SAP HANA Platform, SAP HANA Extended Application Services, Advanced Model, Developing and Deploying Applications, Developing SAP Fiori Applications, Developing SAPUI5 Applications
質問 # 50
You need to check user input data in your OData request. Which exit type do you use? Please choose the correct answer.
- A. Verification
- B. Validation
- C. Modification
- D. Consistency
正解：B
質問 # 51
Which metadata declarations can you specify in a SQL Script procedure when you use the SAP HANA Deployment Infrastructure? There are 2 correct answers to this question.
- A. Default schema
- B. Language
- C. Authorization
- D. Security
正解：B、D
質問 # 52
What do you use to set up unit testing for your SQL Script procedure? Please choose the correct answer.
- A. SQL Script logging procedures
- B. A library with language SQLSCRIPT TEST
- C. The SQL Script debugger
- D. The SQL Script Code Analyzer
正解：B
質問 # 53
Which Git commands are available with the SAP Web IDE for SAP HANA? There are 3 correct answers to this question.
- A. Redeploy the code
- B. Push code
- C. Merge changes
- D. Clone a repository
- E. Test changes
正解：B、C、D
質問 # 54
What happens if you define a database object in the persistence model and deploying using the SAP HANA Deployment Infrastructure (HDI)?
Please choose the correct answer.
- A. The HDI container is created when the design-time object is saved.
- B. The corresponding runtime object is created in the HDI container on deployment
- C. A descriptive representation of the object is created in Hot during runtime.
- D. The corresponding runtime object is created in the database module of the multi-target application during runtime.
正解：B
解説：
According to the SAP HANA Developer Guide, the SAP HANA Deployment Infrastructure (HDI) uses so-called containers to store design-time artifacts and the corresponding deployed run-time (catalog) objects.
The HDI makes a strict separation between design-time and run-time objects by introducing the following, distinct container types:
* Design-time container (DTC): A Git repository that stores the design-time artifacts, such as CDS files, SQL files, or HDB files, that define the database objects in the persistence model. The DTC is part of the database module of the multi-target application (MTA).
* Run-time container (RTC): A schema in the SAP HANA database that stores the run-time objects, such as tables, views, or procedures, that are created based on the design-time artifacts. The RTC is also known as the HDI container.
* Build container (BTC): A temporary schema in the SAP HANA database that is used to build the run-time objects from the design-time artifacts. The BTC is deleted after the build process is completed.
When you define a database object in the persistence model, you create a design-time artifact in the DTC.
When you deploy the database module of the MTA, the HDI creates an RTC and a BTC, and builds the corresponding run-time object in the RTC based on the design-time artifact. The BTC is then dropped, and the RTC remains as the HDI container for the database module. References: SAP HANA Developer Guide, Chapter 6, Section 6.4.2, page 2111.
質問 # 55
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.
- A. The runtime modifications are kept.
- B. The deployment of the role fails.
- C. The runtime modifications are overwritten.
- D. You need to confirm the runtime modifications
正解：C
解説：
When you create an HDI database role using the SAP Web IDE for SAP HANA, you define the role in a design-time file with the extension .hdbrole. This file is part of your project and can be deployed to the HDI container as a runtime role. However, if you make any changes to the runtime role directly in the database, such as granting or revoking privileges, those changes are not reflected in the design-time file. Therefore, if you change and re-build the design-time role, the runtime role will be overwritten with the new version of the design-time role, and any runtime modifications will be lost. This is because the deployment process always drops and recreates the runtime role based on the design-time role. The other options are incorrect because the deployment of the role will not fail, the runtime modifications will not be kept, and you do not need to confirm the runtime modifications. References:
* SAP HANA DI Administrator Roles - SAP Help Portal
* SAP HANA Deployment Infrastructure Reference - SAP Help Portal
* Modifying the default access_role in HDI containers - SAP Blogs
質問 # 56
Which of the following can be used when implementing transaction management logic in SQLScript using savepoints? Note: There are 3 correct answers to this question.
- A. Savepoint
- B. Reverse savepoint
- C. Rollback to savepoint
- D. Release savepoint
- E. Alter system savepoint
正解：A、C、D
解説：
According to the SAP HANA SQLScript Reference, the following statements can be used when implementing transaction management logic in SQLScript using savepoints:
* Savepoint: Creates a savepoint with a specified name within the current transaction. A savepoint marks a point in the transaction that can be rolled back to without affecting the rest of the transaction. For example, SAVEPOINT sp1;
* Rollback to savepoint: Rolls back the current transaction to the specified savepoint. All changes made after the savepoint are undone, but the transaction remains active. For example, ROLLBACK TO SAVEPOINT sp1;
* Release savepoint: Releases the specified savepoint and all subsequent savepoints. The released savepoints are no longer valid and cannot be rolled back to. For example, RELEASE SAVEPOINT sp1; The other options are incorrect, because:
* Reverse savepoint is not a valid statement in SQLScript. There is no such statement in the SAP HANA
* SQLScript Reference.
* Alter system savepoint is not a statement that can be used in SQLScript, but a statement that can be used in SQL. It triggers a savepoint operation for the entire database system, not for a specific transaction. It is used for administrative purposes, such as backup and recovery, not for transaction management logic.
References: SAP HANA SQLScript Reference, Chapter 6, Section 6.4.2, page 2111.
質問 # 57
Which of the following SQL Script elements do you use to transform a set of arrays into an intermediate table variable? Please choose the correct answer.
- A. OSET
- B. ARRAY
- C. UNSET
- D. UNNEST
正解：D
質問 # 58
You want to exclusively use declarative logic in an SQL Script procedure. Which of the following operators can you use? There are 2 correct answers to this question.
- A. COMM IT statement
- B. TABLE variable
- C. IF condition
- D. MAP_REDUCE function
正解：B、D
質問 # 59
Which Git commands are available with the SAP Web IDE for SAP HANA? There are 3 correct answers to this question.
- A. Redeploy the code
- B. Push code
- C. Merge changes
- D. Clone a repository
- E. Test changes
正解：B、C、D
解説：
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.
質問 # 60
To which SAP HANA authorization entities can you grant a role? There are 2 correct answers to this question.
- A. Object
- B. Role
- C. User
- D. Privilege
正解：B、C
質問 # 61
You need to check user input data in your OData request. Which exit type do you use? Please choose the correct answer.
- A. Verification
- B. Validation
- C. Modification
- D. Consistency
正解：B
解説：
To check user input data in your OData request, you need to use the Validation exit type. The Validation exit type is a custom exit that allows you to perform validation of input data and data consistency checks before, after, or during the change operation, or before or after the commit operation. You can specify a maximum of four validation exits per change operation; the exit is registered for the corresponding event with the respective keyword: "before", "after", "precommit" or "postcommit". The validation exit is executed as an SQLScript procedure with a specific signature, and it can raise an error if the input data does not meet the validation criteria1.
The other options, Consistency, Modification, and Verification, are not exit types that you can use to check user input data in your OData request. Consistency is not an exit type, but a property that you can set in the OData service definition to enable or disable the consistency check for the change operations. The consistency check ensures that the data in the database is consistent with the data in the request payload2. Modification is an exit type that allows you to define custom logic to create, update, or delete an entry in an entity set. If a modification exit is specified, it is executed instead of the generic actions provided by the OData infrastructure1. Verification is not an exit type, but a process that you can perform to ensure that the OData service definition is valid and can be activated without errors3. References: 1: Custom Exits for OData Write Requests | SAP Help Portal 2: Consistency Check | SAP Help Portal 3: Verifying the OData Service Definition
| SAP Help Portal
質問 # 62
In a calculation view, what are the different types of input mapping available in Table Function? There are 2 correct answers to this question.
- A. Constant
- B. Data Source Column
- C. Variable
- D. Formula
正解：A、B
解説：
In a calculation view, the different types of input mapping available in Table Function are Constant and Data Source Column. Constant allows you to map a fixed value to the input parameter of the Table Function. Data Source Column allows you to map a column from another node or data source to the input parameter of the Table Function12.
The other two options, Variable and Formula, are not types of input mapping available in Table Function. Variable is a type of input mapping available in Calculation Scenario, which allows you to map a variable from the calculation view to the input parameter of the Calculation Scenario3. Formula is a type of input mapping available in Scripted Calculation View, which allows you to map a formula expression to the input parameter of the Scripted Calculation View4. References: 1: Use Table Functions in Calculation Views | SAP Help Portal 2: Map Input Parameters | SAP Help Portal 3: Map Input Parameters or Variables | SAP Help Portal 4: Map Input Parameters | SAP Help Portal
質問 # 63
......
学習材料は有効なC-HANADEV-18効率的問題集：https://www.jpntest.com/shiken/C-HANADEV-18-mondaishu
最新SAP Certified Development Associate C-HANADEV-18実際の無料試験解答：https://drive.google.com/open?id=1_j9S4WQ3qTozWbXFw8JkATMaFaHQUse3