Oracle Oracle Certifications 1Z0-599 Questions & Answers

• Question 81:

  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?

  A. Configure a Max Threads Constraint and add your application to the list of applications for the Constraint.

  B. Configure a Work Manager with a Maximum Threads Constraint tied to the Connection Pool and configuration your application to use the Work Manager.

  C. Configure a Work Manager with a Minimum Threads Constraint tied to the Connection Pool and configure your application to use the Work Manager.

  D. Configure a global MaxThreads constraint and target it to the server or clusters where your application is deployed.

  E. Configure the startup parameter "-Dwls-maxThreads" to be the same as the number of database connections configured.

  Correct Answer: B

  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.

  *

  WebLogic Server uses a single thread pool, in which all types of work are executed. WebLogic Server

  Administrators can configure a set of scheduling guidelines and associate them with one or more applications, or with particular application components.

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

  A customer has a critical, performance-sensitive web application that connects to a multimode Oracle RAC database. Which feature of WebLogic can provide signification benefit?

  A. The Web Session Affinity feature of Active GridLink for RAC.

  B. WebLogic Clustering

  C. The Transaction Affinity feature of Active GridLink for RAC

  D. Coherence*Web Session Replication

  Correct Answer: C

  Active GridLink for Oracle RAC In Oracle WebLogic Server 10.3.4, a single data source implementation has been introduced to support an Oracle RAC cluster. It responds to FAN events to provide Fast Connection Failover (FCF), Runtime Connection Load-Balancing (RCLB), and RAC instance graceful shutdown. XA affinity is supported at the global transaction Id level. The new feature is called WebLogic Active GridLink for RAC; which is implemented as the GridLink data source within WebLogic Server.

  Note:

  * The WebLogic Server JDBC subsystem has supported Oracle RAC since WLS version 9.0, originally developed for Oracle9i RAC. This support is based on a particular type of data source configuration, called a multi data source. A multi data source is a data source abstraction over one or more individual data sources. It serves JDBC connections from each of the member data sources according to a specified policy. A RAC multi data source configuration requires that each member data source obtain connections to a particular RAC instance.

  Reference: How-To: Use Oracle WebLogic Server with a JDBC GridLink Data Source

• Question 83:

  A customer has a Stock Watch application that publishes stock recommendations to different customers and programs. The stock recommendation message should be processed by only one of the JMS Servers in the cluster. Which JMS model should be used?

  A. JMS Queue

  B. Distributed JMS Queue

  C. Uniform Distributed Topic

  D. Partitioned Distributed Topic

  Correct Answer: A

  JMS queue

  A staging area that contains messages that have been sent and are waiting to be read. Note that, contrary

  to what the name queue suggests, messages don't have to be delivered in the order sent. A JMS queue

  only guarantees that each message is processed only once.

  Incorrect:

  Not B: (Only one queue required)

  *

  A distributed destination is a set of destinations (queues or topics) that are accessible as a single, logical

  destination to a client. A distributed destination has the following characteristics:

  It is referenced by its own JNDI name.

  Members of the set are usually distributed across multiple servers within a cluster, with each destination member belonging to a separate JMS server.

  *

  A distributed queue is a set of physical JMS queue members. As such, a distributed queue can be used to create a QueueSender, QueueReceiver, and a QueueBrowser. The fact that a distributed queue represents multiple physical queues is mostly transparent to your application.

  Not Topic:

  JMS topic

  A distribution mechanism for publishing messages that are delivered to multiple subscribers.

• Question 84:

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

  A. enabling Pinned to Thread

  B. enabling Logging Last Resource

  C. increasing the Statement cache size

  D. setting the statement cache type to LRU

  E. setting the initial and maximum capacity to the same number

  Correct Answer: A

  XA Affinity and Failover When accessed within a global transaction, the member data source from which the JDBC connection was obtained is pinned to the global transaction for the life of the transaction. This ensures that all database operations performed on connections obtained from the Multi Data Source, for a particular transaction, all execute on the same RAC instance. XA affinity results in improved performance and is even a requirement for older versions of RAC, such as prior to 11g. The XA failover is also supported by the Multi Data Source and transaction manager implementations. If a pinned RAC instance suffers a failure, then a global transaction can complete utilizing a different RAC instance using a connection obtained one of the other member data sources.

  Reference: Oracle WebLogic Server Active GridLink for Oracle Real Application Clusters(RAC)

