Questions
ayuda
option
My Daypo

ERASED TEST, YOU MAY BE INTERESTED ONABAP 7.4 - Chapter 08 - SQL Statements, Update Strategies

COMMENTS STATISTICS RECORDS
TAKE THE TEST
Title of test:
ABAP 7.4 - Chapter 08 - SQL Statements, Update Strategies

Description:
ABAP 7.4 - Chapter 08 - SQL Statements, Update Strategies

Author:
ONKIDONKI
(Other tests from this author)

Creation Date:
13/04/2017

Category:
Others

Number of questions: 68
Share the Test:
Facebook
Twitter
Whatsapp
Share the Test:
Facebook
Twitter
Whatsapp
Last comments
AVATAR
Pranaybalava ( uploaded 7 years )
please upload remaining chapters of Abap 7.4 as soon as possible
Answer
Content:
When a transparent table is activated in the ABAP Dictionary, a table of the same name is automatically created within the database. True False.
A difference between using a transparent table and structure type is that a transparent table only contains a list of elementary fields, but the components of a structure type can themselves be structured again, producing nested structures True False.
As of SAP NetWeaver 7.40, new developments in Native SQL are now only possible in ADBC(framework ABAP Database Connectivity), which means that ADBC is now recommended in new programs instead of the static embedding of Native SQL True False.
You can also specify a client in the WHERE clause without the clause CLIENT SPECIFIED True False.
The correct usage of SELECT SINGLE does not require the complet key: True False.
What is correct to say about the SQL Into clause: (There are two correct answers) Only the field types have to match the target. The names of the target structure are not taken into account If you want to use a structure variable as a target that has the same names as the target list, but has a different structure,would use the addition CORRESPONDING FIELDS OF Only the field names have to match the target. The type of the target structure are not taken into account.
What is correct to say about the clause INTO CORRESPONDING FIELDS OF: (There are three correct answers) This fills only the fields with the same type in the target area The corresponding field types must be the same; otherwise, a conversion takes place, and it is possible that incomplete data can be transported to the target field One advantage is that the target structure does not have to be left-justified or in the same order as the field list The disadvantage of this variation is that it requires a program update for every new field added in the structure The disadvantage of this variation is that it requires more work from the system, and it therefore does not perform as quickly.
What is correct to say about SELECT/ENDSELECT statement: The database provides the data to the database interface of the application server in blocks called packages. The data is then copied into the target area row by row for processing The data is copied into an internal table directly instead of row by row.
What is correct to say about the clause INTO TABLE: The database provides the data to the database interface of the application server in blocks called packages. The data is then copied into the target area row by row for processing. The data is copied into an internal table directly instead of row by row. Performance on this is faster than processing row by row because the internal table is filled in blocks, not by rows.
Talking about performance of database access, what is correct to say? (There are three correct answers) If you access the same non-key field search often, you can create a secondary index. A secondary index is an index created in addition to the primary index of a database table Whether an existing secondary index is used in a database, access depends on a function in the database system known as the Database Optimizer. In Open SQL, it is not possible or necessary to explicitly specify the use of a secondary index in the SELECT statement It makes nonsense to include the client field as the first field when you define an index for such tables With data retrieval, a minor proportion of the runtime is needed to transfer the data from the database server to the application server If the data is read frequently and seldom changed, you can reduce the runtime by buffering the data on the application server.Because a limited amount of buffer space is available on the application server, the ideal database table is small, read frequently, rarely changed, and normally accessed directly with its key fields.
What is correct to say about buffering: (There are four correct answers) If you find it is necessary to use a statement that bypasses the buffer, you should try to minimize the number of times the statement is used. If a system is composed of several application servers, a special synchronization mechanism ensures that database changes will validate the corresponding buffer contents The time lags in the synchronization process will, for a short period of time, allow the buffer to be out-of-date or that invalid data could be read from the buffer. You must take this into account when making a decision about buffering If an ABAP program requests data from a buffered table, the database interface first tries to retrieve the data from the SAP table buffer. If it is successful, this speeds up your access between 10 and 100 times in contrast to actually retrieving it from the database If SELECT is used with FOR ALL ENTRIES, then SAP buffering is now also used when accessing tables with single-record buffering and is no longer bypassed All application server use the same SAP table buffer.
Often you are required to read data from multiple database tables. The use of a table join usually provides the best performance. You must specify three things when defining a table join: Join tables, join condition and join columns Join parameters, join access type and join columns Join tables, join access type and join sort criteria.
There are two options for implementing a table join: database view in the ABAP Dictionary or you can implement a join yourself using the SELECT statement in your program DB Procedure or database view SELECT join in your program or a DB Procedure.
A database view is a view of the relevant database tables and does not contain data redundantly: True False.
What is correct to say about Open SQL: (There are five correct answers) Open SQL contains INSERT, DELETE, UPDATE, SELECT and MODIFY statements Commands that process several rows usually provide better performance than the corresponding single set version. The exception is mass data change using UPDATE. All Open SQL commands update the system return code The return value (SY-SUBRC) will be 0 (zero) if the command was successfully executed The system field SY-DBCNT will return the number of rows for which the command was carried out Any return code other than zero indicates that the command was unsuccessful Open SQL commands perform authorization checks automatically.
What is correct to say about ROLLBACK: (There are three correct answers) Database rollback that reverses all changes in the current database LUW There are two ways of causing a database rollback, one is sending a termination dialog message (a message with type A [termination type] or E [error type]) There are two ways of causing a database rollback, one is using the ABAP statement ROLLBACK WORK The message types (E [error type], W [warning type], and I [information type]) involve a dialog but do not trigger a database rollback The ABAP statement ROLLBACK WORK causes a database rollback and terminates the program.
When you use the ABAP statements ROLLBACK WORK and COMMIT WORK: you explicitly implement a database rollback or database commit a database commit is triggered implicitly.
An SAP logical unit of work (LUW): is a group of changes that belong together in the SAP system from a logical point of view. These changes are either carried out together or not made at all. it consists of changes that are executed until the database status is “sealed,” also known as the data being committed to the database.With it it is possible to discard all of the changes that have taken place up to that point through the use of a database rollback.
A database LUW: consists of changes that are executed until the database status is “sealed,” also known as the data being committed to the database. With it, it is possible to discard all of the changes that have taken place up to that point through the use of a database rollback is a group of changes that belong together in the SAP system from a logical point of view. These changes are either carried out together or not made at all.
There are also instances when a database commit is triggered implicitly. Implicit database commits are always initiated whenever the program has to wait (as part of the release of the work process), such as in the following cases: (There are four correct answers) When the system sends an SAP screen to the presentation layer When the system sends a dialog message to the presentation layer Whenever there are synchronous and asynchronous Remote Function Calls (RFCs) When you use the statements CALL TRANSACTION <tcode> or SUBMIT <program> When you use the ABAP statement ROLLBACK WORK When you use the ABAP statement COMMIT WORK.
If you encounter an error during the processing of an SAP LUW, it should be possible to return to a consistent database status that existed before the beginning of the SAP LUW. For this to be possible: the SAP LUW must be placed within a database LUW the SAP LUW must be placed within a checkpoint procedure the SAP LUW must be placed within a SAP Transaction.
With the implicit database commits (image), you cannot place changes that belong to an SAP LUW in different dialog steps (a dialog step is the program processing after a screen). This would place these steps in a separate database LUW, violating the SAP LUW. True False.
Talking about LUW, what is correct to say about three-tier architecture: (There are four correct answers) It means that many users with low-cost personal computers (with low performance) can be mapped to a small number of high-performance and considerably more expensive work processes on application servers Each work process on an application server is assigned a work process on a highperformance database server Distributing user requests to work processes means that individual clients at the presentation server level are assigned to a work process for a particular period After the work process has processed the user input in a dialog step, the user is removed from the work process, thus freeing it for another user The number of database users is considerably higher than the number of active users in the system. This has a positive effect on the behavior of the database. Only when the user has completed processing the screen, requiring the program processing to continue, is the program context commited.
What is correct to say about physicall/database locks: (There are four correct answers) It is important to obtain the lock as soon as possible and release it as quickly as possible so as to not create a bottleneck for other users unnecessarily The Database Management System (DBMS) physically locks the table lines that are read with the intent of being changed (SELECT SINGLE <f> FROM <dbtab> FOR UPDATE). This is a database lock The lock remains until the end of a database LUW, triggered by the database commit, when the DBMS releases all locks that were set during the database LUW Within the SAP system, this means each database lock is released whenever a screen is displayed because the screen change triggers an implicit database commit. Database locks are not sufficient if data is collected throughout several screens and are required to remain locked. It is also possible to use physicall locks for table entries that do not yet exist within the database.
What is correct to say about logical locks: (There are three correct answers) To keep a lock through a series of screens, the SAP system has a global lock table on one application server that is used to set logical locks for table entries The lock table and the enqueue work process that manages the lock table are on a uniquely defined application server of the SAP system. The server containing this enqueue work process is known as the central lock control All of the logical lock requirements of the SAP system, regardless of which application server requested the lock, run on this system-wide, unique work process It is not possible to use logical locks to “lock” table entries that do not yet exist within the database.
What is correct to say about logical lock: (There are four correct answers) You set a logical lock by calling the lock module. This special, table-related function module is created automatically when you activate a table-related lock object When you call the lock module, logical locks are set for the entries in the respective tables You maintain lock objects in the ABAP Dictionary The customer namespace for lock objects is either EY or EZ When you create a lock object, you specify the table whose entries will be locked later. This is known as secondary tables You can specify other tables that have a foreign key relationship to the primary table, which are known as the primary or basis table.
Talking about ENQUEUE and DEQUEUE, what is correct to say: (There is four correct answers) A logical lock is set when you call the enqueue function module, but you can only create a lock if no other lock entry conflicts with it The lock module produces an exception if the lock cannot be obtained Depending on the bundle technique used for database updates, an application program may need to delete the lock entries it created (for an inline update) or have them deleted automatically (during the update task). If a program that created lock entries is terminated, the locks are automatically released (implicitly).A program termination occurs with the production of a message of either type A or X, with the execution of the statements LEAVE PROGRAM and LEAVE TO TRANSACTION, or if the user enters “/n” in the command field The DEQUEUE function module releases the lock entries in the lock table. The DEQUEUE function modules also triggers an exception. If you want to release all locks, you can use the function module DEQUEUE_ALL.
Talking about ENQUEUE and DEQUEUE, what is correct to say: (There are three correct answers) If you call a lock module with a lock parameter set to its initial value or not specified, the system will interpret this as a generic value and locks nothing, giving back an exception If the client is not provided when the ENQUEUE function is called, the lock only applies to the current execution client If the client is specified, the lock only applies to that client. If the client is specified as a space, the lock applies to current client You can override the default lock mode of the lock module specified in the lock object by using the parameter override MODE_<tablename>. The parameter X_<lock_parameter> allows you to lock table records that contain an initial value in the corresponding lock parameter.
Talking about ENQUEUE and DEQUEUE, the parameter _SCOPE defines the validity area of the lock. The values and their meanings are: 1 2 3.
Talking about ENQUEUE and DEQUEUE, what is correct to say about the _WAIT parameter: defines whether a lock request should be repeated if thefirst lock attempt fails store the lock request in a local lock container until the lock container is collected and passed on as a unit to the enqueue server. defines the validity area of the lock.
Talking about ENQUEUE and DEQUEUE, what is correct to say about the _COLLECT parameter: defines whether a lock request should be repeated if thefirst lock attempt fails store the lock request in a local lock container until the lock container is collected and passed on as a unit to the enqueue server. defines the validity area of the lock.
You set the parameter _COLLECT = 'X' whenever you call the lock module. This collects the lock requests in the local lock container for processing together. You send the contents of the lock container with the function module: FLUSH_ENQUEUE RESET_ENQUEUE REFRESH_ENQUEUE.
If you need to delete the contents of the local lock container, you call the function module: RESET_ENQUEUE FLUSH_ENQUEUE REFRESH_ENQUEUE.
Talking about ENQUEUE und DEQUEUE, with the parameter MODE_ you define the lock modes: E X S.
Talking about ENQUEUE und DEQUEUE, what is correct to say about lock modes (E,X,S): (There are four correct answers) The only difference between modes E and X is that E allows accumulation of locks and X does not allow accumulation of locks You implement the mode S if you want to ensure that other users cannot change the data displayed in your program while it is displayed An example for mode S, is a case where you are not attempting to change the data but do not want anyone else changing the data while you are using it. Existing exclusive locks (E or X) always reject every lock attempt of another user, regardless of the mode used by the other user An existing shared lock (S) does not allow other shared locks for protected display.
What is correct to say about Perform on Commit: (There are three correct answers) You can bundle database updates from a dialog program for execution by using the special subroutine technique PERFORM <subroutine> ON COMMIT This registers the specified subroutine for execution, but the subroutine will not be executed until the system reaches the next ENQUEUE statement If you encapsulate the database updates in the subroutines, they can be separated from the program logic and processed at the end of the LUW. A subroutine registered with PERFORM ON COMMIT can be registered multiple times but only executes once per LUW in the order it was first registered. If you nest PERFORM ON COMMIT calls after release 4.6, a runtime error will be triggered The subroutines called with PERFORM ON COMMIT can also have an interface.
What is correct to say about update module: (There are three correct answers) They have only an interface for transferring data through the IMPORTING and TABLES parameters. These must be typed using value fields You create update requests by calling the respective update function module in a dialog program using the IN UPDATE TASK addition The addition IN UPDATE TASK writes the function module and the input data as an exception request and executes the function module immediately The same update key is used to store all of the update flags for an SAP LUW When the system executes a COMMIT WORK statement, it creates a header entry for the request entries, and then the unit is closed.Once the log header is created, the system informs the dispatcher process that an update package is available for processing.
You may need to discard all change requests that were written for the current SAP LUW. To discard the current SAP LUW during the generation phase, which is before the commit work occurs, would you: (There are two correct answers) execute the ABAP statement ROLLBACK WORK produce a type A message produce a type E message produce a type S message.
With a database rollback within the update modul the processing of the current SAP LUW will be terminated, and the log entry belonging to the SAP LUW is flagged as containing an error. The termination message is also entered in the log. If you need to trigger to do that: You use the statement ROLLBACK WORK You issue a type A message You issue a type E message You use the statement DEQUEUE_ALL.
What is correct to say about the update module: (There are two correct answers) A type E message is used to abort the process, log the cause of the error, and abort the update You should use the explicit ABAP statements COMMIT WORK or ROLLBACK WORK in an update module If you set locks in the dialog program with the update technique with _scope = 2, these are passed on to the update task at COMMIT WORK After the commit, the locks are no longer accessible by the dialog program. These locks are automatically released by a Basis program at the end of the update process and do not need to be released explicitly in the update module.
What is correct to say about Asynchronous updates: (There are three correct answers) They make the dialog program and update program to run together The dialog program writes change requests to the log table and with a COMMIT WORK closes the LUW Are useful in transactions where the database updates can take a long time and where the user’s dialog response time is important The update task is started by the COMMIT WORK and processes the change requests The dialog program must wait for the update to continue.
What is correct to say about synchronous update: (There are three correct answers) Is triggered by the statement COMMIT WORK The dialog program and the update function execute in different work processes at the same time You determine the processing success of a synchronous update by examining the system field SY-SUBRC While waiting for the synchronous update to complete, the dialog program is in a rolled-out state, the dialog work process is released for further use When the update completes, the system assigns the dialog program to a free dialog work process to continue processing.
What is correct to say about local updates: (There are four correct answers) Everything runs in a single work process. This is another form of synchronous update To have the update modules executed locally, you must use the statement SET UPDATE TASK LOCAL before you write the requests. When the requests are closed with the COMMIT WORK, these updates are processed in the same dialog work process After the local update is successfully processed, a database commit is initiated implicitly, and the dialog program continues If an error occurs, and one of the update modules produces a termination message, the system executes an automatic database rollback to discard the changes in the current LUW, and the dialog program is terminated with the display of the termination message When you are in the local update mode, changes are not written to the database table VBLOG, but instead are kept in memory. This makes this update quicker than either synchronous or asynchronous updates; however, because this has an exclusive use of a work process, it is only appropriate in batch mode The SET UPDATE TASK LOCAL is only possible if you have created any requests for the current LUW and is only in effect until the next COMMIT WORK.
What is correct to say about SQL expressions: (There are three correct answers) The result of an expression of this type (the operands of which can be the names of columns or host variables) is determined by the database system and passed to the application server in the appropriate column of the results set Can only be used in non Unicode programs, in which the program attribute fixed point arithmetic is activated If SQL expressions are used, then comma-separated lists must be used, the escape character # must be specified in front of host variables, and stricter syntax checks are made on the entire statement. Errors are reported as syntax errors that would otherwise only produce syntax warnings Also, SELECT can be used to access Core Data Services (CDS) views, which have been defined with the DDL of the ABAP CDS by using DEFINE VIEW starting with SAP NetWeaver 7.40 SP05 Automatic client handling is performed for client-specific CDS views. If this handling is deactivated with the addition of CLIENT SPECIFIED, then the client column is part of the results set, even though the column is not an element of the CDS view. New additions for CLIENT SPECIFIED after FROM make it possible to address the column in the SELECT statement.
Update tasks are the only method of making changes to the database: True False.
Which statement is true? A database LUW must be placed within an SAP LUW An SAP LUW must be placed within a database LUW.
Which actions release a database lock? Select all that apply (There are eight correct answers) COMMIT WORK ROLLBACK WORK The display of an SAP screen The display of a dialog message type E The display of a dialog message type A ENQUEUE_<lock_object> An “/n” in the command field A call to a function module A CALL TRANSACTION A SUBMIT.
Which actions release a lock object (with a default value for _SCOPE)? Select all that apply: (There are five correct answers) COMMIT WORK ROLLBACK WORK An “/n” in the command field The display of a dialog message type E The display of a dialog message type A ENQUEUE_<lock_object> DEQUEUE_<lock_object> A call to a function module A CALL TRANSACTION A SUBMIT.
How can you implement a table join other than by using the JOIN statement? A database view A transparent table A structure.
The data buffered on each application server… Is always the same Is never the same Depends on the users.
The target structure of a SELECT statement requires the field names to match the columns selected and to be in the same left-justified order True False.
When is an ENDSELECT not required for a SELECT? Select all that apply. (There are three correct answers) When the FROM is a view When you specify a join of tables When you do a SELECT SINGLE When you specify into a table When you specify appending a table.
The database always uses the primary key when the WHERE clause contains any of the key fields: True False.
Open SQL does not allow you to specify a secondary index during a SELECT: True False.
You should always buffer database tables that contain fewer than 100 records True False.
Buffering data can speed up access to data up to 100 times when compared to reading it from the database True False.
All Open SQL commands allow processing on multiple rows: True False.
The _WAIT parameter of a lock object waits for the lock to be successful: True False.
It is recommended that you place the COMMIT WORK in the update task: True False.
It is possible to PERFORM <subroutine> ON COMMIT in an update task? True False.
What is the correct order for using a lock object? Read the data, set the lock, change the data, release the lock Set the lock, read the data, change the data, release the lock Set the lock, read the data, release the lock, change the data.
Local update tasks are quicker because they stay within the same work process: True False.
V1 update tasks are always non-restartable, whereas V2 update tasks are always restartable: True False.
Lock objects are only required when doing dialog programming; SAP’s best practice does not require them when doing background or en masse changes, as there is no COMMIT WORK that will occur: True False.
An SAP LUW differs from a database LUW in that it allows for multiple screens to be processed: True False.
Beginning with SAP NetWeaver 7.40, if SAP HANA (an in-memory database) is being used as a database, then table buffering is no longer effective and is therefore not possible: True False.
Which of the following types of SQL statements always bypass the SAP table buffers? (There are two correct answers) SELECT SUM (sales) SELECT … UP TO 1 ROW SELECT … INNER JOIN… SELECT SINGLE.
Which comparison operators can you use in a logical expression related to the WHERE clause of the SELECT statement? (There are three correct answers) EQ (equals) CO (contains only) GT (greater than) LIKE (fits pattern) CP (covers pattern).
Report abuse Consent Terms of use