The HR user updates the salary of one of the employees in the non-partitioned EMPLOYEES table, but does not commit the transaction. Which two types of lock exist in this situation?

An exclusive lock on the entire table would prevent other users from performing any DML or DDL, which is not the default behavior for a single row update.

A null lock does not prevent other transactions from accessing or modifying the row; an update operation requires a stronger lock type to ensure data integrity.

A null lock on the table does not prevent other transactions from performing DML or DDL, which is insufficient to protect data consistency during an update operation.

A row-level lock (TX lock) is acquired on the specific row being updated to prevent other transactions from modifying the same row until the current transaction commits or rolls back.

A shared lock (TM lock) is placed on the EMPLOYEES table to prevent DDL operations (like dropping the table) from occurring while DML operations are in progress, ensuring data consistency.