[Free] 2018(Jan) Dumps4cert Testinsides Oracle 1z0-102 Dumps with VCE and PDF 41-50

Dumps4cert.com : Latest Dumps with PDF and VCE Files
2018 Jan Oracle Official New Released 1z0-102
100% Free Download! 100% Pass Guaranteed!

Oracle Weblogic Server 11g: System Administration I

Question No: 41

Which three statements are true about the administration console?

  1. The administration console cannot be disabled.

  2. The context path of the administration console may be changed.

  3. The administration console may be extended.

  4. If a domain is in Development Mode, the administration console no longer requires an administration-level user when logging in.

  5. If a domain is in Production Mode, access to the administration console must be made through secure port.

  6. If the domain#39;s Administration Port is enabled, access to the administration console must be made only through that port.

Answer: B,C,F

Explanation: 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 domain for use in another context, such as migrating a domain containing an application under development to a production 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.

Reference: Administration Console Online Help, Advanced Configuration Options

Reference: Extending the Administration Console for Oracle WebLogic Server 11g Release 1

Question No: 42

Which three statements are true about deployment plans?

  1. A plan is an XML file.

  2. A plan is packaged within an application archive.

  3. You can generate a new plan with the administration console.

  4. A plan is a required to deploy EJB applications and modules.

  5. A plan may override values in an application#39;s deployment descriptors.

  6. A single application deployment can be associated with multiple plans.

Answer: A,C,E

Explanation: A: A deployment plan is an XML document that defines an application#39;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.

Reference: Overview of WebLogic Server Application Development, Deployment Plans

Question No: 43

All the servers in your domain are running.

After you connect to the Administration Server in WLST you run the following command, which completes with no error:

Progress = deploy (appName = ‘salesapp’, path = ‘sales.war’, target = managed1, managed2′, planpath = ‘plan.xml’)

Which two statements are true?

  1. The web application is now quot;Active.quot;

  2. The command creates new deployment plan called plan.xml.

  3. In the administration console, the name of this deployment is sales.war.

  4. The web application has been targeted to managed1, managed2, and the Administration Server.

  5. You can view the status of the deployment by sending a message to the object named progress.

    Answer: A,E

    Explanation: They deploy command is used to deploy an application to a WebLogic Server instance. (A)

    The deploy command returns a WLSTProgress object that you can access to check the status of the command. (E)



    deploy(appName, path, [targets], [stageMode], [planPath], [options])

    * appName

    Name of the application or standalone J2EE module to be deployed.

    * targets

    Optional. Comma-separated list of the target. Each target may be qualified with a J2EE module name (for example, module1@server1) enabling you to deploy different modules of the application archive on different servers. This argument defaults to the server to which WLST is currently connected.

    Note 2: The WebLogic Scripting Tool (WLST) is a command-line scripting interface that system administrators and operators use to monitor and manage WebLogic Server instances and domains.

    Reference: WebLogic Scripting Tool, WLST Command and Variable Reference

    Question No: 44

    Your task is to create and start a managed server on a “remote” computer (a computer other than the one where the domain has been created and the Administration server is currently running).

    So far you have:

    1. Created the managed server, called startmanaged1, in the administration console

    2. Created a managed serverquot; JAR file template by using the pack command or, the Administration server computer.

      Which order of steps on the remote computer will successfully finish your task?


    3. Copy the JAR file from the Administration Server computer.

    4. Run the unpack command on the JAR file.

    5. In the new domain folder created by the command, start managed: by using the startManagedWebLogic. sh script (. cmd in Windows), which is found under its bin directory B.

  1. Install WebLogic Server.

  2. Copy the JAR file from the Administration Server computer.

  3. Run the unpack command on the JAR file.

  4. In the administration console, under the Control tab, select managed1 and click the Start button.


  1. Install WebLogic Server.

  2. Copy the JAR file from the Administration Server computer.

  3. Run the unpack command on the JAR file.

  4. In the new domain folder created by the command, start managed1 by using the Logic. sh script (. cmd in Windows), which is found under its bin directory.


  1. Install WebLogic Server.

  2. Copy the JAR file from the Administration Server computer.

  3. Run the unpack command on the JAR file.

  4. In the new domain folder created by the command, startmanaged1 by using the startManagedWeblogic.sh script (. cmd in Windows), which is found under its bin directory.

    Answer: D

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


    /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

    Question No: 45

    Identify three attributes of a WebLogic cluster.

    1. Listen Address

    2. Cluster Address

    3. Cluster Factory

    4. Messaging Mode

    5. Servers

    6. Targets

Answer: B,D,E

Explanation: WebLogic Cluster Attributes includes: B: * ClusterAddress

Defines the address to be used by clients to connect to this cluster. This address may be either a DNS host name that maps to multiple IP addresses or a comma separated list of single address host names or IP addresses. If network channels are configured, it is possible to set the cluster address on a per channel basis.

D: The Message Mode of a cluster can be either Unicast or multicast. E: Managed Servers are included in a WebLogic cluster.

Note: The config.xml file is an XML document that describes the configuration of a WebLogic Server domain. config.xml consists of a series of XML elements. The Domain element is the top-level element, and all elements in the Domain descend from the Domain element. The Domain element includes child elements, such as the Server, Cluster, and Application elements. These child elements may have children of their own. For example, the Server element includes the child elements WebServer, SSL and Log. The Application element includes the child elements EJBComponent and WebAppComponent.

