Oracle 1Z0-599 Online Practice Questions and Exam Preparation

Oracle 1Z0-599 Online Questions & Answers

• Question 51:

  What are four benefits of recommended basic architecture?

  A. Good load balancing between Presentation Tier and Object Tier
  B. Easy administration
  C. Flexible Load balancing
  D. Optimal performance
  E. Simple security
  B. Easy administration
  C. Flexible Load balancing
  D. Optimal performance
  E. Simple security

• Question 52:

  When a critical error occurs, which module in Enterprise Manager will automatically collect diagnostics data from WebLogic Server?

  A. Reports
  B. Compliance
  C. Support Workbench
  D. Asset Discovery
  E. visual creation of JDBC DataSource object to Oracle RAC
  C. Support Workbench

  ---

  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.

• Question 53:

  You deploy two different applications to the WebLogic container. One application use Xerces parser version A and the other application uses Xerces parser version B. Both these versions are different from the parser version that the WebLogic server uses internally. You want to use the Filtering Classloader feature to solve this problem. What action would you take to generate proper filtering Classloader entries?

  A. Modify the applications to use the same version that WebLogic uses internally.
  B. Based on available examples of Filtering Classloader entries, try to modify get the proper entries.
  C. Deploy and use the Classloader Analyzing Tool to resolve all conflicts with conflicting libraries. This tool will generate all proper entries.
  D. Split the application into separate WebLogic containers and use different WLS versions of Xerces but identical that applications require.
  E. Look for a WebLogic release that uses the same version of Xerces that the applications use.
  B. Based on available examples of Filtering Classloader entries, try to modify get the proper entries.

  ---

  Note:

  *

  The FilteringClassLoader provides a mechanism for you to configure deployment descriptors to explicitly specify that certain packages should always be loaded from the application, rather than being loaded by the system classloader. This allows you to use alternate versions of applications such as Xerces and Ant.

  *

  To configure the FilteringClassLoader to specify a certain package is loaded from an application, add a prefer-application-packages descriptor element to the weblogic- application.xml which details the list of packages to be loaded from the application. The following example specifies that org.apache.log4j.* and antlr.* packages are loaded from the application, not the system classloader:

  org.apache.log4j.* antlr.*

  Reference: Understanding WebLogic Server Application Classloading

• Question 54:

  Which two elements of the Java Enterprise Application Archive are required?

  A. EJB Archive
  B. Deployment Descriptor
  C. META-INF sub directory
  D. Resource Adapter archive
  E. Java library
  A. EJB Archive
  B. Deployment Descriptor

  ---

  A: In WebLogic Server 12c, you can make use of the shared Java EE library feature in WebLogic Server which provides an easy way to share one or more different types of modules among multiple enterprise applications. A shared library is

  a single module or collection of modules that is registered with the Java EE application container upon deployment. A shared library could be:

  ?Standalone EJB module

  ?Standalone web application module

  ?Multiple EJB modules packaged in an enterprise application ?Multiple web application modules packaged in an enterprise application ?Single plain JAR file

  B:

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

