The application placement controller has been configured with elasticity mode enabled.
Intermittently, all instances of a dynamic cluster are removed. After further review, the system
administrator noticed that it occurs during peak load on another dynamic cluster.
The administrator wants to keep at least one instance available. Which configuration is needed in
the dynamic clusters?
A.
Enable application lazy start with elasticity mode.
B.
Set theproactiveldleStopcustom property to true
C.
Set the Number of instances to a value greater than zero.
D.
Disable the option”If other dynamic clusters need resources, stop all instances of this cluster
during periods of inactivity”.
Explanation:
Reference:http://pic.dhe.ibm.com/infocenter/wxdinfo/v6r1/index.jsp?topic=%2Fcom.ibm.webspher
e.ops.doc%2Finfo%2Freference%2Frodccustprop.html
D
0
0
Why not B ?
http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rwve_odccustprop.html?lang=en
0
0
“Lazy start” is a advance feature of Intelligent management. We call it “Lazy” because we won’t Maintain the min instances of the dynamic cluster, and the running instance number can be “0” when there’s no request(work) to do. The cluster is “Lazy” when there are no request come. Then, if a request come, it will response back with 503, and then after a few time, one instance will be “woke up”.
It’s better use this in some application that not have too much access, but customer still want to access the application when needed. It will release the resource for other key application when other application need resources.
So how to set Lazy start? Click “Dynamic Clusters > your_app_cluster” check If other dynamic clusters need resources, stop all instances of this cluster during periods of inactivity
set a value for “Time to wait before stopping instances” , means The application placement controller tracks the amount of time that a dynamic cluster has been inactive. If another dynamic cluster needs resources, the application placement controller can stop the inactive dynamic cluster after the specified time period. The resources that were consumed by the inactive instance are released and made available for use by the dynamic cluster that requires additional resources. If a request arrives for the stopped dynamic cluster instance, the lazy start controller is activated and at least one server instance is started. In the meantime, HTTP error code 503 (server unavailable) is generated. The error page informs you that the requested application is starting and the request is resubmitted shortly.
0
0
B
0
0
D
The name of the property is proactiveIdleStop, not theproactiveldleStopcustom
0
0
I think its B and a sentence typo mistake.
D option says disable option “…” but we need to enable option using “B==> true”
Also looking for correct Answers
0
0
I think ‘D’
It is not recommended to enable elasticity mode when the following option is set in the administrative console for one or more dynamic clusters:
If other dynamic clusters need resources, stop all instances of this cluster during periods of inactivity.
If you have elasticity mode enabled and the option set, the application placement controller can remove all of the custom nodes in the cell.
https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/twve_cfgelastic.html
0
0