View the Exhibit and examine the initialization parameter settings. Which three initialization parameters are to be set manually as they are not automatically tuned? (Choose three.)

LOG_BUFFER is the SGA region that buffers redo log entries before they are flushed to the online redo log files, and it is not included in the set of components that ASMM or AMM automatically resize. The DBA must explicitly set its value based on workload characteristics. An undersized LOG_BUFFER can cause frequent log writer waits and degrade write performance.

SORT_AREA_SIZE is a PGA parameter that is automatically governed by Oracle when PGA_AGGREGATE_TARGET or MEMORY_TARGET is configured, making manual tuning of it unnecessary under those modes.

JAVA_POOL_SIZE is one of the auto-tuned SGA sub-components managed by ASMM when SGA_TARGET is set; Oracle dynamically adjusts its allocation based on demand.

STREAMS_POOL_SIZE is automatically sized by Oracle's ASMM framework when SGA_TARGET is configured, as the Streams pool is included in the set of granule-based auto-tuned memory components.

DB_16K_CACHE_SIZE allocates buffer cache memory dedicated to tablespaces using a 16KB non-standard block size, and Oracle's automatic memory frameworks only manage the default block size cache (DB_CACHE_SIZE). Because non-standard block size caches require a deliberate DBA decision about which tablespaces use them, Oracle does not auto-tune their sizes. If not set, no memory is allocated and tablespaces using 16KB blocks cannot be accessed.

DB_KEEP_CACHE_SIZE defines a separate buffer pool intended to permanently retain frequently accessed segments in memory by preventing them from aging out. This pool is not managed by ASMM or AMM because pinning specific objects in cache requires an explicit DBA strategy rather than algorithmic tuning. The DBA must both set this parameter and assign individual objects to the KEEP pool using the BUFFER_POOL storage clause.