Correct Answer: AE

A: WebLogic Server instances in a cluster communicate with one another using two basic network technologies:

*

IP sockets, which are the conduits for peer-to-peer communication between clustered server instances.

*

IP unicast or multicast, which server instances use to broadcast availability of services and heartbeats that indicate continued availability.

E: In many deployments, clustered server instances reside within a single subnet, ensuring multicast messages are reliably transmitted. However, you may want to distribute a WebLogic Server cluster across multiple subnets in a Wide Area Network (WAN) to increase redundancy, or to distribute clustered server instances over a larger geographical area.

Reference: Using WebLogic Server Clusters, Communications In a Cluster http://docs.oracle.com/cd/E11035_01/wls100/cluster/features.html

Correct Answer: AE

A: Each connection in a data source has its own individual cache of prepared and callable statements used on the connection. However, you configure statement cache options per data source. That is, the statement cache for each connection in a data source uses the statement cache options specified for the data source, but each connection caches it's own statements.

E: When Test Connections On Reserve is enabled, when your application requests a connection from the data source, WebLogic Server tests the connection using the query specified in Test Table Name before giving the connection to the application.

Testing reserved connections can cause a delay in satisfying connection requests, but it makes sure that the connection is viable when the application gets the connection.

Reference: Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1, Configuring JDBC Data Sources http://docs.oracle.com/cd/E12839_01/web.1111/e13737/jdbc_datasources.htm#i1192665

Correct Answer: BE

B: The Administration Server uses the machine definition in conjunction with the Node Manager application to start remote WebLogic Server instances.

E: By default, WebLogic Server attempts to create session state replicas on a different machine than the one that hosts the primary session state. You can further control where secondary states are placed using replication groups. A replication group is a preferred list of clustered servers to be used for storing session state replicas. Using the WebLogic Server Console, you can define unique machine names that will host individual server instances. These machine names can be associated with new WebLogic Server instances to identify where the servers reside in your system. Machine names are generally used to indicate servers that run on the same machine.

Reference: Administration Console Online Help, Machines Reference: Failover and Replication in a Cluster

Correct Answer: AC

C: auto deployment is not allowed in production mode only development mode.

Note 1:

All servers in a domain run either in development mode or production mode. To configure all servers in a domain to run in production mode:

1.

If you have not already done so, in the Change Center of the Administration Console, click Lock and Edit .

In the left pane of the Console, under Domain Structure, select the domain name.

2.

Select Configuration > General and select the Production Mode check box.

3.

Click Save, and then, to activate these changes, in the Change Center, click Activate Changes.

4.

Shut down any servers that are currently running.

5.

Invoke the domain's startWebLogic script.

The Administration Server starts in the new mode.

6.

If the domain contains Managed Servers, start the Managed Servers.

Result

As each Managed Server starts, it refers to the mode of the Administration Server to determine its runtime mode.

Note 2: Once you have changed to production mode, whether by using a start command argument, the Console, or WLST, you cannot change back to development mode without restarting the server.

By default auto deployment is turned off in Production Mode (however it can be later turned on). Incorrect:

E: if you want to go back to development mode you must change the config.xml file and restart the admin server. The window shown below shows from

developemnt to production NOT production to development is allowed.

This is in development mode and you can change to production mode but in production mode this attribute states the word true.

Reference: Administration Console Online Help, Change to production mode

Correct Answer: D

Deployment Staging Mode: stage Behavior: The Administration Server first copies the deployment unit source files to the staging directories of target servers specified by the Staging Directory Name attribute.

The target servers then deploy using their local copy of the deployment files.

Note: The deployment staging mode determines how deployment files are made available to target servers that must deploy an application or standalone module. WebLogic Server provides three different options for staging files: stage mode, nostage mode, and external_stage mode. The following table describes the behavior and best practices for using the different deployment staging modes.

Reference: Overview of WebLogic Server Deployment, Staging Modes

Correct Answer: BC

When you deploy an application to a cluster target, WebLogic Server ensures that the deployment suc- cessfully deploys on all available members of the cluster

Reference: Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server, Deploying to a Cluster Target

Correct Answer: D

The following attributes are displayed in the exhibit:

Session Invalidation Interval (in seconds)

Session Timeout (in seconds)

debug-enabled

Maximum in-memory Sessions

These attributes are stored in the weblogic.xml file as the following elements:

invalidation-interval-sec

timeout-secs

debug-enabled

