C_ABAPD_2507 Practice Questions

Comprehensive and Detailed Explanation from Exact Extract:

With @Environment.systemField: #SYSTEM_LANGUAGE, the system field sy-langu is automatically supplied as a default value for the parameter.

This works both in ABAP and in view-on-view scenarios (A).

Developers can still override this value when calling the view explicitly (B).

Options C and D are incorrect: system fields are not limited to ABAP only, and overriding is allowed.

Study Guide Reference: ABAP CDS Guide – System Fields in View Parameters.

Comprehensive and Detailed Explanation from Exact Extract:

In ABAP Cloud, string functions that support regular expressions (PCRE) include:

match( ) → returns the first substring matching the regex.

matches( ) → checks if the whole string matches the regex.

find( ) → finds a substring based on regex pattern.

Functions such as reverse( ) and condense( ) do not support regex patterns; they are purely string manipulation utilities.

Verified Study Guide Reference: ABAP Keyword Documentation – String Functions with Regular Expressions.

Comprehensive and Detailed Explanation From Exact Extract:

In the RAP model, a Business Object (BO) is composed of the following key parts:

A CDS view, which defines the data model layer (entity structure, projections, associations).

A Behavior Definition (BDEF), which defines the behavior layer – what operations can be performed (create, update, delete, validations, determinations).

Therefore:

Option B and C are correct.

Option A is incorrect because "Process definition" is not a RAP construct; process logic is handled via behavior implementation and determinations.

Option D is incorrect because "Authentication rules" are managed externally (e.g., via IAM, authorizations), not inside the BO.

Comprehensive and Detailed Explanation From Exact Extract:

Parameters in CDS view entities (WITH PARAMETERS) must always be supplied when querying. In ABAP SQL, the syntax rules are:

A.  

CorrectSupplying a literal date ('20230101') directly is valid because the parameter p_date is of type abap.dats.

B.  

CorrectSupplying a value via an ABAP expression using @( ... ) is syntactically correct. Here, cl_abap_context_info=>get_system_date( ) returns the current system date in ABAP Cloud-compliant way, and is wrapped with @() for expression embedding. This is the best practice in ABAP Cloud development.

C.  

IncorrectBackticks (`...`) are used in ABAP for string templates, not for literals in this context. A date literal must be in quotes '...'.

D.  

Incorrect:$session.system_date is not valid in ABAP SQL. Session variables like $session.* are supported in HANA SQL, but in ABAP CDS view consumption via ABAP SQL, this is not allowed.

Therefore, only A and B are correct.

Comprehensive and Detailed Explanation from Exact Extract:

dats_add_days → ✅ Returns the number of days added/subtracted to a given date → INT4.

dats_days_between → ✅ Returns the number of days between two dates → INT4.

dats_add_months → ❌ Returns a DATE, not INT4.

dats_is_valid → ❌ Returns a BOOLEAN (flag), not INT4.

In CDS, these date functions are used for calculations in queries, supporting business logic pushdown.

Verified Study Guide Reference: ABAP CDS Functions Reference – Date and Time Functions.

Comprehensive and Detailed Explanation from Exact Extract:

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.

Comprehensive and Detailed Explanation From Exact Extract:

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).

class_setup( )

setup( )

teardown( )

class_teardown( )

ABAP Unit Test framework defines a fixed sequence for test fixture methods to ensure reliable test execution and cleanup:

class_setup( ):Called once before any tests in the test class are run. Used to prepare global test data or setup that applies to all tests.

setup( ):Called before each individual test method to prepare local test data or preconditions.

teardown( ):Called after each individual test method to clean up what was done in setup( ).

class_teardown( ):Called once after all tests have been executed to clean up class-level resources.

This sequence supports isolation and repeatability of test executions, ensuring that one test's result does not influence another’s.