Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. SAP
  5. C_ABAPD_2309

SAP C_ABAPD_2309 Exam Questions
SAP Certified Associate - Back-End Developer - ABAP Cloud (Page 6 )

Updated On: 21-Feb-2026
Page 3 of 17
PDF with 81 Questions

Which restrictions exist for ABAP SQL arithmetic expressions?
Note: There are 2 correct answers to this question.

  1. Floating point types and integer types can NOT be used in the same expression.
  2. The operator/is allowed only in floating point expressions.
  3. Decimal types and integer types can NOT be used in the same expression.
  4. The operator is allowed only in floating point expressions.

Answer(s): B,D

Explanation:

ABAP SQL arithmetic expressions have different restrictions depending on the data type of the operands. The following are some of the restrictions:
Floating point types and integer types can be used in the same expression, as long as the integer types are cast to floating point types using the cast function. For example, CAST ( num1 AS FLTP ) / CAST ( num2 AS FLTP ) is a valid expression, where num1 and num2 are integer types. The operator / is allowed only in floating point expressions, where both operands have the type FLTP or f. For example, num1 / num2 is a valid expression, where num1 and num2 are floating point types. If the operator / is used in an integer expression or a decimal expression, a syntax error occurs. Decimal types and integer types can be used in the same expression, as long as the expression is a decimal expression. A decimal expression has at least one operand with the type DEC, CURR, or QUAN or p with decimal places. For example, num1 + num2 is a valid expression, where num1 is a decimal type and num2 is an integer type.
The operator ** is allowed only in floating point expressions, where both operands have the type FLTP or f. For example, num1 ** num2 is a valid expression, where num1 and num2 are floating point types. If the operator ** is used in an integer expression or a decimal expression, a syntax error occurs.


Reference:

sql_exp - sql_arith - ABAP Keyword Documentation, SQL Expressions, Arithmetic Calculations - ABAP Keyword Documentation



What are valid statements?
Note: There are 2 correct answers to this question.

  1. ##NEEDED is checked by the syntax checker.
  2. The pragma is not checked by the syntax checker.
  3. #EC_NEEDED is not checked by the syntax checker.
  4. The pseudo-comment is checked by the syntax checker

Answer(s): A,B

Explanation:

Both statements are valid in ABAP, but they have different effects on the program. ##NEEDED is a pragma that can be used to hide warnings from the ABAP compiler syntax check. It tells the check tools that a variable or a parameter is needed for further processing, even if it is not used in the current statement. For example, if you declare a variable without assigning any value to it, you can use ##NEEDED to suppress the warning about unused variables. The pragma is not checked by the syntax checker means that you can use any pragma to hide any warning from the ABAP compiler syntax check, regardless of its effect on the program logic or performance. For example, if you use ##SHADOW to hide a warning about an obscured function, you can also use it to hide a warning about an invalid character in a string.
You cannot do any of the following:
#EC_NEEDED is not checked by the syntax checker: This is not a valid statement in ABAP. There is no pseudo-comment with #EC_NEEDED in ABAP3.
The pseudo-comment is checked by the syntax checker: This is false. Pseudo-comments are obsolete and should no longer be used in ABAP. They were replaced by pragmas since SAP NW 7.0 EhP2 (Enhancement Package)4.


Reference:

1: Pragmas - ABAP Keyword Documentation - SAP Online Help 2: [What are pragmas and pseudo comments in ABAP? | SAP Blogs - SAP Community] 3: ABAP Keyword Documentation - SAP Online Help 4: What are PRAGMAS and Pseudo comments in SAP ABAP



Which internal table type allows unique and non-unique keys?

  1. Sorted
  2. Hashed
  3. Standard

Answer(s): C

Explanation:

The internal table type that allows both unique and non-unique keys is the standard table. A standard table has an internal linear index that can be used to access the table entries. The key of a standard table is always non-unique, which means that the table can contain duplicate entries. However, the system does not check the uniqueness of the key when inserting new entries, so the programmer can ensure that the key is unique by using appropriate logic. A standard table can be accessed either by using the table index or the key, but the response time for key access is proportional to the table size.
The other two internal table types, sorted and hashed, do not allow non-unique keys. A sorted table is filled in sorted order according to the defined table key, which must be unique. A sorted table can be accessed either by using the table index or the key, but the response time for key access is logarithmically proportional to the table size. A hashed table can only be accessed by using a unique key, which must be specified when declaring the table. A hashed table has no index, and the response time for key access is constant, regardless of the table size.


Reference:

Internal Tables - ABAP Keyword Documentation, SAP ABAP: Types Of Internal Table Declaration - dan852.com



In this nested join below in which way is the join evaluated?

  1. From the left to the right in the order of the tables:
    1.
    a is joined with b
    2.
    b is joined with c
  2. From the right to the left in the order of the tables:
    1.
    b is joined with c.
    2.
    b is joined with a.
  3. From the top to the bottom in the order of the on conditions 1.
    b is joined with c
    2.
    a is joined with b
  4. From the bottom to the top in the order of the on conditions:
    1.
    a is joined with b
    2.
    b is joined with c

Answer(s): C

Explanation:

The nested join is evaluated from the top to the bottom in the order of the ON conditions. This means that the join expression is formed by assigning each ON condition to the directly preceding JOIN from left to right. The join expression can be parenthesized implicitly or explicitly to show the order of evaluation. In this case, the implicit parentheses are as follows:

SELECT * FROM (a INNER JOIN (b INNER JOIN c ON b~c = c~c) ON a~b = b~b) This means that the first join expression is b INNER JOIN c ON b~c = c~c, which joins the columns of tables b and c based on the condition that b~c equals c~c. The second join expression is a INNER JOIN (b INNER JOIN c ON b~c = c~c) ON a~b = b~b, which joins the columns of table a and the result of the first join expression based on the condition that a~b equals b~b. The final result set contains all combinations of rows from tables a, b, and c that satisfy both join conditions.


Reference:

1: SELECT, FROM JOIN - ABAP Keyword Documentation - SAP Online Help



Which extensibility type does SAP recommend you use to enhance the existing UI for an SAP Fiori app?

  1. Key user
  2. Classic
  3. Side-by-side
  4. Developer

Answer(s): D

Explanation:

According to the SAP clean core extensibility and ABAP cloud topic, SAP recommends using developer extensibility to enhance the existing UI for an SAP Fiori app. Developer extensibility allows you to use the UI adaptation editor in SAP Web IDE to modify the UI layout, add or remove fields, and bind them to the data model. You can also use the SAPUI5 framework to create custom controls, views, and controllers. Developer extensibility is based on the in-app extensibility concept, which means that the extensions are part of the same application and are deployed together with the app. Developer extensibility requires developer skills and access to the source code of the app.


Reference:

SAP Learning Hub, SAP S/4HANA Cloud Extensibility - In-App Extensibility, SAP Fiori: Extensibility






Post your Comments and Discuss SAP C_ABAPD_2309 exam dumps with other Community members:

Join the C_ABAPD_2309 Discussion