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?
Correct Answer: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.
References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd. doc/ae/twve_cfgelastic.html
After installing an enhanced EAR in a WebSphere Application Server environment, a system administrator with Configurator privileges is able to see a JDBC provider and a data source in the Integrated Solution Console (ISC) but is not able to delete these resources.
How can the administrator resolve this issue?
Correct Answer:A
The JDBCProviderManagement command group for the AdminTask object includes the following commands:
References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd. doc/ae/rxml_atjdbcprovider.html
A new cell contains a cluster with members defined in two managed nodes running on two different machines. The cell also contains two unmanaged nodes running on HTTP servers with HTTP plug-in. Session persistence has been enabled.
Which additional component(s) can the system administrator configure to make this environment highly available?
Correct Answer:D
A system administrator ran the backup Config command to backup the configuration using the -nostop option. The administrator changed the properties for the service integration environment by modifying the sib.properties file. During testing the administrator noticed Service Integration Bus related errors and wanted to restore the service integration environment. The administrator used the restore config command, but the tuning properties for the service integration environment were not restored.
How can the administrator prevent this issue?
Correct Answer:B
A system administrator has configured a cluster containing 40 servers. The cluster members all belong to one core group. While examining the log files, the administrator notices that the core group coordinator is consuming abnormally high amounts of memory and CPU resources.
How can the system administrator reduce the memory and CPU resource usage of the core group coordinator?
Correct Answer:B
Remember that coordinator election occurs whenever the view changes. Electing a new coordinator uses a lot of resources because this process causes increased network traffic and CPU consumption. Specifying a preferred coordinator server, whenever practical, helps eliminate the need to make frequent coordinator changes.
References: https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc
/ae/crun_ha_coordinator.html
An application deployed to a multi-node cluster is reported to have slowness and hung threads. A system administrator is asked to review the logs on each node and identify if the hung threads are a false alarm.
How can the administrator determine that the hung threads are a false alarm? Analyze the:
Correct Answer:C
Problem(Abstract)
The SystemOut.log contains a WSVR0605W message, also called a hung thread message. A javacore, or thread dump on Solaris and HP-UX, is needed in order to determine how to resolve the potentially hung threads.
Cause
WebSphere Application Server attempts to report potentially hung threads using the hung thread detector. Depending on how the hung thread detector policy is configured, a thread running for a certain interval (default 10 minutes) might be reported as hung and a WSVR0605W message is printed in the SystemOut.log file:
WSVR0605W: Thread