C_CPI_2506リアル試験問題解答は更新された[2026年01月21日]
お手軽に合格させる 最新SAP C_CPI_2506問題集には62問があります
SAP C_CPI_2506 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
質問 # 29
You want to use an HTTPS endpoint from an integration flow. In which of the following must you use the HTTP client?
- A. Open Connectors capability within SAP Integration Suite
- B. API Management capability within SAP Integration Suite
- C. SAP Integration Suite, advanced event mesh
- D. SAP Business Application Studio
正解：A
解説：
To use an HTTPS endpoint from an integration flow, you can use the Open Connectors capability within SAP Integration Suite. Open Connectors is a feature that allows you to connect to over 160 third-party applications using standardized and normalized APIs. You can use the HTTP client connector to make HTTP or HTTPS requests to any endpoint that supports these protocols. You can configure the HTTP client connector with various parameters, such as URL, method, headers, query parameters, body, and authentication. Reference: Open Connectors | SAP Help Portal, HTTP Client Connector | SAP Help Portal
質問 # 30
What must you do to find out which entity sets are available in the OData V2.0 interface?
- A. Retrieve the service document from the interface.
- B. Contact the OData interface manufacturer.
- C. Search in the Global Directory of all available OData interfaces.
- D. Retrieve the metadata document from the interface.
正解：D
解説：
In SAP Integration Development, particularly when working with OData V2.0 interfaces, the correct way to identify the available entity sets is by retrieving the metadata document from the OData service. The metadata document, accessible via the $metadata endpoint of the OData service, provides a comprehensive description of the service's data model, including all entity sets, entity types, properties, associations, and navigation properties. This document is formatted in XML (CSDL - Conceptual Schema Definition Language) and is essential for understanding the structure and capabilities of the OData service.
Why Option B is Correct:
* Metadata Document Role: The metadata document is a standard feature of OData V2.0 services, as defined by the OData protocol. It exposes the schema of the service, listing all entity sets and their properties. For example, accessing https://<service-url>/$metadata returns an XML document detailing the entity sets, such as Customers, Orders, or other resources exposed by the service.
* SAP Reference: According to SAP documentation, such as the SAP Gateway Developer Guide and OData V2.0 Protocol Specification, the metadata document is the primary source for discovering the structure of an OData service. In SAP Gateway, which is commonly used for OData services in SAP environments, the $metadata endpoint is automatically generated when an OData service is created using the Service Builder (transaction SEGW).
* Practical Usage: In SAP Integration Suite or SAP Cloud Integration, developers use the metadata document to configure integration flows (iFlows) that interact with OData services. Tools like SAP Business Application Studio or Eclipse with SAP plugins allow developers to import this metadata to generate client code or configure adapters.
Why Other Options are Incorrect:
* A. Retrieve the service document from the interface: The service document (accessed via the root URL of the OData service, e.g., https://<service-url>/) provides a list of entity sets but only includes their names and URLs, not the detailed structure (e.g., properties, types, or relationships). While it's useful for navigating to entity sets, it lacks the comprehensive schema information provided by the metadata document, making it insufficient for fully understanding the entity sets' structure.
* C. Search in the Global Directory of all available OData interfaces: There is no such thing as a
"Global Directory" for OData interfaces in SAP or the broader OData ecosystem. OData services are specific to individual systems or applications, and their discovery is typically done via the service's metadata or service document, not a centralized directory.
* D. Contact the OData interface manufacturer: This option is not practical or standard. OData is a protocol, not a product with a "manufacturer." The metadata document is the standard, self-contained way to explore an OData service, and no external contact is required.
SAP Integration Developer Workflow Example:
* Access the OData Service: In an SAP environment, an Integration Developer identifies the OData service URL (e.g., https://<host>:<port>/sap/opu/odata/sap/<service_name>).
* Retrieve Metadata: Append / $metadata to the service URL to download the metadata XML. For example, https://<host>:<port>/sap/opu/odata/sap/ZCUSTOMER_SRV/$metadata.
* Analyze Entity Sets: Parse the <EntitySet> elements in the metadata XML to identify available entity sets, their properties, and navigation paths.
* Use in Integration: In SAP Cloud Integration, import the metadata into an iFlow's OData adapter to configure operations like querying or updating specific entity sets.
References:
SAP Help Portal: SAP Gateway Developer Guide - "OData Service Metadata" section, which explains the role of the $metadata endpoint in exposing entity sets and their schema.
OData V2.0 Specification: Section 2.2.3.7.1, "Metadata Document," which mandates that OData services provide a metadata document describing entity sets and other resources.
SAP Integration Suite Documentation: "OData Adapter" section, which details how metadata is used to configure integration flows for OData services.
SAP Community Blogs: Articles on OData development in SAP Gateway, such as "Building OData Services with SAP Gateway," emphasize using the metadata document for service exploration.
質問 # 31
Why does the API Management capability of the SAP Integration Suite require API providers?
- A. To create authenticated API instances
- B. To incorporate APIs from source systems
- C. To create APIs
正解：B
解説：
In API Management (Integration Suite):
API Providers represent backend systems (e.g., SAP S/4HANA, SuccessFactors, third-party APIs).
They are required to connect and incorporate APIs from those systems into API Management.
Once defined, API Proxies are created from API Providers to expose APIs securely.
Other options:
Authentication is handled via policies, not API Providers.
APIs are created as API Proxies, not directly by Providers.
Thus, the purpose of API Providers is to incorporate APIs from source systems.
質問 # 32
You configured a content modifier as follows: Action: Create | Name: ProductID | Source Type: XPath Source Value: //ProductID | Data Type: java.lang.string. After testing the content modifier, you receive an error message that contains the following fragment: "Java.lang.ClassNotFoundException: java.lang.string..." What caused the error message?
- A. Incorrect source value
- B. Incorrect data type
- C. Incorrect name
- D. Incorrect source type
正解：B
解説：
In SAP Cloud Integration, when defining Content Modifier properties, the Java data type names are case- sensitive.
Correct type # java.lang.String
In the configuration, java.lang.string was used (lowercase "s"), which causes a ClassNotFoundException, since Java cannot find the class.
Other options are correct in form:
Source Type = XPath # Valid.
Source Value = //ProductID # Valid XPath.
Name = ProductID # Valid.
Thus, the error occurred because of incorrect data type specification.
質問 # 33
For which of the following scenarios can you use scripting in an integration flow?
- A. Add information to the message log.
- B. Configure an OData adapter.
- C. Create XSLT mapping artifacts.
正解：A
解説：
In SAP Cloud Integration (part of Integration Suite), scripting (Groovy, JavaScript) is supported in integration flows to handle custom logic that cannot be achieved by standard adapters or mappings. Example use cases:
Enriching messages with dynamic values.
Adding custom log entries into the Message Processing Log.
Custom validation, conversions, or calculations.
Other options:
A). Create XSLT mapping artifacts # Achieved via XSLT, not scripting.
C). Configure an OData adapter # Done via adapter configuration, not scripting.
Thus, scripting is used for runtime logic enhancements like adding information to the message log.
質問 # 34
What are some message protocols that the AP! Management capability within SAP Integration Suite supports?
Note: There are 2 correct answers to this question.
- A. OData
- B. IDoc
- C. RFC
- D. SOAP
正解：A、D
解説：
API Management in SAP Integration Suite supports HTTP-based protocols.
Supported # SOAP, OData, REST (OpenAPI).
Not supported directly # RFC and IDoc (these are legacy SAP protocols handled via Cloud Integration or On- Premise adapters, not via API Management).
Thus, the correct supported message protocols are SOAP and OData.
質問 # 35
In a Data Store write operation, you want to set an Entry ID by reading a header value from an incoming message.Which notation do you use to implement this?
- A. ${header.receiver}
- B. S${headerreceiver}
- C. S{reaciverheader}
- D. S{reaciverheader}
正解：A
解説：
In SAP Cloud Integration, dynamic configuration values (headers, properties, body elements) are accessed using Expression Language (EL) notation:
${header.<headerName>} # Accesses a message header value.
${property.<propertyName>} # Accesses a message property.
${body} # Accesses the payload.
Therefore, when you want to set an Entry ID in a Data Store Write operation using a header value, the correct syntax is ${header.receiver}.
質問 # 36
Which Sap platform serves as the foundation for SAP' s integration strategy?
- A. SAP Business Technology Platform (SAP BTP).
- B. SAP Netweaver Process Integration (Pl) serves as the foundation for SAP' s integration strategy.
- C. SAP Cloud Platform Integration (CPI) serves as the foundation for SAP' s integration strategy.
- D. SAP S/4HANA serves as the foundation for SAP' s integration strategy.
正解：A
解説：
SAP's integration strategy is founded on the SAP Business Technology Platform (BTP), which provides:
Integration Suite as the strategic iPaaS for process, data, API, and event-driven integration.
Extension Suite for app extensions.
Database & Data Management for unified data access.
Analytics & AI capabilities.
Other options:
SAP CPI # Now part of Integration Suite, not the overall foundation.
SAP S/4HANA # The digital core ERP, but not the integration platform.
SAP NetWeaver PI/PO # Legacy middleware, replaced strategically by Integration Suite on BTP.
Thus, the foundation of SAP's integration strategy is SAP BTP.
質問 # 37
What does the messaging model of the Apache Camel Data Model consist of?
- A. Header, body, properties
- B. Header, properties, attachment
- C. Header, body, attachment
- D. Header, Exchange ID, in-message
正解：A
解説：
The Apache Camel Data Model, which underpins SAP Cloud Integration's message processing model, consists of:
Header # Metadata about the message (e.g., content type, correlation IDs).
Body # Main payload of the message.
Properties # Exchange-level metadata, persisted throughout processing but not transferred with the message.
Other options mix in elements like attachments or exchange IDs, but the standard messaging model is header, body, properties.
質問 # 38
What are some advantages of the cloud integration capability within SAP Integration Suite? Note: There are 2 correct answers to this question.
- A. Integration processes can be developed offline.
- B. Customer-to-Customer(C2C) integrations can be developed
- C. A local installation is not required.
- D. Predefined scenarios can be used out-of-the-box.
正解：C、D
解説：
Some advantages of the cloud integration capability within SAP Integration Suite are:
A local installation is not required. The cloud integration capability is a cloud-based service that runs on SAP Business Technology Platform (BTP). It does not require any installation or maintenance on your local system. You can access it from any web browser and start developing and deploying integration flows using a graphical user interface or an Eclipse-based tooling.
Predefined scenarios can be used out-of-the-box. The cloud integration capability provides a rich set of predefined integration scenarios that cover various use cases and domains, such as SAP-to-SAP integration, SAP-to-non-SAP integration, hybrid integration, process orchestration, and so on. You can browse and discover these scenarios from the Discover page of the cloud integration web UI or from the SAP API Business Hub. You can use these scenarios as they are or customize them according to your needs. Reference: Cloud Integration Capability Overview | SAP Help Portal, Discover Integration Content | SAP Help Portal
質問 # 39
You are creating an API proxy. Which of the following is a valid path prefix?
- A. /sap/odu/odata
- B. /soap/opu/odata
- C. /sap/opu/odata
- D. /sap/opo/odata
正解：C
解説：
In SAP systems (e.g., S/4HANA, SAP Gateway), OData services follow a standard URL path:
/sap/opu/odata # The valid and official prefix for OData services.
Example: /sap/opu/odata/sap/API_BUSINESS_PARTNER
Other options:
/sap/opo/odata and /sap/odu/odata # Typographical variations, not valid.
/soap/opu/odata # Incorrect, since OData is not SOAP-based.
Thus, the valid prefix is /sap/opu/odata.
質問 # 40
Which log level must you use to examine the payload at specific processing steps in an integration flow?
- A. Error
- B. Debug
- C. Info
- D. Trace
正解：D
解説：
To examine the payload at specific processing steps in an integration flow, you must use the Trace log level. The Trace log level provides the most detailed information about the message processing, including the payload content and the headers at each step. You can use the Message Processing Log to view the trace logs for a specific message. Reference: Modernize Integration with SAP Integration Suite | openSAP
質問 # 41
You configured a content modifier as follows: Action Create. Name: ProductID. Source Type: XPath. Source Value: //ProductID. Data Type: java lang string. After testing the content modifier, you receive an error message that contains the following fragment: java.lang.ClassNotFoundException java lang string. What caused the error message?
- A. Incorrect source value
- B. Incorrect data type
- C. Incorrect name
- D. Incorrect source type
正解：B
解説：
The error message is caused by an incorrect data type in the content modifier configuration. The data type should be java.lang.String instead of java lang string. The data type defines the type of the value that will be stored in the header or property of the message. It should match one of the supported Java classes, such as java.lang.String, java.lang.Integer, java.lang.Boolean, and so on. If the data type is not valid, a java.lang.ClassNotFoundException will be thrown. Reference: Content Modifier | SAP Help Portal, Getting clear with SAP Integration Suite Content Modifier | SAP Blogs
質問 # 42
What is Representational State Transfer (REST)?
- A. An architectural style
- B. An application protocol
- C. A message protocol
- D. A description language for APIs
正解：A
解説：
REST (Representational State Transfer) is:
An architectural style for designing networked applications.
Based on principles such as statelessness, resource orientation, uniform interface (HTTP methods: GET, POST, PUT, DELETE).
Used widely in SAP (OData is REST-based).
Other options:
Not a protocol (like HTTP), not a description language (like OpenAPI), and not limited to messaging.
Correct definition # Architectural style.
質問 # 43
You have created a product based on an API proxy, but you have not published the product yet. What is a consequence?
- A. The product is displayed in the API Business Hub Enterprise but is grayed out.
- B. The product is not displayed in the API Business Hub Enterprise.
- C. The product is displayed in the API Business Hub Enterprise with the note "not published".
正解：B
解説：
In API Management (part of SAP Integration Suite), when you create an API Product (which bundles API Proxies for consumption):
Publishing is required before it becomes visible in API Business Hub Enterprise (Developer Portal).
If the product is not yet published, it remains in the design-time environment and is invisible to app developers.
Only published products are available for subscription and discovery.
Other options:
The product will not be shown grayed out or with a "not published" note; it simply won't be visible at all in the Business Hub Enterprise.
質問 # 44
You want to build an architecture that is largely asynchronous. Which design do you use to exchange notifications between the partners involved?
- A. Serverless design
- B. Request-driven design
- C. Hexagonal design
- D. Event-driven design
正解：D
解説：
You can use an OData adapter to implement a synchronous call to a remote HTTP API as an integration flow component. An OData adapter allows you to send and receive messages using the OData protocol. OData stands for Open Data Protocol and is a standard for exposing and consuming data over HTTP or HTTPS. You can use an OData adapter to communicate with OData services that support CRUD (Create, Read, Update, Delete) operations on resources. Reference: Integration Software | SAP Integration Suite, Modernize Integration with SAP Integration Suite | openSAP
質問 # 45
What is a characteristic of a product in the API Management capability within SAP Integration Suite?
- A. It is deployed as a separate artifact on the API business hub enterprise
- B. It encapsulates the API provider.
- C. It is a separate artifact and is required for basic authentication.
正解：A
解説：
A product in the API Management capability within SAP Integration Suite is a bundle of one or more API proxies that are grouped together for a specific business scenario or use case. A product is a separate artifact that can be deployed to the API business hub enterprise, which is a centralized platform for discovering, consuming, and managing APIs. A product can have its own metadata, such as name, title, description, quota limits, and so on. A product can also have its own policies that apply to all the APIs included in it. Reference: Create a Product | SAP Help Portal, API Business Hub Enterprise | SAP Help Portal
質問 # 46
What are the maturity levels of the SAP Integration Solution Advisory Method-ology? Note: There are 2 answers to this question.
- A. Enable your integration structure.
- B. Design your hybrid integration platform.
- C. Implement your integration architectural strategy.
- D. Assess your integration strategy
正解：B、D
解説：
The maturity levels of the SAP Integration Solution Advisory Methodology are as follows:
Assess your integration strategy. This level helps you evaluate your current integration landscape and identify the gaps and challenges that need to be addressed.
Design your hybrid integration platform. This level helps you define your target integration architecture and select the best-fit integration technologies and tools for your scenarios.
Implement your integration architectural strategy. This level helps you execute your integration projects and deliver value to your business.
Enable your integration structure. This level helps you establish a governance model and best practices for your integration operations and maintenance. Reference: Integration Software | SAP Integration Suite, Modernize Integration with SAP Integration Suite | openSAP
質問 # 47
What must you do to find out which entity sets are available in the OData V2.0 interface?
- A. Retrieve the service document from the interface.
- B. Contact the OData interface manufacturer
- C. Retrieve the metadata document form the interface.
- D. Search in the Global Directory of all available OData interfaces.
正解：C
解説：
To find out which entity sets are available in the OData V2.0 interface, you must retrieve the metadata document from the interface. The metadata document is an XML document that describes the data model of the OData service, including the entity types, entity sets, associations, functions, and actions. The metadata document can be accessed by appending $metadata to the service root URL of the OData service. For example, if the service root URL is https://services.odata.org/OData/OData.svc/, then the metadata document URL is https://services.odata.org/OData/OData.svc/$metadata. The metadata document can be used to discover the structure and capabilities of the OData service and to generate client code or proxies. Reference: Overview (OData Version 2.0) | OData - The Best Way to REST, OData API v2 Reference | SAP Help Portal
質問 # 48
You want to send messages over an SOAP adapter to an integration flow. Which method do you use to send the messages?
- A. POST
- B. UPDATE
- C. PATCH
- D. GET
正解：A
解説：
To send messages over a SOAP adapter to an integration flow, you must use the POST method. The POST method is used to create or update a resource on the server using the SOAP message body as the input. The SOAP adapter supports both SOAP 1.1 and SOAP 1.2 protocols and can handle both one-way and request-reply message exchange patterns. The SOAP adapter can be configured as a sender or a receiver channel in an integration flow. Reference: SOAP (SOAP 1.x) Adapter | SAP Help Portal, SOAP Sender Adapter: Example Integration Flow | SAP Help Portal
質問 # 49
You want to set up Exchange Properties in an integration flow.Besides a Content Modifier, what can you use?
- A. Python scripting
- B. Batch scripting
- C. XML scripting
- D. Groovy SDK scripting
正解：D
解説：
In SAP Cloud Integration, Exchange Properties can be created and set using:
Content Modifier # Standard way to configure properties.
Groovy Scripting # Via the SAP CPI Groovy SDK, you can dynamically add or update exchange properties at runtime.
Other options:
Batch scripting, XML scripting, Python scripting # Not supported in SAP CPI.
Thus, besides Content Modifier, you use Groovy SDK scripting.
質問 # 50
......
最新のC_CPI_2506学習ガイド2026年最新の- 提供するのはテストエンジンとPDF：https://www.jpntest.com/shiken/C_CPI_2506-mondaishu
最新版を今すぐ試そうC_CPI_2506練習テスト問題解答：https://drive.google.com/open?id=1QyKicIBHIPzERYDE4SRyRfIWWZJGQwJe