View the Exhibit to examine the replay settings for replay parameters. 
What is the implication for setting the values for replay parameters? (Choose all that apply.)
A.
The COMMIT order in the captured workload is preserved during replay.
B.
The value 100 in the THINK_TIME_SCALE parameter attempts to make the replay client
shorten the think time between calls.
C.
The value 100 in the CONNECT_TIME_SCALE parameter attempts to connect all sessions as
captured.
D.
The value 100 in the THINK_TIME_SCALE parameter attempts to match the captured user
think time while replaying.
E.
The value 100 in the CONNECT_TIME_SCALE parameter attempts to connect all sessions
immediately as soon as the replay begins.
Preserving COMMIT Order
The synchronization parameter controls whether the COMMIT order in the captured workload will be preserved during replay. By default, this option is enabled to preserve the COMMIT order in the captured workload during replay. All transactions will be executed only after all dependent transactions have been committed.
You can disable this option, but the replay will likely yield significant data divergence. However, this may be desirable if the workload consists primarily of independent transactions, and divergence during unsynchronized replay is acceptable.
Controlling Session Logins
The connect_time_scale parameter enables you to scale the elapsed time between the time when the workload capture began and each session connects. You can use this option to manipulate the session connect time during replay with a given percentage value. The default value is 100, which will attempt to connect all sessions as captured. Setting this parameter to 0 will attempt to connect all sessions immediately.
Controlling Think Time
User think time is the elapsed time while the replayed user waits between issuing calls within a single session. To control replay speed, use the think_time_scale parameter to scale user think time during replay. If user calls are being executed slower during replay than during capture, you can make the database replay attempt to catch up by setting the think_time_auto_correct parameter to TRUE. This will make the replay client shorten the think time between calls, so that the overall elapsed time of the replay will more closely match the captured elapsed time.