Oracle 1Z0-102 Online Practice Questions and Exam Preparation

Oracle 1Z0-102 Online Questions & Answers

• Question 21:

  You are creating a new domain by using the Configuration Wizard, based solely on the Basic WebLogic Server Domain product (no template). Select three resources that you can create while still in the Configuration Wizard.

  A. Administration Server
  B. Managed Server
  C. Data Server
  D. JMS Server
  E. Cluster
  F. Domain Log
  A. Administration Server
  B. Managed Server
  E. Cluster

  ---

  A: The Configure the Administration Server window prompts you to define the configuration information for the Administration Server, including: Administration Server name Listen address Nonsecure and secure (optional) listen ports

  B: The Configure Managed Servers window prompts you to define the configuration information for one or more Managed Servers, including: Managed Server name Listen address Nonsecure and secure (optional) listen ports

  E: The Configure Clusters window prompts you to define the configuration information for one or more clusters, including: Cluster name Multicast address and port Cluster address that identifies the Managed Servers in the cluster Frontend host if you are using a proxy server or a firewall. Frontend HTTP port if you are using a proxy server or a firewall. Reference: To create a custom domain with Managed Servers, a cluster, and application services http://docs.oracle.com/cd/E13196_01/ platform/docs81/confgwiz/tutorials.html

• Question 22:

  You monitor a running JMS topic with the console and note the following values:

  Consumers Current = 3 Message Current = 1 Message Pending = 0 These values do not change for several minutes. Which is the most plausible ?

  A. Production on the topic has been paused.
  B. A message arrived after a durable subscribe disconnected from the topic.
  C. One of the consumers received a message but did not acknowledge it.
  D. None of the consumers are durable subscribes.
  B. A message arrived after a durable subscribe disconnected from the topic.

  ---

  For durable subscriptions, WebLogic JMS stores a message in a persistent file or database until the message has been delivered to the subscribers or has expired, even if those subscribers are not active at the time that the message is delivered.

  Note #1: Durable subscriptions means that weblogic server will store the messages in a persistent store (i.e a file-store or a JDBC-store) until those messages are delivered to the subscribers/listener. This technic helps weblogic server to make sure that the messages get delivered even if those subscribers/listeners are not active at the time that the message is getting delivered.

  As all of us know that in Topic's the senders/producers just send the messages to the topic and the receivers/listeners have subscribe them self to get those messages, hence senders/producers does not have any concern if the messages are been received or not. However with this feature weblogic make sure all the subscribers would get the messages as the messages gets stored in a persistence store.

  Note #2:

  *

  Consumers Current Count: Current number of consumers accessing this destination

  *

  MessagesCurrentCount: The current number of messages in the destination. This does not include the pending messages.

  *

  MessagesPendingCount: The number of pending messages in the destination.

  Pending messages are over and above the current number of messages. A pending message is one that has either been sent in a transaction and not committed, or that has been received and not committed or acknowledged.

  Incorrect answers:

  A: When a topic is paused for production, it prevents any new message production operations from both new and existing producers attached to that topic.

  C: There is no pending message here. So there cannot be a message that a consumer has not acknowledged.

  D: Non-durable messages are not stored.

  Reference: eDocs Home > BEA WebLogic Server 8.1 Documentation > Programming WebLogic JMS > Developing a WebLogic JMS Application, Setting Up Durable Subscriptions

