Comprehensive and Detailed Explanation From Exact Extract:
The EXTRACT_YEAR, EXTRACT_MONTH, and EXTRACT_DAY functions in ABAP SQL are SQL built-in functions used for extracting date components. These functions are only supported for timestamp- capable or date-capable fields.
According to the ABAP CDS Development Guide and SAP HANA SQL capabilities available to ABAP SQL via CDS or native SQL:
* DATS (ABAP Dictionary data type for dates) is fully supported for extract functions.
* TIMESTAMP and UTCLONG are also supported since they represent full date-time values and are mapped internally to TIMESTAMP with time zone considerations.
* TIMS is a time-only type and is not valid for extract date functions.
* TIMN is for time periods and is also not valid for extracting year, month, or day.
Therefore:
* Option B (UTCLONG) – correct
* Option C (TIMESTAMP) – correct
* Option D (DATS) – correct
* Options A (TIMS) and E (TIMN) – incorrect
Reference: ABAP CDS Development User Guide, section 2.2 – SQL expressions and supported built-in functions in code pushdown; extract_* documented for date/time-compatible types.

A projection view is a RESTful Application Programming object that contains only the fields required for a particular app. A projection view is a CDS view entity that defines a projection on an existing CDS view entity or CDS DDIC-based view. A projection view exposes a subset of the elements of the projected entity, which are relevant for a specific business service. A projection view can also define aliases, virtual elements, and annotations for the projected elements. A projection view is the top-most layer of a CDS data model and prepares data for a particular use case. A projection view can have different provider contracts depending on the type of service it supports, such as transactional query, analytical query, or transactional interface.
A database view is a CDS DDIC-based view that defines a join or union of database tables. A database view has an SQL view attached and can be accessed by Open SQL or native SQL. A database view can be used as a projected entity for a projection view, but it does not contain only the fields required for a particular app.
A metadata extension is a RESTful Application Programming object that defines additional annotations for a CDS view entity or a projection view. A metadata extension can be used to enhance the metadata of a CDS data model without changing the original definition. A metadata extension does not contain any fields, but only annotations.
A data model view is a CDS view entity that defines a data model based on database tables or other CDS view entities. A data model view can have associations, aggregations, filters, parameters, and annotations. A data model view can be used as a projected entity for a projection view, but it does not contain only the fields required for a particular app.

The annotation @Environment.systemField: #LANGUAGE is used to assign the ABAP system field sy-langu to an input parameter of a CDS view or a CDS table function. This enables the implicit parameter passing in Open SQL, which means that the value of sy-langu will be automatically passed to the CDS view without explicitly specifying it in the WHERE clause. This also applies to the CDS views that use the annotated CDS view as a data source, which means that the value of sy-langu will be propagated to the nested CDS views (view on view)12. For example:
The following code snippet defines a CDS view ZI_FLIGHT_TEXTS with an input parameter p_langu that is annotated with @Environment.systemField: #LANGUAGE:
define view ZI_FLIGHT_TEXTS with parameters p_langu : syst_langu @<Environment.systemField: #LANGUAGE as select from sflight left outer join scarr on sflight.carrid = scarr.carrid left outer join stext on scarr.carrid = stext.carrid { sflight.carrid, sflight.connid, sflight.fldate, scarr.carrname, stext.text as carrtext } where stext.langu = :p_langu The following code snippet shows how to use the CDS view ZI_FLIGHT_TEXTS in ABAP without specifying the value of p_langu in the WHERE clause. The value of sy-langu will be automatically passed to the CDS view:
SELECT carrid, connid, fldate, carrname, carrtext FROM zi_flight_texts INTO TABLE @DATA(lt_flights).
The following code snippet shows how to use the CDS view ZI_FLIGHT_TEXTS in another CDS view ZI_FLIGHT_REPORT. The value of sy-langu will be automatically passed to the nested CDS view ZI_FLIGHT_TEXTS:
define view ZI_FLIGHT_REPORT with parameters p_langu : syst_langu @<Environment.systemField: #LANGUAGE as select from zi_flight_texts(p_langu) { carrid, connid, fldate, carrname, carrtext, count(*) as flight_count } group by carrid, connid, fldate, carrname, carrtext The annotation @Environment.systemField: #LANGUAGE does not prevent the possibility of overriding the default value with a value of your own. You can still specify a different value for the input parameter p_langu in the WHERE clause, either in ABAP or in another CDS view. This will override the value of sy-langu and pass the specified value to the CDS view12. For example:
The following code snippet shows how to use the CDS view ZI_FLIGHT_TEXTS in ABAP with a specified value of p_langu in the WHERE clause. The value ‘E’ will be passed to the CDS view instead of the value of sy-langu:
SELECT carrid, connid, fldate, carrname, carrtext FROM zi_flight_texts WHERE p_langu = ‘E’ INTO TABLE @DATA(lt_flights).
The following code snippet shows how to use the CDS view ZI_FLIGHT_TEXTS in another CDS view ZI_FLIGHT_REPORT with a specified value of p_langu in the WHERE clause. The value ‘E’ will be passed to the nested CDS view ZI_FLIGHT_TEXTS instead of the value of sy-langu:
define view ZI_FLIGHT_REPORT with parameters p_langu : syst_langu @<Environment.systemField: #LANGUAGE as select from zi_flight_texts(p_langu) { carrid, connid, fldate, carrname, carrtext, count(*) as flight_count } where p_langu = ‘E’ group by carrid, connid, fldate, carrname, carrtext

