View the Exhibit and examine the content of the V$SGA_RESIZE_OPS view.
The Shared Pool was shrunk when the Default Buffer Cache required more memory. Why did the
Java Pool not shrink when the Default Buffer Cache grew?
A.
because it is not an auto-tuned component
B.
because it uses memory available outside the total SGA size
C.
because it always requires three granules and cannot be reduced
D.
because it has less free memory than the Database Buffer Cache
E.
because it cannot be shrunk below the value set to the JAVA_POOL_SIZE parameter
E)
Setting Minimums for Automatically Sized SGA Components
You can exercise some control over the size of the automatically sized SGA components by specifying minimum values for the parameters corresponding to these components. Doing so can be useful if you know that an application cannot function properly without a minimum amount of memory in specific components. You specify the minimum amount of SGA space for a component by setting a value for its corresponding initialization parameter.
Manually limiting the minimum size of one or more automatically sized components reduces the total amount of memory available for dynamic adjustment. This reduction in turn limits the ability of the system to adapt to workload changes. Therefore, this practice is not recommended except in exceptional cases. The default automatic management behavior maximizes both system performance and the use of available resources.
JAVA_POOL_SIZE has a target size which can not be shrunk below
So E is right