1Z0-102 Online Practice Questions and Answers

Correct Answer: BD

Incorrect answers:

A: WebLogic JMS defines two default connection factories, which you can look up using the following JNDI names:

weblogic.jms.ConnectionFactory

weblogic.jms.XAConnectionFactory

C: Both Default Priority and Default Time-to-live can be changed:

Default Priority: This attribute is dynamic. It can be changed at any time. However, changing the value does not affect existing connections. It only affects new

connections made with this connection factory.

Default Time-to-Live:

This attribute is dynamic. It can be changed at any time. However, changing the value does not affect existing connections. It only affects new connections made

with this connection factory.

Reference: Programming WebLogic JMS, Understanding WebLogic JMS

Correct Answer: B

JMS Configuration option ' Messages Threshold High':

The upper threshold (number of messages stored in this JMS server) that triggers flow control and logging events. A value of -1 disables the events for this JMS

server. If the number of messages exceeds this threshold, the triggered events are:

Log Messages

-A message is logged on the server indicating a high threshold condition. Flow Control

-If flow control is enabled, the JMS server becomes armed and instructs producers to begin decreasing their message flow.

Reference: Administration Console Online Help, JMS Server: Configuration: Thresholds and Quotas

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: D

The server instance for which you configure the listen address does not need to be running. If it is running, you must restart it after you complete these steps. Reference: Administration Console Online Help, Configuring the Listen Address from the Administration Console

Correct Answer: ACE

A: The embedded LDAP server contains user, group, group membership, security role, security policy, and credential map information.

C: The credential (usually a password) used to connect to the embedded LDAP server. If this password has not been set, WebLogic Server generates a password

at startup, initializes the attribute, and saves the configuration to the config.xml file. If you want to connect to the embedded LDAP server using an external LDAP

browser and the embedded LDAP administrator account (cn=Admin), change this attribute from the generated value.

E: You can use either the WebLogic Auditing provider or a custom Auditing provider in a security realm. Although an Auditing provider is configured per security

realm, each server writes auditing data to its own log file in the server directory. By default, all auditing information recorded by the WebLogic Auditing provider is

saved in the following file:

WL_HOME\yourdomain\yourserver\DefaultAuditRecorder.log.

By writing a custom Auditing provider, however, you can send the records containing audit information to any one of various output repositories, such as an LDAP

server, database, or a simple file.

Incorrect answers:

D: The embedded LDAP server is the default security provider database for the WebLogic Authentication, Authorization, Credential Mapping and Role Mapping providers.

Incorrect answers:

B: The WebLogic Authentication, Authorization, Credential Mapping, and Role Mapping providers use the embedded LDAP server as their database.

Note: The WebLogic Security providers store their data in the embedded LDAP server. When you delete a WebLogic Security provider, the security data in the embedded LDAP server is not automatically deleted. The security data remains in the embedded LDAP server in case you want to use the provider again. Use an external LDAP browser to delete the security data from the embedded LDAP server.

Correct Answer: E

MS Connection Factory: Configuration: Default Delivery

Use this page to define the default delivery configuration parameters for this JMS connection factory, such as the default delivery mode, default time to live, etc.

Reference: JMS Connection Factory: Configuration: Default Delivery

Correct Answer: CDE

C: If you created Managed Server while creating domain then you can start Managed Server using startManagedWebLogic command

$BEA_HOME/user_projects/domains//bin

startManagedWebLogic.cmd (for Windows) startManagedWebLogic.sh (for Unix)

Assume that we a created Managed Server MS1 with Admin Port as 7003. startManagedWebLogic.cmd ms1 http://localhost:7003 (Windows)

D: Starting Administration Server (startWebLogic.cmd or .sh)

E: Starting Managed Server (startManagedWebLogic.sh or .cmd)

Correct Answer: E

The following signature takes the URL, user name, and password all as part of a URL parameter:

getConnection(String URL);

Where the URL is of the form: jdbc:oracle::/@

Reference: oracle.jdbc, Class OracleDriver

Correct Answer: D

To Deploy the EAR File to the Production Server See step 8 below.

Open the WebLogic Server console for the target server running in production mode.

1.

On the left-hand side Change Center pane, click Lock and Edit.

2.

On the left-hand side Domain Structure pane, click Deployments.

3.

On the right-hand content pane, click Install.

Browse to the directory where the EAR file resides, mark the radio button next to the EAR file you want to deploy, and click Next.

4.

Confirm that the radio button next to Install this deployment as an application is marked and click Next.

5.

Click Finish.

6.

On the left-hand side Change Center pane, click Activate Changes.

7.

On the right-hand content pane, mark the radio button next to the EAR just deployed.

8.

Click Start to view the dropdown list and select Servicing all requests.

9.

In the content pane of the new page, click Yes. Reference: Deploying Applications to WebLogic Server

Correct Answer: BE

B: To proxy requests by path, use the Location block and the SetHandler statement. When to use

Use to apply directives to content that lives outside the filesystem. For content that lives in the filesystem, use and . An exception is , which is an easy way to apply a configuration to the entire server.

For all origin (non-proxy) requests, the URL to be matched is a URL-path of the form /path/. No scheme, hostname, port, or query string may be included. For proxy requests, the URL to be matched is of the form scheme://servername/path, and you must include the prefix.

E: Add an IfModule block that defines one of the following:

For a non-clustered WebLogic Server instance:

The WebLogicHost and WebLogicPort parameters.

For a cluster of WebLogic Servers instances:

The WebLogicCluster parameter.

If you are proxying requests by MIME type to a cluster of WebLogic Servers, use the WebLogicCluster parameter.

For example:

WebLogicCluster

w1s1.com:7001,w1s2.com:7001,w1s3.com:7001

Note #1: The ... section is used to mark directives that are conditional on the presence of a specific module. The directives within an

section are only processed if the test is true. If test is false, everything between the start and end markers is ignored.

The test in the section directive can be one of two forms:

module name

!module name

Note #2:

Directive

Description: Applies the enclosed directives only to matching URLs Syntax: ...

Context: server config, virtual host

Status: Core

Module: core

The directive limits the scope of the enclosed directives by URL. It is similar to the directive, and starts a subsection which is terminated

with a directive. sections are processed in the order they appear in the configuration file, after the sections and .htaccess files

are read, and after the sections.

sections operate completely outside the filesystem. This has several consequences. Most importantly, directives should not be used to

control access to filesystem locations. Since several different URLs may map to the same filesystem location, such access controls may by circumvented.

Reference: eDocs Home > BEA WebLogic Server 8.1 Documentation > Using Web Server Plug- Ins with WebLogic Server > Installing and Configuring the Apache HTTP Server Plug-In