• Question 23:

  Consider the following excerpt from mod_wl_ohs.conf:

  WebLogicCluster 192.168.13.1:7001, 192.168.13.2:7001,192.168.13.2:7001

  SetHandler weblogic-handler

  Assuming that this is a valid is a valid configuration, which two conclusions can you make?

  A. A web application name "welcome" is configured to use session replication.
  B. A web application that uses the paths "welcome" is targeted to the cluster.
  C. The proxy server will ignore any requests that contain the name "welcome."
  D. The proxy server is listening on the host name "welcome."
  E. A cluster exists that consists of at least two managed servers.
  F. All cluster members are running on the same machine.
  B. A web application that uses the paths "welcome" is targeted to the cluster.
  E. A cluster exists that consists of at least two managed servers.

  ---

  B: To proxy requests by path, use the Location block and the SetHandler statement. When to use

  Use to apply directives to content that lives outside the filesystem. For content that lives in the filesystem, use and . An exception is , which is an easy way to apply a configuration to the entire server.

  For all origin (non-proxy) requests, the URL to be matched is a URL-path of the form /path/. No scheme, hostname, port, or query string may be included. For proxy requests, the URL to be matched is of the form scheme://servername/path, and you must include the prefix.

  E: Add an IfModule block that defines one of the following:

  For a non-clustered WebLogic Server instance:

  The WebLogicHost and WebLogicPort parameters.

  For a cluster of WebLogic Servers instances:

  The WebLogicCluster parameter.

  If you are proxying requests by MIME type to a cluster of WebLogic Servers, use the WebLogicCluster parameter.

  For example:

  WebLogicCluster

  w1s1.com:7001,w1s2.com:7001,w1s3.com:7001

  Note #1: The ... section is used to mark directives that are conditional on the presence of a specific module. The directives within an section are only processed if the test is true. If test is false, everything

  between the start and end markers is ignored.

  The test in the section directive can be one of two forms:

  module name

  !module name

  Note #2:

  Directive

  Description: Applies the enclosed directives only to matching URLs Syntax: ... Context: server config, virtual host

  Status: Core

  Module: core

  The directive limits the scope of the enclosed directives by URL. It is similar to the directive, and starts a subsection which is terminated with a directive. sections are processed in the order they

  appear in the configuration file, after the sections and .htaccess files are read, and after the sections.

  sections operate completely outside the filesystem. This has several consequences. Most importantly, directives should not be used to control access to filesystem locations. Since several different URLs may map to

  the same filesystem location, such access controls may by circumvented. Reference: eDocs Home > BEA WebLogic Server 8.1 Documentation > Using Web Server Plug- Ins with WebLogic Server > Installing and Configuring the Apache

  HTTP Server Plug-In

• Question 24:

  Identify two supported methods of deploying a JMS module to a domain.

  A. Create a module by using the administration console.
  B. Load a module into the WebLogic database.
  C. Include a module file within a web application archive.
  D. Include a module file within an enterprise application archive.
  E. Define a module within an existing JDBC module.
  A. Create a module by using the administration console.
  D. Include a module file within an enterprise application archive.

  ---

  A: Main Steps for Creating Packaged JMS Application Modules

  Follow these steps to configure a packaged JMS module:

  If necessary, create a JMS server to target the JMS module to, as explained in "Configure JMS Servers" in the Administration Console Online Help. Create a JMS system module and configure the necessary resources, such as queues or

  topics, as described in "Configure JMS system modules and add JMS resources" in the Administration Console Online Help.

  The system module is saved in config\jms subdirectory of the domain directory, with a "- jms.xml" suffix.

  Copy the system module to a new location, and then:

  Give the module a unique name within the domain namespace.

  Delete the JNDI-Name attribute to make the module application-scoped to only the application. Add references to the JMS resources in the module to all applicable J2EE application component's descriptor files, as described in Referencing a

  Packaged JMS Application Module In Deployment Descriptor Files. Package all application modules in an EAR, as described in Packaging an Enterprise Application With a JMS Application Module.

  Deploy the EAR, as described in Deploying a Packaged JMS Application Module.

  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 weblogicapplication.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.

  Reference: Packaging JMS Application Modules In an Enterprise Application

• Question 25:

  A managed server, myserver1, has a boot.properties file in the security directory. It was started with the startManageWeblogic.sh script(.cmd in windows) and his boot.properties file was used for its startup credentials.

  You just used the administration console to change all administrator passwords. To continue using boot.properties, what can you do?

  A. This is not possible. A boot.properties file can be used only with the Administration Server.
  B. Delete boot.properties. In the administration console, under the myserver configuration, select Generate Boot Identity file.
  C. You need not do anything- The password in boot .properties was automatically updated by administration console when you changed the password.
  D. Edit boot.propetties. Type over the encrypted password with the new password in clear text. The next time myserver1 is started, it will encrypt the password in the file.
  E. Delete boot .properties. Use the WLST encrypt () command to create a new boot.properties file containing the new password. Copy that file into the security directory of myserver1
  D. Edit boot.propetties. Type over the encrypted password with the new password in clear text. The next time myserver1 is started, it will encrypt the password in the file.

  ---

  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

