Question 1

Which WebLogic optimization allows one non-XA resource to participate in a distributed transaction?

Accepted Answer

B

Explanation: http://my-java-planet.blogspot.com/2014/04/which-weblogic-optimization-allows-one.html

Question 2

What are the three steps you should take to tune a JDBC Connection pool in WebLogic from the initial settings in a production environment?

Accepted Answer

A, C, E

Explanation: A: * Troubleshooting Slow Response Time from the Client and Low Database Usage These symptoms are usually caused by a bottleneck upstream of the database, perhaps in the JDBC connectionpooling. Monitor the active JDBC connections in the WebLogic Console and watch for excessive waiters and wait times; increase the pool size, if necessary. * Attribute: Maximum Capacity Maximum number of physical database connections that this connection pool can contain. Different JDBC Drivers and database servers may limit the number of possible physical connections. C: Attribute: Statement Cache Size The algorithm used to maintain the statement cache: LRU - After the statementCacheSize is met, the Least Recently Used statement is removed when a new statement is used. Fixed - The first statementCacheSize number of statements is stored and stay fixed in the cache. No new statements are cached unless the cache is manually cleared. E: If the queue appears starved but adding execute threads does not improve performance, there may be resource contention. Because CPU utilization is low, the threads are probably spending much of their time waiting for some resource, quite often a database connection. Use the JDBC monitoring facilities in the console to check for high levels of waiters or long wait times. Adding connections to the JDBC connection pool may be all that is required to fix the problem. Note: * If you had a JDBC connection pool where the Initial Capacity and Maximum Capacity attributes were different, you might want to create a gauge monitor to monitor the maximum and minimum number of connections. By setting the Threshold Low value to be one less than the Initial Capacity, your gauge monitor trapcould monitor the ActiveConnectionsCurrentCount attribute of the JDBCDataSourceRuntime MBean and alert you whenever the number of active connections are less than the Initial Capacity (which might indicate database connectivity problems).

Question 3

Identify four valid requests in a RESTful service using JAX-RS.

Accepted Answer

A, B, D, E

Explanation: The following principles encourage RESTful applications to be simple, lightweight, and fast: * Resource identification through URI * Uniform interface: Resources are manipulated using a fixed set of four create, read, update, delete operations: PUT, GET, POST, and DELETE. PUT creates a new resource, which can be then deleted by using DELETE. GET retrieves the current state of a resource in some representation. POST transfers a new state onto a resource. See Responding to HTTP Methods and Requests for more information. * Self-descriptive messages * Stateful interactions through hyperlinks Reference: The Java EE 6 Tutorial, What Are RESTful Web Services?

Question 4

A customer needs to ensure that the number of threads servicing an application does not exceed the
number of database connections available to the application.
What step must you take to address this situation?

Accepted Answer

B

Explanation: To manage work in your applications, you define one or more of the following Work Manager components: Fair Share Request Class: Response Time Request Class: Min Threads Constraint: Max Threads Constraint: Capacity Constraint Context Request Class: Note: * max-threads-constraint—This constraint limits the number of concurrent threads executing requests from the constrained work set. The default is unlimited. For example, consider a constraint defined with maximum threads of 10 and shared by 3 entry points. The scheduling logic ensures that not more than 10 threads are executing requests from the three entry points combined. A max-threads-constraint can be defined in terms of a the availability of resource that requests depend upon, such as a connection pool. A max-threads-constraint might, but does not necessarily, prevent a request class from taking its fair share of threads or meeting its response time goal. Once the constraint is reached the server does not schedule requests of this type until the number of concurrent executions falls below the limit. The server then schedules work based on the fair share or response time goal. * WebLogic Server prioritizes work and allocates threads based on an execution model that takes into account administrator-defined parameters and actual run-time performance and throughput. Administrators can configure a set of scheduling guidelines and associate them with one or more applications, or with particular application components. * WebLogic Server uses a single thread pool, in which all types of work are executed. WebLogic Server prioritizes work based on rules you define, and run-time metrics, including the actual time it takes to execute a request and the rate at which requests are entering and leaving the pool. The common thread pool changes its size automatically to maximize throughput. The queue monitors throughput over time and based on history, determines whether to adjust the thread count. For example, if historical throughput statistics indicate that a higher thread count increased throughput, WebLogic increases the thread count. Similarly, if statistics indicate that fewer threads did not reduce throughput, WebLogic decreases the thread count. This new strategy makes it easier for administrators to allocate processing resources and manage performance, avoiding the effort and complexity involved in configuring, monitoring, and tuning custom executes queues. Reference: Using Work Managers to Optimize Scheduled Work

