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

The administration console can be disabled.

The context path of the administration console may be changed.

If a domain is in Development Mode, the administration console no longer requires an administration-level user when logging in.

If a domain is in Production Mode, access to the administration console must be made through a secure port.

If the domain’s Administration Port is enabled, access to the administration console must be made only through that port.

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).

The weblogic user does not exist in iplanet.

The Administrators group does not exist in iplanet.

A domain must include the default authentication provider.

Iplanet is not a supported LDAP implementation.

LDAP providers cannot be included in the default security realm.

You need to look at the Events Data Archive. Server log files do not contain WL DF context IDs

You need to look at the Harvested Data Archive. Server log files do not contain WL DF context IDs.

You need to look at the domain log file. Only the domain log file contains WL DF context IDs.

You can search the server log file for the context ID. Any message that was written to the log IDs during that request will contain the context ID.

You need to translate the context ID into the corresponding transaction ID, which is the only ID in server log file entries.

Use a ${macro} in the server template’s listen address.

Assign each dynamic server a separate machine.

Create multiple server templates for the cluster.

Update the cluster’s listen address prefix.

Weblogic –application.xml

Weblogic.xml

Session.xml

Config.xml

Web.xml

Use the Configuration Wizard to clone the domain

Run the pack tool on the administration server’s machine

Transfer the installation certificate to the administration server’s machine

Transfer the managed server template to the new machine

Use the Administration Console to clone the administration server

Run the unpack tool on the new machine

Create one cluster.

Install Oracle HTTP Server.

Create one Coherence server.

Create four managed servers.

Assign three servers to a cluster.

Specify a proxy port for the administration server.

Messaging Mode

Cluster Address

Broadcast Channel

Replication Channel

Cluster Type

Required

Requisite

Sufficient

Optional

The minimum heap size for a 64-bit JVM is 64 Megabytes

For performance reasons, the minimum heap size and maximum heap size should be the same value

The parameter value was entered incorrectly. The correct value is: “-Xms32m –Xmx150m”

The parameter value was entered incorrectly. You must enter memory parameter values in Kilobytes

The parameter value was entered incorrectly. The correct value is: “-Xms:32meg – Xmx:150meg”

Each patch comes with a “read me” file containing installation instructions.

You can use OPatch to see which patches are currently applied to WebLogic Server.

OPatch is a GUI tool and requires the operating system to have a window manager.

OPatch requires a JDK to run.

After installing WLS, you download the OPatch utility from Oracle Support.

Each patch ZIP file comes with the OPatch utility.

managed1 host and port

Administration Server host and port

managed1 host and Administration port

Administration Server host and Administration port

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.

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

Uniform Distribution Request Class

Response Time Request Class

Max Throughput Request Class

Fair Share Request Class

Context Request Class