Oracle 1Z0-102 Online Practice Questions and Exam Preparation

Oracle 1Z0-102 Online Questions & Answers

• Question 71:

  Which three statements are true about the administration console?

  A. The administration console cannot be disabled.
  B. The context path of the administration console may be changed.
  C. The administration console may be extended.
  D. If a domain is in Development Mode, the administration console no longer requires an administration-level user when logging in.
  E. If a domain is in Production Mode, access to the administration console must be made through secure port.
  F. If the domain's Administration Port is enabled, access to the administration console must be made only through that port.
  B. The context path of the administration console may be changed.
  C. The administration console may be extended.
  F. If the domain's Administration Port is enabled, access to the administration console must be made only through that port.

  ---

  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 do- main for use in another context, such as migrating a domain containing an application under development to a pro- duction

  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.

  Incorrect answers:

  A: Exposing the console in your production environment might be security issue. In those cases you can either dis- able the console or hide it. Needless to say if you disable the console then your only option is to depend on com- mand-line and scripting tools for any other administration activity or to even enable the console back. But hiding will provide a level or security.

  To disable the console:

  In the admin console navigate to --> General --> Advanced Options --> Console Enabled. De-select that option to disable console (restart required).

  To hide the cosole:

  E: Access through a secure port is recommended, but not required:

  The administration port requires all communication to be secured using SSL. By default, all servers in a do- main use demonstration certificate files for SSL, but these certificates are not appropriate for a production environment.

  Reference: Administration Console Online Help, Advanced Configuration Options Reference: Extending the Administration Console for Oracle WebLogic Server 11g Release 1

• Question 72:

  Which two are typically found in the WEB-INF folder of a Java web application?

  A. the web application HTML and JSP files
  B. the classes directory containing the compiled classes
  C. the web.xml deployment descriptor
  D. the weblogicserver.xml deployment descriptor
  B. the classes directory containing the compiled classes
  C. the web.xml deployment descriptor

  ---

  The WEB-INF directory contains the deployment descriptors for the Web application (web.xml (C) and weblogic.xml) and two subdirectories for storing compiled Java classes (B) and library JAR files. These subdirectories are respectively

  named classes and lib. JSP taglibs are stored in the WEB-INF directory at the top level of the staging directory. The Java classes include servlets, helper classes and, if desired, precompiled JSPs.

  Reference:

  Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server, Creating and Configuring Web Applications

• Question 73:

  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?

  A. The web application is now "Active."
  B. The command creates new deployment plan called plan.xml.
  C. In the administration console, the name of this deployment is sales.war.
  D. The web application has been targeted to managed1, managed2, and the Administration Server.
  E. You can view the status of the deployment by sending a message to the object named progress.
  A. The web application is now "Active."
  E. You can view the status of the deployment by sending a message to the object named progress.

  ---

  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)

  Note:

  Syntax

  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.

  Incorrect answers:

  B: PlanPath is not created by default. The option createPlan is a Boolean value indicating that user would like to create a default plan. This option defaults to false.

  * planPath Optional. Name of the deployment plan file. The filename can be absolute or relative to the application directory. This argument defaults to the plan/ plan.xml file in the application directory, if one exists.

  C: sales.war is not the name of the deployment.

  * path

  Name of the application directory, archive file, or root of the exploded archive directory to be deployed.

  Reference: WebLogic Scripting Tool, WLST Command and Variable Reference

• Question 74:

  You create a system-wide JMS module named Payroll-JMS and set its default target to an existing cluster in your domain named PayrollCluster. Next, you add a standard JMS topic to Payroll-JMS. To which are you permitted to target this topic?

  A. the entire PayrollCluster
  B. any single JMS server in the domain
  C. any combination of member servers in Payrollcluster
  D. several JMS servers targeted to PayrollCluster
  B. any single JMS server in the domain

  ---

  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

• Question 75:

  Which two statements are true about java EE shared libraries?

  A. A shared library cannot be deployed to a cluster.
  B. An application that is targeted to server1 can use a shared library that is targeted to server 2.
  C. Multiple versions of the same shared library can be deployed and be active at the same time
  D. A shared library is referenced through an application's deployment descriptor.
  C. Multiple versions of the same shared library can be deployed and be active at the same time
  D. A shared library is referenced through an application's deployment descriptor.

  ---

  C: If more than one copy of myLibrary is registered, WebLogic Server selects the library with the highest specification version. If multiple copies of the library use the selected specification version, WebLogic Server selects the copy having the highest implementation version.

  D: A Java EE application can reference a registered shared Java EE library using entries in the application's weblogic-application.xml deployment descriptor. Reference: Referencing Shared Java EE Libraries in an Enterprise Application http://docs.oracle.com/cd/E12840_01/wls/docs103/programming/libraries.html

• Question 76:

  The computer that the Administration Server was running on has crashed and cannot be restarted. Which three steps are required to bring up the Administration Server on the backup computer?

  A. Move the crashed computer's IP address to the backup computer.
  B. Have WebLoqic Server installed on the backup computer.
  C. Have a copy of the configuration and security files of the domain on the backup computer.
  D. Shut down the managed servers of the domain.
  E. Start the Administration Server on the backup computer.
  B. Have WebLoqic Server installed on the backup computer.
  C. Have a copy of the configuration and security files of the domain on the backup computer.
  E. Start the Administration Server on the backup computer.

  ---

  If a machine crash prevents you from restarting the Administration Server on the same machine, you can recover management of the running Managed Servers as follows:

  (B) 1. Install the WebLogic Server software on the new administration machine (if this has not already been done).

  2. Make your application files available to the new Administration Server by copying them from backups or by using a shared disk. Your application files should be available in the same relative location on the new file system as on the file system of the original Administration Server. (C) 3. Make your configuration and security data available to the new administration machine by copying them from backups or by using a shared disk. For more information, refer to Directory and File Backups for Failure Recovery.

  (E) 4. Restart the Administration Server on the new machine.

  Reference: Avoiding and Recovering From Server Failure, Restarting an Administration Server on Another Machine

