SAP SAP Certifications C_ABAPD_2309 Questions & Answers

• Question 41:

  You are given the following information:

  

  1.

  The data source "spfli" on line #2 is an SAP HANA database table

  2.

  "spfli" will be a large table with over one million rows.

  3.

  This program is the only one in the system that accesses the table.

  4.

  This program will run rarely.

  Based on this information, which of the following general settings should you set for the spfli database table? Note: There are 2 correct answers to this question.

  A. "Storage Type" to "Column Store"

  B. "Load Unit to "Column Loadable"

  C. "Storage Type" to "Row Store"

  D. "Load Unit' to 'Page Loadable"

  Correct Answer: CD

  Based on the given information, the spfli database table should have the following general settings: "Storage Type" to "Row Store": This setting determines how the data is stored in the SAP HANA database. Row store is suitable for tables that are accessed by primary key or by a small number of columns. Column store is suitable for tables that are accessed by a large number of columns or by complex analytical queries. Since the spfli table is a large table with over one million rows, and this program is the only one in the system that accesses the table, it is likely that the program will use primary key access or simple queries to access the table. Therefore, row store is a better choice than column store for this table12. "Load Unit" to "Page Loadable": This setting determines how the data is loaded into the memory when the table is accessed. Page loadable means that the data is loaded in pages of 16 KB each, and only the pages that are needed are loaded. Column loadable means that the data is loaded in columns, and only the columns that are needed are loaded. Since the spfli table is a row store table, and this program will run rarely, it is more efficient to use page loadable than column loadable for this table. Page loadable will reduce the memory consumption and the loading time of the table13. References: 1: Table Types in SAP HANA | SAP Help Portal 2: [Row Store vs Column Store in SAP HANA | SAP Blogs] 3: [Load Unit | SAP Help Portal]

• Question 42:

  Which of the following is a generic internal table type?

  A. SORTED TABLE

  B. INDEX TABLE

  C. STANDARD TABLE

  D. HASHED TABLE

  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

• Question 43:

  

  When accessing the subclass instance through go_super, what can you do? Note: There are 2 correct answers to this question.

  A. Access the inherited private components.

  B. Access the inherited public components.

  C. Call a subclass specific public method

  D. Call inherited public redefined methods.

  Correct Answer: AB

  When accessing the subclass instance through go_super, you can do both of the following: Access the inherited private components: A subclass inherits all the private attributes and methods of its superclass, unless they are explicitly overridden by the subclass. Therefore, you can access the inherited private componentsof the superclass through go_super, as long as they are not hidden by other attributes or methods in the subclass12. Access the inherited public components: A subclass inherits all the public attributes and methods of its superclass, unless they are explicitly overridden by the subclass. Therefore, you can access the inherited public components of the superclass through go_super, as long as they are not hidden by other attributes or methods in the subclass12. You cannot do any of the following: Call a subclass specific public method: A subclass does not have any public methods that are not inherited from its superclass. Therefore, you cannot call a subclass specific public method through go_super12. Call inherited public redefined methods: A subclass does not have any public methods that are redefined from its superclass. Therefore, you cannot call inherited public redefined methods through go_super12. References: 1: Object Oriented - ABAP Development Support Wiki 2: Inheritance and Instantiation - ABAP Keyword Documentation

