Which of the following are rules that extensions in SAP S/4HANA Cloud, public edition must adhere to? (Select 3 correct answers)
Answer : C, D, E
Tier 1 (cloud-ready) extensions ''follow ABAP Cloud rules and hence by default can only access the public SAP interfaces (objects released for cloud development).'' This directly supports using released APIs (C) and cloud-enabled/released technologies (D).
The three-tier extensibility model separates safe cloud extensions (Tier 1) from classic code; Tier 2 wrappers exist only to mitigate missing public APIs, but they are not the recommended pattern for S/4HANA Cloud public-edition extensions (therefore B is not a rule).
In S/4HANA Cloud, object changes are not allowed; instead, customers must use predefined extension points (E)---for example, whitelisted extension includes, released BAdIs, or CDS extension points exposed for cloud usage---consistent with the ABAP Cloud principle of public, released artifacts only. (This is the prescribed approach in the ABAP Cloud extensibility guidance that accompanies the three-tier model.)
Question 2
You want to document a global class with ABAP Doc. What do you need to consider?
(Select 3 correct answers)
Answer : B, D, E
ABAP Doc is the integrated documentation system for classes, interfaces, and methods. Rules:
Position Must be placed directly after the declarative statement (B).
Translatable ABAP Doc content can be translated (D).
Syntax Each line must start with ! (E).
HTML tags (A) and repository links (C) are not supported.
Verified Study Guide Reference: ABAP Development Tools (ADT) Documentation -- ABAP Doc Annotations and Rules.
Question 3
How can you control data access of a business user?
(Select 3 correct answers)
Answer : B, C, D
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.
Question 4
What are some features of the current ABAP programming language? (Select 2)
Answer : C, D
ABAP for Cloud Development emphasizes expression-oriented, typed programming with strong static checks (e.g., constructor/operators, REDUCE, COND, etc.), which is the modern ABAP style used in RAP.
ABAP integrates built-in database access tightly via CDS and Open SQL; CDS entities are the building blocks and govern data access that the runtime executes via the SQL view.
(A) is false (ABAP is statically typed). (B) is false (ABAP keywords are not case-sensitive).
Question 5
You want to join two database tables, T_CARRIER and T_CONNECTIONS, to retrieve all carriers, whether they have corresponding connections or not.
Which statements would achieve this?
Note: There are 2 correct answers to this question.
Answer : B, D
The requirement is:
Retrieve all carriers from T_CARRIER
Include them even if no corresponding connections exist in T_CONNECTIONS.
Evaluation of each join type:
A . INNER JOIN:
Only returns rows where a carrier has at least one matching connection.
Incorrect, since carriers without connections would be excluded.
B . LEFT OUTER JOIN (correct):
Returns all rows from the left table (T_CARRIER), and connections if they exist.
Missing connections are represented with NULL.
Correct answer.
C . LEFT INNER JOIN:
This is syntactically invalid in ABAP SQL. INNER JOIN and LEFT OUTER JOIN are separate join types, not combined.
Incorrect.
D . RIGHT OUTER JOIN (correct):
Equivalent to LEFT OUTER JOIN when the tables are reversed.
Returns all rows from T_CARRIER, whether or not connections exist.
Correct answer.
Thus, LEFT OUTER JOIN and RIGHT OUTER JOIN are the valid solutions to retrieve all carriers regardless of connections.
Question 6
Which RAP object can be used to organize the display of fields in an app?
Answer : A
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.
Question 7
What can be translated?
(Select 3 correct answers)
Answer : B, D, E
In ABAP Cloud, translation is supported for:
Data element texts (short, medium, long descriptions).
Message class texts (used in MESSAGE statements).
Text symbols (defined in programs).
Not translatable:
String variables runtime values, no translation.
Text literals hard-coded, not translatable via translation tools.
Study Guide Reference: ABAP Documentation -- Text Elements and Translation in ABAP Cloud.
All Official Question Types