User Scott has updated the salary of one of the employees in the EMPLOYEES table and has not committed the transaction. What are the two types of locks that this scenario would lead to? (Choose two.)

Null locks are placeholder locks used in distributed lock management for lock conversion purposes and are not placed on individual rows during a standard single-instance DML update.

Oracle does not place a null lock on the table for DML operations; it acquires a Row Exclusive (RX) table-level lock instead.

A ROW SHARE (RS) table lock is acquired by SELECT ... FOR UPDATE statements, not by a standard UPDATE DML operation.

Oracle places a TX (transaction) row-level exclusive lock on every row that is being modified by the UPDATE statement. This lock prevents any other transaction from modifying or locking the same row exclusively until the current transaction either commits or rolls back.

A share row-exclusive (SRX) table lock is not acquired during a normal uncommitted UPDATE; it applies to specific programmatic locking scenarios such as LOCK TABLE ... IN SHARE ROW EXCLUSIVE MODE.

Oracle also automatically acquires a table-level DML lock - specifically a Row Exclusive (RX) lock - on the table containing the modified row; this is the 'shareable' table lock because multiple concurrent DML sessions can all hold RX locks on the same table simultaneously, while it still prevents DDL operations that require a full exclusive table lock.

An exclusive table-level lock is acquired only by DDL statements such as DROP TABLE or TRUNCATE TABLE, not by ordinary DML operations like UPDATE.