C-ABAPD-2309 C_abapd_2309 Practice Questions

CDS Access Control Lists (DCLs) are used to implement Data Control Language. Their sole purpose is to define authorizations for the data exposed by a CDS view. The DCL automatically enriches the WHERE clause of any query to the CDS view, filtering the results to show only the rows the current user is authorized to see based on their assigned roles.

Inline declarations (@DATA(...)) allow the ABAP compiler to infer the data type of the variable from its context. In a SELECT statement, the compiler determines the structure of the result set and creates the internal table with a matching row type automatically. This reduces boilerplate code, improves readability, and avoids potential type mismatches from manual declarations.

The FOR BEHAVIOR OF Z_I_MY_BO clause is essential syntax that formally links the ABAP class (the behavior pool) to a specific RAP Behavior Definition. This allows the class to act as the provider for the business logic defined in the BDEF, such as methods for validations, actions, and determinations. Without this link, the RAP framework would not know which class contains the implementation.

The ABAP Cloud model is fundamentally different from classic GUI-based development. Direct access to the presentation server (user's PC) is not possible. The modern approach is to expose the data via a web-based service (OData) and build a Fiori UI. Fiori UIs have built-in capabilities for exporting list data to formats like Excel, which is the cloud-compliant equivalent of GUI_DOWNLOAD.

A RAP Business Object is defined by a single root entity. A Behavior Definition (BDEF) is created specifically for one root entity and its compositional hierarchy of child entities. It is not possible to define multiple root entities within a single BDEF.

Using an INNER JOIN in the ABAP SQL statement is the most efficient method. It pushes the data combination logic down to the database, which performs the join operation much faster than the application server can. This results in a single database roundtrip that returns the complete, pre-joined data set, minimizing network traffic and application server load compared to SELECT...ENDLOOP or FOR ALL ENTRIES.

In the strict ABAP Cloud development model, especially in S/4HANA Cloud Public Edition, using non-released objects is not permitted and will block the transport of the code. The only correct action is to redesign the solution to work within the constraints of the available released APIs. This ensures the extension is upgrade-stable and compliant with Clean Core principles.

The core principle of Clean Core extensibility is to avoid direct dependencies on internal implementation details of the core system. Consuming a stable, released API provided by SAP ensures that the extension is decoupled and upgrade-safe. Direct database access, using unreleased BAPIs, or replicating data without a clear strategy violate these principles.

For a custom operation that acts on a specific instance of a business object (like a draft record) and is triggered by the user, an instance-based action is required. The syntax 'action ( instance )' defines it as such. The 'result [1] $self' part indicates that the action modifies and returns the state of the current instance. A static action is not tied to an instance, and a determination is an internally triggered operation, not a user-initiated one.

A composition is the correct choice for modeling a part-of relationship where the lifecycle of the child entity (item) is dependent on the parent (header). This is a strong association that enables deep create/update/delete operations in RAP business objects. An association is weaker and implies independent lifecycles. A LEFT OUTER JOIN is a query-specific operation, not a reusable data model relationship. TO ONE cardinality is incorrect for a one-to-many relationship.