Review: keep model, behavior, and exposure distinct

A maintainable RAP solution gives each artifact a clear responsibility. The root model describes data, behavior defines transactional operations, projections tailor consumers, and the service artifacts expose a protocol. Authorization, validation, draft, and concurrency controls are part of the design—not automatic consequences of publishing an API.

This original quiz is interactive in the browser, but it does not compile a RAP BO or connect to an SAP system.

Sources

Developer practice · ABAP

Practice: RAP architecture knowledge check

Answer these original review questions about assembling a RAP business object and service.

1. What is the role of a CDS root entity?

2. What does a composition usually express?

3. What does managed RAP provide for standard operations?

4. Why add a projection?

5. What does a validation do?

6. Does CDS DCL alone authorize a RAP update?

7. What is a draft workflow for?

8. What does a service binding do?