Download IBM.C9510-401.RealExams.2018-10-24.46q.vcex

Download Exam

File Info

Exam IBM WebSphere Application Server Network Deployment V8.5.5 and Liberty Profile, System Administration
Number C9510-401
File Name IBM.C9510-401.RealExams.2018-10-24.46q.vcex
Size 362 KB
Posted Oct 24, 2018
Download IBM.C9510-401.RealExams.2018-10-24.46q.vcex

How to open VCEX & EXAM Files?

Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.

Download
ProfExam Simulator

Purchase

Coupon: MASTEREXAM
With discount: 20%





Demo Questions

Question 1

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:


  1. ffdc logs
  2. SystemErr.log
  3. SystemOut.log
  4. native_stderr.log
Correct answer: C
Explanation:
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 <threadname> has been active for <time> and may be hung.  There are <totalthreads> in total in the server that may be hung.References: https://www-01.ibm.com/support/docview.wss?uid=swg21448581
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 <threadname> has been active for <time> and may be hung.  There are <totalthreads> in total in the server that may be hung.
References: https://www-01.ibm.com/support/docview.wss?uid=swg21448581



Question 2

A system administrator suspects that the slow performance of an application might be caused by lock contention. 
To debug this further, what can the administrator do using IBM Support Assistant?


  1. Analyze the running server using IBM Monitoring and Diagnostic Tools for Java – Health Center.
  2. Collect a javacore and analyze it using IBM Monitoring and Diagnostic Tools for Java – Health Center.
  3. Collect three thread dumps at equal time intervals and analyze them using IBM Monitoring and Diagnostic Tools for Java – Dump Analyzer.
  4. Collect three system dumps at equal time intervals and analyze them using IBM Monitoring and Diagnostic Tools for Java – Memory Analyzer.
Correct answer: A
Explanation:
The IBM Monitoring and Diagnostic Tools for Java - Health Center is a lightweight tool that monitors active IBM Virtual Machines for Java with minimal performance overhead. The Health Center suggests live tuning recommendations for Garbage Collection, profiles methods including call stacks, and highlights contended locks. This information can help you optimize performance, improve stability and optimize system resource usage. The tool is provided in two parts:An agent, which collects data from a running application. Java applications are monitored by the Health Center agent The Health Center client, an Eclipse-based GUI which connects to the agent. The client interprets the data that is obtained by the agent and provides recommendations to improve the performance of the monitored application. The client is available as an Eclipse plug-in and as part of IBM Support Assistant (ISA). References: https://www.ibm.com/support/knowledgecenter/SS3KLZ/com.ibm.java.diagnostics.healthcenter.doc/homepage/plugin-homepage-hc.html
The IBM Monitoring and Diagnostic Tools for Java - Health Center is a lightweight tool that monitors active IBM Virtual Machines for Java with minimal performance overhead. The Health Center suggests live tuning recommendations for Garbage Collection, profiles methods including call stacks, and highlights contended locks. This information can help you optimize performance, improve stability and optimize system resource usage. 
The tool is provided in two parts:
  • An agent, which collects data from a running application. Java applications are monitored by the Health Center agent 
  • The Health Center client, an Eclipse-based GUI which connects to the agent. The client interprets the data that is obtained by the agent and provides recommendations to improve the performance of the monitored application. The client is available as an Eclipse plug-in and as part of IBM Support Assistant (ISA). 
References: https://www.ibm.com/support/knowledgecenter/SS3KLZ/com.ibm.java.diagnostics.healthcenter.doc/homepage/plugin-homepage-hc.html



Question 3

A system administrator was asked by the development team to inform them of any warning message which contains a string “Connection” on a WebSphere Application Server with High Performance Extensible Logging (HPEL) enabled. 
What should the administrator do to continuously monitor logs for the required message?


  1. Configure log detail levels to include filter on “Connection” string.
  2. Use the Log Viewer in the administrative console with filter on “Connection” string.
  3. Use the logviewer.sh or logviewer.bat command with appropriate options.
  4. Use the Log Viewer in the administrative console with filter on “Connection” string and enable the “Refresh automatically” feature.
Correct answer: C
Explanation:
The High Performance Extensible Logging (HPEL) facility writes to the log and trace repositories in a binary format. You can view, query and filter the repository using the LogViewer command. logviewer.sh -monitor -includeLoggers Connection -monitor [integer] Specifies that you want the logViewer to continuously monitor the repository and output new log record entries as they are created. You can provide an optional integer argument after this parameter to specify how often you want the LogViewer tool to query the repository for new records. By default the logViewer queries the repository for new records every 5 seconds. When used with other filtering options, only those new records that match the filter criteria are displayed. References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rtrb_logviewer.html
The High Performance Extensible Logging (HPEL) facility writes to the log and trace repositories in a binary format. You can view, query and filter the repository using the LogViewer command. 
logviewer.sh -monitor -includeLoggers Connection 
-monitor [integer] 
Specifies that you want the logViewer to continuously monitor the repository and output new log record entries as they are created. You can provide an optional integer argument after this parameter to specify how often you want the LogViewer tool to query the repository for new records. By default the logViewer queries the repository for new records every 5 seconds. When used with other filtering options, only those new records that match the filter criteria are displayed. 
References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/rtrb_logviewer.html



