Oracle 1Z0-102 Exam Questions

C: All JMS resources that can be configured in a JMS system module can also be configured and managed as deployable application modules, similar to standard J2EE modules.

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.

A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process.

Incorrect answers:

A: A cluster is part of a particular WebLogic Server domain.

D: In each domain, one WebLogic Server instance acts as the Administration Server---the server instance which configures, manages, and monitors all other server instances and resources in the domain. Each Administration Server manages one domain only. If a domain contains multiple clusters, each cluster in the domain has the same Administration Server.

http://docs.oracle.com/cd/E11035_01/wls100/cluster/overview.html

B: Attribute label: Cluster

The cluster to which this server belongs. If set, the server will listen for cluster multicast events.

This is a configurable attribute.

C: Attribute label: Machine

The WebLogic Server host computer (machine) on which this server is meant to run.

This is a configurable attribute.

D: Server --> Configuration --> Cluster

A WebLogic Server cluster is a group of servers that work together to provide a more scalable, more reliable application platform than a single server.

Use this page to specify a server's primary and secondary replication group, cluster weight, and the interface address used to handle multicast traffic.

Attribute label: Replication Group

Description: Defines preferred clustered instances considered for hosting replicas of the primary HTTP session states created on the server.

Incorrect answers:

A: Attribute Label: Name

After you have created a server, you cannot change its name.

Instead, clone the server and provide a new name for the clone.

Note:

An alphanumeric name for this server instance. This field will not accept spaces.

Each server instance in your WebLogic environment must have a unique name, regardless of the domain or cluster in which it resides, or whether it is an Administration Server or a Managed Server. Within a domain, each server, machine, cluster, JDBC connection pool, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain.

F: There is no attribute within a server's configuration that designates it as an Administration Server or Managed Server. Instead, the first server instance that you start in a domain always functions as the Administration Server.

A subdeployment is a mechanism by which JMS module resources (such as queues, topics, and connection factories) are grouped and targeted to a server resource (such as JMS servers, server instances, SAF agents, or a cluster).

For example, you can group a connection factory with stand-alone queues or topics in a subdeployment targeted to a specific JMS server, which guarantees that all these resources are co-located to avoid extra network traffic. Another advantage of such a configuration would be if the targeted JMS server needs to be migrated to another WebLogic server instance, then the connection factory and all its connections will also migrate along with the JMS server's destinations. However, when stand-alone queues or topics are members of a subdeployment, a connection factory can only be targeted to the same JMS server.

A cluster must include at least one server.

A clustered is administered through an administration server, but the cluster consists of managed servers only.