• Question 77:

  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?

  A. Application Persistence
  B. Message Persistence
  C. Session Replication
  D. Dynamic Failover
  E. Stateful Pooling
  C. Session Replication

  ---

  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's request accordingly.

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

• Question 78:

  Which three statements are true about the Node Manager?

  A. The Node Manager can restart the Managed Serves that have failed.
  B. The Node Manager should be run as either a daemon or a service so that if the host computer is rebooted, the Node Manager will also be automatically started.
  C. The Node Manager runs on a different host from the Managed Server it is controlling.
  D. The Node Manager can start a Managed Server the first time the Managed Server starts if the Administration Server is unavailable because MSI mode is enabled by default.
  E. The Node Manager allows you to start Managed Servers from the administration console.
  A. The Node Manager can restart the Managed Serves that have failed.
  B. The Node Manager should be run as either a daemon or a service so that if the host computer is rebooted, the Node Manager will also be automatically started.
  E. The Node Manager allows you to start Managed Servers from the administration console.

  ---

  A, E: Node Manager enables you to perform these tasks:

  *

  Start and stop remote Managed Servers. (E)

  *

  Monitor the self-reported health of Managed Servers and automatically kill server instances whose health state is "failed".

  *

  Automatically restart Managed Servers that have the "failed" health state, or have shut down unexpectedly due to a system crash or reboot. (A)

  B: The WebLogic Server installation process installs Node Manager to run as an operating system service: a daemon on UNIX machines, or a Windows service on Windows-based machines. An operating system service starts up automatically each time the operating system boots. A key Node Manager feature is the ability to restart Managed Servers after a failure. If the failure is a machine crash, running Node Manager as a service ensures that Node Manager starts up automatically when the machine reboots, and is available to restart Managed Servers on that machine.

  E: Requests from the Administration Console (or JMX utilities such as weblogic.Admin) to start a Managed Server using Node Manager are issued to the Administration Server for the domain that contains the Managed Server.

  Reference: Configuring and Managing WebLogic Server, Overview of Node Manager

• Question 79:

  As an Oracle WebLogic Server administrator, you are given an EAR file application to deploy. Identity three reasons for creating an EAR file first.

  A. After the .ear file has been deployed, the developer will not have to ask for your assistance to deploy it again.
  B. The EAR file is created to avoid namespace clashes in the Java code.
  C. The EAR file can contain multiple WAR, EAR, and other resources to easily bundle together.
  D. The EAR file is required if you are deploying an application.
  E. The EAR file can declare application-wide security roles definitions.
  A. After the .ear file has been deployed, the developer will not have to ask for your assistance to deploy it again.
  B. The EAR file is created to avoid namespace clashes in the Java code.
  E. The EAR file can declare application-wide security roles definitions.

  ---

  E: An EARfile contains:

  * Web module

  A WAR file containing the view logics like JSPs, Servlets, Html contents. Every web module must have one Web Deployment descriptor placed inside "WEB-INF/ web.xml"

  web.xml is a J2EE standard deployment descriptor. Among other settings, it has a set of elements for configuring security for the web application.

  Note:

  *

  An EAR file provides a convenient way to bundle up all pieces of a J2EE application. It may contain Java Module, WAR Module or an EJB Jar module. An EAR can contain at least any one of these modules. EAR may contain more Modules as well.

  *

  To bring your portal online in a production environment, it is first necessary to prepare your portal application. Typical preparation steps include modifying deployment descriptors for the product, building the Enterprise archive (EAR) with all its pre-compiled classes, and deciding if you want to compress that EAR into an archive or leave it exploded.

  Reference: Preparing and Deploying the EAR File

• Question 80:

  The project's architect has provided you with a design diagram that identifies the key components of the new insurance system. From the diagram, you can clearly see that JMS will be used as the communication channel between several applications. Identify four tasks that you may need to perform to support this design.

  A. Create a JMS server
  B. Create a JMS message template
  C. Add JMS destinations to a JMS module
  D. Add a JMS module to a JMS factory
  E. Target JMS destinations to JMS servers
  F. Target a JMS server to a WebLogic Server
  G. Target a JMS module to a JMS store
  A. Create a JMS server
  C. Add JMS destinations to a JMS module
  E. Target JMS destinations to JMS servers
  F. Target a JMS server to a WebLogic Server

  ---

  A: If necessary, create a JMS server to target the JMS module.

  F: Target the JMS Server to a weblogic server

  Note: The major components of the WebLogic JMS Server architecture:

  *

  JMS servers that can host a defined set of modules and any associated persistent storage that reside on a WebLogic Server instance.

  *

  JMS modules contains configuration resources (such as queues, topics, and connections factories) and are defined by XML documents that conform to the weblogic-jms.xsd schema.

  *

  Client JMS applications that either produce messages to destinations or consume messages from destinations.

  *

  JNDI (Java Naming and Directory Interface), which provides a resource lookup facility. JMS resources such as connection factories and destinations are configured with a JNDI name. The runtime implementations of these resources are then bound into JNDI using the given names.

  *

  WebLogic persistent storage (file store or JDBC-accessible) for storing persistent message data.

  Reference: Understanding WebLogic JMS