What is a class defined as part of an ABAP program called?
Answer : D
In ABAP Cloud/RAP examples, test classes are created inside the development object (e.g., inside the behavior implementation) and are marked FOR TESTING---these are local classes (they live in the program/class include, not as separate global repository classes). The guides show creating test classes under the Test Classes tab and referencing the Local Types section of the implementation (friends etc.), i.e., local to the program/object.
This contrasts with global classes that exist as standalone repository objects; the RAP test patterns explicitly model the former (local) for unit tests within the object's context.
Question 2
Which of the following is a technique for defining access controls?
Answer : A
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 -- Defining Access Controls in CDS and RAP BOs.
Question 3
In CDS views, what do joins and associations have in common?
(Select 2 correct answers)
Answer : A, C
In CDS views:
A . Aliases Allowed for data sources and their fields, both in joins and associations.
C . ON clause Both joins and associations use ON conditions to link data sources.
B . Expose entire data source without fields Incorrect; explicit field selection is required.
D . Field list without data source prefix Incorrect; unless aliased, fields must be qualified.
Thus, the overlap between joins and associations lies in aliasing and ON clause usage.
Verified Study Guide Reference: ABAP CDS Development Guide -- Joins vs Associations.
Question 4
Which of the following custom code use cases falls under Tier 1 extensibility guidelines?
Answer : B
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.
Question 5
In a RAP business object, where is the validation implementation code contained?
Answer : A
In RAP, validations, determinations, and actions are implemented inside the local handler class (lhc_...) of the behavior pool.
Global classes are not used directly for RAP BO logic, only for reusable utilities.
Functions or subroutines are not cloud-compliant for RAP implementation.
Thus, validation code always resides in the local handler class inside the RAP behavior pool.
Study Guide Reference: RAP Development Guide -- Validations in Behavior Implementation.
Question 6
Setting a field to read-only in which object would make the field read-only in all applications of the RAP model?
Answer : B
Behavior Definition (BDEF) is where read-only, mandatory, and transactional rules are enforced across all RAP applications.
Projection view restricts fields per app, not globally.
Metadata extension UI annotations only.
Service definition defines exposure, not behavior.
Therefore, setting field read-only in the behavior definition enforces it globally across all RAP BO usages.
Study Guide Reference: RAP Development Guide -- Behavior Definitions and Field Control.
Question 7
Which models must you use to develop artifacts that expose ABAP-based backend services based on semantic data models? (Select 2)
Answer : A, D
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.
All Official Question Types