Which of the following are benefits of using the OData Virtual Data Model of the SAP Cloud SDK? Note: There are 3 correct answers to this question.

Question

Options

• ACommonly used SQL query technology
• BEasy access to create, update, and delete operations
• CType safety for functions
• DAuto-completion of function names and properties
• EDatabase procedures provided out of the box

• A
  6% (2)
• B
  91% (30)
• C
  3% (1)

Explanation

Options B, D, and E correctly describe benefits of the SAP Cloud SDK's OData Virtual Data Model (VDM). The VDM provides a fluent, type-aware API that makes CRUD operations (B) straightforward without manually crafting HTTP requests. Because the VDM is auto-generated from OData service metadata, your IDE gains full auto-completion for entity properties and function names (D), dramatically reducing typos and guesswork. The SDK also ships with pre-built client libraries for standard SAP S/4HANA OData services (E), meaning function imports (analogous to procedures) are ready to use immediately without custom generation.

Why A is wrong: The VDM uses OData query conventions ($filter, $select, $expand), not SQL - these are entirely different technologies targeting APIs, not databases directly.

Why C is wrong: While the VDM does leverage TypeScript's type system, "type safety for functions" is not a distinct VDM benefit - it's a general TypeScript feature. The VDM's specific value-add is auto-completion and structured access to entity models (covered by D), not function-level type safety as a standalone feature.

Memory tip: Think "BDA" - Build (easy CRUD), Discover (auto-complete), Available (out-of-the-box services). The wrong answers distract with SQL (a database language, not OData) and a vague claim about "type safety for functions" that blurs into what D already covers.

No community discussion yet for this question.