• Question 26:

  Indentify two attributes of a JMS server.

  A. Target
  B. Persistent Store
  C. Destination
  D. Connection Factory
  E. Store and Forward
  A. Target
  B. Persistent Store

  ---

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

  Which three statements are true about deployment plans?

  A. A plan is an XML file.
  B. A plan is packaged within an application archive.
  C. You can generate a new plan with the administration console.
  D. A plan is a required to deploy EJB applications and modules.
  E. A plan may override values in an application's deployment descriptors.
  F. A single application deployment can be associated with multiple plans.
  A. A plan is an XML file.
  C. You can generate a new plan with the administration console.
  E. A plan may override values in an application's deployment descriptors.

  ---

  A: A deployment plan is an XML document that defines an application'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. Incorrect answers:

  B: A deployment plan resides outside of an application's archive file.

  Reference: Overview of WebLogic Server Application Development, Deployment Plans

• Question 28:

  You wish to restrict access to a JMS queue so that only specific accounts may receive messages from the queue. Identify two steps that, when performed together, implement this security requirement.

  A. Create a policy for queue's URL pattern.
  B. Add a policy to the queue and associate it with a role.
  C. Configure an identify assertion provider.
  D. Acquire the domain configuration lock.
  E. Create a global role and assign users to it.
  B. Add a policy to the queue and associate it with a role.
  E. Create a global role and assign users to it.

  ---

  B:

  Security policy for a JMS Queue (Resource Level).

  When you define a security policy for an individual destination on a JMS server, you can protect all operations of the destination.

  a.

  Login into the Admin server console > Navigate to the Queue that needs to be secured.

  b.

  Click on the security tab > Policies sub tab.

  You can see a small drop down list, which lists the set of the operations that can be protected.

  c.

  Click Add Conditions to add the policy conditions.

  d.

  From the predicate list, specify the policy conditions.

  e.

  Specify the role (the global created in E below) which needs to have the access permissions for the JMS Queue. Click Add > Finish.

  E: Create a Global Role and assign the appropriate user accounts to it.

  Note: There are two ways of securing the JMS resources.

  1.

  At the JMSModule level (Group level), where a single security policy is specified for a set of JMS resources.

  2.

  At the individual JMS resource level, which provides much more grained controlled over the operations that you want to secure.

  Reference: SECURING WEBLOGIC JMS RESOURCES

• Question 29:

  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.
  C. The console allows you to add new and existing servers to a cluster.
  E. You cannot remove a server that is running from a cluster.

  ---

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

  Refer to the Exhibit.

  

  You use the Start button in the administration console to start managed2 successfully. Which two statements must be true?

  A. Managad2 is part of a cluster.
  B. The Administration Server is running.
  C. Managed2 has applications deployed to it.
  D. The Node Manager for machine2 is configured and running.
  E. The Node Manager for the Administration Server machine is configured and running.
  B. The Administration Server is running.
  D. The Node Manager for machine2 is configured and running.

  ---

  B: The administration server must be running.

  Note: A WebLogic Server administration domain is a logically related group of WebLogic Server resources. Domains include a special WebLogic Server instance called the Administration Server, which is the central point from which you

  configure and manage all resources in the domain.

  D:

  Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your

  WebLogic Server environment hosts applications with high availability requirements. 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. Node Manager must run on each computer that hosts WebLogic Server instances -- whether

  Administration Server or Managed Server -- that you want to control with Node Manager.

  Incorrect answers:

  A: We could not know if Managed2 is in a cluster or not.

  C: We could not know if Managed2 has deployed applications.