Which file includes by default the configuration for an external OData service in a Node.js CAP project?

Question

Options

• Aindex.js
• Bpackage.json
• Cmanifest.json
• Dservice.cds

• A
  7% (3)
• B
  2% (1)
• C
  2% (1)
• D
  89% (39)

Explanation

In SAP CAP (Cloud Application Programming Model) for Node.js, external OData service definitions are declared using CDS (Core Data Services) syntax, making service.cds the default home for modeling an external OData service's interface - you typically import its metadata here using using ... from './external/ServiceName' after running cds import on the service's EDMX file.

Why the distractors are wrong:

• A (index.js): This is a generic Node.js application entry point and has no role in CAP service modeling.
• B (package.json): While package.json holds the cds.requires block for runtime binding (credentials, URLs), the structural definition of the service belongs in .cds files.
• C (manifest.json): This is an SAP Fiori/UI5 frontend descriptor - it lives in the webapp/ folder and is unrelated to backend CAP service configuration.

Memory tip: The extension is your cue - CAP uses CDS files (.cds) for Configuring services. If it's about the service shape, think .cds; if it's about the runtime connection, think package.json.

No community discussion yet for this question.