• Question 44:

  Which of the following integration frameworks have been released for ABAP cloud development? Note: There are 3 correct answers to this question.

  A. SOAP consumption

  B. CDS Views

  C. Business Add-ins (BAdls)

  D. Business Events

  E. OData services

  Correct Answer: ADE

  The following are the integration frameworks that have been released for ABAP cloud development: SOAP consumption: This framework allows you to consume SOAP web services from ABAP cloud applications. You can use the ABAP Development Tools in Eclipse to create a service consumption model based on a WSDL file or URL. The service consumption model generates the required ABAP artifacts, such as proxy classes, data types, and constants, to access the web service. You can then use the proxy classes to call the web service operations from your ABAP code1 Business Events: This framework allows you to publish and subscribe to business events from ABAP cloud applications. Business events are messages that represent a change in the state of a business object or process. You can use the ABAP Development Tools in Eclipse to create a business event definition based on a CDS view entity or a projection view. The business event definition specifies the event key, the event payload, and the event metadata. Youcan then use the ABAP Messaging Channel (AMC) framework to publish and subscribe to business events using the AMC API2 OData services: This framework allows you to expose and consume OData services from ABAP cloud applications. OData is a standardized protocol forcreating and consuming RESTful APIs. You can use the ABAP RESTful Application Programming Model (RAP) to create OData services based on CDS view entities or projection views. The RAP framework generates the required OData metadata and runtime artifacts, such as service definitions, service bindings, and service implementations. You can then use the SAP Gateway framework to register and activate your OData services. You can also use the ABAP Development Tools in Eclipse to consume OData services from other sources using the service consumption model3 The other integration frameworks are not released for ABAP cloud development, as they are either not supported or not recommended for cloud scenarios. These frameworks are: CDS Views: CDS views are not an integration framework, but a data modeling framework. CDS views are used to define data models based on database tables or other CDS view entities. CDS views can have associations, aggregations, filters, parameters, and annotations. CDS views can also be used as the basis for other integration frameworks, such as OData services or business events4 Business Add-ins (BAdls): BAdls are not supported for ABAP cloud development, as they are part of the classic ABAP enhancement framework. BAdls are used to implement custom logic in predefined enhancement spots in the standard SAP code. BAdls are not compatible with the cloud strategy and the clean core paradigm, as they modify the SAP code and can cause upgrade and maintenance issues. For ABAP cloud development, SAP recommends using the key user extensibility tools or the side-by-side extensibility approach instead of BAdls. References: Consuming SOAP Services - ABAP Keyword Documentation, Business Events - ABAP Keyword Documentation, OData Services - ABAP Keyword Documentation, CDS Data Model Views - ABAP Keyword Documentation, [Business Add- Ins (BAdIs) - ABAP Keyword Documentation]

• Question 45:

  You want to define the following CDS view entity with an input parameter:

  Define view entity Z_CONVERT With parameters currency : ???

  Which of the following can you use to replace "???" ? Note: There are 2 correct answers to this question.

  A. built-in ABAP type

  B. A built-in ABAP Dictionary type

  C. A data element

  D. A component of an ABAP Dictionary structure

  Correct Answer: AC

  The possible replacements for "???" in the CDS view entity definition with an input parameter are A. built-in ABAP type and C. A data element. These are the valid types that can be used to specify the data type of an input parameter in a CDS

  view entity. A built-in ABAP type is a predefined elementary type in the ABAP language, such as abap.char, abap.numc, abap.dec, etc.A data element is a reusable semantic element in the ABAP Dictionary that defines the technical attributes

  and the meaning of a field12. For example:

  The following code snippet defines a CDS view entity with an input parameter currency of type abap.cuky, which is a built-in ABAP type for currency key:

  Define view entity Z_CONVERT With parameters currency : abap.cuky as select from ... { ... }

  The following code snippet defines a CDS view entity with an input parameter currency of type waers, which is a data element for currency key:

  Define view entity Z_CONVERT With parameters currency : waers as select from ... { ... } You cannot do any of the following:

  B. A built-in ABAP Dictionary type: This is not a valid type for an input parameter in a CDS view entity. A built-in ABAP Dictionary type is a predefined elementary type in the ABAP Dictionary, such as CHAR, NUMC, DEC, etc. However, these types cannot be used directly in a CDS view entity definition. Instead, they have to be prefixed with abap.to form a built-in ABAP type, as explained above12. D. A component of an ABAP Dictionary structure: This is not a valid type for an input parameter in a CDS view entity. A component of an ABAP Dictionary structure is a field that belongs to a structure type, which is a complex type that consists of multiple fields.However, an input parameter in a CDS view entity can only be typed with an elementary type, which is a simple type that has no internal structure12. References:1:ABAP CDS - SELECT, parameter_list - ABAP Keyword Documentation - SAP Online Help2:ABAP Data Types - ABAP Keyword Documentation - SAP Online Help

