1. After changing the JNDI name of a datasource, what must be changed within an application using this datasource to keep them running correctly?
A. The reference to resource mappings.
B. The EJB references to match the new JNDI name.
C. The name of the JDBC provider to match the new datasorce name.
D. The datasources.xml file for the application.
-A
2. A security role has been mapped to the special group Everyone. What is the result of this action?
A. Every user defined for the group has access to the resource.
B. Everyone will be denied access to the resource.
C. Every user has access to the resource.
D. Anyone logged in has access to the resource.
Security role to user and group mapping
Use this page to map security roles to users. You can map roles to specific users, to specific groups, or to different categories.
To view this administrative console page, click Applications > Install New Application. While running the Application Installation Wizard, prompts display to help you map security roles to users or groups. To change role to user or group mappings for deployed applications, click Applications > Enterprise Application > deployed_application > Security roles to user/group mapping.
Everyone
Specifies to map roles to everyone. Mapping a role to everyone means that anyone can access resources protected by this role, and essentially, there is no security.
-D
3. A WAR file in an enterprise application has been changed. How can a system administrator update it on the server with a minimal amount of work?
A. Re-package the EAR file using Application Server Toolkit then use the "Update -> Full application" function on the administrative console.
B. Use the "Update -> Single file" function of the Administrative console to replace the WAR file.
C. Use the "Update -> Single module" of the Administrative console to replace the WAR file.
D. Use the "Update -> Partial application" of the Administrative console to replace the WAR file.
Single module
Under Update options, specifies to replace a module in or add a module to an installed application. The module can be a Web module (.war file), enterprise bean module (EJB .jar file), or resource adapter module (connector .rar file).
After selecting this option, specify whether the module is on a local or remote file system and the full path name of the module. The path provides the location of the updated module before installation. For information on Local file system and Remote file system, refer to the description of Full application above.
-C
If you select Update, you will be given with four options
Full Application
Single Module
Single File
Partial Application
Full Application :
Select this option to replace the enterprise archive (*.ear) file for an installed application. The uploaded enterprise archive replaces the existing installed application.
Single module
Select this option to update an existing module or to add a new module to the application. If the relative path to the module matches an existing path to a module in the installed application, the uploaded module replaces the existing module. If the relative path to the module does not exist in the installed application, the uploaded module is added to the application.
Single file
Select this option to update an existing file or to add a new file to the application. If the relative path to the file matches an existing path to a file in the installed application, the uploaded file replaces the existing file. If the relative path to the file does not exist in the installed application, the uploaded file is added to the application.
Partial application
Select this option to update or add several files to an application. Use a valid compressed file format such as .zip or .gzip. The compressed file is unzipped into the installed application directory. If the uploaded files exist in the application with the same paths and file names, the uploaded files replace the existing files. If the uploaded files do not exist, the files are added to the application. You can remove existing files from the installed application by specifying metadata in the compressed file.
4. While performing a node federation, the addNode operation failed. From the following list of options, what would MOST likely induce this failure?
A. The cell already exists
B. The cell's deployment manager is running before the addNode command was run
C. The name of the new node is not unique in the cell
D. The addNode did not specify to carry over the applications
-A
5.Cluster creation requires the system administrator to specify the weight for a cluster member. This weight is significant because it is used in the WebSphere WLM runtime by the:
A. Random scheduling algorithm
B. Round Robin scheduling algorithm
C. Both Random and Round Robin scheduling algorithm
D. Weighted Random algorithm
In the simplest case, the cluster contains only one server definition. In the case in which more than one server is defined, the plug-in will load balance across the defined servers using either a Round Robin or a Random algorithm. The default is Round Robin.
LoadBalanceWeight (zero or one attribute for each Server)
Specifies the weight associated with this server when the plug-in does weighted Round Robin load balancing. The starting value for a server can be any integer between 0 and 20. However, zero should be specified only for a server that is shut down.
The algorithm for this attribute decrements all weights within the server cluster until all weights reach zero. After the weight specified for a particular server reaches zero, no more requests are routed to that server until all servers in the cluster have a weight of zero. After all servers reach zero, the weights for all servers in the cluster are reset and the algorithm starts over.
When a server is shut down, it is recommended that you set the weight for that server to zero. The plug-in can then reset the weights of the servers that are still running, and maintain proper load balancing.
The answer for this is Weighted Round Robin
6. A new JDBC provider is being created in a cell in which the servers run on different operating systems. Which of the following scopes should be used?
A. Cluster scope
B. Server scope
C. Node scope
D. Cell scope
??
7. A system administrator is asked to help explain why a NameNotFoundException is happening while attempting to access an enterprise bean, data source, messaging resource, or other resource. What action would be the LEAST useful to do to explain the problem?
A. Browse the properties of the target object in the administrative console, and verify that the JNDI name it specifies matches the JNDI name the client is using.
B. Browse the properties of the target object in its deployment descriptor, and verify that the JNDI name it specifies matches the JNDI name the client is using.
C. Determine if the object being looked up resides on a server different from the one from which the initial context was obtained since, in this case, the fully qualified name must be used.
D. Use the showNameSpace utility to export the entire JNDI tree to determine if the desired resource is listed.
Incorrect lookup name
If you encounter a NameNotFoundException when trying to access an enterprise bean, data source, messaging resource, or other resource:
Determine the cause of the NameNotFoundException.
Browse the properties of the target object in the administrative console, and verify that the JNDI name it specifies matches the JNDI name the client is using.
If you are looking up an object that resides on a server different from the one from which the initial context was obtained, you must use the fully qualified name.
If access is from another server object such as a servlet accessing an enterprise bean and you are using the default context, not specifying the fully qualified JNDI name, you might get a NameNotFoundException if the object is hosted on a different server.
If access is from a standalone client, it might be that the object you are attempting access is on a server different from the server from which you obtained the initial context.
Use the fully-qualified JNDI name to correct the problem.
If the object is in a single server, the fully-qualified JNDI name is as follows:
cell/nodes/nodeName/servers/serverName/jndiName
Restriction: Objects are not supported in this release.
If the object is on a server cluster, the fully-qualified JNDI name is as follows:
cell/clusters/clusterName/jndiName
-A