max-in-memory-sessions

Incorrect answers:

A: config.xml does not contain session related information.

The config.xml file consists of a series of XML elements. The Domain element is the top-level element, and all elements in the Domain are children of the Domain

element. The Domain element includes child elements, such as the Server, Cluster, and Application elements. These child elements may have children

themselves.

For example, the Server element includes the child elements WebServer, SSL and Log. The Application element includes the child elements EJBComponent and WebAppComponent. Each element has one or more configurable attributes. An attribute has a corresponding attribute in the configuration API. For example, the Server element has a ListenPort attribute, and likewise, the weblogic.management.configuration.ServerMBean class has a ListenPort attribute.

Reference: weblogic.xml Deployment Descriptor Elements

Correct Answer: BE

B:

Security policy for a JMS Queue (Resource Level).

When you define a security policy for an individual destination on a JMS server, you can protect all operations of the destination.

a.

Login into the Admin server console > Navigate to the Queue that needs to be secured.

b.

Click on the security tab > Policies sub tab.

You can see a small drop down list, which lists the set of the operations that can be protected.

c.

Click Add Conditions to add the policy conditions.

d.

From the predicate list, specify the policy conditions.

e.

Specify the role (the global created in E below) which needs to have the access permissions for the JMS Queue. Click Add > Finish.

E: Create a Global Role and assign the appropriate user accounts to it.

Note: There are two ways of securing the JMS resources.

1.

At the JMSModule level (Group level), where a single security policy is specified for a set of JMS resources.

2.

At the individual JMS resource level, which provides much more grained controlled over the operations that you want to secure.

Reference: SECURING WEBLOGIC JMS RESOURCES

Correct Answer: AD

A (not B): For any given WebLogic Server instance, you can override the default filter and create a log filter that causes a different set of messages to be written to

the domain log file.

Note:

To create and configure a log filter:

1.

If you have not already done so, in the Change Center of the Administration Console, click Lock and Edit (not B) (see Use the Change Center).

2.

In the left pane of the Console, select the name of the active domain in the Domain Structure panel.

3.

On the Configuration: Log Filters page, click New.

4.

On the Create a New Log Filter page, enter a value to identify the filter in the Name field.

5.

Click Finish.

The new log filter appears in the Log Filters table.

6.

To configure a filter expression, in the Log Filters table, click the log filter name.

7.

On the Configuration page, in the Filter Expression text box, enter criteria for qualifying messages.

A filter expression defines simple filtering rules to limit the volume of log messages written to a particular log destination.

See D) below.

8.

Click Save.

The filter and filter expression are listed in the Log Filters table.

D: Log Filter Configuration

Use this page to define a custom log filter to restrict the set of messages that one or more servers send to a message destination, such as the domain log,

standard out, server log file, or memory buffer of recent log events.

You can click Edit to type or paste in an expression directly, using WLDF Query Language syntax (see Related Topics, below); or you can click Add Expression to

construct an expression by choosing items from lists.

Once you create a filter, you cannot change its name. Instead, you must create a new filter under a different name.

Reference: Administration Console Online Help, Log Filter Configuration Reference: Administration Console Online Help, Create log filters

Correct Answer: D

-targetstarget_list (for the redeploy command) is not specified here. It is used to specify the targets on which to distribute, deploy, or redeploy the application or module.

If you do not specify a target list with the -deploy command, the target defaults to:

*

the Administration Server instance for new deployments (not the case here)

*

the application's current targets for deployed applications (the case in this scenario)

Note:

Syntax:

java [SSL Arguments] weblogic.Deployer [Connection Arguments] [User Credentials Arguments] COMMAND-NAME command-options

[Common Arguments]

Connection Arguments

The -adminurl value must specify the listen address and listen port of the Administration Server.

. The Administrator username. If you supply the -username option but you do -usernameusername

not supply a corresponding -password option, weblogic.Deployer prompts you for the password.

-redeploy.redeploys a running application or part of a running application.

-name deployment_name. Specifies the deployment name of a deployed application or module. The option can be omitted, in which case the name is taken from

the -source fileargument.

-name

Note: weblogic.Deployer is a Java-based deployment tool that provides a command-line interface to the WebLogic Server deployment API. weblogic.Deployer is

intended for administrators and developers who want to perform interactive, command-line based deployment operations.

Reference: Deploying Applications to WebLogic Server, weblogic.Deployer Command-Line Reference