Question 5

You installed WebLogic, SOA Suite, and Oracle Service Bus on a machine and want to use the WebLogic Node Manger to start servers for each product. Which statement is true?

Accepted Answer

B

Explanation: Note: * In managing multiple servers, Node Manager uses multiple configuration files and outputs log files to multiple directories. * nodemanager.domains This file contains mappings between the names of domains managed by Node Manager and their corresponding directories. * Node Manager in the WebLogic Server Environment https://kxbjsyuhceggsyvxdkof.supabase.co/storage/v1/object/public/file-images/1Z0-599/page_28_img_1.jpg Reference; Node Manager Administrator's Guide for Oracle WebLogic Server 12c

Question 6

You deployed a Java EE Shared Library and want to use it from an application that is also deployed on
the same cluster.
Which two manifest attributes must be specified at a minimum with corresponding values in the
deployment descriptor of the application that requires

Accepted Answer

A, C

Explanation: When an application that

Question 7

Which four steps are involved to use Active Cache Dependency Injection in a WebLogic Java EE application?

Accepted Answer

A, B, C, E

Explanation: Note: * Example If you have additional Coherence caches running on Coherence*Web, then you must merge the cache configuration information (typically defined in the coherence-cache-config.xml file) with the session configuration contained in the session-cache-config.xml file. The cache and session configuration must be consistent across WebLogic Server and Coherence cache servers.

Question 8

When you use WebLogic Management Pack EE, which three operations are enabled compared to managing WebLogic Server only through web console?

Accepted Answer

A, B, E

Explanation: The WebLogic Server Management Pack EE greatly improves application performance by providing unique functionality to automatically detect performance bottlenecks; quickly diagnose these performance problems, and identify their root cause. Key application performance management features of the pack include the following: * (A) Manage multiple farms and WebLogic Domains centrally * Monitor Oracle Coherence Cluster – including all nodes within a cluster, all caches, services, connection managers and connections * Monitor middleware availability and performance out-of-box; track such data historically, and receive notifications of potential problems * Obtain real-time, in-depth JVM diagnostics without instrumentation overhead * Trace transactions across containers as well as to the database * (E) Analyze call paths and dependencies via graphical, architecture views * (E) Automatically discover and model dependencies between Java components, frameworks, and web services Reference: Weblogic Server Management Pack Enterprise Edition

Question 9

A WebLogic team is developing an enterprise application from their desktop WebLogic environment.
All development systems are connected to the same eight data sources for testing.
As a WebLogic Administrator supporting this team, which two actions should you perform to free the
developers from creating and configuring all the data sources on their desktop WebLogic
environment?

Accepted Answer

E

Explanation: WebLogic Administrators typically use the Administration Console or the WebLogic Scripting Tool (WLST) to create and deploy (target) JDBC modules. Note: * (not A) Domain template—defines the full set of resources within a domain, including infrastructure components, applications, services, security options, and general environment and operating system options. * Extension template—defines the applications and services that you can add to an existing domain, including product component functionality and resources such as JDBC or JMS. * (not B) Each domain describes its configuration in an XML document that is located in the domain’s configuration directory. At run time, each WebLogic Server instance in a given domain creates an in- memory representation of the configuration described in this document. The central configuration file for a domain is DOMAIN_NAME/config/config.xml. This file specifies the name of the domain and the configuration of each server instance, cluster, resource, and service in the domain. The file includes

Question 10

A customer is developing a custom application that involves a multistep provisioning process for a
new account. There is a custom Java client application that is generating multiple JMS messages as
part of the process and sending them to the WebLogic tier where they are processed.
Which three steps must you take to implement the solution to allow for scalability and parallel
processing of multiple simultaneous provisioning requests while ensuring messages for an individual
process are not delivered out of order?

Accepted Answer

B, C, D

Explanation: C: Message Unit-of-Order is a WebLogic Server value-added feature that enables a stand-alone message producer, or a group of producers acting as one, to group messages into a single unit with respect to the processing order. This single unit is called a Unit-of-Order and requires that all messages from that unit be processed sequentially in the order they were created. D Transactions required for parallel processing. Incorrect: A: Many applications need an even more restricted notion of a group than provided by the Message Unit-of-Order (UOO) feature. If this is the case for your applications, WebLogic JMS provides the Unit-of-Work (UOW) Message Groups, which allows applications to send JMS messages, identifying some of them as a group and allowing a JMS consumer to process them as such. For example, an JMS producer can designate a set of messages that need to be delivered to a single client without interruption, so that the messages can be processed as a unit. Further, the client will not be blocked waiting for the completion of one unit when there is another unit that is already complete. Note: * WebLogic JMS defines two default connection factories, which you can look up using the following JNDI names: weblogic.jms.ConnectionFactory weblogic.jms.XAConnectionFactory Reference: Using Message Unit-of-Order

