Oracle WebLogic Server 12c Essentials v6.4 (1z0-599)

Answer : A,B

Explanation: A:
* The WEB-INF directory contains the deployment descriptors for the Web application
(web.xml and weblogic.xml) and two subdirectories for storing compiled Java classes and library JAR files.
* Web Application - WEB-INF/web.xml ( WEB-INF/weblogic.xml )
The WEB-INF directory is a vital component of your web application. Web application wont run without it.It contains a heirarcy in which youll find the necessary configuration information for your web application, and all the class files for your servlets and classes that are called up by your JSPs.
WEB-INF folder contains all the class files for your servlets and classes that are called up by your JSPs
B:
Enterprise Application - META-INF/application.xml (META-INF/weblogic-application.xml) and META-INF/ejb-jar.xml ( META-INF/weblogic-ejb-jar.xml )
Generally comprises of EJBs. Bussiness Tier of an application and EJB basically handels the Bussiness logic of application (distributed objects)
META-INF/application.xml containes Mappings and security roles etc.whereas META-
INF/ejb-jar.xml containes ejb classes , session beans mapping etc.,
The META-INF directory is related to .jar files, It contains the manifest file which has list of jars.
A context-root setting in application.xml takes precedence over context-root setting in weblogic.xml (The context root of a web application determines which URLs weblogic will delegate to your web application.
Note:
* Deployment descriptors are xml documents that describe runtime behaviour for the deployment unit. The XML file contains information such as the context root of the web application and the mapping of the portable names of an application's resources to the application Server's resources

Answer : B,E

Explanation: B: WLST enables you to create a new domain or update an existing domain without connecting to a running WebLogic Server (that is, using WLST offline)supporting the same functionality as the Configuration Wizard.

E: With WLST you can -
Creating a Domain (Offline)
Updating an Existing Domain (Offline)
Creating a Domain Template (Offline)
Exporting Diagnostic Data (Offline)
Stepping Through a Sample Script: Creating a Domain Using WLST Offline
Reference: Creating and Configuring WebLogic Domains Using WLST Offline

Answer : B,C

Explanation:
* A WAR file deployed to WebLogic Server always includes the following files:
One servlet or Java Server Page (JSP), along with any helper classes.
An optional web.xml deployment descriptor, which is a Java EE standard XML document that describes the contents of a WAR file.
A weblogic.xml deployment descriptor, which is an XML document containing WebLogic
Server-specific elements for Web applications.
A WAR file can also include HTML or XML pages and supporting files such as image and multimedia files.

Answer : E

Explanation: Session Affinity Policy
Web applications where a user session has back-to-back online transaction processing
(OLTP) have better performance when repeated operations against the same set of records are processed by the same RAC instance. Business applications such as online shopping and online banking are typical examples of this pattern.
A GridLink data source uses the Session Affinity policy to ensure all the data base operations for a web session, including transactions, are directed to the same Oracle RAC instance of a RAC cluster.
Note:
The context is stored in the HTTP session. It is up to the application how windows (within a browser or across browsers) are mapped to HTTP sessions.
Note 2:
* GridLink Affinity
WebLogic Server GridLink affinity policies are designed to improve application performance by maximizing RAC cluster utilization. A GridLink data source monitors RAC load balancing advisories (LBAs) using the AffEnabled attribute to determine if RAC affinity is enabled for a RAC cluster. The first connection request is load balanced using Runtime Connection
Load-Balancing (RCLB) and is assigned an Affinity context. All subsequent connection requests are routed to the same Oracle RAC instance using the Affinity context of the first connection until the session ends or the transaction completes.
* Session Affinity

Answer : A,B,C

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

Answer : B

Explanation:
Incorrect:
Not A: New or enhanced WebLogic 12c features include
JAVA EE 6 support all kinds of JEE6 specifications
Not C: 12c do include a new Maven plug-in
Not D: For 1.6 adapters, you can embed metadata annotations in the resource adapter class files to specify deployment information, eliminating the need to create the ra.xml file manually.

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-constraintThis 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

Answer : B,D,E

Answer : B

Explanation:
Note:
* 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 instanceswhether Administration Server or Managed
Serverthat you want to control with Node Manager.
* 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

Answer : C

Explanation: Support Workbench is a feature where, on identification of a problem, targeted diagnostics data is dumped in a well-known format and location, for further analysis by administrators, Oracle Support and development. In case of Support
Workbench for FMW, this feature works for Weblogic Server Targets.

Answer : C

Answer : C

Explanation: The WebLogic Server JDBC subsystem has supported Oracle RAC since

WLS -
version 8.1 SP5, 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 policy2. A RAC multi data source configuration requires that each member data source obtain connections to a particular RAC instance, as illustrated in the following diagram of a three-node RAC cluster configuration.

Answer : D

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

Answer : D