Consider an IT infrastructure comprising several web and EJB applications. Each application is expected to handle significantly different workloads, and therefore has different resource and scalability requirements. Which is the best solution for this scenario?
A. Configure a dedicated server for each application.
B. Configure a separate cluster for each application.
C. Configure a separate domain for each application.
D. Configure a separate proxy for each application.
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.
Question 12:
Which two statements are true about cluster configuration?
A. A server must be running before it can be added to a cluster.
B. You cannot define cluster membership through the Configuration Wizard.
C. The console allows you to add new and existing servers to a cluster.
D. The console allows you to add an administration server to a cluster.
E. You cannot remove a server that is running from a cluster.
Correct Answer: CE
o assign server instances to a cluster:
C: T
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 Console, expand Environment and
select Clusters.
3.
Select the cluster to which you want to assign servers.
4.
Select Servers and click Add.
5.
To add an existing server to a cluster:
a.
Select the Select an existing server and add it
as a member of this cluster option.
b.
Select a server from the drop-down list.
Note: You cannot change the cluster of the Administation Server using the Administration Console. You cannot change the cluster or machine of a running server.
c.
Click Finish.
6. To create a new server as part of a cluster:
a.
Select the Create a new server and add it to
this cluster option.
b.
Click Next.
c.
Provide the following information:
Server Name
Server Listen Address
Server Listen Port
d.
Click Finish.
The new server appears in the list of servers and is added as a member of the current cluster.
7. To activate these changes, in the Change Center of the
Administration Console, click Activate Changes.
Incorrect answer:
Not A. See screenshot below.
Reference: edocs Home > Oracle WebLogic Server Documentation > Administration Console Online Help > Assign servers to clusters
Question 13:
You are deploying an EAR by using the administration console. You are part way through the process. In the administration console, you see that the EAR has the State of "Prepared." What can you do in the administration console to bring the deployment to the "Active" State?
A. Select it and click the Install button.
B. Select it, and then from the Install drop-down list, select "Servicing all requests"
C. Select it, and then from the update drop-down list, select "Servicing all requests"
D. Select it, and then from the Start drop-down list, select "Servicing all requests"
E. Select it, and then from the Start drop-down list, select "Servicing only administration requests"
Correct Answer: D
To Deploy the EAR File to the Production Server See step 8 below.
Open the WebLogic Server console for the target server running in production mode.
1.
On the left-hand side Change Center pane, click Lock and Edit.
2.
On the left-hand side Domain Structure pane, click Deployments.
3.
On the right-hand content pane, click Install.
Browse to the directory where the EAR file resides, mark the radio button next to the EAR file you want to deploy, and click Next.
4.
Confirm that the radio button next to Install this deployment as an application is marked and click Next.
5.
Click Finish.
6.
On the left-hand side Change Center pane, click Activate Changes.
7.
On the right-hand content pane, mark the radio button next to the EAR just deployed.
8.
Click Start to view the dropdown list and select Servicing all requests.
9.
In the content pane of the new page, click Yes. Reference: Deploying Applications to WebLogic Server
Question 14:
Your domain includes a cluster of five servers, but only three are currently running. A colleague then uses the administration console to install and deploy a new
EJB application to the cluster.
By default, which outcome would you expect?
A. The application deploys successfully on the three servers that are running.
B. The deployment fails because the entire cluster is not running.
C. The deployment succeeds, but the application is not accessible.
D. The user is prompted to start the two unavailable servers before continuing.
E. The two unavailable servers are automatically removed from the cluster.
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
Question 15:
Indentify two requirements for in-memory session replication.
A. Clusters must contain an even number of members.
B. Web applications must be configured to use replication.
C. Web applications must be deployed as an archive file.
D. Cluster members must be started by using the Node Manager.
E. Web applications must be accessed via a proxy that supports session cookies
Correct Answer: BE
B: When in-memory replication is enabled for a web application, WebLogic Server copies session state from one server in the cluster (primary) to one other server
in the same cluster (secondary). The replica on the secondary server is kept up-to-date so that it may be used if the primary server fails.
E: To utilize in-memory replication for HTTP session states, you must access the WebLogic Server cluster using either a collection of Web servers with identically
configured WebLogic proxy plug-ins, or load balancing hardware.
If you choose to use load balancing hardware instead of a proxy plug-in, it must support a compatible passive or active cookie persistence mechanism, and SSL
persistence.
Note 1: In its default configuration, WebLogic Server uses client-side cookies to keep track of the primary and secondary server that host the client's servlet session state. If client browsers have disabled cookie usage, WebLogic Server can also keep track of primary and secondary servers using URL rewriting. With URL rewriting, both locations of the client session state are embedded into the URLs passed between the client and proxy server. To support this feature, you must ensure that URL rewriting is enabled on the WebLogic Server cluster.
Note 2: To support automatic failover for servlet and JSP HTTP session states, WebLogic Server replicates the session state in memory. WebLogic 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. The process of copying a session state from one server instance to another is called in-memory replication.
Reference: eDocs Home > BEA WebLogic Server 8.1 Documentation > Using WebLogic Server Clusters > Failover and Replication in a Cluster, Failover and Replication in a Cluster
Question 16:
Indentify two attributes of a JMS server.
A. Target
B. Persistent Store
C. Destination
D. Connection Factory
E. Store and Forward
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
Question 17:
The master Embedded LDAP has the capability to back up its data. Which statement is true?
A. The Managed Servers should be shut down when backups are being performed on the Embedded LDAP.
B. The backup feature is enabled by default.
C. The backup feature of the Embedded LDAP should be enabled for all the servers in the domain on a per-basis.
D. The backup is stored in a comma-separated variable format.
Correct Answer: C
The backup of the embedded LDAP server is enabled for a domain at a time. See step 2) in Note below.
Incorrect answers:
A: No need to shut down the server. See Note below.
B: The backup feature need to be configured. See Note below.
D: The format of the backup file is not comma-seperated.
Note: To configure the backups of the embedded LDAP server:
1.
If you have not already done so, in the Change Center of the Administration Console, click Lock and Edit
2.
Select the Domain you want to configure (for example, mydomain).
3.
Expand Security > Embedded LDAP.
4.
Set the Backup Hour, Backup Minute, and Backup Copies attributes on the Embedded LDAP Server page.
5.
Click Save to save your changes.
6.
To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
Question 18:
When creating a new Managed Server using the administration console, which two points must be considered?
A. The Server Name must be unique within the domain.
B. After you assign a Listen Port value for the server, you cannot change it
C. The Listen Port value must be unique for ever server.
D. The Server Name cannot be changed after you have created the server.
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.
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
Question 19:
A web application called sales was deployed and is currently "Active". It is targeted to managed1 and managed2. The developers have given you an upload WAR file and you have replaced the original WAR file with it. From the directory where the WAR file resides, you run the following weblogic.Deployer command:
java weblogic.Deployer adminurl t3://192.168.1.101:7001-username weblogic password welcom1 name sales redeploy Which statement best describes what happens?
A. The command fails because no target was specified.
B. The application is deployed to the Administration Server because no target was specified.
C. The application is deployed to whichever server is running at 192.168.1.101:7001.
D. The application is deployed to managed1 and managed2 because that is where it is currently targeted.
Correct Answer: D
-targetstarget_list (for the redeploy command) is not specified here. It is used to specify the targets on which to distribute, deploy, or redeploy the application or module.
If you do not specify a target list with the -deploy command, the target defaults to:
*
the Administration Server instance for new deployments (not the case here)
*
the application's current targets for deployed applications (the case in this scenario)
The -adminurl value must specify the listen address and listen port of the Administration Server.
. The Administrator username. If you supply the -username option but you do -usernameusername
not supply a corresponding -password option, weblogic.Deployer prompts you for the password.
-redeploy.redeploys a running application or part of a running application.
-name deployment_name. Specifies the deployment name of a deployed application or module. The option can be omitted, in which case the name is taken from
the -source fileargument.
-name
Note: weblogic.Deployer is a Java-based deployment tool that provides a command-line interface to the WebLogic Server deployment API. weblogic.Deployer is
intended for administrators and developers who want to perform interactive, command-line based deployment operations.
Reference: Deploying Applications to WebLogic Server, weblogic.Deployer Command-Line Reference
Question 20:
Which four tasks can be accomplished in the administration console only after the configuration is locked?
A. deploying an application
B. changing console preferences
C. creating a new JMS Server
D. monitoring the health of a server
E. enabling the Administrator Port
F. creating a new Managed Server
G. adding a new user to the default authentication provider
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
Nowadays, the certification exams become more and more important and required by more and more enterprises when applying for a job. But how to prepare for the exam effectively? How to prepare for the exam in a short time with less efforts? How to get a ideal result and how to find the most reliable resources? Here on Vcedump.com, you will find all the answers. Vcedump.com provide not only Oracle exam questions, answers and explanations but also complete assistance on your exam preparation and certification application. If you are confused on your 1Z0-102 exam preparations and Oracle certification application, do not hesitate to visit our Vcedump.com to find your solutions here.
