Correct Answer: ADE

An Access Control Object (ACO) is a CDS annotation that defines the access control rules for a CDS view entity. An ACO consists of one or more clauses that specify the role name, the data source, the access conditions, and the return code of the authority check12. Some of the clauses that are used in an ACO are: Where (to specify the access conditions): This clause is used to define the logical expression that determines whether a user has access to the data source or not. The expression can use the fields of the data source, the parameters of the CDS view entity, or the predefined variables $user and $session. The expression can also use the functions check_authorization and check_role to perform additional authority checks12. Define role (to specify the role name): This clause is used to assign a name to the role that is defined by the ACO. The role name must be unique within the namespace of the CDS view entity and must not contain any special characters. The role name can be used to reference the ACO in other annotations, such as @AccessControl.authorizationCheck or @AccessControl.grant12. Revoke (to remove access to the data source): This clause is used to explicitly deny access to the data source for a user who meets the conditions of the where clause. The revoke clause overrides any grant clause that might grant access to the same user. The revoke clause can be used to implement the principle of least privilege or to enforce data segregation12. You cannot do any of the following: Grant (to identify the data source): This is not a valid clause in an ACO. The grant clause is a separate annotation that is used to grant access to a CDS view entity or a data source for a user who has a specific role. The grantclause can reference an ACO by its role name to apply the access conditions defined by the ACO12. Return code (to assign the return code of the authority check): This is not a valid clause in an ACO. The return code of the authority check is a predefined variable that is set by the system after performing the access control check. The return code can be used in the where clause of the ACO to specify different access conditions based on the outcome of the check12. References: 1: Access Control Objects - ABAP Keyword Documentation - SAP Online Help 2: Access Control in Core Data Services (CDS) | SAP Help Portal

Correct Answer: BD

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

References: 1: String Functions - ABAP Keyword Documentation

Correct Answer: B

A generic internal table type is a table type that does not define all the attributes of an internal table in the ABAP Dictionary; it leaves some of these attributes undefined. A table type is generic in the following cases1:

You have selected Index Table or Not Specified as the access type. You have not specified a table key or specified an incomplete table key.

You have specified a generic secondary table key.

A generic table type can be used only for typing formal parameters or field symbols. A generic table type cannot be used for defining data objects or constants2. Therefore, the correct answer is B. INDEX TABLE, which is a generic table type

that does not specify the access type or the table key. The other options are not generic table types, because:

A. SORTED TABLE is a table type that specifies the access type as sorted and the table key as a unique or non-unique primary key3.

C. STANDARD TABLE is a table type that specifies the access type as standard and the table key as a non-unique standard key that consists of all the fields of the table row in the order in which they are defined4. D. HASHED TABLE is a table type that specifies the access type as hashed and the table key as a unique primary key5. References: 1: Generic Table Types - ABAP Dictionary - SAP Online Help 2: Generic ABAP Types - ABAP Keyword Documentation - SAP Online Help 3: Sorted Tables - ABAP Keyword Documentation - SAP Online Help 4: Standard Tables

- ABAP Keyword Documentation - SAP Online Help 5: Hashed Tables - ABAP Keyword Documentation - SAP Online Help

Correct Answer: AC

To redefine a component of a superclass in a subclass, you need to do the following12:

You add the clause REDEFINITION to the component declaration in the subclass. This indicates that the component is inherited from the superclass and needs to be reimplemented in the subclass. The redefinition must happen in the same

visibility section as the component declaration in the superclass. For example, if the superclass has a public method m1, the subclass must also declare the redefined method m1 as public with the REDEFINITION clause.

You implement the redefined component in the subclass. This means that you provide the new logic or behavior for the component that is specific to the subclass. The redefined component in the subclass will override the original component

in the superclass when the subclass object is used. For example, if the superclass has a method m1 that returns `Hello', the subclass can redefine the method m1 to return `Hi' instead.

You cannot do any of the following:

You implement the redefined component for a second time in the superclass. This is not possible, because the superclass already has an implementation for the component that is inherited by the subclass. The subclass is responsible for

providing the new implementation for the redefined component, not the superclass. You add the clause REDEFINITION to the component in the superclass. This is not necessary, because the superclass does not need to indicate that the

component can be redefined by the subclass. The subclass is the one that needs to indicate that the component is redefined by adding the REDEFINITION clause to the component declaration in the subclass.

References:1:METHODS - REDEFINITION - ABAP Keyword Documentation - SAP Online Help2:Redefining Methods - ABAP Keyword Documentation - SAP Online Help

Correct Answer: ACE

In a RESTful Application Programming (RAP) application, you can bind a CDS view to create a value help in the following objects:

Data model view: A data model view is a CDS view that defines the data structure and the associations of an entity in the RAP application. You can use the annotation @Consumption.valueHelpDefinition to bind a value help provider CDS

view to an element of the data model view. The value help provider CDS view must contain the key fields of the value help entity and the fields that are displayed in the value help dialog. The value help annotation specifies the entity name,

the element name, and optionally the additional binding conditions for the value help provider1.

Metadata Extension: A metadata extension is a CDS view that extends the metadata of another CDS view without changing its data structure. You can use the annotation @MetadataExtension.extendView to specify the target CDS view that

you want to extend. You can then use the same annotation @Consumption.valueHelpDefinition to bind a value help provider CDS view to an element of the target CDS view. The metadata extension allows you to add value help definitions to

existing CDS views without modifying them2. Projection View: A projection view is a CDS view that defines the projection of another CDS view. You can use the annotation @AbapCatalog.sqlViewType:

#PROJECTION to specify that the CDS view is a projection view. You can then use the same annotation @Consumption.valueHelpDefinition to bind a value help provider CDS view to an element of the projection view. The projection view

allows you to add value help definitions to projected elements of another CDS view3. You cannot bind a value help provider CDS view to a behavior definition or a service definition, because these objects do not define the data structure or the

metadata of an entity in the RAP application. A behavior definition defines the behavior and thevalidation rules of an entity, such as the create, read, update, and delete (CRUD) operations, the draft handling, the authorization checks, and the

side effects4. A service definition defines the service exposure and the service binding of an entity, such as the protocol, the version, the namespace, and the service name5.

References: 1: Value Help with Additional Binding | SAP Help Portal 2: Metadata Extensions - ABAP Keyword Documentation 3: Projection Views - ABAP Keyword Documentation 4: Behavior Definition - ABAP Keyword Documentation 5:

Service Definition

-ABAP Keyword Documentation