Oracle 1Z0-599 Online Practice Questions and Exam Preparation

Oracle 1Z0-599 Online Questions & Answers

• Question 11:

  What are the three steps you should take to tune a JDBC Connection pool in WebLogic from the initial settings in a production environment?

  A. Ensure the maximum size is increased to an appropriate setting.
  B. Set the minimum and maximum size of the connection pool to the same value.
  C. Increase the statement cache size.
  D. Add more heap to the JVM.
  E. Add more nodes to the cluster.
  A. Ensure the maximum size is increased to an appropriate setting.
  C. Increase the statement cache size.
  E. Add more nodes to the cluster.

  ---

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

• Question 12:

  Assume that you would like to clone an existing WebLogic Domain and enable some customizations. What scenario would you choose?

  A. In the Enterprise Manager, find the domain to be cloned. Choose "Clone WebLogic Domain" from the context menu. In the graphical wizard, customize and extend the domain if needed. These steps will only clone only the domain configuration. Binaries with deployments are needed to be cloned by operation on the file system.
  B. In the Enterprise Manager, find the domain to be cloned. Choose "Clone WebLogic Domain" from the context menu. In the graphical wizard, customize the domain. These steps clone the binaries and domain configuration. If the extension is needed, perform it after cloning in the WebLogic web-based console.
  C. In the Enterprise Manager, find the domain to be cloned. Choose "Clone WebLogic Domain" from the context menu. In the graphical wizard, customize and extend the domain if it is needed. These steps clone the binaries and domain configuration.
  D. In the Enterprise Manager, find the domain to be cloned. Choose "Clone WebLogic Domain" from the context menu. These steps clone the binaries and domain configuration. If the customization or extension is needed, complete that after cloning in the WebLogic web-based console.
  E. In the file system, copy the domain structure of the configuration directory and paste it in the new location. Modify configuration files for address and port. If further customization is needed, open the WebLogic web-based console and perform these modifications.
  C. In the Enterprise Manager, find the domain to be cloned. Choose "Clone WebLogic Domain" from the context menu. In the graphical wizard, customize and extend the domain if it is needed. These steps clone the binaries and domain configuration.

  ---

  The Clone WebLogic Domain option launches a wizard that enables you to clone a WebLogic Domain from an existing reference domain that is already discovered with Cloud Control. It allows you to clone the Middleware Home and its binaries, and the domain configuration.

  * If you selected the Cloning a WebLogic Domain option, the Middleware Provisioning:

  Domain Configuration page appears. This page contains a set of links to several pages where you can enter the properties that are most likely to be reconfigured like domain name, listen addresses for the administration server and managed

  servers, Node Manager/Machine configuration, and JDBC data sources.

• Question 13:

  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
  C. The Transaction Affinity feature of Active GridLink for RAC

  ---

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

  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
  A. enabling Pinned to Thread

  ---

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

  Which three scenarios are true about Domains?

  A. Domains can be created using the Configuration Wizard.
  B. Domains can be created using WLST.
  C. Domain configuration files are located in the WebLogic home directory.
  D. Domains can be created based on a domain template.
  A. Domains can be created using the Configuration Wizard.

  ---

  A: a WebLogic domain can be created by using the Configuration Wizard in graphical mode.

  B: WLST enables you to create a new domain or update an existing domain

  D: A domain template is a JAR file that contains domain configuration documents, applications, security data, startup scripts, and other information needed to create a domain.

• Question 16:

  A customer wants to improve the availability of a web application and provide more predictable scalability when scaling out the application. Which Feature of WebLogic should you recommend to help solve this problem?

  A. Oracle Web Grid
  B. ActiveCache
  C. Coherence Grid Edition
  D. WebLogic Session Replication
  E. Coherence Web Edition
  C. Coherence Grid Edition

  ---

  *

  Built on top of Oracle Coherence (Coherence), Coherence*Web:

  / brings Coherence data grid's data scalability, availability, reliability, and performance to in- memory session management and storage.

  / can be deployed to many mainstream application servers such as Oracle GlassFish Server, Oracle WebLogic Server, IBM WebSphere, Tomcat, and so on

  *

  Coherence*Web enables HTTP session sharing and management across different Web applications, domains, and heterogeneous application servers. Session data can be stored in data caches outside of the application server, thus

  freeing application server heap space and enabling server restarts without losing session data.

  Incorrect:

  A: No such thing Oracle Web Grid

  C: Grid Edition licensing includes the unlimited use of Real Time Clients which may be of the following two types: Real Time Cluster Member Client Real Time Extend/TCP Client Reference: Oracle Coherence User's Guide for Oracle Coherence*Web

• Question 17:

  WebLogic 12c, the Maven plug-in has been enhanced with which Maven goal?

  A. wls:unzip, wls:install-domain, wls:start-domain, wls:wlst, wls:appc
  B. wls:install, wls:install-domain, wls:start-domain, wls:wlst, wls:appc
  C. wls:unzip, wls:create-domain, wls:start-domain, wls:wlst, wls:appc
  D. wls:install, wls:create-domain, wls:start-server, wls:wlst, wls:appc:
  D. wls:install, wls:create-domain, wls:start-server, wls:wlst, wls:appc:

  ---

  wls-maven-plugin--Delivered in WebLogic Server 12c, provides enhanced functionality to install, start and stop servers, create domains, execute WLST scripts, and compile and deploy applications.

  Reference: Developing Applications for Oracle WebLogic Server, Using the WebLogic Development Maven Plug-In

• Question 18:

  What are the two proper locations of deployment descriptors files inside of archives deployed to WebLogic?

  A. the WEB-INF subdirectory for a WAR file
  B. the META-INF subdirectory for an EAR file, or EJB-JAR
  C. the DD-INF subdirectory
  D. the root of archive
  E. any searchable location
  A. the WEB-INF subdirectory for a WAR file
  B. the META-INF subdirectory for an EAR file, or EJB-JAR

  ---

  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

• Question 19:

  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.
  A. There may be a bottleneck in the application that additional hardware would not solve.
  C. Adding hardware at the application layer may place additional load on an already overloaded database, network appliance, or storage system.

• Question 20:

  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
  B. Assign more than one application to one managed server to better utilize threads within a single JVM process.
  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