Simulation of 1Z0-599 book materials and answers for Oracle certification for client, Real Success Guaranteed with Updated 1Z0-599 pdf dumps vce Materials. 100% PASS Oracle WebLogic Server 12c Essentials exam Today!


♥♥ 2017 NEW RECOMMEND ♥♥

Free VCE & PDF File for Oracle 1Z0-599 Real Exam (Full Version!)

★ Pass on Your First TRY ★ 100% Money Back Guarantee ★ Realistic Practice Exam Questions

Free Instant Download NEW 1Z0-599 Exam Dumps (PDF & VCE):
Available on: http://www.surepassexam.com/1Z0-599-exam-dumps.html

Q21. What type of Java EE application can be upgraded to WebLogic 12c using the Smart Upgrade tool?

A. GlassFish

B. iAS

C. WebLogic Server 11g

D. JBoss

Answer:

Explanation: Note:

* iAS: Oracle Application Server

* Oracle WebLogic Server SmartUpgrade is one several Oracle software tools that can help you upgrade your entire Oracle Application Server or Oracle WebLogic Server environment to Oracle Fusion Middleware 11g.


Q22. In WebLogic 10.3.6 and WebLogic 12c on ExaLogic, performance of JMS is further improved through and .

A. Web Session Affinity

B. Concurrent Request Manager

C. Coherence

D. Elastic Message Overflow

Answer: B,D

Explanation:

D: Elastic message overflow is the ability for WebLogic JMS to take advantage of solid state disks, especially on Exalogic, for paging of JMS messages. This is especially important in spikes of traffic. Access to SSD is much faster than disks or the database, which are used for true persistent storage. This speed of writing and reading enables the system to absorb the spikes in traffic.


Q23. Which WebLogic edition bundles JRockit Real Time?

A. WebLogic Server Standard Edition

B. WebLogic Server Enterprise Edition

C. WebLogic Server Suite

D. WebLogic Server Grid Edition

E. WebLogic Server Cloud Edition

Answer: C


Q24. WebLogic Node Manager can be used to manage the life cycle of WebLogic servers. WebLogic Node Manager is installed and started .

A. Per Machine

B. Per Domain

C. Per Managed Server

D. Per Admin Server

Answer: A

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


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

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


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

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


Q27. An airline is building a booking system for its premium and general customers. The goal is to ensure premium members are given higher access priority when user traffic is high.

What configuration will achieve this goal?

A. Configure a Work Manager for premium users with a Minimum Thread Constraint.

B. Configure a Work Manager for premium users with a higher fair-share-request-class.

C. Configure a Work Manager for premium users with a higher response-time-request- class.

D. Configure a Work Manager general users with a Maximum Thread Constraint.

E. Configure a Work Manager for premium users with a custom request-class.

Answer: B

Explanation: fair-share-request-class—Specifies the average thread-use time required to process requests. The default fair share value is 50.

For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fair-share-request-class of 80 and the Work Manager

for ModuleB specifies a fair-share-request-class of 20.

During a period of sufficient demand, with a steady stream of requests for each module such that the number requests exceed the number of threads, WebLogic Server will

allocate 80% and 20% of the thread-usage time to ModuleA and ModuleB, respectively.

* Example:

<work-manager>

<name>lowpriority_workmanager</name>

<fair-share-request-class>

<name>low_priority</name>

<fair-share>10</fair-share>

</fair-share-request-class>

</work-manager>

<work-manager>

<name>highpriority_workmanager</name>

<fair-share-request-class>

<name>high_priority</name>

<fair-share>100</fair-share>

</fair-share-request-class>

</work-manager>

Note:

* A request class expresses a scheduling guideline that WebLogic Server uses to allocate threads to requests. Request classes help ensure that high priority work is scheduled before less important work, even if the high priority work is submitted after the lower priority work.

Incorrect:

Not C: response-time-request-class—Specifies a response time goal in milliseconds. Response time goals are not applied to individual requests. Instead, WebLogic Server computes a tolerable waiting time for requests with that class by subtracting the observed average thread use time from the response time goal, and schedules requests so that the average wait for requests with the class is proportional to its tolerable waiting time.

Not A, D: Not related to thread constraints.

For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-share-request-class of 20.


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

A. Deploy Active Cache shared library

B. Declare dependency on the shared library

C. Declare all dependency injection entries

D. Package tangosol-coherence-override.xml in modules classpath

E. Package coherence-cache-config.xml in modules classpath

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.


Q29. What does the Fast Connection Failover feature of Active GridLink for RAC provide?

A. instant notification of a RAC node failure so applications never have to retry a transaction that was sent to a node that failed during the transaction

B. near-instant notification of the failure of a RAC node failure that minimizes the possibility connection to a failed node being provided to an application

C. application level notification of a failed RAC node such that an application can retry a transaction if required

D. faster failover for Multi Datasources

E. guaranteed transaction high availability when interacting with an Oracle RAC Database

Answer: B

Explanation: * WebLogic Server supports Fast Connection Failover, a Oracle feature which provides an application independent method to implement RAC event notifications, such a detection and cleanup of invalid connections, load balancing of available connections, and work redistribution on active RAC instances.

* A GridLink data source uses Fast Connection Failover and responds to Oracle RAC events using ONS. This ensures that the connection pool in the GridLink data source contains valid connections (including reserved connections) without the need to poll and test connections


Q30. A customer needs to analyze an application that was developed for Oracle Application Server 10gR2 or 10gR3 (OC4J) in order to prepare to upgrade the infrastructure to WebLogic 12c. The customer wants understand the changes required to be made to the application and how to configure WebLogic in to support the newly upgraded application.

Which three actions would you recommend for upgrading the customer's application and server configuration?

A. Use Oracle Upgrade Manager to create a new WebLogic domain template from an OAS/OC4J installation and redeploy the application.

B. Use SmartUpgrade to analyze the OAS/OC4J server configuration and create WebLogic configuration files.

C. Use SmartUpgrade to analyze the application archive (EAR/WAR/JAR) Source Directory or IDeveloper project and generate a report that describes the areas of the application that need to be updated.

D. Use the Configuration Wizard to extend an existing WebLogic domain with OAS/OC4J support libraries and redeploy the application.

E. Use SmartUpgrade to generate application artifacts and deployment descriptors that can be deployed to WebLogic.

Answer: B,D,E

Explanation:

Note:

* Oracle WebLogic SmartUpgrade is part of the Oracle Fusion Middleware 11g upgrade tools that were designed to maximize the automation of the upgrade process, minimize the application

downtime and allows for rapid and seamless uptake of the Oracle Fusion Middleware 11g features and capabilities.

* SmartUpgrade : (B) When generating an upgrade report into an existing project, an Oracle Application Server

configuration home could be specified to be included as part of the report. Additionally, both the

server home and OracleAS enterprise archives can be localized into the JDevelopoer project file

system by checking "Copy OC4J Deployment Archives Into Project".

* SmartUpgrade : (E) The advisory reports and the configuration artifacts will be generated. The generated artifacts will be located at the JDeveloper project mywork directory

* You can add product component functionality or additional applications and services to an existing WebLogic domain by extending it using the Configuration Wizard. For example, if you created a base WebLogic domain and you want to add the Avitek Medical Records Examples functionality, you can extend the domain by using the medrec.jar template.

The Configuration Wizard simplifies the task of extending an existing WebLogic domain by using extension templates. Oracle provides various sample extension templates, as well as extension templates for various Fusion Middleware products. You can also create your own extension templates using WLST or the unpack command.