IBM WebSphere Application Server Network Deployment v9.0.5 Questions and Answers
An administrator has configured High Performance Extensible Logging (HPEL) in a WebSphere cell. Which option lets them access logs throughout the cell?
Options:
HPELControlService and HPELLogDataService
HPELLogDataService and HPEL API
HPELTraceDataService and HPEL API
HPELControlService and HPEL API
Answer:
DExplanation:
High Performance Extensible Logging stores log and trace records in a binary repository, and it exposes that content through services and an API. Two management interfaces matter. The HPELControlService is the MBean used to configure the logging service, for example to change repository settings, and the HPEL API, which provides programmatic access for reading and filtering repository data. Where logs must be reached across the whole cell, the control service lets the administrator manage HPEL behaviour for servers in every node, and the API lets a program read records from multiple servers' repositories. This pairing is what option D lists.
The other options mix the services in ways that fall short. HPELLogDataService is a service for retrieving log records from a single server, which makes it narrower than the cell-wide requirement. HPELTraceDataService concerns trace records and, with the same limitation, offers retrieval for a particular server and not cell-wide access.
For day-to-day work, the LogViewer command line tool, which reads HPEL repositories, is the most common method of seeing the content in a readable form, and it can be used with filters on time, thread, logger, or message level. Administrators can also view logs from the administrative console's log viewer when HPEL is the active log framework.
Which wsadmin command generates migration reports for one or more enterprise applications in WebSphere Application Server ND?
Options:
AdminTask.createMigrationReport
AdminConfig.getMigrationReport
AdminConfig.getMigrationSummary
AdminTask.createMigrationRecord
Answer:
AExplanation:
Migration reports for enterprise applications are produced through administrative tasks. In wsadmin the AdminTask object provides createMigrationReport, which analyses one or more installed applications against a target, identifies issues, and stores the report with the application. Option A is correct. The task accepts parameters that identify the application or applications and the target of the analysis, and the resulting report can then be viewed in the console or with getMigrationReport. The matching console action is the Analyze button on the enterprise applications page.
The other commands do not exist or belong to a different object. AdminConfig.getMigrationReport, option B, combines a real task name with the wrong object, since AdminConfig deals with configuration objects and does not provide migration report functions. AdminConfig.getMigrationSummary, option C, is not a command in the product. AdminTask.createMigrationRecord, option D, uses a made-up command name, since the term used is "report".
Because the report depends on the application files, administrators must regenerate it after any redeployment, which removes the earlier version automatically. When many applications are to be assessed, a script that loops through the installed applications and calls createMigrationReport for each is an effective way to produce the whole set, and the reports can be examined together to plan the order of migration.
Which option can be used to remove an incorrect profile?
Options:
Installation Manager
manageprofiles command
Administrative Console
Profile Management Tool
Answer:
BExplanation:
A profile is a set of files that defines the runtime environment for a deployment manager, node, or stand-alone server, and the manageprofiles command is the product's supported interface for its lifecycle. The command accepts the -create, -delete, -augment, -backupProfile, -restoreProfile, -listProfiles, and -validateAndUpdateRegistry options. Running it with -delete unregisters the named profile from the profile registry and removes its configuration, which is exactly what is required when a profile was created with incorrect settings. Option B is correct. A typical sequence is to stop every process that belongs to the profile, run manageprofiles -delete -profileName with the profile name, and then remove any directory that remains on disk, since deletion can leave residual files when the profile had been used.
The other tools do not perform this task. Installation Manager installs, updates, modifies, and uninstalls product packages; it does not manage individual profiles within an installed package. The administrative console manages the cell configuration of servers, applications, and resources, and a profile's existence on a machine falls outside its scope. The Profile Management Tool is a graphical front end that can create and augment profiles, but it does not offer a delete function, which is why administrators fall back on the command line when a profile has to be removed.
After deletion, -listProfiles confirms that the registry no longer shows the entry.
Which two functions does Transformation Advisor provide?
Choose two
Options:
It generates reports that compare benefits of usage for each supported provider
It determines the complexity of applications.
It suggests changes to make applications faster when moved to the cloud.
It suggests partitions and generates microservices for an easier move to the cloud.
It identifies application changes required for modernization
Answer:
B, EExplanation:
Transformation Advisor is an IBM tool that analyses existing applications and the environments on which they run, in order to help plan a move to a modern platform such as containers or a cloud service. Its collector examines the application and server configuration and produces an assessment. Two functions from the list belong to it, options B and E. First, it determines the complexity of applications: the report assigns each application a rating, such as simple, moderate, or complex, together with an estimated development effort for migration. Second, it identifies the application changes that are required for modernisation, listing issues in the code or configuration, grouped by severity, that must be addressed for the target runtime.
The other statements go beyond what the tool provides. Option A, a comparison of benefits for each supported provider, is not a report function, because the output evaluates applications and not the commercial features of providers. Option C, suggesting changes that would make applications faster in the cloud, confuses migration readiness with performance tuning, which the tool does not perform. Option D, partitioning an application and generating microservices, is refactoring work that the tool does not undertake; it can recommend a target but does not decompose code.
The recommendations are typically used to prioritise which applications to move first and to estimate the effort involved.
Which two scenarios are supported for SPNEGO web authentication when a Java client uses the HTTP protocol?
Choose two
Options:
Azure realm trust
Cross-forest trust
Forest external trust
Kerberos realm trust
Domain trust within the same forest
Answer:
D, EExplanation:
SPNEGO, the Simple and Protected GSS-API Negotiation mechanism, lets a browser or Java client authenticate to WebSphere Application Server using Kerberos credentials obtained at desktop login. For the HTTP protocol, the product supports a defined set of trust relationships between the Kerberos realms or Active Directory domains in which the client and the server's service principal reside. The two that appear in the list are the Kerberos realm trust and the domain trust within the same forest, so options D and E are correct. In a realm trust, a client in one Kerberos realm obtains a service ticket for a server registered in a trusted realm. In a same-forest domain trust, users in a child domain authenticate to services registered elsewhere in the forest because the trust is transitive and implicit.
Options B and C describe cross-forest and forest external trusts, which carry restrictions and are not included among the supported scenarios, and option A, an Azure realm trust, is not a SPNEGO trust type recognised by the product.
Administrators configuring SPNEGO must also create the service principal name for the host, generate a Kerberos keytab and configuration file, and set up the SPNEGO trust association interceptor or the SPNEGO web authentication settings in the security configuration. Clock synchronisation between the client, the KDC, and the server is essential because Kerberos tickets are time-sensitive.
When security is enabled in WebSphere Application Server ND, which two administrative commands may be used without providing a user name and password?
Choose two
Options:
serverStatus
stopServer
stopManager
startServer
startManager
Answer:
D, EExplanation:
When administrative security is enabled, most administrative commands authenticate to the server before acting on it, so they need a user ID and password supplied as arguments or through a properties file. Commands that stop servers or query their status communicate with a running process and are therefore subject to authentication. The commands that start a server are different, because the start commands launch a local operating-system process on the machine where they are run; they do not connect to an existing server's administrative service and therefore need no credentials. startServer and startManager are the two commands that can be run without a user name and password, so options D and E are correct.
serverStatus, option A, queries a running server through the administrative connector, so it requires credentials with at least the monitor role when security is enabled. stopServer, option B, and stopManager, option C, send a stop request to a running server, which calls for the operator or administrator role and thus needs authentication.
The practical rule is that anything operating on a live process requires credentials, while launching a process requires only operating-system privileges to run the script. Administrators who dislike passing credentials on the command line can place them in the soap.client.props file, ideally with the password encoded.
An administrator configured database session persistence for an application deployed to a WebSphere Application Server ND cluster. Application users have begun reporting data loss in HTTP session objects. How can the administrator resolve the issue with database session persistence?
Options:
Write session data at periodic intervals.
Select multi-row schema on session datasource: drop the existing session table, and recreate it.
Switch to memory to memory session persistence.
Create a session database with large BUFFERPOOL SIZE with PAGESIZE 32K.
Answer:
BExplanation:
Database session persistence stores HTTP session data in a table of a relational database, so that sessions survive a server failure and can be shared among cluster members. The product offers two layouts. In the single-row schema, all of the session's data is held in one row, and the size of that row is limited by the database's row size, so large sessions can exceed the limit and be truncated or lost. In the multi-row schema, a session's data is spread across several rows, which removes the limit on session size and allows large sessions to be saved without loss. When users report data loss in session objects, the likely cause is large session data exceeding the single-row limit. The remedy is to select the multi-row schema on the session data source, drop the existing session table, and let the product recreate it with the new layout. Option B is correct.
Option A, periodic writing, would raise the risk of loss between writes because data changed since the last write is lost on failure. Option C, switching to memory-to-memory replication, changes the persistence mechanism altogether and does not correct the cause. Option D, enlarging the buffer pool and page size, may help the database performance but does not address a limit on the session's data in a row.
Dropping the table discards existing sessions, so the change should be scheduled for a quiet period, with users informed of the need to log in again.
What is the purpose of setting the com.ibm.ws.cache.CacheConfig.disableTemplateInvalidation JVM custom property to true?
Options:
It enables template-based invalidations during JSP caching
It disables template-based invalidations during JSP reloads
It disables template-based invalidations during JSP caching
It enables template-based invalidations during JSP reloads
Answer:
BExplanation:
The dynamic cache service uses templates, meaning the JSP or servlet entries that carry the output of a particular resource, and it invalidates cached entries based on those templates when the underlying resources change. When a JSP is reloaded after being modified, the cache by default invalidates the template's cached entries so that stale output built from the old version is not served. The custom property com.ibm.ws.cache.CacheConfig.disableTemplateInvalidation changes that behaviour. Setting it to true disables template-based invalidations during JSP reloads, which matches option B.
Option A and option D state the opposite effect, as both describe the property enabling invalidation. Option C describes the effect as occurring during JSP caching, but the trigger is the reloading of the JSP, not the act of caching it, so the wording does not fit.
The setting suits cases in which JSPs are reloaded frequently, for instance in an environment where files are touched by a deployment process without content change, and the resulting invalidations would empty the cache and reduce its benefit. Administrators accept a trade-off, because with invalidation disabled a changed JSP may continue to be served from cache until entries expire or are invalidated by another mechanism, so the property should be applied with an understanding of the content update process. It is configured as a JVM custom property for the server.
Which two approaches can be used to update an application in a WebSphere Application Server ND production environment?
Choose two
Options:
Hot deployment
Dynamic reloading
Monitored directories
Administrative console
wsadmin
Answer:
D, EExplanation:
Updating an application in a production cell has to be done in a controlled, repeatable manner, and the product supports this through its administrative interfaces. The administrative console includes an update wizard, available from the enterprise application list, that lets the administrator replace the whole application, a single module, a single file, or part of the application, with the changes synchronised to the nodes. The wsadmin scripting client provides the same capability through AdminApp.update, which is suited to automation and to release procedures that must be scripted. Options D and E are correct.
The other approaches are intended for development or are not controlled enough for production. Hot deployment, option A, refers to placing files directly in the deployed application directory, a technique that is not supported for production. Dynamic reloading, option B, refreshes classes when files change on disk and, again, is a development convenience; in production it may be turned off. Monitored directories, option C, install applications automatically when the archive is dropped into a folder, and they apply default bindings and give no control over the process, so the facility is suitable for test environments.
In production, administrators generally combine the console or wsadmin update with a rolling restart of cluster members, so the application stays available. A backup of the configuration beforehand allows a rollback if the update has unwanted effects.
What are two legitimate reasons to modernize an application and move it to a cloud environment?
Choose two
Options:
Make source code simpler
Speed in-market delivery
Make application faster
Reduce complexity and costs
Better user experience
Answer:
B, DExplanation:
Modernisation is justified by business and operational outcomes, and two of the listed reasons are legitimate. Speeding in-market delivery is a central motive: moving an application to a cloud environment, and often packaging it in containers, lets teams use automated build and release pipelines, provision environments on demand, and deliver changes more often. Reducing complexity and costs is the second: consolidating infrastructure, using pay-as-you-go capacity, and retiring ageing platforms lower the burden of operating the estate. Options B and D are correct.
The remaining statements describe side effects or goals that are not reasons in themselves. Making source code simpler, option A, may occur if an application is refactored, but a move to the cloud does not simplify code, and rewriting for that purpose is an expensive end in itself. Making the application faster, option C, is not a dependable result, because performance depends on design, and an application that is moved without change usually performs much as before. A better user experience, option E, relates to the application's interface and functionality, which modernisation of the platform does not by itself change.
Transformation Advisor helps to prioritise by estimating the effort per application, so the organisation can begin with the candidates that have the best ratio of benefit to work.
Which statement characterizes the Service Integration Bus?
Options:
A WebSphere Application Server component dedicated for internal communication between administrative services.
A mediation service that can be deployed onto the embedded IBM MQ JMS provider.
A WebSphere Application Server component used by the default messaging provider for transport.
An IBM product that can be used instead of the embedded JMS provider.
Answer:
CExplanation:
A service integration bus is the messaging infrastructure of WebSphere Application Server's service integration technology. It supplies the transport, destinations, and persistence behind the default messaging provider: applications look up JMS connection factories and destinations that resolve to a bus, and the messaging engines running on bus members move the messages. Option C captures that relationship, a component used by the default messaging provider for transport.
Each alternative misplaces the bus. Option A is wrong because internal communication between administrative services is handled by the administrative connectors and the high availability manager, not by a bus. Option B is wrong because mediations are services that can be attached to bus destinations to process messages in flight; they are not deployed onto an embedded IBM MQ JMS provider, and the embedded provider concept does not apply to the bus in that way. Option D is wrong because the bus is not a separate product. IBM MQ is the separate product, and it can be connected to a bus through an MQ link or used directly through the IBM MQ messaging provider, but the bus itself is part of the application server.
When planning a bus, administrators add application servers or clusters as bus members, and each member hosts or can host messaging engines, which determines availability and scalability.
Which two diagnostic options can be used to gather thread dumps for analyzing slowness in an application?
Choose two
Options:
WebSphere Developer Tools
Job Manager
Administrative consoler
Administrative Agent
wsadmin
Answer:
C, EExplanation:
A thread dump is a snapshot of the stacks of all threads in a JVM, and a series of them taken a few seconds apart shows which threads are stuck or consuming time, so they are the standard evidence for analysing slowness. The product offers administrators two supported routes. In the administrative console, the server's runtime page offers a Java Virtual Machine section with a Generate Thread Dump option, which signals the JVM to produce a javacore on the host. In wsadmin, the administrator can obtain the JVM MBean and call its dumpThreads operation, which triggers the same action and is easy to script, so that repeated dumps are taken at set intervals. Options C and E are correct.
The other choices are not thread dump tools. WebSphere Developer Tools, option A, are an Eclipse-based development environment used to build and test applications. The Job Manager, option B, coordinates administrative jobs across multiple environments, and the administrative agent, option D, manages unfederated nodes; neither is a diagnostic collector for thread dumps.
Whichever route is chosen, three to five dumps with an interval of about thirty seconds are normally collected, and these are then analysed with the IBM Thread and Monitor Dump Analyzer to identify blocked threads and contention. The javacore files are written to the profile's root directory.
In WebSphere Application Server ND, what is the function of the dynamic cache service policy?
Options:
Monitor network traffic
Define rules for caching responses
Encrypt user data during transmission
Load balancing
Answer:
BExplanation:
The dynamic cache service stores generated output such as servlet and JSP responses, command results, and web services data so that repeated requests can be served without regenerating the content. A dynamic cache policy, normally expressed in a cachespec.xml file, supplies the rules that make this work. It identifies which servlets, JSPs, or commands are cacheable, defines the cache-id elements that build the key for each entry, sets timeouts and priorities, and specifies the dependency IDs and invalidation rules that remove entries when underlying data changes. In short, the policy defines the rules for caching responses, as option B states.
The other options describe unrelated functions. Option A, monitoring network traffic, belongs to network analysis or request-metrics tooling, not to the cache. Option C, encrypting user data in transit, is the role of SSL/TLS configuration. Option D, load balancing, is performed by the web server plug-in, the on demand router, or workload management; the dynamic cache can replicate or share entries between servers through the data replication service, but that is cache coherence, not request distribution.
Well-designed cache policies reduce CPU use and response times for read-heavy content, and the dynamic cache monitor application can be used afterwards to confirm hit ratios and evictions.
An EJB client application received a java.net.ConnectException: Connection timed out error while making remote EJB calls. The EJBs on the remote server were found to be slow because of heavy client traffic. Which client-side ORB custom property can be tuned to prevent the error and give the server additional time to complete the client request?
Options:
com.ibm.ws.orb.SSLHandshakeTimeout
com.ibm.CORBA.ConnectTimeout
com.ibm.CORBA.MaxOpenConnections
com.ibm.CORBA.RequestTimeout
Answer:
DExplanation:
A java.net.ConnectException reporting a timeout during a remote EJB call needs careful reading, because the ORB has several timeout properties and each one governs a different stage. A client-side property that gives a busy server more time to complete the client request is com.ibm.CORBA.RequestTimeout. It defines the number of seconds the client ORB waits for a response to a request before it gives up, so increasing it allows slow server-side processing to finish before the client reports a failure. Option D is the property intended for this circumstance.
The other properties do not match the situation. com.ibm.CORBA.ConnectTimeout, option B, controls the time allowed to establish the socket connection to the server, which is before any request is processed. com.ibm.ws.orb.SSLHandshakeTimeout, option A, limits the time for the SSL handshake and concerns only secured connections. com.ibm.CORBA.MaxOpenConnections, option C, sets the size of the connection table, so it governs how many connections are cached, not how long requests are given.
Raising the request timeout hides the symptom rather than correcting the cause. Because the server is slow under heavy client traffic, administrators should also consider tuning the ORB thread pool, adding cluster members, or reducing the work performed per call, with the timeout adjusted as a temporary measure.
Following an upgrade to WebSphere Application Server ND 9.0.5, a JMS application that uses an indirect JNDI lookup cannot connect to the MQ Queue Manager and receives an MQRC_NOT_AUTHORIZED exception.
Which Queue Connection Factory property can be set to fix the error?
Options:
Component-managed authentication alias
Container-managed authentication alias
XA recovery alias
username and password
Answer:
BExplanation:
An indirect JNDI lookup in a JMS application resolves the queue connection factory through a JNDI reference, typically declared as a resource reference in the application's deployment descriptor. In that configuration, the resource reference's authentication type determines which credentials are used at the time of connection. When the reference specifies container authentication, the application server supplies the credentials, taken from the container-managed authentication alias on the connection factory. If no valid alias is set, the connection to the queue manager is attempted without suitable credentials, and a current IBM MQ queue manager responds with MQRC_NOT_AUTHORIZED. Setting the container-managed authentication alias, option B, therefore resolves the error.
The component-managed authentication alias, option A, applies when the application itself requests the credentials, for example by passing an alias in code, so it would not be used for a container-authenticated reference. The XA recovery alias, option C, is used by the transaction service when it reconnects to resources during recovery and does not govern normal application connections. Option D, specifying a plain user name and password, is not the recommended route, and a defined alias keeps credentials encrypted and administered centrally.
The need for explicit credentials following the upgrade is consistent with the stricter security defaults of recent IBM MQ releases, which require authenticated access, and the queue manager's authority records must also grant the alias's user the right to connect.
What occurs when an application running on WebSphere Application Server is updated?
Options:
The application continues to run without any interruption.
The application is updated but needs to be redeployed manually.
The application is stopped, updated, and restarted automatically.
The application is stopped and needs to be started manually.
Answer:
CExplanation:
When an administrator updates an enterprise application that is installed on a running server, the product manages the replacement itself. The update replaces the application files in the configuration repository, the changes are synchronised to the nodes, and each affected server then applies them. Where the server has to restart the application to load the new version, it stops the application, replaces the files, and starts it again without administrator action. Option C describes that sequence.
The other options misdescribe the behaviour. Option A, no interruption, applies only when the change can be handled through fine-grained operations and the application does not have to be restarted, and it does not describe the general case; users can still experience a brief outage or a lost session when classes are reloaded. Option B suggests that a manual redeploy is required, which is not the case, since the update is itself the deployment step. Option D is incorrect because an automatic restart takes place, and the administrator is not required to start the application by hand.
Administrators concerned with availability use a clustered topology and a rolling update, taking members out of service in sequence, so that the application remains available while each member is updated. Session persistence or replication keeps in-flight sessions from being lost during the restarts.
Which statement correctly describes the role of WebSphere Application Server Deployment Manager?
Options:
It cannot manage all elements in a WebSphere Application Server environment across distributed cells.
It can be deployed multiple times into a WebSphere cell to achieve high availability for administration.
It is a regular server which can host next to the WebSphere administrative console also business applications.
It has a master configuration repository which contains for all servers in the cell the deployed application EARs.
Answer:
DExplanation:
The deployment manager is the central administrative server of a Network Deployment cell. Its master configuration repository holds the configuration documents for every node and server in the cell, and that includes the application enterprise archives that have been installed. Each node agent synchronises its node's copy from this master. Option D describes that structure accurately.
Each remaining statement conflicts with the architecture. Option A claims that the deployment manager cannot manage all elements across cells; its authority covers the whole cell, though it does not span separate cells unless they are linked through a job manager or similar facility, so as worded the statement misleads. Option B suggests that the deployment manager can be deployed multiple times in one cell for availability. A cell has a single active deployment manager, and availability is addressed through a high availability configuration with standby instances, or by relying on the fact that running servers continue without it, which is a different matter from multiple deployments. Option C describes the deployment manager as an ordinary server that hosts business applications; it is a dedicated management process hosting the administrative console and services, and applications are installed on application servers instead.
For that reason, the master repository should be backed up regularly with backupConfig, since it is the authoritative source of cell configuration.
An administrator attempted to install an interim fix with Installation Manager, but the installation failed with this error: CRIMA1228E ERROR: Cannot find profile: null.
Investigation showed that the Installation Manager agent data location was set to a location other than the default. Which parameter must be provided to the imcl install command to set the correct agent data location and install the interim fix successfully?
Options:
–appdataLocation
–shareddataLocation
–agentdataLocation
–dataLocation
Answer:
DExplanation:
Installation Manager keeps its record of installed products and its working state in an agent data location. If the installation was performed with a non-default data location, any later operation, such as installing an interim fix, has to be pointed at the same place, otherwise Installation Manager looks at the default registry, cannot find the installation, and reports an error such as "Cannot find profile: null". The parameter that tells imcl which data location to use is -dataLocation, so option D is correct. The command might look like imcl install with the fix identifier, the -installationDirectory option, the -repositories option, and -dataLocation followed by the path used originally.
The other parameters are not imcl options. -appdataLocation and -agentdataLocation are plausible labels, but they do not exist as arguments. The -sharedResourcesDirectory option governs the shared resources directory, which is a different concept from the agent data location, and the name shareddataLocation in option B is not used.
Because the same location must be used consistently, administrators who use non-default data locations should record the value in their procedures. The imcl listInstalledPackages command with -dataLocation can also be used to confirm that the registry in that location holds the installation before the fix is applied.
In WebSphere Application Server, which approach should be used to implement an outbound SSL connection in an application?
Options:
Programmatic selection
Scope selection
Dynamic selection
Direct selection
Answer:
AExplanation:
WebSphere Application Server supports four ways of choosing the SSL configuration for an outbound connection: scope selection, direct selection, dynamic selection, and programmatic selection. Scope selection relies on the management-scope hierarchy, so the configuration defined at the most specific applicable scope is used. Direct selection names an SSL configuration for a particular endpoint. Dynamic selection maps outbound protocol, host, and port information to a configuration through the dynamic outbound selection mechanism. Programmatic selection is the application-level method, and it is the correct answer when the question concerns code that opens an outbound SSL connection.
With programmatic selection, application code calls the com.ibm.websphere.ssl.JSSEHelper API, for instance to set an SSL alias or a set of SSL properties on the running thread before the connection is made. The settings apply to outbound connections made on that thread, and the helper allows the properties to be cleared once the call completes. Because the application states its requirement explicitly at run time, this approach carries the highest precedence of the four, overriding whatever the administrator defined through scope, direct, or dynamic selection.
The remaining options describe administrator-side configuration rather than something an application implements, so none of them answers a question about application-level implementation.
An administrator wants to use the addNode command to federate an application server installation into a cell. They use the --includeapps option to bring over the applications from the node. One application on that node is the default application, which is already installed on another server in the cell.
What is the outcome?
Options:
As the application already exists in the cell, the default application will not be installed.
The two nodes will each have their own version of the default application installed.
Applications that are shipped with WebSphere Application Server are ignored when running the addNode command.
As the binaries of the default application are identical, the application will be merged.
Answer:
AExplanation:
The addNode command federates a stand-alone application server node into a cell, and its -includeapps option brings the node's installed applications into the cell's master repository. The default application, supplied with the product, is a sample application that is commonly present on every base server. When the cell already contains an application with the same name, installed through another node, the command does not install it again. The existing application is retained and the duplicate from the new node is skipped, with a message in the addNode log noting that it was not installed because an application of that name already exists. Option A is correct.
Option B is wrong because two applications with the same name cannot coexist in a cell, since application names must be unique. Option C is wrong because the command does not ignore the product's shipped applications as a class of its own; the outcome results from the name conflict, and applications with unique names would be included. Option D is wrong because no merging of applications takes place, whatever the similarity of their binaries.
An administrator who wants the applications of a node preserved should confirm names are unique before the federation. If the application that was skipped needs to run on the new node as well, it can be mapped to the node's server afterwards, through the console's module mapping, or by reinstalling it with that target added.
An administrator has deployed several enterprise applications in WebSphere Application Server ND. How can the administrator configure the applications to start in a particular order?
Options:
WebSphere does not support ordered starting of applications.
Configure the Launch application before server completes startup parameter.
The applications are started in the order that they are defined.
Configure the Startup order parameter.
Answer:
DExplanation:
Applications deployed to an application server are started during server startup, and the product provides a setting to control the order. On the application's configuration page in the console, and as an attribute in wsadmin, there is a Startup order parameter, which accepts an integer. Applications with lower values start before those with higher values, so an administrator can start a shared service application before the applications that depend on it. Option D is correct.
Option A is wrong because the ordering is supported. Option C is wrong because the applications are not started in the order in which they were defined or installed; without ordering values, the sequence is not something that can be relied on. Option B concerns a different parameter, "Launch application before server completes startup", which determines whether the server waits for the application to start before it declares itself started and accepts requests. That is related to startup behaviour but does not set the order among applications.
Administrators typically combine the two settings: the startup order sets the sequence, and the launch-before-completion option makes sure a critical application is fully up before the server opens for traffic. The values should be checked after changes, since the product starts applications in parallel by default when ordering is not specified, and the server log records the start messages for confirmation.
An administrator is using the default load balancing in plugin-cfg.xml with three cluster members in the cluster group. They observe that one cluster member receives more requests than its configured LoadBalanceWeight.
How can they investigate and resolve this issue?
Options:
Set LogLevel=Trace in plugin-cfg.xml and open a case and investigate the issue
Set LogLevel=Stats in plugin-cfg.xml, review the stats and investigate for session-affinity-requests.
Set LogLevel=Stats in plugin-cfg.xml, review the stats and investigate distribution of request load balancing correctly.
Set LogLevel=Stats in plugin-cfg.xml, review the stats and investigate for connectivity issues to backend servers.
Answer:
BExplanation:
The plug-in distributes requests among cluster members according to the configured weights, using Round Robin by default, but weights apply only to requests that have no existing session affinity. A request that carries a session cookie identifying a particular cluster member is routed directly to that member, bypassing the weight calculation. Consequently, if many users already hold sessions on one member, that member can serve more requests than its LoadBalanceWeight suggests, and nothing is malfunctioning in the weighting.
The way to confirm this is to raise the plug-in log level to Stats in plugin-cfg.xml. At that level the plug-in records, for each server, the number of affinity requests and non-affinity requests, along with the current weight and in-flight counts. By reading the statistics, the administrator can see whether the surplus load on the busy member consists of session-affinity requests, which supports option B. Trace, as proposed in option A, produces extremely verbose output and is intended for support-guided problem determination, not for a first look at distribution. Options C and D point to causes, namely incorrect balancing and backend connectivity, that the statistics would reveal only if affinity were ruled out.
If affinity explains the imbalance, the remedies include reducing session lifetime or using session replication so requests are not bound to one member.
Which memory-to-memory session-persistence configuration should be used to minimize session-data loss during failover?
Options:
Use more than one session replica to avoid single point of failure.
Peer-to-peer replication and set GetDWLMTable=true in plugin-cfg.xml
Server replication and set GetDWLMTable=false in plugin-cfg.xml
Client replication mode and set GetDWLMTable=true in plugin-cfg.xml
Answer:
AExplanation:
Memory-to-memory session persistence uses the data replication service to copy session state between servers, so sessions survive the failure of one server without a database. The risk to avoid is concentrating the only copy of a session in a single place. Configuring more than one session replica means each session's data exists in at least two other locations, so a failover can still find the session even if a replica is lost at the same time. Option A states this principle and describes the configuration that minimises data loss.
The options mentioning GetDWLMTable are less suitable. GetDWLMTable is a plug-in setting that makes the plug-in retrieve dynamic workload management table data from the server, which concerns routing information in the Intelligent Management environment and does not govern how many copies of the session data are kept. Peer-to-peer replication, option B, copies sessions between all members of a replication domain, and it is a valid mode, but the question asks about minimising loss, which depends on the number of replicas. Server replication and client replication, options C and D, specify where the replicas are held, with different trade-offs, and the GetDWLMTable setting alone does not reduce the risk.
Administrators should size the replication domain to the number of replicas chosen, as additional copies increase network traffic and memory usage.
Which two class loader policy options are valid in WebSphere Application Server ND?
Choose two
Options:
Multiple
Sequential
Single
Compact
Ordered
Answer:
A, CExplanation:
A class loader policy in WebSphere Application Server controls how many application class loaders are created for the applications on a server. The product recognises two values, Multiple and Single, so options A and C are correct. With the Multiple policy, each application receives its own class loader, which isolates applications from one another and allows each to carry its own versions of libraries without conflict. With the Single policy, one class loader is shared by all applications on that server, so classes are visible across applications. That reduces memory consumption in some cases but removes the isolation, and a library version required by one application becomes visible to all of them.
The remaining options are not defined by the product. Sequential, Compact, and Ordered do not describe a class loader policy. The term "ordered" might be confused with the class loading order setting, which is a separate attribute choosing between parent first and parent last delegation; it is not a policy value for application class loaders.
Administrators set the policy on the application server's configuration, and it works together with the class loading mode, which determines the search order. Most deployments retain Multiple because isolation prevents version collisions between applications that share a server.
For security auditing events to function correctly, which options must be enabled in WebSphere Application Server ND?
Options:
Enable security subsystem and Java 2 security.
Enable security subsystem and global security.
Enable global security and auditable events.
Enable global security and application security.
Answer:
BExplanation:
Security auditing records events that relate to authentication, authorisation, and administrative actions, so that an organisation can establish accountability and detect misuse. The audit function is part of the security subsystem and depends on it being active. Two prerequisites follow from that arrangement: the administrative security, which is global security, has to be turned on, and the security auditing subsystem itself has to be enabled. In the product's terminology these are the security subsystem and global security, and option B names them together.
Option A is incorrect because Java 2 security is a separate policy mechanism governing code access to resources and is not a prerequisite for auditing. Option C introduces auditable events, which are the event types that are selected for recording once auditing is functioning; selecting them is part of audit policy configuration and not a precondition for enabling it. Option D uses application security, which controls whether security applies to applications, and, although it commonly accompanies global security, it is not what auditing requires.
After enabling the subsystem, administrators configure the audit event types, the audit filters, and the audit service provider, including the binary log provider with signing and encryption where tamper resistance is needed. They also need an auditor role assigned to review and manage the audit records.
Which statement about Tivoli Performance Viewer's logging feature is correct?
Options:
Once enabled, logging will always configure until it is manually stopped.
It monitors the performance activity of all servers on a node.
Log files are always written in text format.
If the Maximum Number of Historical Files option is specified, logging will stop once that limit is reached.
Answer:
BExplanation:
Tivoli Performance Viewer, available within the administrative console, displays PMI data for servers and can record it to logs for later review. Its logging feature works at the level of the node: the viewer retrieves performance data from every server on the node that is selected, and records it, which matches option B.
The other statements misdescribe the feature. Logging does not continue indefinitely once started, so option A is wrong. It operates for a set duration, which the administrator specifies, and it ceases once that duration elapses unless it is stopped earlier. Option C is wrong because the logs can be written either as binary files or as XML, so they are not always text. Option D is wrong because the Maximum Number of Historical Files setting controls the retention of older log files: when the limit is reached, the oldest files are removed to make way for new ones, and logging goes on instead of terminating.
These characteristics shape how the viewer is best used. Short, targeted recording periods are appropriate for diagnosing a particular problem, and the saved logs can be reloaded in the viewer for analysis away from the live system. For long-term trend monitoring, administrators generally rely on external tooling that polls PMI data continuously.
Which WebSphere application server directory should not be used to store non-default XML or XML backup files?
Options:
profile_root/temp
profile_root/config
profile_root/wstemp
profile_root/bin
Answer:
BExplanation:
A profile's directory contains areas with different purposes, and the product treats some of them as private, because their contents are overwritten or removed by the product's own processes. The config directory is the master configuration repository for the profile, or for the node's local copy, and the product manages its structure carefully. Administrators are warned not to place non-default XML files or XML backups there. Stray XML documents can be mistaken by the repository and synchronisation mechanisms for configuration documents, which results in errors during synchronisation or when the configuration is loaded, and a backup copy of a real document may even be read in place of the intended one. Option B is the right answer.
The other directories are less sensitive. The temp and wstemp directories, options A and C, are used for temporary files and for working copies of configuration during administrative sessions, so, although they are not designed for permanent storage, they do not take part in the repository itself. The bin directory, option D, holds the profile's scripts and commands, and files placed there do not affect the repository.
If administrators need to keep copies of configuration files, a location outside the profile's config directory is appropriate, or the backupConfig command can be used, which produces a complete archive and avoids hand-made copies altogether.
Within a migration report, under which category are deprecated APIs that do not affect most applications labeled?
Options:
Fatal
Severe
Recommendations
Warnings
Answer:
CExplanation:
Application migration reports in the administrative console classify each finding by severity, and the categories are shown with distinct icons on the enterprise application collection page. Severe issues identify APIs that are unavailable on the target runtime, or behavioural changes that can break the application. Warning issues identify behavioural changes that might break the application and that deserve evaluation. Recommendations are informational findings: they cover deprecated APIs or minor behavioural changes that do not affect most applications. Option C is therefore correct.
Option A, Fatal, is not a category used by the migration report, so it can be dismissed on terminology alone. Option B, Severe, is the opposite end of the scale and is reserved for items that must be resolved before the application can run correctly on the target. Option D, Warnings, applies to changes that could break an application depending on how it uses the affected behaviour; those findings call for review rather than being merely advisory.
In practice, a reviewer should work through Severe items first, assess each Warning against actual application usage, and treat Recommendations as optional clean-up that reduces future migration effort. Recommendations alone should not block a move to the target environment, which is why they are labelled informational rather than as a defect.
What is the proper sequence for setting up LTPA SSO between two WebSphere cells?
Options:
Export the LTPA key from CellA and then import the LTPA key to CellB
Export the LTPA key and then import the LTPA key to a text file.
Generate the LTPA key from CellA, export CellB, and then import the LTPA key to CellA.
Export the LTPA key from CellB and then export the LTPA key from CellA.
Answer:
AExplanation:
Lightweight Third Party Authentication tokens are encrypted and signed with keys held in each cell's configuration. A token generated in one cell can only be accepted by another cell if both cells share the same LTPA keys, along with the same password and a compatible realm configuration. Single sign-on between two cells is therefore set up by taking the keys from one cell and placing them in the other. The sequence is to export the LTPA key from the first cell to a file, using the console's LTPA page or the exportLTPAKeys wsadmin task, and then to import that file into the second cell. Option A describes this: export from Cell A and import to Cell B.
The other sequences are not workable. Option B proposes importing the key to a text file, which is not an import into a cell and so does not share the key. Option C generates a key in Cell A, exports from Cell B, and imports to Cell A, which mixes the cells' roles and ends with Cell B's key unchanged, so the cells do not end up holding the same key. Option D exports from both cells, and neither cell receives the other's key.
After importing, the administrator saves the configuration, and generally restarts servers so that the new keys take effect. The user registries of the cells should resolve users to the same identities, and the domain name for the SSO cookie should be common to both.
When PMI data is collected to reduce monitoring overhead, updates to CountStatistic, AverageStatistic, and TimeStatistic are not synchronized. If necessary, how can updates to every statistic type be synchronized?
Options:
By writing a JMX client to offload the collection of the performance statistics from the cell.
By using the ‘Custom’ option for the statistic set.
By selecting the ‘Use sequential update’ check box.
By enabling the ‘All’ option for the statistic set.
Answer:
CExplanation:
The Performance Monitoring Infrastructure collects counters from server components, and it is designed to cause as little overhead as possible. To that end, updates to the three basic statistic types, CountStatistic, AverageStatistic, and TimeStatistic, are not synchronised by default. Without synchronisation, two threads that update the same counter at once might overwrite each other, so the reported values can be slightly inaccurate, but the cost of locking is avoided. Where accuracy matters more than overhead, the administrator can turn on synchronisation for every statistic type. In the administrative console, this is done in the PMI settings for the server by selecting the Use sequential update check box. Option C is correct.
The other approaches do not alter how counters are updated. Writing a JMX client, option A, changes how the data is retrieved and leaves the collection untouched. The Custom option, option B, selects which counters are enabled, and the All option, option D, enables every counter in the set; both govern the volume of data and are unrelated to update synchronisation. Enabling all counters would, in fact, increase the overhead.
Because sequential update increases the cost of monitoring, it should be applied only when slight inaccuracies are unacceptable. In most tuning exercises the default's accuracy is adequate, since trends rather than exact values drive decisions.
Which two commands can be used to modify configurations in WebSphere Application Server ND?
Choose two
Options:
ws_ant.sh
wasadmin.sh
manageprofiles.sh
WsAnt.sh
wsadmin.sh
Answer:
A, EExplanation:
Configuration of a Network Deployment cell is modified through the administrative interfaces, and two of the listed commands can do it. wsadmin.sh is the scripting client. It connects to the deployment manager and, through objects such as AdminConfig, AdminTask, and AdminApp, creates, changes, and removes configuration documents, which is the primary scripted method for configuration changes. ws_ant.sh starts Apache Ant with the WebSphere-supplied environment and tasks. The product ships Ant tasks, including the wsadmin task, that run administrative scripts, install applications, and start or stop servers, so a build script launched with ws_ant.sh can change cell configuration in an automated manner. The correct selections are A and E.
The other options do not fit. manageprofiles.sh manages the lifecycle of profiles: creating, deleting, augmenting, backing up, and restoring them. It operates on profile structure on the local machine and is not the tool used to change configuration of servers, resources, or applications in a running cell. WsAnt.sh is not a script shipped with the product, and "wasadmin.sh" is a misspelling of the scripting client and does not exist.
When automation is required, administrators typically choose wsadmin with Jython for fine-grained control and ws_ant.sh when administrative steps must be embedded in a larger build or deployment pipeline.
In the WebSphere Application Server ND administrative console, which security role is mapped to special subjects within an enterprise application that uses external identity providers?
Options:
All authenticated in the trusted realm
All authenticated in the application realm
None
Everyone
Answer:
AExplanation:
Application security roles in an enterprise application are mapped to users, groups, or special subjects, and the special subjects are a convenient way to grant a role to broad categories of caller without naming individuals. The product supplies two principal special subjects: All Authenticated, in the application's realm or in the trusted realms, and Everyone. When the application uses external identity providers, such as when authentication is carried out by a third-party provider through a trust association or by a token from another realm, the callers belong to a realm other than the application's own. The special subject that covers any authenticated user in the trusted realms is "All authenticated in the trusted realm", which is option A.
The application-realm variant, option B, includes only users authenticated in the application's own realm, which would exclude callers who arrive from the external provider. Everyone, option D, grants the role to any caller including unauthenticated ones, which is a much weaker control than the question implies. None, option C, is not a mapping that would grant access.
When mapping roles in the administrative console during installation, or later through the Security role to user/group mapping page, administrators should prefer the narrowest subject that serves the purpose, and test with a user from the external provider to confirm the expected access.
Which supported client type uses the Client Container in the runtime environment to make system services—such as security, transactions, naming, and database access—easier for client applications to access?
Options:
Java thin client
Applet client
ActiveX to EnterpriseJavaBeans Bridge
Java EE client
Answer:
DExplanation:
WebSphere Application Server distinguishes several client types according to the runtime support they receive. A Java EE client is an application client component packaged as an application client module and run inside the application client container. The container supplies the client-side runtime and gives the client simplified access to system services, including security, transactions, JNDI naming, and, through configured resource references, data access. Declared resource and EJB references are resolved by the container, so the client does not have to code the lookup and configuration logic itself. That is the characteristic the question describes, and it identifies D.
The remaining client types do not use a client container. A Java thin client is a standalone Java SE program that uses the thin client runtime libraries and must handle naming and security itself. An applet client runs inside a browser and relies on the browser's Java plug-in, with the limitations that environment imposes. The ActiveX to EnterpriseJavaBeans Bridge lets non-Java ActiveX clients, such as those written for Windows environments, reach enterprise beans; it is a bridging technology rather than a container-managed client type.
Choosing between these types is largely a decision about how much infrastructure the client should receive from the platform. The Java EE client gives the greatest degree of container-provided function.