Oracle 1Z0-599 Online Practice Questions and Exam Preparation

Oracle 1Z0-599 Online Questions & Answers

• Question 31:

  Identify three components of the WebLogic JMS architecture.

  A. JMS Server
  B. JMS Module
  C. Node Manager
  D. Queue Manager
  E. Persistent Store
  A. JMS Server
  B. JMS Module
  E. Persistent Store

  ---

  The major components of the WebLogic JMS Server architecture, as illustrated in the figure below.

  *

  (A) JMS servers that can host a defined set of modules and any associated persistent storage that reside on a WebLogic Server instance.

  *

  (B) JMS modules contains configuration resources (such as queues, topics, and connections factories) and are defined by XML documents that conform to the weblogic-jmsmd.xsd schema.

  *

  Client JMS applications that either produce messages to destinations or consume messages from destinations.

  *

  JNDI (Java Naming and Directory Interface), which provides a resource lookup facility. JMS resources such as connection factories and destinations are configured with a JNDI name. The runtime implementations of these resources are then bound into JNDI using the given names.

  *

  (E) WebLogic persistent storage (file store or JDBC-accessible) for storing persistent message data.

  The following figure illustrates the WebLogic JMS architecture.

  

  Reference: Understanding WebLogic JMS

• Question 32:

  Identify four features of WebLogic that provide value above and beyond a simple Java EE container.

  A. Active GridLink for RAC
  B. support for enterprise Web Services standards beyond Java EE specification
  C. Integration with Enterprise Manager
  D. market leading performance
  E. Java EE6 Specification Support
  F. Java SE 7 support
  A. Active GridLink for RAC
  B. support for enterprise Web Services standards beyond Java EE specification
  E. Java EE6 Specification Support
  F. Java SE 7 support

  ---

  B: Java EE Enterprise Web Services is supported.

  E: New or enhanced WebLogic 12c features include

  JAVA EE 6 support all kinds of JEE6 specifications are implemented like :

  JSF 2.0,Java Servlets 3.0 JPA 2.0 and EJB 3.1.

  Managed Beans 1.0

  F: WebLogic 12c also supports supports Java SE 7 (and Java SE 6).

  Java language optimizations and Internationalization Client and server support SSL/TLS 1.2 in JSSE to support JAVA Socket Transport security Converged Java VM:JRockit and HotSpot are incorporated with the best features from both. Oracle's Publisher Seminar 2011 during OOW

  Incorrect: not C:

  

• Question 33:

  Which is the correct WebLogic Server distribution version to download if you want to install WebLogic Server 12c to run in 64 bit mode on a 64 bit Linux X86?

  A. Linux x86 with 64 bit JVM
  B. ZIP distribution for Linux
  C. Linux x86 with 32 bit JVM
  D. Generic distribution
  E. Network installer
  C. Linux x86 with 32 bit JVM

  ---

  WebLogic Server 12c (12.1.1), WebLogic Server 11g (10.3.6)

  The following provides links to WebLogic Server 12.1.1 installers with 32-bit JVMs for Windows and Linux, the generic installer that can be used on any supported platform, and the zip distribution

  *

  Installers with Oracle WebLogic Server, Oracle Coherence and Oracle Enterprise Pack for Eclipse

  *

  Installers with Oracle WebLogic Server and Oracle Coherence:

  *

  Zip distribution with Oracle WebLogic Server only and intended for WebLogic Server development only.

• Question 34:

  A customer has a Stock Watch application that publishes stock recommendations to different customers and programs. The stock recommendation message should be processed by only one of the JMS Servers in the cluster. Which JMS model should be used?

  A. JMS Queue
  B. Distributed JMS Queue
  C. Uniform Distributed Topic
  D. Partitioned Distributed Topic
  A. JMS Queue

  ---

  JMS queue

  A staging area that contains messages that have been sent and are waiting to be read. Note that, contrary to what the name queue suggests, messages don't have to be delivered in the order sent. A JMS queue only guarantees that each

  message is processed only once.

  Incorrect:

  Not B: (Only one queue required)

  *

  A distributed destination is a set of destinations (queues or topics) that are accessible as a single, logical destination to a client. A distributed destination has the following characteristics: It is referenced by its own JNDI name.

  Members of the set are usually distributed across multiple servers within a cluster, with each destination member belonging to a separate JMS server.

  *

  A distributed queue is a set of physical JMS queue members. As such, a distributed queue can be used to create a QueueSender, QueueReceiver, and a QueueBrowser. The fact that a distributed queue represents multiple physical queues is mostly transparent to your application.

  Not Topic:

  JMS topic

  A distribution mechanism for publishing messages that are delivered to multiple subscribers.

