[Free] 2018(Jan) EnsurePass Examcollection Oracle 1z0-599 Dumps with VCE and PDF 1-10

Ensurepass.com : Ensure you pass the IT Exams
2018 Jan Oracle Official New Released 1z0-599
100% Free Download! 100% Pass Guaranteed!
http://www.EnsurePass.com/1z0-599.html

Oracle WebLogic Server 12c Essentials

Question No: 1

Which four service offerings are included in Oracle Public Cloud?

  1. Database Service

  2. Data Service

  3. Java Service

  4. Security Service

  5. .NET Service

  6. SOA Service

Answer: A,B,C,D

Question No: 2

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?

  1. Configure Node Manager on the machines where WebLogic Managed Servers need to be started/restarted.

  2. Enable quot;Auto Restartquot; in the Node Manager Configuration.

  3. Enable quot;Auto Kill if Failedquot; in the Node Manager Configuration.

  4. Enable quot;Auto Kill if Failedquot; for the Managed Server in question.

  5. Enable quot;Auto Restartquot; for the Managed Server in question.

Answer: A,D,E Explanation:

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 -gt; Configuration -gt; Health Monitoring

Question No: 3

What does the Fast Connection Failover feature of Active GridLink for RAC provide?

  1. instant notification of a RAC node failure so applications never have to retry a transaction that was sent to a node that failed during the transaction

  2. near-instant notification of the failure of a RAC node failure that minimizes the possibility connection to a failed node being provided to an application

  3. application level notification of a failed RAC node such that an application can retry a transaction if required

  4. faster failover for Multi Datasources

  5. guaranteed transaction high availability when interacting with an Oracle RAC Database

Answer: B

Explanation: * WebLogic Server supports Fast Connection Failover, a Oracle feature which provides an application independent method to implement RAC event notifications, such a detection and cleanup of invalid connections, load balancing of available connections, and work redistribution on active RAC instances.

  • A GridLink data source uses Fast Connection Failover and responds to Oracle RAC events using ONS. This ensures that the connection pool in the GridLink data source contains valid connections (including reserved connections) without the need to poll and test connections

    Question No: 4

    Active Cache is the integration of Coherence and WebLogic Server. Which component is NOT part of this integration?

    1. Coherence*Web

    2. Coherence*Extend

    3. TopLink Grid with Coherence

    4. Coherence cluster lifecycle management in WebLogic Server

    5. Named cache dependency Injection

    Answer: B

    Explanation: WebLogic Server includes features that allow deployed applications to easily use Coherence data caches, and seamlessly incorporate Coherence*Web (not A) for session management and TopLink Grid (not C) as an object-to-relational persistence framework. Collectively, these features are referred to as ActiveCache.

    ActiveCache is employed by applications running on WebLogic Server and provides replicated and distributed caching services that make an application#39;s data available to all servers in a Coherence data cluster. New features in this release provide direct access by applications to data caches, either through resource injection or component-based JNDI lookup, and let you display, monitor, create, and configure Coherence clusters using the WebLogic Server Administration Console and WLST.

    Reference: Oracle Coherence Tutorial for Oracle Coherence

    Question No: 5

    Identify four valid requests in a RESTful service using JAX-RS.

    1. GET

    2. PUT

    3. UPDATE

    4. DELETE

    5. POST

    6. REMOVE

    Answer: A,B,D,E

    Explanation: The following principles encourage RESTful applications to be simple, lightweight, and fast:

  • Resource identification through URI

  • Uniform interface: Resources are manipulated using a fixed set of four create, read, update, delete operations: PUT, GET, POST, and DELETE. PUT creates a new resource, which can be then deleted by using DELETE. GET retrieves the current state of a resource

    in some representation. POST transfers a new state onto a resource. See Responding to HTTP Methods and Requests for more information.

  • Self-descriptive messages

  • Stateful interactions through hyperlinks

Reference: The Java EE 6 Tutorial, What Are RESTful Web Services?

Question No: 6

You have a domain that was created and configured with WebLogic 10.3.5. You want to upgrade the domain to use WebLogic 12c. Which Oracle tool must you use to upgrade your domain?

  1. Oracle WebLogic Domain Upgrade tool

  2. Smart Update

  3. Smart Upgrade

  4. No tool required, just install WebLogic 12c, update the domain to point to the new WebLogic installation and start your domain.

  5. JDeveloper

Answer: D Explanation:

Note:

You can use the 12.1.1 WebLogic Upgrade Wizard to upgrade domains created in WebLogic Server 8.1. You can also use the WebLogic Upgrade Wizard to upgrade a WebLogic domain created in WebLogic Server 9.x or 10.x to 12.1.1, but this is optional.

Question No: 7

You have a durable subscriber, and the subscriber is down or not reachable when the message is produced. Which two options regarding the expiry of these messages are true?

  1. after the subscriber is unavailable for 10 minutes

  2. when the subscriber is available

  3. after the subscriber is unavailable for after an hour

  4. are available until the specified time elapses

  5. are expired instantly

