SAPは2024年最新のC-HANADEV-18サンプル問題は信頼され続けるC-HANADEV-18テストエンジン [Q40-Q57]

SAPは2024年最新のC-HANADEV-18サンプル問題は信頼され続けるC-HANADEV-18テストエンジン

無料お試しSAP C-HANADEV-18問題集PDFは必ずベストの問題集オプションを使おう

認定試験は、SAP HANAと協力しており、SAP HANAプラットフォームをよく理解している開発者に適しています。この試験では、SQLやSAP HANA開発ツールの使用など、SAP HANAアプリケーションの開発と展開に焦点を当てています。この試験では、データモデリング、情報モデル、計算ビューなど、さまざまなモデリング手法もカバーしています。

SAP C-Hanadev-18認定試験の準備をするには、候補者はSAP HANAプラットフォーム上のアプリケーションの開発と展開の経験が必要です。また、SAP HANAアーキテクチャとプログラミング、およびデータモデリングと管理を深く理解する必要があります。オンラインコース、学習ガイド、練習試験など、候補者が試験の準備を支援するために利用可能な多くのリソースがあります。

質問 # 40
You create a simple data model to store user information. The model contains two tables: one for the user information, and the other for user address details.
The user can only have one address. You also need a view to show the complete information of the user including the address.
Which actions do you perform if you use CDS artifacts only? Please choose the correct answer.

A. Define a User Details view using select on the user entity and using the association to read the address information.
Create two entities for the user and address.
Extend the user entity with address columns.
B. Create a view named User Details using select on the user entity.
x-s Create two entities for the user and address.
Create a User Details calculation view and join the user and address information.
C. Create two entities for the user and address.
Create an association in the user entity to the address entity.
D. Create two entities for the user and address.
Create an association in the user entity to the address entity.
Define a User Details view using select on the address entity and using the association to read the user information.

正解：A

解説：
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

質問 # 41
What types of user-defined functions are supported by SAP HANA? Note: There are 2 correct answers to this question.

A. Hierarchy
B. Scalar
C. Table
D. Aggregate

正解：B、C

解説：
SAP HANA supports two types of user-defined functions: table and scalar. User-defined functions are functions that are created by users to perform specific tasks or calculations on data. User-defined functions can be used in SQL expressions, such as in the SELECT, WHERE, or GROUP BY clauses of SQL statements.
User-defined functions can also be used in SQLScript, which is a scripting language for SAP HANA that extends SQL with procedural and analytical features.
Table functions are user-defined functions that return a table as the output. Table functions can be used to implement complex logic or transformations on data, such as pivoting, unpivoting, aggregation, or ranking.
Table functions can also be used to create calculation views, which are virtual data models that expose data from SAP HANA tables or views. Table functions are created by using the CREATE FUNCTION statement with the RETURNS <return_table_type> clause, where <return_table_type> specifies the table type of the output. Table functions can be called in the FROM clause of SQL statements, or in the node expression of calculation views.
Scalar functions are user-defined functions that return a scalar value as the output. Scalar functions can be used to perform simple calculations or validations on data, such as converting units, checking conditions, or generating IDs. Scalar functions are created by using the CREATE FUNCTION statement with the RETURNS
<return_parameter_list> clause, where <return_parameter_list> specifies the scalar type of the output. Scalar functions can be called in the SELECT or WHERE clauses of SQL statements, or in the expression of calculated columns.
The following types of functions are not supported by SAP HANA as user-defined functions, but as built-in functions or features:
* Aggregate functions: Aggregate functions are functions that perform calculations on a set of values and return a single value. For example, SUM, COUNT, MIN, MAX, or AVG are aggregate functions.
Aggregate functions are built-in functions that are provided by SAP HANA and can be used in SQL expressions, such as in the SELECT or GROUP BY clauses of SQL statements, or in the expression of aggregated columns. Aggregate functions cannot be created by users as user-defined functions.
* Hierarchy functions: Hierarchy functions are functions that operate on hierarchical data, such as parent-child or level-based hierarchies. For example, HIERARCHY_ANCESTORS, HIERARCHY_DESCENDANTS, or HIERARCHY_LEVEL are hierarchy functions. Hierarchy functions are built-in functions that are provided by SAP HANA and can be used in SQL expressions, such as in the SELECT or WHERE clauses of SQL statements, or in the expression of hierarchy columns. Hierarchy functions cannot be created by users as user-defined functions.
References:
* [SAP HANA Platform Documentation], SAP HANA SQL and System Views Reference, Chapter 3:
SQL Expressions, Section 3.5: Function Expressions, pp. 59-60.
* [SAP HANA Platform Documentation], SAP HANA SQLScript Reference, Chapter 6: SQLScript Test Framework, Section 6.1: User-Defined Functions, pp. 153-154.

質問 # 42
What is the package descriptor package.json used for? There are 2 correct answers to this question.

