1Z0-102 Online Practice Questions and Answers

Correct Answer: A

The WLST life cycle shutdown command gracefully shuts down a running server instance or cluster.

Reference: WebLogic Scripting Tool ,Life Cycle Commands

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

B: The Console Context Path is an advance configuration option. The context path that you want to use in URLs that specify the Administration Console. Note: Create a new WebLogic Server domain based on a template. Templates allow you to re-create an existing do- main for use in another context, such as migrating a domain containing an application under development to a pro- duction environment.

C: An Administration Console extension is a WAR file that contains the resources for a section of a WebLogic Portal Web application. When you deploy the extension, the Administration Console creates an in-memory union of the files and directories in its WAR file with the files and directories in the extension WAR file. Once the extension has been deployed, it is a full member of the Administration Console: it is secured by the WebLogic Server security realm, it can navigate to other sections of the Administration Console, and if the extension modifies WebLogic Server resources, it participates in the change control process.

Incorrect answers:

A: Exposing the console in your production environment might be security issue. In those cases you can either dis- able the console or hide it. Needless to say if you disable the console then your only option is to depend on com- mand-line and scripting tools for any other administration activity or to even enable the console back. But hiding will provide a level or security.

To disable the console:

In the admin console navigate to --> General --> Advanced Options --> Console Enabled. De-select that option to disable console (restart required).

To hide the cosole:

E: Access through a secure port is recommended, but not required:

The administration port requires all communication to be secured using SSL. By default, all servers in a do- main use demonstration certificate files for SSL, but

these certificates are not appropriate for a production environment.

Reference: Administration Console Online Help, Advanced Configuration Options Reference: Extending the Administration Console for Oracle WebLogic Server 11g Release 1

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

There are three ways to create domain templates:

*

Domain Template Builder (config_builder.sh under WL_HOME/common/bin) Go to Start Menu->All programs->weblogic10gR3->Tools->Domain Template Builder

*

pack command The pack command creates a template archive (.jar) file that contains a snapshot of either an entire domain or a subset of a domain. You can use a template that contains a subset of a domain to create a Managed Server domain directory hierarchy on a remote machine.

*

WLST offline command line tool

Reference: Creating Domain Templates Using the Domain Template Builder Reference: Creating Domains Using WLST Offline

Correct Answer: C

If a change is made to a non-dynamic configuration setting, no changes to dynamic configuration settings will take effect until after restart. This is to assure that a

batch of updates having a combination of dynamic and non-dynamic attribute edits will not be partially activated.

Note: Some changes you make in the Administration Console take place immediately when you activate them. Other changes require you to restart the server or

module affected by the change.

These latter changes are called non-dynamic changes.

Changes to dynamic configuration attributes become available once they are activated, without restarting the affected server or system restart. These changes are

made available to the server and runtime hierarchies once they are activated. Changes to non-dynamic configuration attributes require that the affected servers or

system resources be restarted before they become effective.

Reference: Overview of the Administration Console, Dynamic and Non-Dynamic Changes

Correct Answer: AB

A: Target

The target that this JMSServer is deployed to.

See step 5) in the Note below.

B: Persistent Store

The file or database in which this JMS server stores persistent messages. If unspecified, the JMS server uses the default persistent store that is configured on

each targeted WebLogic Server instance.

Note: See step 4) below.

To create a JMS server:

1.

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

2.

In the Administration Console, expand Services > Messaging and select JMS Servers.

3.

On the Summary of JMS Servers page, click New.

Note: Once you create a JMS server, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

4.

On the Create a JMS Server page:

a.

In Name, enter a name for the JMS server.

b.

In Persistent Store, select a pre-configured

custom file or JDBC store that will be used by

the JMS server or click the Create a New

Store button to create a store on the fly.

5.

On the Select Targets page, select the server instance or migratable server target on which to deploy the JMS server.

Migratable targets define a set of WebLogic Server instances in a cluster that can potentially host a pinned service, such as a JMS server.

6.

Click Finish

Incorrect answer:

C: There is no such JMS Server destination attribute.

Reference: OTN Home > Oracle WebLogic Server 10.3.5.0 Documentation > Administration Console Online Help > JMS Servers

Correct Answer: A

Note #1: If your EJBs will run on a WebLogic Server cluster, Oracle recommends that you deploy them homogeneously--to each Managed Server in the cluster. Alternatively, you can deploy an EJB to only to a single server in the cluster (that is, "pin" a module to a server). This type of deployment is less common, and should be used only in special circumstances where pinned services are required.

Note #2: When you deploy an EJB, you specify the servers and clusters to which the EJB deployment is targeted. After you have deployed an EJB, you can update the servers and clusters to which it is targeted.

To set target servers and clusters for a deployed EJB:

1.

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

2.

In the left pane of the Administration Console, select Deployments.

The right pane lists the EJBs and other modules that you have deployed, or tried to deploy.

3.

In the right pane, click the desired EJB.

4.

Select the Targets tab.

Servers and clusters in the domain are displayed.

5.

Select the check box next to the individual servers and/or clusters to which you wish to deploy the EJB and click Save.

By default, the Administration Console deploys an EJB to all server instances in the cluster (the "All servers in the cluster" option). To deploy the EJB to selected servers in a cluster, select "Part of the cluster", and then select the individual server instances to which you want to deploy the EJB.

6.

To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately--some require a restart

Correct Answer: B

A WebLogic domain can be composed of a number of WebLogic instances, and several of these servers may be grouped into clusters. For instance, you could set up a cluster of WebLogic servers, all of which host your web application and related resources. This cluster of servers could be fronted by a load balancer that distributes requests evenly across all the members of the cluster. The load balancer could itself be another WebLogic instance. All server instances must belong to the same WebLogic domain. Thus, a WebLogic cluster is a group of servers working together with services, such as clustered JNDI, to provide support for failover and load balancing. A domain may in turn have a number of WebLogic instances, several groups of which can be placed into different clusters.

Correct Answer: BD

In WebLogic Server, you configure database connectivity by adding data sources to your WebLogic domain. WebLogic JDBC data sources provide database access and database connection management. Each data source contains a pool of database connections that are created when the data source is created and at server startup. Applications reserve a database connection from the data source by looking up the data source on the JNDI tree or in the local application context and then calling getConnection(). When finished with the connection, the application should call connection.close() as early as possible, which returns the database connection to the pool for other applications to use.