1Z0-102 Online Practice Questions and Answers

Correct Answer: B

Node Manager security relies on a one-way SSL connection between the client and server.

Reference: Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1, Configuring Java-based Node Manager Security http://docs.oracle.com/cd/E21764_01/web.1111/e13740/java_nodemgr.htm#i1068397

Correct Answer: D

If you install the WebLogic Server Examples component, the default user weblogic is created that has permission to start and stop WebLogic Server. The default password is welcome1. If you change the password of the weblogic user, WebLogic Server does not automatically update this password in the boot.properties file, which is located in the DOMAIN_NAME/servers/AdminServer/security directory.

If you change the password for user weblogic, you can use either of the following workarounds so that you can continue to boot a WebLogic Server instance via that username and its new password:

*

Remove the boot.properties file. Subsequently each time you start WebLogic Server, you are prompted for the username and password. The changed password for the weblogic user will be accepted.

*

Modify the existing boot.properties file, changing the username and password as follows:

username=weblogic password=welcome1 Subsequently during the server startup process, the boot.properties file is encrypted again.

Reference: Oracle Fusion Middleware Oracle WebLogic Server Administration Console Online Help 11g Release 1, Limitation Regarding User weblogic http://docs.oracle.com/cd/E15523_01/web.1111/e13708/overview.htm

Correct Answer: ABD

A: When the HTTP client requests the servlet, HttpClusterServlet proxies the request to the WebLogic Server cluster. HttpClusterServlet maintains the list of all servers in the cluster, and the load balancing logic to use when accessing the cluster. In the above example, HttpClusterServlet routes the client request to the servlet hosted on WebLogic Server A. WebLogic Server A becomes the primary server hosting the client's servlet session. To provide failover services for the servlet, the primary server replicates the client's servlet session state to a secondary WebLogic Server in the cluster. This ensures that a replica of the session state exists even if the primary server fails (for example, due to a network failure). In the example above, Server B is selected as the secondary. The servlet page is returned to the client through the HttpClusterServlet, and the client browser is instructed to write a cookie that lists the primary and secondary locations of the servlet session state. If the client browser does not support cookies, WebLogic Server can use URL rewriting instead. Figure, Accessing Servlets and JSPs using a Proxy:

B: In clusters that utilize Web servers with WebLogic proxy plug-ins, the proxy plug-in handles failover transparently to the client. If a server fails, the plug-in

locates the replicated HTTP session state on a secondary server and redirects the client's request accordingly.

D: The WebLogic proxy plug-in maintains a list of WebLogic Server instances that host a clustered servlet or JSP, and forwards HTTP requests to those instances

on a round-robin basis.

Incorrect answers:

C: The WebLogic proxy plug-in maintains a list of WebLogic Server instances that host a clustered servlet or JSP, and forwards HTTP requests to those instances

on a round-robin basis. This load balancing method is described in Round Robin Load Balancing. The plug-in also provides the logic necessary to locate the

replica of a client's HTTP session state if a WebLogic Server instance should fail.

F: SSL Parameters for Web Server Plug-ins

Parameter: SecureProxy

Default: OFF

Description: Set this parameter to ON to enable the use of the SSL protocol for all communication between the plug-in and WebLogic Server.

Reference: Using WebLogic Server Clusters, Failover and Replication in a Cluster Reference: Using WebLogic Server Clusters, Load Balancing in a Cluster

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

File persistence use less memory than in-memory replication, and does not need access rights to the company's database.

Note:

You use session persistence to permanently store data from an HTTP session object to enable failover and load balancing across a cluster of WebLogic Servers.

When your applications stores data in an HTTP session object, the data must be serializable. There are five different implementations of session persistence:

*

Memory (single-server, non-replicated)

*

File system persistence

*

JDBC persistence

*

Cookie-based session persistence

*

In-memory replication (across a cluster)

Incorrect answers:

A: Using in-memory replication, WebLogic Server copies a session state from one server instance to another. The primary server creates a primary session state on the server to which the client first connects, and a secondary replica on another WebLogic Server instance in the cluster. The replica is kept up-to-date so that it may be used if the server that hosts the servlet fails.

D: JDBC persistence stores session data in a database table using a schema provided for this purpose. You can use any database for which you have a JDBC driver. You configure database access by using connection pools.

Note: When you use memory-based storage, all session information is stored in memory and is lost when you stop and restart WebLogic Server.

Reference: Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server, Using Sessions and Session Persistence

Correct Answer: B

Administrator machine:

The Choose the Administration Server window prompts you to designate a server as the Administration Server. This window is displayed automatically only if the

selected template includes multiple servers that are not assigned to clusters.

To choose the Administration Server:

1.

From the list of Available Servers, select the server that you want to designate as the Administration Server. The Administration Server cannot be assigned to a cluster.

2.

Select Next to proceed to the next configuration window.

The Server Details area displays detailed information about the selected server. By default, the currently assigned Administration Server is selected.

The Configure the Administration Server and Configure Managed Server(s) windows are updated to reflect your changes.

Managed machine:

The minimum requirement for your domain is a single Administration Server on a single machine. In addition, however, you have the option of configuring other

resources to be managed by the Administration Server and distributing them across multiple machines. Specifically, you can:

*

Add, change, or delete Managed Servers

*

Add, change, or delete clusters

*

Group Managed Servers into clusters, or change current groupings

*

Assign servers to machines, or change current assignments

Note: The Managed Servers, Clusters, and Machines Options window prompts you to specify whether you want to distribute your WebLogic configuration across

Managed Servers, clusters, and physical machines

Note 2:

The Configure Managed Servers window prompts you to provide the configuration information for one or more Managed Servers. Production environments

typically deploy one or more Managed Servers, in addition to the Administration Server, to host enterprise applications.

Reference: Creating WebLogic Configurations Using the Configuration Wizard, Configuring Managed Servers, Clusters, and Machines

Correct Answer: AD

A: 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, virtual host, and any other resource type must be named uniquely and must not use the same name as the domain.

D: The server name cannot be changed.

Incorrect answers:

B: Listen ports can be changed.

Change Weblogic Listen Port:

We need to use WLST (weblogic scripting tool) utility if we need to change from back- end.

Example:

wls:/offline/wl_server/Server/examplesServer> set(`ListenPort',10890); wls:/offline/wl_server/Server/examplesServer> updateDomain(); wls:/offline/wl_server/

Server/examplesServer> exit();

C: port is 7001. It does not need to be unique for each server. They all use the same Listen port by default. In Weblogic server default Listen

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

MedRec-Spring is not installed by default when you install WebLogic Server. You must choose Custom installation, then select Server Examples from the Choose Products and Component page.

Note: MedRec is an end-to-end sample Java EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application provides a framework for patients, doctors, and administrators to manage patient data using a variety of different clients.

MedRec demonstrates WebLogic Server and Java EE features, and highlights Oracle- recommended best practices. MedRec is included in the WebLogic Server distribution, and can be accessed from the Start menu on Windows machines. For Linux and other platforms, you can start MedRec from the WL_HOME\samples \domains\medrec directory, where WL_HOME is the top-level installation directory for WebLogic Server. A Spring version of the application is accessible from the WL_HOME\samples\domains\medrec-spring directory.

Reference: Oracle Fusion Middleware Spring Support in Oracle WebLogic Server 11g Developing Spring-Based Applications for Oracle WebLogic Server