Each element has one or more configurable attributes. An attribute defined in config.dtd has a corresponding attribute in the configuration API. For example, the Server element has a ListenPort attribute, and likewise, the weblogic.management.configuration.ServerMBean has a ListenPort attribute. Configurable attributes are readable and writable, that is, ServerMBean has a getListenPort and a setListenPort method.

Reference: WebLogic Server Configuration Reference, Cluster attributes http://docs.oracle.com/cd/E13222_01/wls/docs81/config_xml/Cluster.html#447012

Question No: 46

A client accesses a web application named companystore that is running on WebLogic Server. After adding several items to the shopping cart, the host server crashes. The client is automatically redirected to another server by a proxy, but the shopping cart is now empty.

Which WebLogic Server feature would you enable to remedy this situation?

  1. Application Persistence

  2. Message Persistence

  3. Session Replication

  4. Dynamic Failover

  5. Stateful Pooling

Answer: C

Explanation: In order for a cluster to provide high availability it must be able to recover from service failures.

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#39;s request accordingly.

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

Question No: 47

Which three statements are true about the Change Center in administration console?

  1. The Change Center has a link to view the changes made so far.

  2. The Change Center is available only in a Production Mode domain.

  3. The Change Center has a link to view any servers that need to be restarted.

  4. After activating the changes to a server#39;s configuration, you must always restart that server.

  5. In a Development Mode domain, the configuration lock can be acquired automatically.

  6. Changes must always be activated before they can be undone.

    Answer: A,C,F

    Explanation: A: You can view any changes that you have saved, but not yet activated, by clicking the View Changes and Restarts link in the Change Center.

    C: The View Changes and Restarts link presents two tabs, Change List and Restart Checklist:

    • The Change List tab presents all changes that have been saved, but not yet activated.

    • The Restart Checklist lists all servers for which non-dynamic changes have been activated, but which require restarts before the changes become effective.

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

      Note: To change a production domain’s configuration, you must:

      1. Locate the Change Center in the upper left of the Administration Console screen.

      2. Click the Lock amp; Edit button to lock the configuration edit hierarchy for the domain.

      3. Make the changes you desire on the relevant page of the Console. Click Save on each page where you make a change.

      4. When you have finished making all the desired changes, click Activate Changes in the Change Center.

        You can revert any pending (saved, but not yet activated) changes by clicking Undo All Changes in the Change Center. You can revert any individual change by going to the appropriate page in the Administration Console and restoring the attribute to its previous value.

        Reference: Using the Change Center


        Question No: 48

        Identify two methods for utilizing WebLogic Server#39;s production redeployment feature.

        1. Specify a version identifier when deploying the application.

        2. Include a version identifier in the application#39;s manifest file.

        3. Provide a version identifier when running the Plan Generator tool.

        4. Include a unique context root in the application#39;s descriptor files.

Answer: A,B

Explanation: A: If you are testing the production redeployment feature, or you want to use production redeployment with an application that does not include a version string in the manifest file, specify a unique version string by using the -appversion option when deploying or redeploying an application

B: To assign a version identifier to an application, BEA recommends that you store a unique version string directly in the MANIFEST.MF file of the EAR or WAR being deployed.

Reference: Redeploying Applications in a Production Environment, Specifying an application version identifier


Question No: 49

Identify four attributes of a JDBC data source.

  1. URL

  2. Targets

  3. JNDI Name

  4. Delivery Mode

  5. Database Driver

  6. Server Log

Answer: A,B,C,E

Explanation: A: When creating a JDBC data source using the Administration Console, you are prompted to select a JDBC driver. The Administration Console provides the driver class name and helps you construct the URL as required by the driver.

B: JDBC Data Source: Targets. Use this page to select the servers or clusters on which you would like to deploy this JDBC data source.

C: JNDI Name, The JNDI path to where this data source is bound. By default, the JNDI name is the name of the data source.

E: When deciding which JDBC driver to use to connect to a database, you should try drivers from various vendors in your environment. In general, JDBC driver performance is dependent on many factors, especially the SQL code used in applications and the JDBC driver implementation.

Reference: Configuring and Managing WebLogic JDBC, Understanding JDBC Data Sources

Question No: 50

Identify two reasons for defining machines and assigning servers to them in Weblogic Server.

  1. A machine can be the proxy to a cluster.

  2. A machine definition is required to configure the Node Manager.

  3. To reference an instance of WebLogic Server, you must know its machine and port.

  4. Machine is a required organizational unit. A domain contains machines and machines contain servers.

  5. WebLogic Server uses server machine assignments to help it choose servers in a cluster on which to replicate session state.

  6. The machine#39;s Cluster Weight attribute may be used by load balancers to help them determine how often to send requests to servers assigned to that machine.

Answer: B,E

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

100% Dumps4cert Free Download!
Download Free Demo:1z0-102 Demo PDF
100% Dumps4cert Free Guaranteed!
1z0-102 Dumps

Dumps4cert ExamCollection Testking
Lowest Price Guarantee Yes No No
Up-to-Dated Yes No No
Real Questions Yes No No
Explanation Yes No No
Free VCE Simulator Yes No No
Instant Download Yes No No

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.