Free Practice Questions for Oracle 1z0-599 Exam

Note:

* Apache Maven is a software tool for building and managing Java-based projects. WebLogic Server provides support for Maven through the provisioning of plug-ins that enable you to perform various operations on WebLogic Server from within a Maven environment.

* Continuous Integration is a software engineering practice which attempts to improve quality and reduce time to deliver software by applying small, frequent quality control efforts. It is characterized by these key practices:

Use of a version control system

All developers commit to the ‘HEAD’ (main code line) every day

The product is built on every commit

The build must be automated and fast

Automated deployment to a production-like environment

Automated testing

Results of all builds are published (so everyone can see who broke the build)

Deliverables are easily available (for developers, testers, other stakeholders)

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.

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 you’ll 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

Oracle WebLogic Server Logging Last Resource (LLR) An additional option for XA transactions is Oracle WebLogic Server’s Logging Last Resource (LLR) transaction optimization through JDBC data sources. LLR is a performance enhancement option that enables one non-XA resource to participate in a distributed transaction with the same ACID guarantee asXA. In a distributed transaction with an LLR participant, the Oracle WebLogic Server transaction

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.

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.

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.

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

Reference; Node Manager Administrator's Guide for Oracle WebLogic Server 12c

WAN HTTP Session State Replication

Resources in a wide area network (WAN) are frequently spread across separate geographical regions. In addition to requiring network traffic to cross long distances, these resources are often separated by multiple routers and other network bottle necks. Network communication in a WAN generally has higher latency and slower interconnect.

Slower network performance within a WAN makes it difficult to use a synchronous replication mechanism like the one used within a MAN. WebLogic Server provides failover across clusters in WAN by using an asynchronous data replication scheme.

Note:

HTTP Session State Replication

Weblogic Server uses two methods for replicating HTTP session state across clusters:

in-memory replication

* Using in-memory replication, WebLogic Server copies a session state from one server instance to another. The primary server creates a primary session state on the server to which the client first connects, and a secondary replica on another WebLogic Server instance in the cluster. The replica is kept up-to-date so that it may be used if the server that hosts the servlet fails.

* JDBC-based persistence

In JDBC-based persistence, WebLogic Server maintains the HTTP session state of a servlet or JSP using file-based or JDBC-based persistence.

JDBC-based persistence is also used for HTTP session state replication within a Wide Area Network (WAN).