Comprehensive and Detailed Explanation From Exact Extract:

Multi-column internal tables are defined using a structured row type, meaning each row is defined by a structure (either defined inline or as a global structure type in the Dictionary).

Option B is correct because it describes how internal tables with multiple fields are built using structured rows.

Option A is incorrect because the row type must be complete and consistent.

Option C is incorrect because nested components are not a requirement.

Option D is misleading. Though “complete data type” may sound correct, it lacks specificity. The correct technical description is that the row type is a structure.

Comprehensive and Detailed Explanation From Exact Extract:

RAP defines the architecture for OData services based on CDS semantic data models and ABAP behavior—this is the current model.

The predecessor is the ABAP Programming Model for SAP Fiori (BOPF/CDS-based), which can be migrated into RAP; it also exposes ABAP backend logic via CDS semantics.

ABAP Cloud Development Model (B) is the rule set/contract (release contracts, checks), not the service-building model. CAP (C) targets Node.js/Java on BTP, not ABAP-based backend services.

Comprehensive and Detailed Explanation From Exact Extract:

In ABAP, inheritance is declared in the class DEFINITION using the keyword INHERITING FROM. The RAP documentation shows this exact syntax in multiple class definitions, for example:

“CLASS lcl_local_event_consumption DEFINITION INHERITING FROM cl_abap_behavior_event_handler.” This proves the inheritance clause belongs to the DEFINITION section, not the IMPLEMENTATION, and uses the form INHERITING FROM .(Back-End Developer – ABAP Cloud study areas: RAP handler/event classes use standard ABAP OO rules; architecture shows inheritance declared in DEFINITION with INHERITING FROM.)

===========