A. To define the routes
B. To list the package dependencies
C. To define back-end destinations
D. To set the router version

正解：B、D

質問 # 43
How do you debug a Node.js module in SAP Web IDE for SAP HANA? Please choose the correct answer.

A. Add the sap.hana .xs.debugger::Debugger role to the HDI Container's #RT User.
B. Attach the debugger to the application in the SAP Web IDE for SAP HANA.
C. Start the debugger from the XS command line interface and run the program in SAP Web IDE for SAP HANA.
D. Set the enabled parameter to true in the section debugger of the xsengine.ini file.

正解：B

解説：
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.

質問 # 44
Which tool do you use to create a calculation view in a multi-target application? Please choose the correct answer.

A. SAP HANA studio
B. SAP HANA Web-based Development Workbench
C. SAP HANA database explorer
D. SAP Web IDE for SAP HANA

正解：D

質問 # 45
What are the steps to debug a Node.js application using SAP Web IDE for SAP HANA? There are 3 correct answers to this question.

A. Attach the debugger to the node module.
B. Open the debugger.
C. Specify the proper Git repository in the debug properties.
D. Build the application with the debug option.
E. Set a breakpoint in the application.

正解：A、B、E

解説：
To debug a Node.js application using SAP Web IDE for SAP HANA, you need to perform the following steps:
* Open the debugger. You can open the debugger from the toolbar by clicking the \uE921 (debugger) icon, or from the menu by choosing Tools Debugger . The debugger opens in a new browser tab and shows a list of all Node.js modules in your project, as well as the available debug configurations.
* Attach the debugger to the node module. You can attach the debugger to any running Node.js module in your project by selecting the module name and clicking the \uE921 (attach) icon. Alternatively, you can create a new debug configuration for the module by clicking the \uE921 (create) icon and specifying the module name, the port number, and the source mapping. The debugger will connect to the Node.js module and switch it to debug mode.
* Set a breakpoint in the application. You can set a breakpoint in the application code by opening the file in the editor and clicking the left margin next to the line number where you want to pause the execution.
A red dot will appear to indicate the breakpoint. You can also use the \uE921 (breakpoints) pane to view, enable, disable, or remove breakpoints.
* Run the application. You can run the application from the browser by clicking the application URL in the run console, or from the command line by using the cf CLI commands. The application will execute until it reaches a breakpoint or an exception, and then pause and show the current state of the variables, call stack, and watch expressions in the debugger.
* Debug the application. You can use the debugger to inspect and modify the variables, evaluate expressions, step over, step into, step out, or resume the execution, as well as view the console output and the server log. You can also detach the debugger from the module by clicking the \uE921 (detach) icon, or stop the module by clicking the \uE921 (stop) icon.
The other option is incorrect because you do not need to specify the proper Git repository in the debug properties. The Git repository is used to manage the source code of the application, but it is not relevant for the debugging process. You also do not need to build the application with the debug option, because the debugger can attach to any running Node.js module without any special build settings. References:
* Running and Testing Node.js Modules - SAP Help Portal
* Debugging Node.js Modules - SAP Help Portal

質問 # 46
What are the different types of graphical calculation views that can handle measures? There are 2 correct answers to this question.

A. Cube with star join
B. SQL Access Only
C. Dimension
D. Cube

正解：A、D

解説：
Graphical calculation views are graphical or scripted views that can be used for complex calculations and data transformations in SAP HANA. There are three types of graphical calculation views: cube, dimension, and SQL access only. Cube and cube with star join are the only types that can handle measures, which are numeric values that can be aggregated, such as sales amount or quantity. Dimension views are used to model master data or attributes, such as product name or customer ID. SQL access only views are used to expose the data of another view without any additional logic or transformation. References:
* SAP HANA 2.0 SPS06 - Application Development for SAP HANA1, Section 4.1, p. 77-78
* SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.1, p. 7
* SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.2, p. 8-9
* SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.3, p. 10-11
* SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.4, p. 12-13
* SAP HANA 2.0 SPS06 - Calculation View Modeling2, Section 1.5, p. 14-15

質問 # 47
What are the main SAP HANA engines responsible for executing calculation views? There are 3 correct answers to this question.

A. OLAP Engine
B. XS Engine
C. Join Engine
D. Calculation Engine
E. Java Engine

正解：A、C、D

質問 # 48
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.

A. The objects owned by other users are NOT dropped.
B. The objects on which other users have privileges are dropped.
C. The objects on which other users have privileges are NOT dropped.
D. The objects owned by other users are dropped.

正解：A、C