Question 11

How can you configure High Availability for interacting with a non-Oracle database using WebLogic?

Accepted Answer

C

Explanation: Note: * A multi data source can be thought of as a pool of data sources. Multi data sources are best used for failover or load balancing between nodes of a highly available database system, such as redundant databases or Oracle Real Application Clusters (Oracle RAC). * (not B) A single GridLink data source provides connectivity between WebLogic Server and an Oracle Database service, which may include multiple Oracle RAC clusters * High Availability Storage Solutions If you have applications that need access to persistent stores that reside on remote machines after the migration of a JMS server or JTA transaction log, then you should implement one of the following highly-available storage solutions: / File-based stores (default or custom)—Implement a hardware solution, such as a dual-ported SCSI disk or Storage Area Network (SAN) to make a file store available from shareable disks or remote machines. / JDBC-accessible stores—Configure a JDBC store or JDBC TLOG store and use JDBC to access this store, which can be on yet another server. Applications can then take advantage of any high- availability or failover solutions offered by your database vendor. In addition, JDBC stores support GridLink data sources and multi data sources, which provide failover between nodes of a highly available database system, such as Oracle Real Application Clusters (Oracle RAC). Reference: Oracle Fusion Middleware Configuring Server Environments for Oracle WebLogic Server 12c, High Availability Storage Solutions

Question 12

In WebLogic 10.3.6 and 12c, transaction logs can optionally write to a JDBC store instead of a file store on the file system. Identify the three benefits as a result of this capability.

Accepted Answer

A, C, D

Explanation: Comparing File Stores and JDBC-accessible Stores The following are some similarities and differences between file stores and JDBC-accessible stores: * (A) JDBC stores may make it easier to handle failure recovery since the JDBC interface can access the database from any machine on the same network. With the file store, the disk must be shared or migrated. * The default persistent store can only be a file store. Therefore, a JDBC store cannot be used as a default persistent store. * Both have the same transaction semantics and guarantees. As with JDBC store writes, file store writes are guaranteed to be persisted to disk and are not simply left in an intermediate (that is, unsafe) cache. * Both have the same application interface (no difference in application code). * (not B, not E) All things being equal, file stores generally offer better throughput than a JDBC store. / If a database is running on high-end hardware with very fast disks, and WebLogic Server is running on slower hardware or with slower disks, then you may get better performance from the JDBC store. * File stores are generally easier to configure and administer, and do not require that WebLogic subsystems depend on any external component. * File stores generate no network traffic; whereas, JDBC stores generate network traffic if the database is on a different machine from WebLogic Server. Reference: Configuring Server Environments for Oracle WebLogic Server 12c, Comparing File Stores and JDBC-accessible Stores

Question 13

A highly available WebLogic cluster in UNIX is configured for automatic server migration. Node
Managed is configured on both machines to start managed servers.
How should you simulate a managed server failure to test whether automatic server migration is
working?

Accepted Answer

A

Explanation: Note: * It is recommended that you shutdown WebLogic Server instances through the Administration Console. * If automatic server migration is enabled, the servers are required to contact the cluster leader and renew their leases periodically. Servers will shut themselves down if they are unable to renew their leases. The failed servers will then be automatically migrated to the machines in the majority partition.

Question 14

You are configuring a JMS server with a need for load balancing the messages. To achieve the load balance you should _______and _______.

Accepted Answer

B, C

Explanation: Load Balancing for JMS WebLogic Server JMS supports server affinity for distributed JMS destinations and client connections. (B, not A) By default, a WebLogic Server cluster uses the round-robin method to load balance objects. To use a load balancing algorithm that provides server affinity for JMS objects (not D), you must configure the desired method for the cluster as a whole. Reference: Using Clusters for Oracle WebLogic Server 12c , Load Balancing for JMS

Question 15

Which option must you choose to configure Node Manager on a machine (server or zone)?

Accepted Answer

B

Explanation: 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. Reference: Overview of WebLogic Server Domains

Free Oracle 1Z0-599 Actual Exam Questions