• Question 35:

  To use Active Cache features in WebLogic 12C, which three libraries are needed from the WebLogic Server installation to be deployed in WebLogic Server?

  A. coherence-work.jar
  B. coherence.jar
  C. active-cache-1.0.jar
  D. coherence-web-spi.war
  B. coherence.jar
  C. active-cache-1.0.jar
  D. coherence-web-spi.war

  ---

  B, D: In addition to the coherence.jar file, Coherence provides a deployable shared library, coherence- web-spi.war, that contains a native plug-in to WebLogic Server's HTTP Session Management interface. Coherence also provides the active-cache-1.0.jar file which contains the classes that allow WebLogic Server to interact with Coherence.

  C: The active-cache-1.0.jar is included in the WebLogic Server installation. Reference: Oracle Coherence Tutorial for Oracle Coherence

• Question 36:

  A customer has a development environment that uses the auto-deployment feature. The customer claims the application is not redeployed even if the new version is copied to an application subdirectory. Which two parameters of the configuration should you check?

  A. Check if archive file in the compressed version has a new REDEPLOY file.
  B. If server was started in the Development Mode. Auto-deployment is not supported in production mode.
  C. If the application includes an EJB 3 module. Auto-deployment is not supported for EJBs.
  D. You change JVM from HotSpot to JRockit. Auto-deployment is not supported in HotSpot auto deployment.
  E. If the domain is a single-server domain. Auto-deployment is not supported in multiserver domains.
  B. If server was started in the Development Mode. Auto-deployment is not supported in production mode.
  E. If the domain is a single-server domain. Auto-deployment is not supported in multiserver domains.

  ---

  Auto-deployment is intended for use with a single server target in a development environment.

  Note:

  *

  If auto-deployment is enabled, when an application is copied into the \autodeploy directory of the Administration Server, the Administration Server detects the presence of the new application and deploys it automatically (if the Administration Server is running). If WebLogic Server is not running when you copy the application to the \autodeploy directory, the application is deployed the next time the WebLogic Server Administration Server is started. Auto-deployment deploys only to the Administration Server.

  *

  Limitations of Auto-Deployment

  Auto-deployed applications are very convenient in a development environment, but there are some limitations:

  There is no configuration in config.xml for an auto-deployed application. Therefore, in the Administration Console, there are no notes or target pages associated with an auto-deployed application because there is no backing configuration for

  that information.

  You cannot associate an auto-deployed application with a deployment plan since auto-deployed applications do not support any configuration operations which would be reflected in a deployment plan.

  You cannot set up security policies or roles for auto-deployed applications.

  You cannot undeploy or redeploy auto-deployed applications using WebLogic Server tools. Reference; Developing Applications for Oracle WebLogic Server 12c, Auto-Deploying Applications in Development Domains

• Question 37:

  You want to configure WebLogic so that Managed Servers are restarted when they are in a FAILED state. Which three steps are necessary to accomplish this?

  A. Configure Node Manager on the machines where WebLogic Managed Servers need to be started/ restarted.
  B. Enable "Auto Restart" in the Node Manager Configuration.
  C. Enable "Auto Kill if Failed" in the Node Manager Configuration.
  D. Enable "Auto Kill if Failed" for the Managed Server in question.
  E. Enable "Auto Restart" for the Managed Server in question.
  A. Configure Node Manager on the machines where WebLogic Managed Servers need to be started/ restarted.
  D. Enable "Auto Kill if Failed" for the Managed Server in question.
  E. Enable "Auto Restart" for the Managed Server in question.

  ---

  D: auto-kill-if-failed

  Specifies whether the Node Manager should automatically kill this server (the managed server) if its health state is failed. (Interface=weblogic.management.configuration.ServerMBean Attribute=getAutoKillIfFailed)

  When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot.

  E: When Auto Restart is enabled, Node Manager will try to restart the Managed Server if it crashes or goes down unexpectedly, for instance, as the result of a machine reboot.

  Reference: Server --> Configuration --> Health Monitoring

• Question 38:

  Which feature is enabled when you start a WebLogic server with the DserverType=wlx option?

  A. JDBC
  B. JCA
  C. JMS
  D. EJB
  E. Java EE
  A. JDBC

  ---

  -DserverType={"wls" | "wlx"}

  Specifies the Server Type, which determines the set of services that are started in the server runtime.

  The default is "wls", which starts all WebLogic Server services, including EJB, JMS, Connector, Clustering, Deployment, and Management.

  The "wlx" option starts a server instance that excludes the following services, making for a lighter weight runtime footprint:

  *

  (not D) Enterprise JavaBeans (EJB)

  *

  (not B, not E) Java EE Connecter Architecture (JCA)

  *

  (not C) Java Message Service (JMS)

  Reference: Oracle Fusion Middleware Command Reference for Oracle WebLogic Server , Options for Configuring Deployment Attributes

