C9510-401 Dumps

C9510-401 Free Practice Test

IBM C9510-401: IBM WebSphere Application Server Network Deployment V8.5.5 and Liberty Profile, System Administration

QUESTION 16

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 has been active for

QUESTION 17

Which of the following comprises an initial Liberty profile server process?

Correct Answer: A
The server process comprises a single JVM, the Liberty kernel, and any number of optional features.
References: https://www.ibm.com/support/knowledgecenter/SSEQTP_8.5.5/com.ibm.websphere.wlp.do c/ae/cwlp_about.html

QUESTION 18

An organization updated their LDAP directories and modified user roles. The roles that were configured to have access to a highly secured enterprise application were deleted and new roles with new names were created. The application then had security related exceptions.
How can a system administrator resolve the exceptions and restore security for the
application?

Correct Answer: A

QUESTION 19

A system administrator needs to trigger a javacore only when a java,net.SocketTimeoutException is encountered in real time.
What does the administrator have to configure to trigger the javacore dump?

Correct Answer: B
Dump agents are set up during JVM initialization. They enable you to use events occurring within the JVM, such as Garbage Collection, thread start, or JVM termination, to initiate one of four types of dump or to launch an external tool. Default dump agents are set up at JVM initialization They are sufficient for most cases, but the use of the -Xdump option on the command line allows more detailed configuration of dump agents. The total set of options and sub-options available under -Xdump is very flexible and there are many examples presented in this chapter to show this flexibility.
Example: To generate system cores:
-Xdump:system:events=user
References: http://www-01.ibm.com/support/docview.wss?uid=swg21242497