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

A: If an object is clustered, failover and load balancing for that object is available. In a WebLogic Server cluster, application processing can continue when a server instance fails. You "cluster" application components by deploying them on multiple server instances in the cluster--so, if a server instance on which a component is running fails, another server instance on which that component is deployed can continue application processing.

The choice to cluster WebLogic Server instances is transparent to application developers and clients.

B: A clustered application or application component is one that is available on multiple WebLogic Server instances in a cluster. If an object is clustered, failover and load balancing for that object is available. Deploy objects homogeneously--to every server instance in your cluster --to simplify cluster administration, maintenance, and troubleshooting.

Web applications can consist of different types of objects, including Enterprise Java Beans (EJBs), servlets, and Java Server Pages (JSPs).

Note: Load balancing and failover for EJBs and RMI objects is handled using replica-aware stubs, which can locate instances of the object throughout the cluster.

C: Cluster Multicast Address and Port

Identify the address and port you will dedicate to multicast communications for your cluster.

Incorrect answers:

D: Cluster heartbeats-- Each WebLogic Server instance in a cluster uses multicast to broadcast regular "heartbeat" messages that advertise its availability. By monitoring heartbeat messages, server instances in a cluster determine when a server instance has failed.

E: All server instances in a cluster must reside in the same domain; you cannot "split" a cluster over multiple domains. Similarly, you cannot share a configured resource or subsystem between domains.

F: Proxy might be needed depending how you set up the architecture, but a proxy is not required for web applications.

Reference: Using WebLogic Server Clusters , Understanding WebLogic Server Clustering

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

Creating a Managed Server on a Remote Machine

(Step 3) * Install WebLogic Server on the machines on which you want to host Managed Servers for the WebLogic domain.

*

Establish a session with the remote machine. You may use any valid method, such as telnet, to do so. Step 4:

*

Copy the Managed Server template to the remote machine.

*

On the remote machine, navigate to the WLS_HOME\common\bin directory.

*

(Step 5) Run the following command:

unpack -domain=domain -template=template.jar

Starting Managed Servers on a Remote Machine

*

Start the Administration Server for the WebLogic domain

*

On the remote machine, navigate to the directory for the WebLogic domain that you created *(Step 6) Start the Managed Server on the remote machine. On a Windows system, run one of the following commands at the DOS prompt: startmy_managed_server startManagedWebLogic my_managed_server admin-url On a UNIX system, run one of the following commands: ./startmy_managed_server.sh ./startManagedWebLogic.sh my_managed_server admin-url Reference: Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1, Reference: Creating and Starting a Managed Server on a Remote Machine

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

B:

Enclose all other elements within library-ref.

A reference to a shared Java EE library.

Note: A Java EE application can reference a registered shared Java EE library using entries in the application's weblogic-application.xml deployment descriptor.

Elements include:

library-ref

library-name

D:

Specifies the Work Manager that is associated with the application.

Note: The weblogic-application.xml file is the BEA WebLogic Server-specific deployment descriptor extension for the application.xml deployment descriptor from Sun Microsystems. This is where you configure features such as shared Java EE libraries referenced in the application and EJB caching.

The file is located in the META-INF subdirectory of the application archive.

Reference: Developing Applications With WebLogic Server. weblogic-application.xml Deployment Descriptor Elements Reference: Referencing Shared Java EE Libraries in an Enterprise Application

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

A: Steps to Deploy Application using Administration Console

1.

Start the Admin Server and Managed Server.

2.

Navigate to Administration console http://localhost:7001/console and login.

3.

Navigate to Domain Environment > Deployments. Lock the console.

4.

Etc.

E: To enable the administration port for your domain:

1.

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

2.

Shutdown all Managed Servers in the domain. You cannot enable the administration port dynamically on a Managed Server.

3.

Ensure that all servers in the domain are properly configured to use SSL.

4.

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

5.

Select Configuration > General and select the Enable Administration Port check box to enable the SSL administration port for this domain.

6.

In the Administration Port field, enter the SSL port number that server instances in the domain use as the administration port. You can override an individual server instance's administration port assignment on the Advanced options portion of the Configuration: General page for the server instance.

7.

Click Save.

8.

To activate these changes, in the Change Center of the Administration Console, click Activate Changes.

Note: If you want to use the Administration Console to make configuration changes, you must first click the Lock and Edit button in the Change Center. When you click Lock and Edit, you obtain a lock on the editable hierarchy of Configuration MBeans for all servers in the domain (the edit tree). As you make configuration changes using the Administration Console, you click Save (or in some cases Finish) on the appropriate pages. This does not cause the changes to take effect immediately; instead, when you click Save, you are saving the change to the edit tree and to the DOMAIN_NAME/pending/config.xml file and related configuration files. The changes take effect when you click Activate Changes in the Change Center. At that point, the configuration changes are distributed to each of the servers in the domain. If the changes are acceptable to each of the servers, then they take effect. (Note, however, that some changes require a server to be restarted.) If any server cannot accept a change, then all of the changes are rolled back from all of the servers in the domain. The changes are left in a pending state; you can then either edit the pending changes to resolve the problem or revert the pending changes.

Incorrect answers:

G: There is no need to lock the configuration when you add a user (to the default authentication provider). Note: To create a new user in the embedded WebLogic LDAP server:

1.

Log in to the Oracle WebLogic Server Administration Console

2.

In Oracle WebLogic Server Administration Console, select Security Realms from the left pane and click the realm you are configuring. For example,myrealm.

3.

Select Users and Groups tab, then Users. Click New. etc.

Reference: Administration Console Online Help, Use the Change Center

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

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.