Question 4

A system administrator is required to monitor the application server logs for heap memory issues and determine if the heap memory usage is reaching close to 70% of the maximum heap. The application server is configured with an initial heap of 256 MB and a max heap of 1 GB. 
How should the administrator determine if the application server is utilizing 70% of the max allocated heap memory?


  1. Check the System logs for OutOfMemoryErrors. 
    Trigger a heap dump from the Integrated Solutions Console (ISC). 
    Analyze the heap dump.
  2. Configure WebSphere Application Server to enable verbose garbage collection. 
    Analyze the garbage collection cycles in the native logs.
  3. Configure Initial heap to be equal to the max heap. 
    Trigger a heap dump from the Integrated Solutions Console (ISC). 
    Analyze the heap dump.
  4. Configure WebSphere Application Server to increase max heap. 
    Trigger a heap dump from the Integrated Solutions Console (ISC). 
    Analyze the heap dump.
Correct answer: B
Explanation:
Enabling verboseGC (Garbage Collection) output is often required when diagnosing issues with WebSphere Application Server. Because verboseGC data is critical to troubleshooting memory and performance problems and the overhead is generally very low, you may want to consider proactively enabling it in your environment. References: http://www-01.ibm.com/support/docview.wss?uid=swg21114927
Enabling verboseGC (Garbage Collection) output is often required when diagnosing issues with WebSphere Application Server. Because verboseGC data is critical to troubleshooting memory and performance problems and the overhead is generally very low, you may want to consider proactively enabling it in your environment. 
References: http://www-01.ibm.com/support/docview.wss?uid=swg21114927



Question 5

After collecting diagnostic trace from a server running under a cell, a system administrator noticed that the trace files contained sensitive information. 
To avoid this issue in the future, what can the administrator do?


  1. Configure entries in the ras.rawtracelist.properties.
  2. Configure suppressSensitiveTrace in the bootstrap.properties file.
  3. Clear the “Disable logging and tracing of potentially sensitive data” checkbox.
  4. Add the entry com.ibm.websphere.logging.RawTraceList=off to the end of the trace string.
Correct answer: C
Explanation:
You can either enable or disable the sensitive log and trace guard to help control whether loggers write sensitive information in your log and trace files. Use the administrative console to enable or disable the sensitive log and trace guard. Procedure Log on to the administrative console. If you are using an administrative agent topology, then select a node that you want to manage, and navigate to it. From the navigation section in the console, choose Troubleshooting > Logs and trace. Select the server that you want to enable or disable with sensitive log and trace guard. Click Change log detail levels. Select the Disable logging and tracing of potentially sensitive data check box to enable sensitive log and trace guard. To disable sensitive log and trace guard, clear the Disable logging and tracing of potentially sensitive data check box. Click OK Save the changes. References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/ttrb_enablesensitivelogtrace.html
You can either enable or disable the sensitive log and trace guard to help control whether loggers write sensitive information in your log and trace files. 
Use the administrative console to enable or disable the sensitive log and trace guard. 
Procedure 
  1. Log on to the administrative console. 
  2. If you are using an administrative agent topology, then select a node that you want to manage, and navigate to it. 
  3. From the navigation section in the console, choose Troubleshooting > Logs and trace. 
  4. Select the server that you want to enable or disable with sensitive log and trace guard. 
  5. Click Change log detail levels. 
  6. Select the Disable logging and tracing of potentially sensitive data check box to enable sensitive log and trace guard. To disable sensitive log and trace guard, clear the Disable logging and tracing of potentially sensitive data check box. 
  7. Click OK 
  8. Save the changes. 
References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/ttrb_enablesensitivelogtrace.html



Question 6

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?


  1. Configure the JAVA_DUMP_OPTS environment variable to capture javacore for ANYSIGNAL and all exceptions.
  2. Configure an –Xdump:java Generic JVM argument on WebSphere Application Server with the filter for java.net.SocketTimeoutException.
  3. Code wsadmin script to capture javacore and then execute it after the java.net.SocketTimeoutException has been encountered.
  4. Use the log filter in HPEL to monitor for java.net.SocketTimeoutException and then gather a javacore dump from the Integrated Solutions Console (ISC).
Correct answer: B
Explanation:
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=userReferences: http://www-01.ibm.com/support/docview.wss?uid=swg21242497
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



Question 7

