1Z0-102 Online Practice Questions and Answers

Correct Answer: B

The server staging mode specifies the default deployment mode for a server if none is specified at deployment time. For example, the server staging mode is used

if you deploy an application or module using weblogic.Deployer and you do not specify a staging mode.

Reference:

http://docs.oracle.com/cd/E12840_01/wls/docs103/ConsoleHelp/taskhelp/deployment/SetAServe rStagingMode.html

Correct Answer: AEF

Please refer to the screenshot below:

Incorrect answers:

F: Custom Identity and Command Line Trust are not valid choices.

Reference:

http://docs.oracle.com/cd/E23549_01/apirefs.1111/e13952/pagehelp/Corecoreserverserverconfig keystoretitle.html#attributes

Correct Answer: AD

A: Main Steps for Creating Packaged JMS Application Modules

Follow these steps to configure a packaged JMS module:

If necessary, create a JMS server to target the JMS module to, as explained in "Configure JMS Servers" in the Administration Console Online Help.

Create a JMS system module and configure the necessary resources, such as queues or topics, as described in "Configure JMS system modules and add JMS

resources" in the Administration Console Online Help.

The system module is saved in config\jms subdirectory of the domain directory, with a "- jms.xml" suffix.

Copy the system module to a new location, and then:

Give the module a unique name within the domain namespace.

Delete the JNDI-Name attribute to make the module application-scoped to only the application. Add references to the JMS resources in the module to all

applicable J2EE application component's descriptor files, as described in Referencing a Packaged JMS Application Module In Deployment Descriptor Files.

Package all application modules in an EAR, as described in Packaging an Enterprise Application With a JMS Application Module.

Deploy the EAR, as described in Deploying a Packaged JMS Application Module.

D: JMS application modules can be packaged as part of an Enterprise Application Archive (EAR), as a packaged module. Packaged modules are bundled with an

EAR or exploded EAR directory, and are referenced in the weblogic-application.xml descriptor. The packaged JMS module is deployed along with the Enterprise

Application, and the resources defined in this module can optionally be made available only to the enclosing application (i.e., as an application-scoped resource).

Such modules are particularly useful when packaged with EJBs (especially MDBs) or Web Applications that use JMS resources. Using packaged modules

ensures that an application always has required resources and simplifies the process of moving the application into new environments.

Reference: Packaging JMS Application Modules In an Enterprise Application

Correct Answer: ACE

A: A deployment plan is an XML document that defines an application's WebLogic Server deployment configuration for a specific WebLogic Server environment.

C: The Administration Console updates or creates new deployment plans as necessary when you change configuration properties for an installed application.

E: A deployment plan can apply changes to deployment properties stored in the application's existing WebLogic Server deployment descriptors. Incorrect answers:

B: A deployment plan resides outside of an application's archive file.

Reference: Overview of WebLogic Server Application Development, Deployment Plans

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

To prevent the Administration Server from becoming a single point of failure, Managed Servers can always function without the presence a running Administration Server. When a Managed Server starts, it contacts the Administration Server to retrieve its configuration information. If a Managed Server is unable to connect to the specified Administration Server during startup, it can retrieve its configuration directly by reading a copy of the config.xml file and other files located on the Managed Server's own file system. A Managed Server that starts in this way is running in Managed Server Independence mode. In this mode, a server uses cached application files to deploy the applications that are targeted to the server.

Reference: Overview of WebLogic Server System Administration, Managed Server Indepenence http://docs.oracle.com/cd/E13222_01/wls/docs81/adminguide/ overview.html

Correct Answer: B

JMS system modules are owned by the Administrator, who can delete, modify, or add JMS system resources at any time. With the exception of standalone queue

and topic resources that must be targeted to a single JMS server, the connection factory, distributed destination, foreign server, and JMS SAF destination

resources in system modules can be made globally available by targeting them to server instances and clusters configured in the WebLogic domain. These

resources are therefore available to all applications deployed on the same targets and to client applications.

Note #1: JMS modules are application-related definitions that are independent of the domain environment. You create and manage JMS resources either as

system modules or as application modules.

System modules are globally available for targeting to servers and clusters configured in the domain, and therefore are available to all applications deployed on

the same targets and to client applications.

Note #2: JMS servers are environment-related configuration entities that act as management containers for the queues and topics in JMS modules that are

targeted to them. A JMS server's primary responsibility for its destinations is to maintain information on what persistent store is used for any persistent messages

that arrive on the destinations, and to maintain the states of durable subscribers created on the destinations. JMS servers also manage message paging on

destinations, and, optionally, can manage message and/or byte thresholds, as well as server-level quota for its targeted destinations. As a container for targeted

destinations, any configuration or run-time changes to a JMS server can affect all the destinations that it hosts.

Reference: Understanding JMS Resource Configuration, JMS System Modules http://docs.oracle.com/cd/E15051_01/wls/docs103/jms_admin/overview.html

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

D: 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().

E: Each data source that you configure contains a pool of database connections that are created when the data source instance is created--when it is deployed or targeted, or at server startup. Applications lookup a data source on the JNDI tree or in the local application context (java:comp/env), depending on how you configure and deploy the object, and then request a database connection. When finished with the connection, the application calls connection.close(), which returns the connection to the connection pool in the data source.

Incorrect answers: A: There is no such Weblogic utility.

B: This is a JDBC error. There is no JDBC application target. There is JDBC data source target, however.

Correct Answer: CDFH

The Administration Console user interface includes the following panels.

*

Breadcrumb Navigation

A series of links that show the path you have taken through the Administration Console's pages.

*

Change Center

This is the starting point for using the Administration Console to make changes in WebLogic Server.

*

Domain Structure

This panel is a tree you can use to navigate to pages in the Administration Console.

*

How do I...

This panel includes links to online help tasks that are relevant to the current Console page.

*

Tool Bar

The tool bar at the top of the Console.

*

System Status

The System Status panel reports on the number of information, error, and warning messages that have been logged.

H: To help automate the task of configuring a domain, you can record your configuration actions in the Administration Console as a series of WebLogic Scripting

Tool (WLST) commands and then use WLST to replay the commands.

For details see: Administration Console Online Help, Record WLST Scripts

Incorrect answers:

A: To edit XML files, use the BEA XML Editor, an entirely Java-based XML stand-alone editor.

B: On Windows, a shortcut on the Start menu sets the environment variables and invokes WLST (Tools-->WebLogic Scripting Tool).

E: he Template Builder is a standalone Java application that prompts you to create custom configuration and extension templates that can be used later for

creating and updating domains via the Configuration Wizard. Using an existing domain or template, the Template Builder guides you through the process of

creating custom configuration and extension templates. You can then package these templates or extension templates with your software so your customers can

use them to customize their WebLogic Platform environments. The Template Builder is especially useful for ensuring that the required environment for WebLogicbased products can be installed and configured easily by your customers at their sites.

G: * To start and run the Configuration Wizard on a Windows computer, select the Configuration Wizard option from the BEA program group in the Windows Start

Menu.

* To start and run the Configuration Wizard in a GUI environment on a UNIX computer (or from a Windows command prompt):

Log in to a Windows or UNIX system on which the WebLogic Server software is installed.

Open a command-line shell.

Go to the following directory: WL_HOME/common/bin

where WL_HOME is the directory in which you installed WebLogic Server. For example:

cd ~/bea/weblogic810/common/bin

Invoke the config.cmd or config.sh script.

If you try to start the Configuration Wizard on a system that cannot support the graphical display, the wizard automatically starts in console mode.

Reference: Overview of the Administration Console http://docs.oracle.com/cd/E13222_01/wls/docs90/intro/console.html#1122030