• Question 39:

  You want to capture WebLogic internal events correlated with JVM events for viewing offline. What three actions must you take to enable this within WebLogic?

  A. Run WebLogic in a JRockit JVM and ensure the Flight Recorder is enabled.
  B. Configure the WebLogic Diagnostic Framework Event Volume to Low, Medium, or High depending on the type of events you want to capture.
  C. Configure the WebLogic Diagnostic Framework bridge to send events to the JRockit Flight Recording.
  D. Take a dump from the default recording or create a new recording for the time period you want to capture.
  A. Run WebLogic in a JRockit JVM and ensure the Flight Recorder is enabled.
  B. Configure the WebLogic Diagnostic Framework Event Volume to Low, Medium, or High depending on the type of events you want to capture.
  D. Take a dump from the default recording or create a new recording for the time period you want to capture.

  ---

  A: You can enable JFR at runtime to take JRA recordings from the JRockit Management Console. You also have the option of turning off the JFR and recordings at the JRockit JVM level from the java command line using:

  $ java -XX:-FlightRecorder

  B:

  *

  In most environments, there is little performance impact when the Diagnostic Volume is set to Low and the most performance impact if Diagnostic Volume is set to High. The volume of diagnostic data produced by WebLogic Server needs to

  be weighed against potential performance loss.

  *

  WLDF provides the Diagnostic Volume attribute to set the amount of code coverage that is enabled and the amount of data provided in the events that are generated for the covered code The following code example sets the volume to

  Medium:

  . . .

  connect()

  edit()

  startEdit()

  cd("Servers/myserver")

  cd("ServerDiagnosticConfig")

  cd("myserver")

  cmo.setWLDFDiagnosticVolume("Medium")

  save()

  activate()

  D: Integrated with the WebLogic Diagnostic Image and Watch and Notification system ?Enables capture based on system state, event capture during event; no need to replicate ?Watch for stuck thread count, heap size increase, available

  memory, etc.

  ?Set up notifications: capture WLDF image

  ?Diagnostic image capture spurs JFR file generation; JFR file included in diagnostic image ?Includes full JFR data from all event generators

  Note:

  * WebLogic Diagnostic Framework (WLDF) provides specific integration points with JRockit Mission Control Flight Recorder. WebLogic Server events are propagated to the Flight Recorder for inclusion in a common data set for runtime or post-incident analysis.

  Reference: Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server, Tuning WebLogic Diagnostic Framework and JRockit Flight Recorder Integration Reference: JRockit Flight Recorder and WebLogic Diagnostic FrameWork (WLDF) Integration

• Question 40:

  An application that needs to use a shared library has a deployment descriptor that only specifies the Specification-Version and Extension-Name of the shared library. When the application is deployed, which shared library will be used?

  A. The application will go into an ADMIN state and fail to deploy because the Implementation-Version is required.
  B. The application will be deployed but the classes in the shared library will not be available.
  C. If you are using the WebLogic Admin Console, you will be prompted for the version you want to use; otherwise, the application will fail to deploy.
  D. If there are multiple versions of the shared library deployed, WebLogic will use the one with the highest Implementation-Version.
  E. If there are multiple versions of the shared library deployed, WebLogic will use the one that was deployed most recently.
  D. If there are multiple versions of the shared library deployed, WebLogic will use the one with the highest Implementation-Version.

  ---

  An internal application may be configured to always use a minimum version of the same library. Applications that require no specific version can be configured to use the latest version of the library. Note:

  * Specification-Version (a manifest Attributes for Java EE Libraries) An optional String value that defines the specification version of the shared Java EE library. Referencing applications can optionally specify a required Specification-Version for a library; if the exact specification version is not available, deployment of the referencing application fails.

  The Specification-Version uses the following format:

  Major/minor version format, with version and revision numbers separated by periods (such as "9.0.1.1")

  Referencing applications can be configured to require either an exact version of the shared Java EE library, a minimum version, or the latest available version.

  *

  Implementation-Version (a manifest Attributes for Java EE Libraries) An optional String value that defines the code implementation version of the shared Java EE library. You can provide an Implementation- Version only if you have also defined a Specification-Version.

  *

  Extension-Name (a manifest Attributes for Java EE Libraries) An optional string value that identifies the name of the shared Java EE library. Referencing applications must use the exact Extension-Name value to use the library.

  As a best practice, always specify an Extension-Name value for each library. If you do not specify an extension name, one is derived from the deployment name of the library. Default deployment names are different for archive and exploded archive deployments, and they can be set to arbitrary values in the deployment command.

  *

  After a library is deployed, the extension-name, specification-version and implementation- version of the library can be found in Administration console. Reference: Creating Shared Java EE Libraries and Optional Packages