An EJB application posts a request message into a JMS destination and waits for a response message on a different JMS destination. To correlate the response message to the request message, the application uses the JMS correlationId of the message. The application waits up to five seconds for a response before timing out the request. 
A Message Driven Bean (MDB) running on a different cluster is responsible for consuming the request message, process it and post a response message. 
The destinations are defined in a Service Integration Bus (SIB) within the cell. 
Intermittent timeout exceptions have occurred for the requester application. How can a system administrator correlate and analyze the debug information from both requester and consumer applications?


  1. Enable High Performance Extensible Logging (HPEL). 
    Use HPEL logViewer command to see debug information.
  2. Enable a diagnostic trace in both requester and consumer servers. 
    Use the Integrated Solutions Console (ISC) to set the admin=all trace. 
    Analyze the trace.
  3. Enable High Performance Extensible Logging (HPEL). 
    Enable Cross Component Trace (XCT) to include request IDs in log and trace records. 
    Use HPEL logViewer command with appropriate filters to see debug information.
  4. Using the Integrated Solutions Console (ISC), browse the request message that has timed out and look for any key application data. 
    Search for exceptions using the key application data in both requester and consumer in native_stderr.log and native_stdout.log.
Correct answer: C
Explanation:
Cross Component Trace (XCT) annotates the logs so that log entries that are related to a request that is serviced by more than one thread, process, or even server are identified as belonging to the same unit of work. XCT helps identify the root cause of problems across components. References: WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile (July 2013), page 1091
Cross Component Trace (XCT) annotates the logs so that log entries that are related to a request that is serviced by more than one thread, process, or even server are identified as belonging to the same unit of work. XCT helps identify the root cause of problems across components. 
References: WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile (July 2013), page 1091



Question 8

A WebSphere system administrator needs to install the Installation Manager (IM) on an unmanaged node on a host named <machine2>. The deployment manager is running on a host named <machine1>. 
What step must the administrator take before submitting a job from the Integrated Solutions Console (ISC) to install the IM on <machine2>?


  1. Install a node agent on <machine2>.
  2. Install the job manager on <machine1>.
  3. Start the job manager on <machine1>.
  4. Register <machine2> as a target for job manager.
Correct answer: D
Explanation:
Submitting jobs to install Installation Manager on remote hosts In a flexible management environment, you can submit the Install IBM Installation Manager job to install the Installation Manager on registered hosts of the job manager. References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.installation.zseries.doc/ae/tagt_jobmgr_install_im.html
Submitting jobs to install Installation Manager on remote hosts 
In a flexible management environment, you can submit the Install IBM Installation Manager job to install the Installation Manager on registered hosts of the job manager. 
References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.installation.zseries.doc/ae/tagt_jobmgr_install_im.html



Question 9

A system administrator has created a wsadmin script with several steps to install and configure an application and some resources in a WebSphere Application Server process. The script executed but the application was not installed successfully. The administrator suspects that the script has problems. 
How can the administrator test and debug the script?


  1. In WebSphere Application Server Developer Tools for Eclipse, right click on the script file and select Validate from context menu.
  2. Execute the script using the wsadmin with the option –conntype NONE and monitor the commandAssistanceJythonCommands.log file.
  3. Use WebSphere Application Server Developer Tools for Eclipse in the debug perspective connected to the server and execute the script step by step.
  4. Run the script using wsadmin with these parameters: -lang jython –javaoption “-Xdebug” and then execute the logViewer command with the option -listInstances
Correct answer: C



Question 10

A system administrator has been asked to uninstall an application from a cluster running in a WebSphere Application Server Network Deployment cell. This application was installed from the Integrated Solutions Console (ISC). The monitored directory for the cluster is <cluster1_dir>. 
What step(s) can the administrator perform to uninstall the application?


  1. Delete the application file from <cluster1_dir>.
  2. Stop the running cluster. 
    Delete the application file from <cluster1_dir>.
  3. Stop the running cluster. 
    Copy the application file to <cluster1_dir>. 
    Delete the application file from <cluster1_dir>.
  4. Create a properties file to describe the deletion of the application file. 
    Copy the properties file to <cluster1_dir>.
Correct answer: D
Explanation:
You can use application properties files to install enterprise application files on a server or cluster, update deployed applications or modules, or uninstall deployed applications or modules. Drag or copy a properties file to a monitored directory and the product performs the deployment action described in the properties file. The enterprise application files that you can install, update, or uninstall using properties files include enterprise archive (EAR), web archive (WAR), Java archive (JAR), and Session Initiation Protocol (SIP) archive (SAR) files. References: https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/trun_app_install_dragdrop_prop.html
You can use application properties files to install enterprise application files on a server or cluster, update deployed applications or modules, or uninstall deployed applications or modules. Drag or copy a properties file to a monitored directory and the product performs the deployment action described in the properties file. The enterprise application files that you can install, update, or uninstall using properties files include enterprise archive (EAR), web archive (WAR), Java archive (JAR), and Session Initiation Protocol (SIP) archive (SAR) files. 
References: https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/trun_app_install_dragdrop_prop.html









CONNECT US

Facebook

Twitter

PROFEXAM WITH A 20% DISCOUNT

You can buy ProfExam with a 20% discount!

Get Now!


HOW TO OPEN VCEX FILES

Use ProfExam Simulator to open VCEX files