The questions were taken from SAP course UADM315 (course version 2018 / Q2).
Wait time
Roll-in time
Enqueue time
Rendering time
Design time
Rate this question:
Yes, because database request time is measured at SAP instance level
No, because database request time is measured by the database
Rate this question:
Optimization of SAP system parameters
Optimization of SAP end-user trainings
Optimization of database and operating system configuration
Optimization of workload distribution
Optimization of SAP disaster recovery procedures
Synchronous RFC (sRFC)
Asynchronous RFC (aRFC)
Transactional RFC (tRFC)
Queued RFC (qRFC)
Rate this question:
Work processes that are started in certain situation and are stopped again when no longer needed
Dialog work processes that can only be used for a specific task
Work processes used to communicate with printer
Work processes used to perform non-urgent changes to a database
Rate this question:
Heap memory
Extended memory
Paging memory
PRIV memory
Rate this question:
As the timespan between the dispatcher receives a request till he sends out the final response to the front end
As the timespan between the browser sends a request to the backend till he completely rendered the response
As the timespan between the roll-in and the roll-out of a work process is once completed
As the timespan between an ABAP requested is being loaded into the program buffer till the request processing is finished
Rate this question:
LAN check by ping in transaction Operating System Monitor (ST06(n))
Connection test in Work Process Overview (SM5O/SM66)
Trace, in transaction Single Transaction Analysis (ST12). Trace, in transaction Single Transaction Analysis (ST12)
Check Cursor Cache in transaction DBA Cockpit (DBACOCKPIT)
Rate this question:
An SAP proprietary standalone program for collecting Operating System usage information
An alternative to transaction Operating System Monitor (ST06(n)) for non-ABAP systems
The built-in tool in ABAP systems for collecting Operating System usage information
A third party tool for collecting Operating System usage information
Rate this question:
Average DB request time of more than 40% of average response time
Average DB request time is higher than average CPU time
Average DB request time of more than twice the average CPU time
Average DB request time of more than 100ms
Rate this question:
By using scheduled periodic refreshes
By using update jobs that are scheduled when an issue occurs
By manual updates to avoid inconsistencies
By triggering the AS ABAP update work process
Rate this question:
RFC client profile
RFC server profile
RFC client-destination profile
RFC server-destination profile
Rate this question:
Local Work Process Overview (SM50)
Operating System Monitor (ST06)
Global Work Process Overview (SM66)
Workload Monitor (ST03n)
Rate this question:
By creating an index using selective fields from the where clause
By updating the statistics, so the optimizer will create an appropriate index
By creating an index using all fields from the where clause
By educating end users to use the program that calls this SQL statement correctly
Rate this question:
In a Unix system, more than 20% of RAM paged out/ swapped out per hour
In a Windows system, more than 25% of RAM paged in per hour
In a Unix system, more than 20% of RAM paged in / swapped in per hour
In a Windows system, more than 20% of RAM paged out per hour
Rate this question:
Rdisp/rfc_use_quotas
Rdisp/rfc_max_login
Rdisp/queue/wait
Rdisp/max_sessions
Rate this question:
In the cursor cache of the DBA cockpit
In the transaction Operating System Monitor (ST06(n))
In transaction SQL trace (ST05 or ST12)
In transaction Work Process Overview (SM50 and SM66)
Rate this question:
High CPU utilization near 100%
High swap/paging activity
High database time
High wait time
Rate this question:
If there is one instance on one host, only one SAPOSCOL process is required
If there are multiple instances on one host, multiple SAPOSCOL processes are required
If there are multiple instances on one host, only one SAPOSCOL process is required
If there are multiple virtual hosts, only one SAPOSCOL process is required
Rate this question:
An SQL statement that causes the database to read many blocks (from disk or database buffer)
An SQL statement that does not use the best possible access path
An SQL statement that causes the database to read more blocks (from disk or buffer) than required
An SQL statement that cannot be tuned by implementing database related changes
Rate this question:
If it is a database process, you use the database monitor (ST04) and check if this activity can be tuned or moved to another time
If this process leaves 10% or less overall CPU idle time, there is no need for further action because there is still headroom
If it is an SAP work process, you compare the process ID (PID) to the list of transactions in SMSO to find out what activity is causing the load
If it is the SAP gateway process, you might check if update processing can be moved to another instance
Rate this question:
Roll wait time
Roll out time
Processing time
Time to establish the RFC connection
Database request time
Rate this question:
User context data
Buffered programs and tables
Objects associated with individual users and their open transactions
Application program data that corresponds to specific ABAP commands, such as "export to memory"
Rate this question:
If the table is larger than 1MB
If the table experiences many invalidations
If the table is already buffered in the database buffer
If the table is frequently accessed
Rate this question:
How often is the statement executed
Which user is executing the statement
What the contribution is to the system's overall response
Which work process type is executing the statement
Rate this question:
Shared memory is only accessible on operating system level
Shared memory is accessible by all processes across all instances
Shared memory is accessible only by dialog work processes of one instance
Shared memory is accessible by all processes of one instance
Rate this question:
Work process utilization data of all instances of an SAP system
Automatically refreshed information on local work process utilization
The status of an individual work process, for example, waiting, running, on hold, etc.
The process ID of the work process
The program that is currently executed by the work process
Rate this question:
Data that is NOT bound to a specific user context
Authorization data to enable faster user access
Local heap memory in the work process that is not assigned to a user context
Data associated with individual users and their open transactions
Rate this question:
Its total response time and average response time are high
Its average CPU time and/or database time are high
Its number of steps is very low
Its average CPU time is greater than average processing time
Rate this question:
The fields specified in the WHERE clause of the SQL statement
How often an SQL statement is executed
The number of database records that will be retrieved
The availability of indexes for the queried tables
Rate this question:
Rdisp/bufrefmode
Rdisp/bufreftime
Rdisp/max_alt_modes
Rdisp/buffer_on
Rate this question:
Check if load can be distributed to other servers with spare CPU capacity
Check the 'Top 40 CPU Processes' in transaction Operating System Monitor (ST06(n))
Check that there are enough Dialog work processes configured on the instance(s) on that server
Perform a detailed analysis of the memory configuration of the SAP system
Rate this question:
Tables with a high number of invalidations
Tables with a high number of invalidations
Tables with a large buffer size
Tables with buffer state 'pending'
Tables with more direct reads than sequential reads
Rate this question:
Distribute processes that do not need to run on this specific hardware to other hardware with unused capacity
Increase CPU capacity to avoid that memory is being paged
Optimize the database interface so that unneeded data is not being paged out
Identify users/programs that cause high memory consumption and optimize expensive SQL statements and suboptimal programming
Rate this question:
The database is updated and the buffer of the current application server is invalidated
Changes are written to table DDLOG, which is read at a certain interval to invalidate the buffered content on the other application servers
The buffered table is updated at all application servers and the database is updated afterward asynchronously by report DDLOG
Changes are written to table DDLOG, which is read at a certain inten/al to update the content of the database
Rate this question:
Not enough CPU resource available to hold the object in the buffer.
Not enough user activity to preserve the object in the buffer
Not enough space left in the buffer for buffering the new object
No enough directory entries to buffer the new object
Rate this question:
Without extended memory, a release of allocated memory in the OS paging file would not be possible
The large size of extended memory avoids context switches where possible
Fast context switches are needed in SAP systems because many users share few work processes
SAP transactions usually consist of more than one step or screen
Extended memory is accessed through pointers; therefore, fast context switches are possible
Rate this question:
During the first access to a table, all table content is copied to the table buffer on the SAP instance
You set some of key fields for a table to determine the data to be buffered during access
Each individual record accessed is buffered on the SAP instance
You set all key fields of a table to specify which records are buffered on the SAP instance
Rate this question:
CPU memory
Physical memory
OS paging file/OS swap space
File system cache
Rate this question:
Quiz Review Timeline (Updated): Mar 22, 2023 +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.