View the current parameter settings shown in the output below. NAMETYPEVALUE - db_file_multiblock_read_count integer 107 ddl_lock_timeout integer Distributed_lock_timeout - integer dml_locks integer 748 lock_sga boolean FALSE - enab1e_dd1_1ogging boolean FALSE - resumable_timeout integer A user logs in to the hrschema and issues the following commands: SQL> CREATE TABLE emp - (empno NUMBER(3), enamo VARCHAR2(20), sal NUMBER (8, 2)); SQL> INSERT INTO emp (empno, ename) VALUES(1, `JAMES`); At this moment, a second user also logs in to the hrschema and issues the following command: SQL> ALTER TABLE emp MODIFY salNUMBER(10, 2); What happens in this scenario? 

Answer options:

A. The second user`s session immediately produces a "resource busy" error.
B. The second user`s command executes successfully.
C. The second user`s session waits for a time before producing a "resource busy" error.
D. A deadlock is created.

C