解説：
When a user is dropped with the "cascade" option, the user and all the objects owned by the user are deleted from the database. However, the objects that are owned by other users, or on which other users have privileges, are not affected by the drop command. The privileges granted to or by the dropped user are also revoked automatically. Therefore, the objects on which other users have privileges are not dropped, and the objects owned by other users are not dropped12.
The other options are not correct because they are not the consequences of dropping a user with the "cascade" option. The objects on which other users have privileges are not dropped, because they are not owned by the dropped user, and they may still be needed by the other users. The objects owned by other users are not dropped, because they are not related to the dropped user, and they may have dependencies or references to other objects. References:
* SAP HANA Platform, SAP HANA SQL and System Views Reference, SQL Reference Manual, SQL Statements, DROP USER
* SAP HANA Platform, SAP HANA Administration Guide, Security, User Management, Dropping Users

質問 # 49
Which services can you use in SAP HANA, express edition? There are 3 correct answers to this question.

A. Dynamic tiering
B. Columnar OLTP and OLAP
C. Multi-core and parallelization
D. Text analytics
E. System replication

正解：B、C、D

質問 # 50
What are the key characteristics of the calculation view's Input Parameter? There are 3 correct answers to this question.

A. It is passed using a WHERE clause.
B. It is passed via reserved word PLACEHOLDER.
C. It can be used to pass values to table functions.
D. It can NOT be used to filter measure values.
E. It can be used in a conditional expression.

正解：B、C、E

質問 # 51
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. Choose the supported SAP HANA versions.
B. Create objects in the SAP HANA repository.
C. Configure the artifact namespaces.
D. Deploy HTML5 modules to the SAP HANA database.

正解：B、D

質問 # 52
Which join type is NOT supported by join optimization (pruning)? Please choose the correct answer.

A. Inner Join
B. Text Join
C. Outer Join
D. Referential Join

正解：A

解説：
Join optimization (pruning) is a technique that allows you to omit join fields from the aggregation if they are not requested by the query and they do not affect the result set. Join optimization (pruning) can improve the query performance by reducing the data volume and the number of join operations. However, join optimization (pruning) is only supported for certain types of joins, such as outer join, text join, and referential join. These types of joins preserve the number of records from one of the join partners, regardless of the join condition. Therefore, the join execution does not influence the result set, and the join fields can be safely omitted12.
Inner join is not a type of join that is supported by join optimization (pruning). Inner join is a type of join that only returns the records that have a matching partner in both join partners, based on the join condition. Inner join can add or delete records from the result set, depending on the data and the join condition. Therefore, the join execution does influence the result set, and the join fields cannot be omitted without changing the query semantics12. References: 1: Optimize Join Execution | SAP Help Portal 2: Prerequisites for Pruning Join Columns | SAP Help Portal

質問 # 53
What are the characteristics of SAP HANA calculation views? There are 2 correct answers to this question.

A. Need database tables to execute
B. Do NOT need database tables to execute
C. Do NOT need an application server to execute
D. Need an application server to execute

正解：A、C

解説：
SAP HANA calculation views are flexible information views that you can use to define more advanced slices on the data available in the SAP HANA database. Calculation views can be created using graphical or script-based editors, and can include any combination of tables, column views, attribute views, analytic views, and other calculation views. Calculation views can also support complex expressions, multidimensional analysis, currency conversion, hierarchies, and other analytic capabilities. Some general characteristics of calculation views are:
* Need database tables to execute. Calculation views are based on the data stored in the SAP HANA database tables, either in column or row format. Calculation views can access data from local or remote tables, as well as virtual tables that are mapped to external data sources. Calculation views can also use data from other information views, such as attribute views or analytic views, which are also based on database tables. Calculation views do not store any data themselves, but rather perform calculations on the fly when queried.
* Do NOT need an application server to execute. Calculation views are executed by the SAP HANA Calculation Engine, which is a component of the SAP HANA database that handles the processing of complex calculations and transformations on the data. Calculation views do not require any application server or middleware layer to run, as they are directly exposed to the reporting tools and applications via SQL or MDX interfaces. Calculation views can also be accessed by SAP HANA extended application services, advanced model (XS advanced), which is a framework for developing and running applications on the SAP HANA platform.
The other options are incorrect because calculation views do not need an application server to execute, nor do they not need database tables to execute. These are the opposite of the correct characteristics of calculation views. References:
* Using Calculation Views - SAP Help Portal
* Calculation View Instantiation Process - SAP Help Portal
* SAP HANA Calculation Engine - SAP Help Portal
* SAP HANA Extended Application Services, Advanced Model - SAP Help Portal
* [HA300 - SAP HANA 2.0 SPS06 Modeling] - SAP Training

質問 # 54
What characterizes the Node.js environment? There are 2 correct answers to this question.

A. It is a client-side design-time environment for JavaScript.
B. It uses a synchronous programming model.
C. It is single-threaded.
D. It is built on Google's V8 JavaScript engine.

正解：C、D

解説：
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.

質問 # 55
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. Consistency
D. Modification

正解：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

質問 # 56
You need to create a native SAP HANA application that fully leverages the SAP HANA platform. How do you implement data-intensive calculations?
Please choose the correct answer.