Oracle 1z0-133 - Oracle WebLogic Server 12c: Administration I

Under the managed server's Services configuration select “JDBC” as the type for the transaction log store.

Under the managed server's Services configuration, select “Disable the Default Store”.

Create a non-XA data source in the domain for the database transaction log.

Create an XA data source in the domain for the database transaction log.

The Embedded LDAP can be accessed by an external LDAP viewer

The Embedded LDAP cannot be used in a production environment

The Embedded LDAP uses the file system to store WebLogic security provider data

The Embedded LDAP uses the database to store WebLogic security provider data

The Embedded LDAP can be used to store user, group, security roles and security policies for the WebLogic security providers

Timeout Seconds

Abandon Timeout Seconds

Before Completion Iteration Limit

Checkpoint Interval Seconds

Unregister Resource Grace Period

Average execution time

Session timeout

Current session count

High session count

Cookie domain

If you stop Node Manager, the managed servers it started will also stop.

You may kill the Node Manager process by using operating system commands.

Use the stopNodeManager.sh script so Node Manager stops gracefully.

Using the administration console, select the appropriate machine and click Stop.

The administration server goes into ADMIN mode if it can no longer communicate with Node Manager.

The managed servers that Node Manager started go into ADMIN mode if they can no longer communicate with Node Manager.

This is true because the domain files can be re-created with the pack and unpack utilities.

This is true (with an exception) because the domain files can be re-created with the pack and unpack utilities. The exception is if your security realm uses the embedded LDAP system. Which is not included in the JAR file created by the pack utility.

This is true (with an exception) because the domain files can be re-created with the pack and unpack utilities. The exception is for applications that are deployed to the managed server. Those files are not included in the JAR file created by the pack utility. If you back those up manually, then pack and unpack can be used.

This is not true. You need to back up the domain files on a machine on which only managed servers run by using operating system commands (such as tar or zip).

This is only possible if the application is deployed to a cluster. Cluster deployments allow current users to continue to use the previous version of an application

This is possible if the application is versioned by using the WebLogic Server feature called Production Redeployment.

This is not possible. When an application is redeployed, it replaces the old version and all users then access the new version

This is not possible. When an application is redeployed, all users continue to access the old version. Once all current users have exited the system, then all users from that point on access the new version

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.

Click the server ‘s Debug > Heap tab.

Click the server’s Debug > Health tab.

Click the server’s Monitoring > Health tab.

Click the server’s Monitoring > Threads tab.

Click the server ‘s Monitoring > Performance tab.

Messaging Mode

Cluster Address

Broadcast Channel

Replication Channel

Cluster Type