The predicate condition that can be used to ensure that the CAST will work is IS INSTANCE OF. The IS INSTANCE OF predicate condition checks whether the operand is an instance of the specified class or interface. This is useful when you want to perform a downcast, which is a conversion from a more general type to a more specific type. A downcast can fail if the operand is not an instance of the target type, and this can cause a runtime error. Therefore, you can use the IS INSTANCE OF predicate condition to check whether the downcast is possible before using the CAST operator12. For example:
The following code snippet uses the IS INSTANCE OF predicate condition to check whether the variable g_super is an instance of the class lcl_super. If it is, the CAST will work and the variable g_sub1 will be assigned the value of g_super.
DATA: g_super TYPE REF TO lcl_super, g_sub1 TYPE REF TO lcl_sub1. IF g_super IS INSTANCE OF lcl_super. g_sub1 = CAST #( g_super ). g_sub1->method( … ). ENDIF.
You cannot do any of the following:
IS SUPPLIED: The IS SUPPLIED predicate condition checks whether an optional parameter of a method or a function module has been supplied by the caller. This is useful when you want to handle different cases depending on whether the parameter has a value or not. However, this predicate condition has nothing to do with the CAST operator or the type of the operand12.
IS NOT INITIAL: The IS NOT INITIAL predicate condition checks whether the operand has a non-initial value. This is useful when you want to check whether the operand has been assigned a value or not. However, this predicate condition does not guarantee that the CAST will work, because the operand may have a value but not be an instance of the target type12.
IS BOUND: The IS BOUND predicate condition checks whether the operand is a bound reference variable. This is useful when you want to check whether the operand points to an existing object or not. However, this predicate condition does not guarantee that the CAST will work, because the operand may point to an object but not be an instance of the target type12.

Comprehensive and Detailed Explanation From Exact Extract:
* Use ABAP Development Tools (ADT) in Eclipse: For ABAP Cloud development, ADT must be used
, and modern object types such as CDS View Entities and Behavior Definitions can only be edited in ADT. This confirms option B.
* Use SAP-released/predefined extension points: RAP extensibility is opt-in; every possible extension point must be defined explicitly in the original BO artifacts. Extensions are performed only at these predefined points to ensure lifecycle stability-this is exactly the “use SAP-released extension points” rule. This confirms option A.
* In contrast, directly modifying SAP objects is not part of the clean-core, upgrade-stable model for public cloud; extensions must adhere to released APIs and predefined points (therefore C is not correct).
The classic Web Dynpro UI technology is not the target for ABAP Cloud development in S/4HANA Cloud public edition (therefore D is not correct). (Context anchored by the extensibility/clean-core guidance above.) Study-Guide anchors: ABAP Cloud development with ADT only; RAP opt-in extensibility and predefined extension points for cloud-ready, upgrade-safe extensions.

Comprehensive and Detailed Explanation From Exact Extract:
* 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.)

Comprehensive and Detailed Explanation from Exact Extract:
* from_mixed converts a mixed-case string into uppercase with a chosen separator between words.
* Given input ‘LorelpsumFactum’, the function splits at uppercase letters, uppercases the parts, and joins them with _.
* Output: LORE_IPSUM_FACTUM.
* condense only removes extra spaces, to_upper only changes case, and to_mixed does the reverse of from_mixed.
Study Guide Reference: ABAP Keyword Documentation – String Functions (from_mixed, to_mixed).

Comprehensive and Detailed Explanation from Exact Extract:
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.

In ABAP SQL, the syntax to retrieve the association field of a CDS view is to use the @ sign followed by the association name and the field name, separated by a period sign (.). For example, to retrieve the association field _Airline-Name of a CDS view, the syntax is @_Airline.Name. This syntax allows the access to the fields of the target data source of the association without explicitly joining the data sources1. The other options are incorrect because they use the wrong symbols or formats to access the association field.

String functions are expressions that can be used to manipulate character-like data in ABAP. String functions can be either predicate functions or non-predicate functions. Predicate functions are string functions that return a truth value (true or false) for a condition of the argument text. Non-predicate functions are string functions that return a character-like result for an operation on the argument text1.
The following string functions are predicate functions:
B . contains_any_of(): This function returns true if the argument text contains at least one of the characters specified in the character set. For example, the following expression returns true, because the text ‘ABAP’ contains at least one of the characters ‘A’, ‘B’, or ‘C’:
contains_any_of( val = ‘ABAP’ set = ‘ABC’ ).
D . matches(): This function returns true if the argument text matches the pattern specified in the regular expression. For example, the following expression returns true, because the text ‘ABAP’ matches the pattern that consists of four uppercase letters:
matches( val = ‘ABAP’ regex = ‘[A-Z]{4}’ ).
The following string functions are not predicate functions, because they return a character-like result, not a truth value:
A . find_any_not_of(): This function returns the position of the first character in the argument text that is not contained in the character set. If no such character is found, the function returns 0. For example, the following expression returns 3, because the third character of the text ‘ABAP’ is not contained in the character set ‘ABC’:
find_any_not_of( val = ‘ABAP’ set = ‘ABC’ ).
C . count_any_of(): This function returns the number of characters in the argument text that are contained in the character set. For example, the following expression returns 2, because there are two characters in the text ‘ABAP’ that are contained in the character set ‘ABC’:
count_any_of( val = ‘ABAP’ set = ‘ABC’ ).

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.

Comprehensive and Detailed Explanation from Exact Extract:
* A. Automatic execution # # A constructor (CONSTRUCTOR) is automatically invoked when an instance of a class is created.
* B. Importing parameters # # Constructors can have importing parameters to initialize the object with values.
* C. First method called by client # # Not correct, because constructors are called by the system, not the client explicitly.
* D. Returning parameters # # Constructors cannot return values; they only set up the object.
This behavior is consistent across ABAP Cloud OOP classes, ensuring encapsulated initialization logic.
Verified Study Guide Reference: ABAP Objects Guide – Class Constructors and Instance Constructors.