Practice Free C_ABAPD_2507 Exam Online Questions
Which of the following integration frameworks have been released for ABAP Cloud development? (Select 3)
- A . CDS Views
- B . Business events
- C . OData services
- D . Business Add-ins (BAdIs)
A, B, C
Explanation:
OData services are the standard way to expose RAP services; service bindings bind a service definition to a protocol such as OData.
Business events are a released RAP capability for integration; RAP BOs can define, raise, and consume business events, with remote consumption via SAP Event Mesh and event bindings.
CDS views define the semantic data models used for exposure and consumption; ADT defines CDS entities for the data model that can be used in applications.
Together, CDS (data modeling) + OData (service exposure) + Events (event-driven integration) constitute the released, recommended integration building blocks in ABAP Cloud/RAP. (BAdIs are classic enhancement spots and not positioned as the primary integration frameworks for ABAP Cloud developer extensibility; SOAP is not the recommended channel in the RAP guidance above.)
You have two database tables – ZDEPARTMENTS and ZEMPLOYEES. They are linked by a foreign key relationship: ZEMPLOYEES is the foreign key table and ZDEPARTMENTS is the check table. A department may have any number of employees (including none at all).
What is the correct cardinality of the foreign key relationship?
- A . [0..,1]
- B . (0..1,1)
- C . (1..1,1)
- D . (1..,1)
A
Explanation:
The situation described is a classic one-to-many relationship from department→employees, with “including none at all” implying 0..* employees per department. In SAP modeling, cardinalities are expressed with ranges like [0..*] to denote zero-to-many. This notation is used consistently in ABAP Cloud/RAP documentation for compositions/associations as well (e.g., tables/structures or nested lists), where [0..*] means “any number (including none)”.
Therefore, the correct foreign-key cardinality that matches “a department may have any number of employees (including none)” is [0..*,1] (many employees per one department). The same documentation set also uses “pure foreign key” associations with multiplicities to model such relationships.
===========
Which of the following is a technique for defining access controls?
- A . Inheritance
- B . Redefinition
- C . Singleton
- D . Casting
A
Explanation:
In ABAP CDS access controls, the technique used is inheritance, which allows one access control object to reuse rules defined in another.
This makes authorization definitions consistent, reusable, and maintainable, which is essential in RAP applications where business objects require layered and reusable authorization concepts.
Options such as Redefinition, Singleton, or Casting belong to OO concepts, not to access control in CDS.
Verified Study Guide
Reference: ABAP Cloud Documentation C Defining Access Controls in CDS and RAP BOs.
Which of the following actions cause an indirect change to a database table requiring a table conversion? (Select 2)
- A . Deleting a field from a structure that is included in the table definition.
- B . Changing the field labels of a data element that is used in the table definition.
- C . Shortening the length of a domain used in a data element that is used in the table definition.
- D . Renaming a field in a structure that is included in the table definition.
A, C
Explanation:
In ABAP Cloud projects, structural changes to persisted artifacts must respect upgrade-safe contracts. Changes that alter the physical layout of a table (removing a column that comes via an included structure, or shortening the length of a column by changing its domain) lead to a database conversion because data type/column layout changes must be reconciled on the DB. While our RAP/CDS guides focus on modeling and service exposure, they emphasize strict, typed modeling and upgrade stability―any structural change that affects persistence is subject to strict checks and lifecycle handling.
By contrast, field labels (texts) do not change the physical table layout and thus don’t require a conversion.
In RESTful Application Programming, a business object contains which parts? Note: There are 2 correct answers to this question.
- A . Process definition
- B . Behavior definition
- C . CDS view
- D . Authentication rules
B, C
Explanation:
In the RAP model, a Business Object (BO) is composed of the following key parts:
A CDS view, which defines the data model layer (entity structure, projections, associations).
A Behavior Definition (BDEF), which defines the behavior layer C what operations can be performed (create, update, delete, validations, determinations).
Therefore:
Option B and C are correct.
Option A is incorrect because "Process definition" is not a RAP construct; process logic is handled via behavior implementation and determinations.
Option D is incorrect because "Authentication rules" are managed externally (e.g., via IAM, authorizations), not inside the BO.
Reference: SAP Help 1, page 6 C RAP Architecture Overview and layers (Data Modeling and Behavior).
You have attached a system field to an input parameter of a CDS view entity as follows:
define view entity Z_ENTITY
with parameters
@Environment.systemField: #SYSTEM_LANGUAGE
language : spras
What are the effects of this annotation? (Select 2 correct answers)
- A . The value of sy-langu will be passed to the CDS view automatically both when you use the CDS view in ABAP and in another CDS view entity (view on view).
- B . You can still override the default value with a value of your own.
- C . The value of sy-langu will be passed to the CDS view automatically when you use the CDS view in ABAP but not when you use it in another view entity.
- D . It is no longer possible to pass your own value to the parameter.
A, B
Explanation:
With @Environment.systemField: #SYSTEM_LANGUAGE, the system field sy-langu is automatically supplied as a default value for the parameter.
This works both in ABAP and in view-on-view scenarios (A).
Developers can still override this value when calling the view explicitly (B).
Options C and D are incorrect: system fields are not limited to ABAP only, and overriding is allowed.
Study Guide
Reference: ABAP CDS Guide C System Fields in View Parameters.
How can you execute test classes? (Select 3)
- A . As a mass test when executing an ABAP Test Cockpit (ATC) check variant.
- B . As a mass test when releasing a transport request with the ABAP Transport Organizer.
- C . Interactively by calling function “Run as a unit test” from within the tested object.
- D . Interactively by calling function “Run as a unit test” from within the test class.
- E . Interactively during the release of transport request.
A, C, D
Explanation:
Interactive runs from the tested object or its test class in ADT: In RAP/ABAP Cloud test guides, you specify a test relation, which then lets you run unit tests directly from the context menu of the behavior definition (tested object) in ADT. This is the “Run as unit test” interaction from the tested object.
Interactive runs from the test class itself: Test classes are declared with FOR TESTING, and the same RAP guides show the canonical test-class structure used for ABAP Unit. In ADT, you can execute the test class via its context menu (“Run as Unit Test”).
Mass execution with ATC: The same document set prescribes governance via ABAP Test Cockpit (ATC) check variants applied across many objects, supporting mass test/check execution. ATC is used broadly to enforce ABAP Cloud rules and quality gates across developments, which covers running checks/tests at scale (mass).
There is no built-in mechanism to execute unit tests during transport release; the recommended mass execution path is via ATC, not via the Transport Organizer. (Hence B and E are not correct.)
===========
Which of the following types of Core Data Services Views can be used at the consumption layer? Note: There are 3 correct answers to this question.
- A . Table Function
- B . Transactional Interface
- C . Transactional Query
- D . Analytical Query
- E . Hierarchy
A, D, E
Explanation:
The consumption layer in ABAP CDS views is used to define views for user-facing applications, analytical scenarios, and UI services.
The valid view types used at this layer include:
Table Function: Used where custom logic or complex data transformations are required. These are implemented with AMDP or class-based logic and exposed via CDS consumption views.
Analytical Query: Designed for analytical use cases with annotations like @Analytics.query: true to allow exposure to Fiori Analytical apps.
Hierarchy: Used for defining and consuming hierarchical data in CDS. These can be displayed in Fiori Tree tables and analytical contexts.
The following options are incorrect:
Transactional Interface and Transactional Query are not standard view types or part of the CDS view hierarchy used in the consumption layer. These terms may have been incorrectly stated and do not reflect supported CDS artifacts.
Reference: SAP Help 3, page 3 C Developing Common Capabilities, and ABAP CDS Development User Guide, section 3.1 C Creating and Activating Data Models
HOTSPOT
In what order are objects created to generate a RESTful Application Programming application?
Explanation:
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.
Reference: SAP Help 1, pages 4C6 ― RAP design time development flow (data modeling, business service provisioning, service consumption).
Which of the following are personas under the SAP S/4HANA Cloud Extensibility Framework? (Select 2 correct answers)
- A . Report Writer
- B . Business Expert
- C . Workflow Administrator
- D . Citizen Developer
B, D
Explanation:
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 C Personas in SAP S/4HANA Cloud.