SAP Updated C_ABAPD_2507 Exam Questions and Answers by stevie

Comprehensive and Detailed Explanation From Exact Extract:

UI layout is defined with @UI annotations; it is recommended to maintain the UI annotations in metadata extensions to separate concerns and keep CDS clean.

Metadata extensions provide CDS annotations (such as @UI) outside the data definition and allow layered, switchable UI metadata.

In the RAP tutorial, the “Adding UI Metadata to the Data Model” section explicitly instructs creating metadata extensions for projection views to control the presentation (line items, identification, hidden fields, search, text arrangement). Therefore, the RAP artifact used to organize how fields are displayed in the app is the Metadata Extension.

Comprehensive and Detailed Explanation from Exact Extract:

In ABAP Cloud / RAP, authorization control follows a structured approach:

Read access → can be controlled implicitly via an Access Control object (D).

Create, Update, Delete access → can be controlled both:

Explicitly with AUTHORITY-CHECK (B),

Or implicitly through Access Control object definitions (C).

General implicit control via Access Control (A) or explicit checks for Read (E) are not correct because the system differentiates access levels precisely.

This ensures that business users can only access the data they are authorized for, following RAP’s security-by-default principle.

Verified Study Guide Reference: RAP Security & Access Control Documentation – Authorization in RAP BOs.

Comprehensive and Detailed Explanation from Exact Extract:

SAP S/4HANA Cloud Extensibility Framework defines personas for extension activities:

Business Experts → implement extensions with business knowledge (using in-app extensibility).

Citizen Developers → build extensions with low-code/no-code tools.

Report Writer and Workflow Administrator are roles, but not part of extensibility personas.

Verified Study Guide Reference: ABAP Cloud Extensibility Guide – Personas in SAP S/4HANA Cloud.

Comprehensive and Detailed Explanation from Exact Extract:

Sorted tables can be declared with unique keys (ensuring no duplicates) or with non-unique keys (allowing duplicates).

Hashed tables only allow unique keys.

Standard tables allow non-unique keys only.

Thus, sorted internal tables are the only type that can be configured with both unique and non-unique keys.

Verified Study Guide Reference: ABAP Dictionary and ABAP Cloud Programming Guide – Internal Table Types.