Question3 for IBM Test 340

[Jason Hunt]

What BEST describes setting the 'Minimum Heap Size' close to or equal to the 'Maximum Heap Size'?

A. High performance web applications waste more processing power on low performance functions.

B. Low performance web applications spend more processing power than necessary on low performance functions.

C. Can improve WebSphere Application Server start up.

D. Garbage collection cycles are more frequent that can affect performance.

I think should be D, but some ppl with C

---------------------------------------------------

A WebSphere Application Server V5.0 Administrator is attempting to understand WebSphere Connection Pooling. In which of the following examples should her application use WebSphere Connection Pooling?
(Select 3)

A. Whenever the application cannot tolerate the overhead of obtaining and releasing a database connection.

B. Whenever the application requires Java Transaction API (JTA) transactions within the WebSphere Application Server.

C. Whenever the application developers have implemented connection pooling in the code.

D. Whenever the application needs to share connections among multiple users.

E. Whenever the application manages the specifics of creating a connection, such as the database name, username, or password.

I go with A, C, E, but some ppl with A, B, D

Any idea ?

[Jayadev Pulaparty]

On the heap size thing, i still don't understand how option D is not correct I think both C & D are correct.

On the connection pooling thing, the correct options are undoubtedly A,B & D.

We never "implement" connection pooling in the code. We leave that complex responsibility to the container. Also, when we create a datasource (for connection pooling), we associate JAAS authentication with it that takes care of the required authentication credentials to access the database.

[Jason Hunt]

I agree with you on the connection pool question,

but for heap size question, the WAS startup shouldn't be affected by setting the minimum heap size equal to maximum heap size, right ?

thanks.

[Jayadev Pulaparty]

I think by setting max=min heapsize, we are utilizing the max possible heap and a good heap is going to help when the server is starting up as its going to initialize lots of things.

[Jason Hunt]

But I think if only select one, D is stronger than C.

[ March 23, 2005: Message edited by: Jason Hunt ]

[Jayadev Pulaparty]

Now i got why the heap thing is not correct option. This is purely based on how the question has been framed. If we look at the question, it says "which of the following BEST describes ......". Hence we cannot say that we go for max=min heap size so that the garbage cycles get more frequent (slowing doing the performance). Instead, we can say that we do it so that the server starts up quickly.

I guess this confirms the selection.

[Jason Hunt]

that is really tricky.

thanks.

[Luigui Paredes]

I think
1)Heap Size
C. Can improve WebSphere Application Server start up.

2.-Connection Pooling
A. obtaining and releasing a database connection.
C.(get Datasource, get Connection, close Connection)
D. share connections