Answer: B,D

Explanation: By default, JMS messages never expire. When applications send messages to queues or topics with durable subscribers, WebLogic must retain the message until it is consumed. This is fine in most point-to-point messaging applications because consumers are constantly consuming messages. Any message sent to a queue will typically be consumed in a relatively short period of time. If the consumers get disconnected, they will usually reconnect as soon as possible and start processing any messages that might have built up in the queue.

D: For durable subscribers to a topic, this is not necessarily true. The messaging system is forced to retain any message that has not been consumed by a durable subscriber, regardless of whether that durable subscriber will ever return. In this case, WebLogic is at the mercy of the durable subscriber to unsubscribe when it no longer wishes to receive the messages. If the durable subscriber logic is flawed in such a way that the subscribers do not unsubscribe properly, the messaging system will start to fill up with messages that may never be delivered. This calls for real caution in using durable subscribers. Fortunately, there is another way to help deal with this problem. Message expiration can be set at the connection factory level. Using a connection factory’s default time-to-live attribute, we can specify the number of milliseconds that WebLogic should retain an undelivered message after it is sent.

Question No: 8

In WebLogic 10.3.6 and 12c, transaction logs can optionally write to a JDBC store instead of a file store on the file system. Identify the three benefits as a result of this capability.

  1. simplified disaster recovery architecture and efforts

  2. better performance than writing logs to a file store

  3. common storage of transaction logs with application data

  4. common replication of transaction logs with application data

  5. higher transaction throughput

Answer: A,C,D

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

    Reference: Configuring Server Environments for Oracle WebLogic Server 12c, Comparing File Stores and JDBC-accessible Stores

    Question No: 9

    Which four actions can you perform using the WebLogic Admin Console?

    1. Stop and start Managed Servers using the Node Manager.

    2. Stop and start Coherence Servers using the Node Manager.

    3. Create a WebLogic Domain Template.

    4. Create and target JDBC connection pools.

    5. Create and target WebLogic Diagnostic Framework Diagnostic Modules.

    6. Change Java command-line parameters at run time.

    Answer: A,B,D,F

    Explanation: Use the Administration Console to:

  • (A) Configure, start, and stop WebLogic Server instances

  • Configure WebLogic Server clusters

  • (D) Configure WebLogic Server services, such as database connectivity (JDBC) and messaging (JMS)

  • Configure security parameters, including managing users, groups, and roles

  • Configure and deploy your applications

  • Monitor server and application performance

  • View server and domain log files

  • View application deployment descriptors

  • (F) Edit selected run-time application deployment descriptor elements

  • (B) Control (start, stop, and restart) standalone Coherence cache servers

  • (B) Create and configure Coherence clusters

    Incorrect:

    Not C: The separate Domain Template Builder is used for creating Domain Templates.

    Question No: 10

    You are configuring the data source for an Oracle database. You will need to specify a test table for WebLogic to test the status of the database. Which option should you choose?

    1. a table name which has 100s of records

    2. a table name which has 10s of records

    3. a table name which has empty records

    4. a table name which has 1000s of records

    5. never use a table name

    Answer: C

    Explanation: * When you create a data source using the Administration Console, the Administration Console automatically sets the Test Table Name attribute for a data source based on the DBMS that you select. The Test Table Name attribute is used in connection testing which is optionally performed periodically or when you create or reserve a connection, depending on how you configure the testing options. For database tests to succeed, the database user used to create database connections in the data source must have access to the database table. If not, you should either grant access to the user (make this change in the DBMS) or change the Test Table Name attribute to the name of a table to which the user does have access (make this change in the WebLogic Server Administration Console).

  • To manually test a connection from a data source, you can use the Test Data Source feature on the JDBC Data Source: Monitoring: Testing page in the Administration Console (see ” Test JDBC data sources”) or the testPool() method in the JDBCDataSourceRuntimMBean. To test a database connection from a data source, Test Reserved Connections must be enabled and Test Table Name must be defined in the data source configuration. Both are defined by default if you create the data source using the Administration Console.

    When you test a data source, WebLogic Server reserves a connection, tests it using the query defined in Test Table Name, and then releases the connection.

    Reference: Configuring and Managing JDBC Data Sources for Oracle WebLogic Server, Tuning Data Source Connection Pools

    100% Ensurepass Free Download!
    Download Free Demo:1z0-599 Demo PDF
    100% Ensurepass Free Guaranteed!
    Download 2018 EnsurePass 1z0-599 Full Exam PDF and VCE

    EnsurePass ExamCollection Testking
    Lowest Price Guarantee Yes No No
    Up-to-Dated Yes No No
    Real Questions Yes No No
    Explanation Yes No No
    PDF VCE Yes No No
    Free VCE Simulator Yes No No
    Instant Download Yes No No

Leave a Reply

Your email address will not be published. Required fields are marked *