Which two statements describe good practices for an application developer to reduce locking conflicts in Oracle database? (Choose two.)

Long-running transactions hold row-level locks for extended periods, forcing other sessions to wait; keeping transactions as short as possible minimizes the lock hold time and reduces contention.

Oracle's default locking model uses fine-grained row-level locks combined with multi-version concurrency control (MVCC) so readers never block writers; this default behavior is already highly optimized and overriding it with explicit locks typically introduces unnecessary contention.

Explicitly coding lock statements (such as SELECT FOR UPDATE) beyond what the application truly requires introduces additional contention and increases the risk of deadlocks.

Oracle does not support lock escalation from row level to block or table level - that concept belongs to SQL Server; Oracle maintains row-level granularity regardless of the number of row locks held.