• Question 85:

  A customer needs to implement a Highly Available solution for JMS that has a primary data center and a backup. Which three steps would you perform when designing your solution?

  A. Store Transaction Logs in a database and use Database stores for JMS to make replication between sites easier.

  B. Use file based Transaction Logs and JMS stores and implement a separate replication solution for files in addition to database in case database replication fails.

  C. Implement Oracle RAC at each site to provide a highly available solution within each datacenter.

  D. Configure Whole Server Migration to migrate WebLogic Managed Servers from the primary to the secondary site.

  E. Configure Automatic Service Migration for JMS high availability within a datacenter.

  Correct Answer: ACE

  Note:

  

• Question 86:

  A common approach to solve application performance issues is to add more hardware. Which two reasons describe why this alone does not always solve performance problems?

  A. There may be a bottleneck in the application that additional hardware would not solve.

  B. Adding more hardware is costly and time consuming.

  C. Adding hardware at the application layer may place additional load on an already overloaded database, network appliance, or storage system.

  D. Adding more hardware may introduce new configuration requirements that need to be tested.

  Correct Answer: AC

• Question 87:

  A customer has a critical, performance-sensitive web application that connects to a multinode Oracle RAC database. Which feature of WebLogic can provide significant performance benefit?

  A. The Web Session Affinity feature of Active GridLink for RAC

  B. WebLogic Clustering

  C. The Transaction Affinity feature of Active GridLink for RAC

  D. Coherence*Web Session Replication

  Correct Answer: C

  XA Affinity and Failover When accessed within a global transaction, the member data source from which the JDBC connection was obtained is pinned to the global transaction for the life of the transaction. This ensures that all database operations performed on connections obtained from the Multi Data Source, for a particular transaction, all execute on the same RAC instance. XA affinity results in improved performance and is even a requirement for older versions of RAC, such as prior to 11g. The XA failover is also supported by the Multi Data Source and transaction manager implementations. If a pinned RAC instance suffers a failure, then a global transaction can complete utilizing a different RAC instance using a connection obtained one of the other member data sources.

  Reference: Oracle WebLogic Server Active GridLink for Oracle Real Application Clusters(RAC)

• Question 88:

  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?

  A. Shut down the managed server from the WebLogic console.

  B. Shut down the managed server using the WLST command through Node Manager.

  C. Run "kill -9" once to kill the managed server process.

  D. Run "kill -9" to kill the managed server process, and run "kill -9" one more time if the managed server is restarting.

  Correct Answer: A

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

  A customer claims that while redeploying a web application in the production system all their customers are having to log in again. What do you recommend?

  A. Sessions can't be preserved when redeploying applications. The customer needs to consider redeployment during late nights when the traffic is low.

  B. Change the flag responsible for the development mode of their environment. In the production mode, all sessions are preserved while redeploying application.

  C. Change Hotspot to JRockit. Sessions can't be preserved on HotSpot when redeploying application.

  D. Use flag -version when redeploying the application. This will switch on the Side By Side deployment feature and preserve existing sessions.

  E. Open a service request with Oracle Support. This is unexpected behavior. Sessions are preserved without any extra settings.

  Correct Answer: D

  Restrictions on Production Redeployment Updates

  WebLogic Server can host a maximum of two different versions of an application at one time.

  Note:

  * When you redeploy a new version of an application, you cannot change: An application's deployment targets

  An application's security model

  A Web application's persistent store settings

  To change any of the above features, you must first undeploy the active version of the application.

  Incorrect:

  *

  (not A)

  Production redeployment enables you to update and redeploy an application in a production environment

  without stopping the application or otherwise interrupting the application's availability to clients. Production

  redeployment saves you the trouble of scheduling application downtime, setting up redundant servers to

  host new application versions, manually managing client access to multiple application versions, and

  manually retiring older versions of an application.

  *

  (not C) Not dependant on whether the application is JRockit or Hotspot.

  *

  (not E)

  The production redeployment strategy is supported for:

  Standalone Web Application (WAR) modules and enterprise applications (EARs) whose clients access the application via a Web application (HTTP).

  Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.

  All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.

  Production redeployment is not supported for:

  Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.

  Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.

  Applications that obtain JDBC data sources via the DriverManager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.

  Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP.

  Reference: Reference; Deploying Applications to Oracle WebLogic Server 12c, Redeploying Applications in a Production Environment

• Question 90:

  When your WebLogic Server solution needs to be scaled out with additional capacity and you don't want to add additional hardware, which three techniques should you us?

  A. Assign more than one managed server to a physical hardware that allows better CPU utilization.

  B. Assign more than one application to one managed server to better utilize threads within a single JVM process.

  C. Assign the same application to more than one managed server to load balance requests between servers.

  D. Assign the same heap size to the managed server across the cluster for easier control of memory footprint

  E. Create a virtualized environment with hypervisor for an easier solution

  Correct Answer: BDE