Why should you use SAP Fiori annotations in CAP projects?

Question

Options

• ATo facilitate real-time data synchronization
• BTo enable automatic database schema migration
• CTo improve frontend loading time
• DTo enrich the service with Ul-specific instructions

• B
  5% (1)
• D
  95% (20)

Explanation

SAP Fiori annotations in CAP projects exist to enrich OData services with UI-specific metadata - things like labels, field groups, list columns, and form layouts - so that Fiori Elements apps can automatically generate their UIs from the service definition without hand-coding each view. This is a declarative approach where the backend service "tells" the frontend how data should be presented.

Why the distractors are wrong:

• A (real-time sync): That's the domain of WebSockets or OData subscriptions, not annotations.
• B (database schema migration): Schema migration in CAP is handled by cds deploy and the underlying database adapters, not annotations.
• C (frontend loading time): Annotations don't optimize asset delivery or reduce payload size; performance tuning uses techniques like lazy loading, caching, and compression.

Memory tip: Think of annotations as sticky notes you attach to your data model - they don't change the data or the database, they just leave instructions for the UI renderer about how things should look and behave.

No community discussion yet for this question.