C_CPE_2409 · Question #10
Out of the box, which of the following can CAP applications use to interact with external APIs and services? Note: There are 2 correct answers to this question.
The correct answer is C. OData D. REST. CAP (SAP Cloud Application Programming model) natively supports OData and REST as protocols for interacting with external services out of the box. OData is deeply integrated into CAP's service layer - you can import EDMX definitions and consume remote OData APIs using…
Question
Out of the box, which of the following can CAP applications use to interact with external APIs and services? Note: There are 2 correct answers to this question.
Options
- AWebSockets
- Bsoap
- COData
- DREST
How the community answered
(28 responses)- A4% (1)
- B7% (2)
- C89% (25)
Explanation
CAP (SAP Cloud Application Programming model) natively supports OData and REST as protocols for interacting with external services out of the box. OData is deeply integrated into CAP's service layer - you can import EDMX definitions and consume remote OData APIs using cds.connect.to() with no extra setup. REST is equally supported as a first-class protocol for external service consumption, letting you define and call REST endpoints directly within the CAP framework.
Why the distractors are wrong:
- A (WebSockets): CAP does not provide out-of-the-box support for WebSocket-based external service communication - it's focused on request/response patterns.
- B (SOAP): SOAP requires additional wrappers or adapters (e.g., via the SAP Cloud SDK) and is not natively supported by CAP for external service consumption.
Memory tip: Think "CAP speaks OR" - OData and REST are its native languages for the outside world. Anything else (SOAP, WebSockets) needs extra plumbing.
Topics
Community Discussion
No community discussion yet for this question.