A. W1scontrol.sh (.cmd in Windows)

B. startNodeManager.sh (.cmd in Windows)

C. startNM.sh (.cmd in Windows)

D. Wisifconfig.sh (.cmd in Windows)

A. Verify the Target attribute of the data source.

B. Verify the Targets attribute of the application.

C. Verify the target server's JNDI tree in the console.

D. Verify the Dependencies attribute of the data source.

E. Launch the JDBCDiagnostics utility.

A. 3.
Install WebLogic Server.
4.Copy the JAR file from the Administration Server computer.
5.Run the unpack command on the JAR file.
6.In the new domain folder created by the command, start managed1 by using the Logic. sh script (. cmd in Windows), which is found under its bin directory.

B. 3.
Install WebLogic Server.
4.Copy the JAR file from the Administration Server computer.
5.Run the unpack command on the JAR file.
6.In the new domain folder created by the command, startmanaged1 by using the startManagedWeblogic.sh script (. cmd in Windows), which is found under its bin directory.

C. 3.
Copy the JAR file from the Administration Server computer.
4.Run the unpack command on the JAR file.
5.In the new domain folder created by the command, start managed: by using the startManagedWebLogic. sh script (. cmd in Windows), which is found under its bin directory

D. 3.
Install WebLogic Server.
4.Copy the JAR file from the Administration Server computer.
5.Run the unpack command on the JAR file.
6.In the administration console, under the Control tab, select managed1 and click the Start button.

A. It starts the managed server named server1, which is running at 192.168.1.102.8001.

B. It starts the Managed Server named server1 whose Administration Server is running at 192.168.1.102:8001.

C. It starts the managed server named server1 whose Node Manager is running at 192.168.1.102.8001.

D. It starts the administration server named server1, which is running at 192.168.1.102.8001.

A. The security realm for a domain is optional.

B. All instances of WebLogic Server must be defined within a domain.

C. A domain maybe created by using the Configuration Wizard.

D. A domain may be set up in either Production Mode Production Mode or Development Mode.

E. The domain configuration is stored in Oracle database by default.

F. Any instance of WebLogic Server may update the domain configuration

A. creating a new Managed Server

B. changing console preferences

C. deploying an application

D. monitoring the health of a server

E. creating a new JMS Server

F. enabling the Administrator Port

G. adding a new user to the default authentication provider

A. A JMS Connection Factory's Default Priority and Default Time-to-Live attribute cannot be modified after the Connection Factory is created.

B. A JMS Connection factory can be created as a system module resource within the administration console.

C. A Connection Factory can be targeted to only one WebLogic Server.

D. A default JMS Connection Factory exists and is named weblogic.jms.connections

A. You must explicitly identify which servers belong to the cluster.

B. When you create a cluster, you must add at least one server to it.

C. The administration server is automatically added to a new cluster.

D. Only managed servers can be in a cluster.

A. This change may be made only through the Administration Server's secure port.

B. Only the Administration Server must be restarted.

C. Auto-deployment will no longer be available for this domain.

D. All running servers must be restarted.

E. If you decide to go back to Development Mode, uncheck Production Mode in the administrate console.