1Z0-599 Online Practice Questions and Answers

Correct Answer: E

Similar to the configuration information, WebLogic Server runtime MBeans are arranged in a hierarchical data structure. When connected to an Administration Server, you access the runtime MBean hierarchy by entering the serverRuntime or the domainRuntime command. The serverRuntime command places WLST at the root of the server runtime management objects, ServerRuntimeMBean; the domainRuntime command, at the root of the domain-wide runtime management objects, DomainRuntimeMBean.

Reference: WebLogic Scripting Tool, Browsing Runtime MBeans

Correct Answer: D

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.

Correct Answer: E

Session Affinity Policy

Web applications where a user session has back-to-back online transaction processing (OLTP) have

better performance when repeated operations against the same set of records are processed by the same

RAC instance. Business applications such as online shopping and online banking are typical examples of

this pattern.

A GridLink data source uses the Session Affinity policy to ensure all the data base operations for a web

session, including transactions, are directed to the same Oracle RAC instance of a RAC cluster.

Note:

The context is stored in the HTTP session. It is up to the application how windows (within a browser or

across browsers) are mapped to HTTP sessions.

Note 2:

*

GridLink Affinity WebLogic Server GridLink affinity policies are designed to improve application performance by maximizing RAC cluster utilization. A GridLink data source monitors RAC load balancing advisories (LBAs) using the AffEnabled attribute to determine if RAC affinity is enabled for a RAC cluster. The first connection request is load balanced using Runtime Connection Load- Balancing (RCLB) and is assigned an Affinity context. All subsequent connection requests are routed to the same Oracle RAC instance using the Affinity context of the first connection until the session ends or the transaction completes.

*

Session Affinity

Reference; Configuring and Managing JDBC Data Sources for Oracle Weblogic server 12c, Using GridLink Data Sources

Correct Answer: AB

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.

Correct Answer: D

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

Correct Answer: ACD

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

Correct Answer: C

Note:

* When you configure multiple Authentication providers, use the JAAS Control Flag for each provider to control how the Authentication providers are used in the login sequence. You can choose the following the JAAS Control Flag settings, among others:

REQUIRED--The Authentication provider is always called, and the user must always pass its authentication test. Regardless of whether authentication succeeds or fails, authentication still continues down the list of providers.

SUFFICIENT--The user is not required to pass the authentication test of the Authentication provider. If authentication succeeds, no subsequent Authentication providers are executed. If authentication fails, authentication continues down the list of providers.

OPTIONAL--The user is allowed to pass or fail the authentication test of this Authentication provider. However, if all Authentication providers configured in a security realm have the JAAS Control Flag set to OPTIONAL, the user must pass the authentication test of one of the configured providers.

* Example:

Setting the Order of Providers

Re-order the OAM Identity Asserter, OID Authenticator, and Default Authenticator by ensuring that the control flag for each authenticator is set as follows:

OAMAuthenticator (REQUIRED) OracleInternetDirectoryAuthenticator (SUFFICIENT)

DefaultAuthenticator (SUFFICIENT)

Reference: Oracle Fusion Middleware Security Guide

Correct Answer: C

Using JNDI, a JMS client can obtain access to a JMS provider by first looking up a ConnectionFactory. The ConnectionFactory is used to create JMS connections, which can then be used for sending and receiving messages. Destination objects, which represent virtual channels (topics and queues) in JMS, are also obtained via JNDI and are used by the JMS client. The directory service can be configured by the system administrator to provide JMS administered objects so that the JMS clients don't need to use proprietary code to access a JMS provider.

Note:

* The Java Naming and Directory Interface (JNDI) is part of the Java platform, providing applications based on Java technology with a unified interface to multiple naming and directory services.

Correct Answer: B

fair-share-request-class--Specifies the average thread-use time required to process requests. The default fair share value is 50.

For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA specifies a fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-sharerequest-class of 20. During a period of sufficient demand, with a steady stream of requests for each module such that the number requests exceed the number of threads, WebLogic Server will allocate 80% and 20% of the thread-usage time to ModuleA and ModuleB, respectively.

* Example:

lowpriority_workmanager low_priority 10

highpriority_workmanager high_priority 100

Note:

* A request class expresses a scheduling guideline that WebLogic Server uses to allocate threads to requests. Request classes help ensure that high priority work is scheduled before less important work, even if the high priority work is submitted after the lower priority work.

Incorrect:

Not C: response-time-request-class--Specifies a response time goal in milliseconds. Response time goals

are not applied to individual requests. Instead, WebLogic Server computes a tolerable waiting time for

requests with that class by subtracting the observed average thread use time from the response time goal,

and schedules requests so that the average wait for requests with the class is proportional to its tolerable

waiting time.

Not A, D: Not related to thread constraints.

For example, assume that WebLogic Server is running two modules. The Work Manager for ModuleA

specifies a fair-share-request-class of 80 and the Work Manager for ModuleB specifies a fair-sharerequest-class of 20.

Correct Answer: B

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'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