Question 6 of 138
An IBM Security Access Manager V9.0 deployment professional is charged with monitoring request response times from WebSEAL to the backend. The deployment professional wants the flexibility to see response times per request, per junction, per HTTP return code, or other criteria that may come up in the future.
What action will generate the required data for this analysis?
    Correct Answer: A

    To monitor request response times from WebSEAL to the backend and have the flexibility to analyze data per request, per junction, per HTTP return code, or other criteria, customizing the request.log to include response times is the best approach. This method provides detailed and granular data necessary for comprehensive analysis.

Question 7 of 138
A deployment professional attempts to log into an appliance which is part of a cluster to run pdadmin commands and receives the following message: pdadmin> login-a sec_master ""p password
2016-03-03-02:04:38:.683-06:001 ---0x1354A420 pdadmin ERROR ivc socket mtsclient.cpp 2376
0x7fc2b7b0c720
HPDCO1056E Could not connect to the server 192.168.254.11, on port 7135.
Error: Could not connect to the server. (status 0x1354a426)
What should the deployment professional check concerning the login target?
    Correct Answer: D

    The error message indicates that the login attempt could not connect to the server on a specific IP address and port, which suggests that the issue might be related to the state of the server within the cluster. In the context of clustered environments, if the primary policy server is down, attempts to log in to nodes that are not primary will fail because they rely on the primary server for policy administration. Therefore, the correct answer is that the login was attempted on a non-primary master of a cluster and the primary policy server is down.

Question 8 of 138
A customer is migrating from TAM v6.1 running on AIX to IBM Security Access Manager (ISAM) V9.0 hardware appliance.
Which information form the TAM v6.1 environment will be useful in sizing the new ISAM V9.0 hardware configuration?
    Correct Answer: A

    The WebSEAL request logs are essential for sizing the new ISAM V9.0 hardware configuration. These logs provide detailed information about the volume and types of requests handled by the WebSEAL servers, which directly impacts the hardware requirements. Analyzing these logs will help in understanding the load and performance characteristics, crucial for accurate sizing.

Question 9 of 138
There is an SSL connectivity issue between the IBM Security Access Manager V9.0 Reverse Proxy and the backend business application.
Which Two troubleshooting commands under Tools in the application SSH interface can be used to validate the Reverse Proxy can successfully connect to the backend host: secure-port? (Choose two.)
    Correct Answer: B, C

    To troubleshoot SSL connectivity issues between the IBM Security Access Manager Reverse Proxy and the backend business application, the appropriate commands are 'Session' and 'Connect'. The 'Session' command allows checking for active sessions and helps verify if any live connections are established, while the 'Connect' command is used to test direct connectivity to the backend host on the specified secure port. 'Ping' checks network reachability but not SSL connectivity, 'Traceout' traces the route packets take but doesn't confirm successful SSL connections, and 'Connections' lists existing connections but does not verify new ones.

Question 10 of 138
An IBM Security Access Manager V9.0 Reverse Proxy has a stateful junction to a Portal application called "/wps" There is no web server in front of Portal. This junction has three Portal servers defined behind it. The Portal team needs to do maintenance on each of the three servers. The team wants to accomplish with least impact to end users.
Which pdadmin "server task" based steps will accomplish this?
    Correct Answer: C

    To perform maintenance on each of the three servers with the least impact to end users, the appropriate approach is to take one server offline, apply the necessary maintenance, and then bring it back online before repeating the process for the other servers. This ensures that the remaining servers can continue to handle requests, maintaining the availability of the application and minimizing disruption to the end users.