IBM C9510-401 Exam Practice Questions (P. 3)
- Full Access (73 questions)
- Six months of Premium Access
- Access to one million comments
- Seamless ChatGPT Integration
- Ability to download PDF files
- Anki Flashcard files for revision
- No Captcha & No AdSense
- Advanced Exam Configuration
Question #11
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.
Application Server with High Performance Extensible Logging (HPEL) enabled.
- AConfigure log detail levels to include filter on "Connection" string.
- BUse the Log Viewer in the administrative console with filter on "Connection" string.
- CUse the logviewer.sh or logviewer.bat command with appropriate options.
- DUse the Log Viewer in the administrative console with filter on "Connection" string and enable the "Refresh automatically" feature.
Correct Answer:
C
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
C
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
send
light_mode
delete
Question #12
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?
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?
- ACheck the System logs for OutOfMemoryErrors. Trigger a heap dump from the Integrated Solutions Console (ISC). Analyze the heap dump.
- BConfigure WebSphere Application Server to enable verbose garbage collection. Analyze the garbage collection cycles in the native logs.
- CConfigure Initial heap to be equal to the max heap. Trigger a heap dump from the Integrated Solutions Console (ISC). Analyze the heap dump.
- DConfigure WebSphere Application Server to increase max heap. Trigger a heap dump from the Integrated Solutions Console (ISC).
Correct Answer:
B
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
B
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
send
light_mode
delete
Question #13
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?
To avoid this issue in the future, what can the administrator do?
- AConfigure entries in the ras.rawtracelist.properties.
- BConfigure suppressSensitiveTrace in the bootstrap.properties file.
- CClear the "Disable logging and tracing of potentially sensitive data" checkbox.
- DAdd the entry com.ibm.websphere.logging.RawTraceList=off to the end of the trace string.
Correct Answer:
C
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
C
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
send
light_mode
delete
Question #14
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?
What does the administrator have to configure to trigger the javacore dump?
- AConfigure the JAVA_DUMP_OPTS environment variable to capture javacore for ANYSIGNAL and all exceptions.
- BConfigure an –Xdump:java Generic JVM argument on WebSphere Application Server with the filter for java.net.SocketTimeoutException.
- CCode wsadmin script to capture javacore and then execute it after the java.net.SocketTimeoutException has been encountered.
- DUse 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
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
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
send
light_mode
delete
Question #15
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?
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?
- AEnable High Performance Extensible Logging (HPEL). Use HPEL logViewer command to see debug information.
- BEnable a diagnostic trace in both requester and consumer servers. Use the Integrated Solutions Console (ISC) to set the admin=all trace. Analyze the trace.
- CEnable 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.
- DUsing the Integrated Solutions Console (ISC), browse the request message that has timed out and look for any key application data.
Correct Answer:
C
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
C
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
send
light_mode
delete
All Pages