Which two would you recommend to an application developer for reducing locking conflicts on tables in an Oracle database? (Choose two.)

Creating objects in locally managed tablespaces with Automatic Segment Space Management (ASSM) significantly reduces contention for segment header blocks, as space management is handled using bitmaps, allowing concurrent DML without common bottlenecks.

Avoiding long-running transactions is a good practice for overall performance and resource utilization, but it primarily minimizes the *duration* of locks rather than preventing the initial *occurrence* of locking conflicts.

Oracle's default locking mode employs fine-grained row-level locking, which minimizes conflicts by locking only the affected rows, making it highly efficient for concurrent transactions and generally superior to manual locking schemes.

Using manual segment space management (MSSM) can actually *increase* locking conflicts, as multiple sessions may contend for the same segment header blocks when trying to allocate or deallocate space.

Enabling undo retention guarantee ensures undo information is preserved for a specified duration, primarily supporting long-running queries and Flashback features, and does not directly reduce locking conflicts on tables.