SAP C_ABAPD_2507 Practice Test Questions Answers

 Database table

 Data model view

 Projection view

 Service definition

 Service binding

In RAP, the development flow follows a bottom-up approach, beginning with persistence and ending with OData exposure:

Database table:The persistence layer where data is stored. This is the foundation of the business object model.

Data model view (CDS entity):The CDS view is defined on top of the database table to provide a semantic data model. It represents entities like Travel or Booking.

Projection view:Provides an abstraction of the data model view and controls which fields and associations are exposed externally.

Service definition:Specifies which projection views (entities) are exposed in the OData service.

Service binding:Connects the service definition to a communication protocol (e.g., OData V2 or V4), generating the final consumable service endpoint.

This sequence ensures a layered architecture consistent with RAP guidelines:

Persistence layer → Data model layer → Projection layer → Service layer → Binding to protocol.

Comprehensive and Detailed Explanation From Exact Extract:

In a CDS view entity defined AS SELECT FROM, the association ON condition must use the source aliases defined in the FROM clause.

$projection is used in projection views (AS PROJECTION ON …), not in a basic select view entity. Therefore, options using $projection (B, C) are invalid here.

Using global names (Z_SOURCE1, Z_SOURCE2) in the ON (A) ignores the declared aliases and is not the recommended/valid form within the view definition.

The correct ON clause uses the aliases _Source1 and Source2 with the matching key fields:ON _Source1.carrier_id = Source2.carrier_id (D).

This aligns with CDS modeling rules in RAP: use aliases consistently and model associations with precise ON conditions based on keys.

Study Guide Reference: ABAP CDS Development—Associations & ON conditions; RAP Data Modeling.

Comprehensive and Detailed Explanation From Exact Extract:

Let’s evaluate each field:

field1: Defined as REFERENCE TO abap.clnt(3) — this is correct. It follows standard definition for client fields.

field2: Defined as abap.char(1332) — this is incorrect. In ABAP CDS view entities, the maximum length for CHAR fields is limited to 1333 bytes total row size for all fields in a view or table. A single CHAR(1332) is almost the full limit and considered impractical or invalid in real implementations.

field3: Defined as abap.quan(2) — this is correct, representing a quantity field with 2 decimal places.

field4: Defined as abap.unit(2) — this is correct and compatible with the @Semantics.quantity.unitOfMeasure annotation used in field3.

Therefore, field2 is the invalid field due to its excessive length, likely breaching the allowable memory layout in the HANA table or violating SAP CDS limits.

Comprehensive and Detailed Explanation from Exact Extract:

Tier 1 extensibility in ABAP Cloud corresponds to the safe and upgrade-stable extension layer.

Adding custom fields to released DB tables or CDS views via released extension includes is fully supported.

Using classic user exits (A), manual note corrections (C), or wrappers for unreleased APIs (D) belong to Tier 2 or Tier 3, and are not part of Tier 1 safe extensibility.

This guarantees that custom code in Tier 1 is cloud-ready, upgrade-stable, and based only on released extension points and APIs.

Verified Study Guide Reference: ABAP Cloud Extensibility Model – Three-Tier Extensibility Rules.

Comprehensive and Detailed Explanation From Exact Extract:

The requirement is:

Retrieve all carriers from T_CARRIER

Include them even if no corresponding connections exist in T_CONNECTIONS.

Evaluation of each join type:

A. INNER JOIN:Only returns rows where a carrier has at least one matching connection.❌ Incorrect, since carriers without connections would be excluded.

B. LEFT OUTER JOIN (correct):Returns all rows from the left table (T_CARRIER), and connections if they exist.Missing connections are represented with NULL.✔ Correct answer.

C. LEFT INNER JOIN:This is syntactically invalid in ABAP SQL. INNER JOIN and LEFT OUTER JOIN are separate join types, not combined.❌ Incorrect.

D. RIGHT OUTER JOIN (correct):Equivalent to LEFT OUTER JOIN when the tables are reversed.Returns all rows from T_CARRIER, whether or not connections exist.✔ Correct answer.

Thus, LEFT OUTER JOIN and RIGHT OUTER JOIN are the valid solutions to retrieve all carriers regardless of connections.