• Question 46:

  What variable type is connection full based on the following code?

  DATA connection full TYPE /DMD/I_Connection.

  A. Simple variable

  B. Structure

  C. Internal Table

  Correct Answer: B

  Based on the following code, the variable type of connection_full is a structure. A structure is a complex data type that consists of a group of related data objects, called components, that have their own data types and names. A structure can be defined using the TYPES statement or based on an existing structure type, such as a CDS view entity or a CDS DDIC-based view. In this case, the variable connection_full is declared using the TYPE addition, which means that it has the same structure type as the CDS view entity /DMO/I_Connection. The CDS view entity /DMO/I_Connection is a data model view that defines a data model based on the database table /DMO/Connection. The CDS view entity /DMO/ I_Connection has the following components: carrid, connid, airpfrom, airpto, distance, and fltime. Therefore, the variable connection_full has the same components as the CDS view entity /DMO/I_Connection, and each component has the same data type and length as the corresponding field in the database table /DMO/Connection. References: CDS Data Model Views - ABAP Keyword Documentation, DATA - ABAP Keyword Documentation, Structure Types - ABAP Keyword Documentation

• Question 47:

  In a subclass subl you want to redefine a component of a superclass superl. How do you achieve this? Note: There are 2 correct answers to this question.

  A. You add the clause REDEFINITION to the component in subl.

  B. You implement the redefined component for a second time in superl.

  C. You implement the redefined component in subl.

  D. You add the clause REDEFINITION to the component in superl.

  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

• Question 48:

  Exhibit

  

  (Sorry, we do not have a more clear image. If we have a better resource for the image, we will update this one immediately.)

  Which of the following ABAP SQL snippets are syntactically correct ways to provide a value for the parameter on line #4? Note: There are 2 correct answers to this question

  A. ...SELECT * FROM deno_cds_param_view_entity (p_date = @ (cl_abap_context_info- >get_system_date ())...

  B. ...SELECT * FROM deno_cds_param_view_entity (p_date - '20230101')... )

  C. ...SELECT * FROM demo_cds_param_view_entity (p_date: 20238181')... )

  D. ...SELECT * FROM demo_cds_param_view entity (p_date: $session.system_date)...

  Correct Answer: AB

• Question 49:

  What is the purpose of a foreign key relationship between two tables in the ABAP Dictionary?

  A. To document the relationship between the two tables

  B. To ensure the integrity of data in the corresponding database tables

  C. To create a corresponding foreign key relationship in the database

  Correct Answer: B

  The purpose of a foreign key relationship between two tables in the ABAP Dictionary is to ensure the integrity of data in the corresponding database tables. A foreign key relationship defines a logical link between a foreign key table and a check table, where the foreign key fields of the former are assigned to the primary key fields of the latter. This means that the values entered in the foreign key fields must exist in the check table, otherwise the system will reject the entry. This way, the foreign key relationship prevents the insertion of invalid or inconsistent data in the database tables. A foreign key relationship also serves to document the relationship between the two tables in the ABAP Dictionary, but this is not its primary purpose. A foreign key relationship does not necessarily create a corresponding foreign key relationship in thedatabase, as this depends on the database system and the settings of the ABAP Dictionary. Some database systems do not support foreign keys at all, while others require additional steps to activate them. Therefore, the foreign key relationship in the ABAP Dictionary is mainly a logical concept that is enforced by the ABAP runtime environment. References: Foreign Keys (SAP Library - ABAP Dictionary), Foreign Keys (SAP Library - BC - ABAP Dictionary) https://help.sap.com/doc/saphelp_snc70/7.0/enUS/cf/21ea77446011d189700000e8322d00/content.htm

• Question 50:

  When processing an internal table with the statement LOOP AT itab... ENDLOOP, what system variable contains the current row number?

  A. sy-index

  B. sy-subrc

  C. sy-linno

  D. sy-tabix

  Correct Answer: D

  When processing an internal table with the statement LOOP AT itab... ENDLOOP, the system variable that contains the current row number is sy-tabix. The sy-tabix variable is a predefined field of the system structure sy that holds the index or the row number of the current line in an internal table loop. The sy-tabix variable is initialized with the value 1 for the first loop pass and is incremented by 1 for eachsubsequent loop pass. The sy-tabix variable can be used to access or modify the current line of the internal table using the index access12. References: 1: LOOP AT itab - ABAP Keyword Documentation - SAP Online Help 2: System Fields - ABAP Keyword Documentation - SAP Online Help