Value helps in CDS are defined using annotations like:
@Consumption.valueHelpDefinition: '_association'
This enriches fields with semantic metadata for Fiori/UIs. Associations provide technical links, but the value help definition itself is given by annotations.
Study Guide Reference: ABAP CDS Guide -- Annotations for Value Helps.
Question 2
What are some principles of encapsulation?
(Select 2 correct answers)
Answer : A, D
Encapsulation in ABAP OO and ABAP Cloud ensures that internal object details are hidden from outside consumers.
A . Attributes can be changed through public methods Correct, because controlled access is provided through getter/setter or other methods.
B . Attributes can be changed by the client program directly Incorrect, this violates encapsulation.
C . Attributes cannot be changed Incorrect, they can be changed, but only via allowed mechanisms.
D . Attributes can only be changed by the class itself Correct, ensuring business logic consistency.
This aligns with RAP behavior definitions (BDEF) where internal attributes are encapsulated and only manipulated through behavior implementation methods.
Which of the following integration frameworks have been released for ABAP Cloud development? (Select 3)
Answer : A, B, C
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.)
===========
Question 4
What are some necessary parts of the singleton pattern? (Select 3)
Answer : A, D, E
Modern ABAP encourages well-structured OO patterns under ABAP for Cloud Development, with static checks and typed APIs. A singleton is realized by:
Holding a static reference attribute to the single instance.
Providing a public static factory (get_instance) that returns the single instance.
This aligns with the ABAP Cloud guidance on architecture-driven, upgrade-stable design (strict language, typed APIs, static checks).
(C) is wrong: the factory method must be public so callers can get the instance.
Question 5
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 6
In a booking record, how can you calculate the difference in days between the order date (type D) and the flight date (type D) of a flight?
Answer : B
In ABAP, when calculating the difference between two date fields (type DATS), the result is directly a type i (integer) representing the difference in days.
This directly subtracts two DATS fields, resulting in an integer value for the number of days difference. No conversion is necessary.
Statements A and D are incorrect because the conv d( ... ) attempts to convert the result back to a DATS type, which is invalid since the result is an integer (number of days), not a date.
Statement C is syntactically correct but would produce the negative of the desired value (flight date - order date). It is semantically incorrect for the use case.
This approach is consistent with ABAP for Cloud Development, which requires explicit typing, and ABAP language version strict mode, where automatic type inference is restricted.
Question 7
Which of the following ABAP SQL aggregate functions accept an ABAP SQL expression (e.g., f1 + f2) as input?
All Official Question Types