• Question 55:

  Identify three unique integration features of Spring and WebLogic Server.

  A. ability to automatically convert Spring application to JavaEE 6 framework
  B. ability to export the WebLogic Container feature to another Spring enabled JavaEE server.
  C. ability to extend the WebLogic Server console with some Spring-related pages
  D. official support of Spring apps inside WebLogic by Oracle Support
  E. support for injection of WebLogic MBeans and Resources into Spring applications
  C. ability to extend the WebLogic Server console with some Spring-related pages
  D. official support of Spring apps inside WebLogic by Oracle Support
  E. support for injection of WebLogic MBeans and Resources into Spring applications

  ---

  C: Spring Console Extension. WebLogic provides an Admin Console extension for Spring to provide administrators with visual tools for monitoring the Spring parts of deployed applications (first navigate to WebLogic Admin Console's Preferences | Extension menu option and and enable spring-console). This Spring console extension is basically a set of pages which are added amongst the normal pages of the standard WebLogic admin console, rather than being a separate console per se. The extension provides a view onto the values of the WebLogic generated Spring MBeans

  D: If you have an issue, you use the Oracle Support organisation for help with WebLogic specific problems and any Spring parts to your application are treated just like your own custom code is, from an Oracle Support perspective.

  E: WebLogic Injected Spring Beans is a Weblogic feature that is enabled by default. Reference: WebLogic and Spring

• Question 56:

  In WebLogic, the development feature to automatically load/refresh the changes of a Java classes at run time is called__________.

  A. HotSwap
  B. FastSwap
  C. HotDeploy
  D. FastDeploy
  E. FastReload
  B. FastSwap

  ---

  Using FastSwap Deployment to Minimize Redeployment

  Java EE 5 introduces the ability to redefine a class at runtime without dropping its ClassLoader or abandoning existing instances. This allows containers to reload altered classes without disturbing running applications, vastly speeding up iterative development cycles and improving the overall development and testing experiences. The usefulness of the Java EE dynamic class redefinition is severely curtailed, however, by the restriction that the shape of the class its declared fields and methods cannot change. The purpose of FastSwap is to remove this restriction in WLS, allowing the dynamic redefinition of classes with new shapes to facilitate iterative development.

  With FastSwap, Java classes are redefined in-place without reloading the ClassLoader, thereby having the decided advantage of fast turnaround times. This means that you do not have to wait for an application to redeploy and then navigate back to wherever you were in the Web page flow. Instead, you can make your changes, auto compile, and then see the effects immediately.

  Reference: Using FastSwap Deployment to Minimize Redeployment

• Question 57:

  Which three JVM options would you add to investigate performance issues in a Hot-Spot JVM?

  A. -xx:+PrintGCDetails
  B. -xx:+PrintGCTimeStamps
  C. -xx:+HandlePromotionFailure
  D. -verbose:gc
  E. -server
  A. -xx:+PrintGCDetails
  B. -xx:+PrintGCTimeStamps
  E. -server

  ---

  A: Print more details at garbage collection.

  B: Print timestamps at garbage collection.

  C: The youngest generation collection does not require a guarantee of full promotion of all live objects.

  E: Default values are listed for Java SE 6 for Solaris Sparc with -server.

  Reference: Java HotSpot VM Options

• Question 58:

  Identify three reasons that explain why assigning more than one managed serve achieve better performance than running one managed server with more resources?

  A. Thread management inside the JVM process might be less effective than context switching between processes on the OS level. It is better to combine both these technologies to achieve full saturation of resources.
  B. Current CPUs are multicore units. So starting managed servers in the amount of physical cores and pinning them 1:1 to cores will always get the best performance.
  C. By a combination of prioritization of processes on the OS level and Work Manager in WLS, one could tune the whole environment more precisely.
  D. Assigning more than one managed server to hardware will never bring better performance.
  E. More instances means more connections to databases, so one could serve more concurrent calls on the database level. This is primarily why this approach will give better performance numbers.
  F. Depending on the profile of the application, having more JVMs with smaller heaps will lead to more predictable response times than fewer JVMs with a large heap.
  C. By a combination of prioritization of processes on the OS level and Work Manager in WLS, one could tune the whole environment more precisely.
  E. More instances means more connections to databases, so one could serve more concurrent calls on the database level. This is primarily why this approach will give better performance numbers.
  F. Depending on the profile of the application, having more JVMs with smaller heaps will lead to more predictable response times than fewer JVMs with a large heap.

  ---

  Note:

  *

  Two or more Managed Servers can be configured as a WebLogic Server cluster to increase application scalability and availability. In a WebLogic Server cluster, most resources and services are deployed identically to each Managed Server (as opposed to a single Managed Server), enabling failover and load balancing. A single domain can contain multiple WebLogic Server clusters, as well as multiple Managed Servers that are not configured as clusters. The key difference between clustered and non-clustered Managed Servers is support for failover and load balancing. These features are available only in a cluster of Managed Servers.

  *

  A WebLogic Server cluster provides these benefits: Scalability The capacity of an application deployed on a WebLogic Server cluster can be increased dynamically to meet demand. You can add server instances to a cluster without interruption of service--the application continues to run without impact to clients and end users. High-Availability In a WebLogic Server cluster, application processing can continue when a server instance fails. You "cluster" application components by deploying them on multiple server instances in the cluster--so, if a server instance on which a component is running fails, another server instance on which that component is deployed can continue application processing.

• Question 59:

  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?

  A. You need to install a separate node manager for each Middleware Home that has a unique major and minor WebLogic Version Number.
  B. You need to install and configure only one instance of Node Manager for all products, regardless of the WebLogic version number.
  C. You need to install and configure a separate Node Manager for each domain of each product you want to run on the machine.
  D. You need to install one Node Manager but use separate SSL certificates for each product when searching the network communication to the machine
  B. You need to install and configure only one instance of Node Manager for all products, regardless of the WebLogic version number.

  ---

  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

• Question 60:

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

  A. management of many WebLogic Server Domains from a single web console
  B. tracking changes in the configuration of WebLogic Domain
  C. automation of provisioning process in the new environment
  D. checking compliance with the licenses that a customer has
  E. visual creation of JDBC DataSource object to Oracle RAC
  A. management of many WebLogic Server Domains from a single web console
  B. tracking changes in the configuration of WebLogic Domain
  E. visual creation of JDBC DataSource object to Oracle RAC

  ---

  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