Timeout Seconds

Abandon Timeout Seconds

Before Completion Iteration Limit

Checkpoint Interval Seconds

Unregister Resource Grace Period

Proxy plug-in or hardware load balancer

Configured or dynamic cluster

Replicated or persistent HTTP sessions

Unicast or multicast communication

Single or multiple domains

A machine can be the proxy to a cluster.

A machine definition is required to configure the Node Manager.

To reference an instance of WebLogic Server, you must know its machine and port.

A machine is a required organizational unit. A domain contains machines and machines contain servers.

WebLogic Server uses server machine assignments to help it choose servers in a cluster on which to replicate session state.

A machine’s Cluster Weight attribute may be used by load balancers to help them determine how often to send requests to servers assigned to that machine.

Run the jstat tool in your JDK.

Write and run a custom WLST script.

Use the application’s Monitoring tab in the Administration Console.

Use the Monitoring Dashboard in the Administration Console.

Use the Cloud Control page in the Administration Console.

The pmap command lists all processes running with their associated port number.

The UNIX lsof command can report information on the process that is listening at a particular IP and port on the local machine.

netstat, which is available on Windows and Linux/UNIX, can report on the process bound to this IP and port.

pstat will report detailed runtime statistics on any process currently listening at this IP and port.

The Linux port watching tool PortInfo can raise an alert anytime a process attempts, succeeds, or fails to connect to a specific IP and port. It can also be used to identify if a port is being used by a java process.

Data sources are targeted to a domain.

Data sources are bound in the JNDI tree of a server.

Data sources are based on the JMS specification.

A data source contains a connection pool.

A domain requires at least one data source.

All servers that will be part of the cluster must be created before the cluster is created.

You must pick the cluster messaging mode.

Even though you create a non-dynamic cluster, you can change it to a dynamic cluster later.

Once the cluster is created, you cannot change its messaging mode.

The administration console does not provide a way to manually migrate singleton services. It must be set up to be done automatically or by using WLST.

Create a Node Manager and enroll it with the domain

Create a domain using a custom template

Assign virtual IP addresses to all servers

Distribute domain files across multiple machines

Create a dynamic cluster of five servers

Create tables in the data store.

Execute SQL scripts in WebLogic server’s server/lib directory.

Populate the database tables with external LDAP users.

Test the connection to a back-end database.

Allocate tablespace for the data store.

You cannot do this from the admin console. You must use WLST or a JVM command- line tool.

In the Monitoring > Performance tab, click Dump Thread Stacks.

In the Monitoring > Threads tab, click Dump Thread Stacks.

In the Monitoring > Performance tab, click Garbage Collect.

In the Monitoring > Performance tab, click GC.

Server startup fails

The server binds to localhost

The server prompts for an address when it is started the first time

The server attempts to bind to all network interfaces on the host OS

You can upgrade any domain that was created using WLS 9.2 and above

The Reconfiguration Wizard allows you to change the domain mode

The Reconfiguration Wizard allows you to select a different Java JDK

The Reconfiguration Wizard does not allow the reconfiguration of JDBC data sources

You can upgrade only a domain which is running WLS 10.3.x or later

name attribute for user objects

connection pool maximum size

base DN for group objects

realm name

host name and port

The proxy will pin a client to a specific server if a session cookie is created.

The proxy fails over to another server if a connection or request times out.

The proxy distributes requests to cluster members based on their CPU usage.

The proxy dynamically learns the latest locations of cluster members.

The proxy always uses SSL, regardless of the client’s protocol.

The proxy replicates session data to its backup proxy.

Add the option to the start script that allows servers to be started without credentials

Update the credentials in the boot identity file

Update the credentials in the start script

Create a boot identity username and password by using the administration console

The boot identity file does not exist. Create one.

Option A

Option B

Option C

Option D

Option E