Free Download 1z0-599 Examp Dump: Oracle.1z0-599.CertDumps.2017-12-10.91q.vcex

Question 1

You deploy more than one application to the same WebLogic container. The security is set on JavaEE level and all deployed JavaEE applications use the same security roles.

What is your recommendation for architecture with those requirements?

Combine all applications into a single one.
Define global roles on the WebLogic Domain level.
Use Ms Active Directory to keep the roles there.
Use Oracle Identity and Access Management solution to simplify the management.
Keep role mapping in the external WebLogic Role Mapped developed for that solution.

Correct answer: B

Explanation:

Note:* Types of Security Roles: Global Roles and Scoped RolesThere are two types of security roles in WebLogic Server:/ A global security role can be used in any security policy. Oracle provides several default global roles that you can use out of the box to secure your WebLogic resource / A scoped role can be used only in policies that are defined for a specific instance of a WebLogic resource (such as a method on an EJB or a branch of a JNDI tree). You might never need to use scoped roles. They are provided for their flexibility and are an extra feature for advanced customers. Incorrect:Not E: Role mapping is the process whereby principals (users or groups) are dynamically mapped to security roles at runtime. In WebLogic Server, a Role Mapping provider determines what security roles apply to the principals stored a subject when the subject is attempting to perform an operation on a WebLogic resource. Because this operation usually involves gaining access to the WebLogic resource, Role Mapping providers are typically used with Authorization providers.

Note:

* Types of Security Roles: Global Roles and Scoped Roles

There are two types of security roles in WebLogic Server:

/ A global security role can be used in any security policy. Oracle provides several default global roles that you can use out of the box to secure your WebLogic resource

/ A scoped role can be used only in policies that are defined for a specific instance of a WebLogic resource (such as a method on an EJB or a branch of a JNDI tree). You might never need to use scoped roles. They are provided for their flexibility and are an extra feature for advanced customers.

Incorrect:

Not E: Role mapping is the process whereby principals (users or groups) are dynamically mapped to security roles at runtime. In WebLogic Server, a Role Mapping provider determines what security roles apply to the principals stored a subject when the subject is attempting to perform an operation on a WebLogic resource. Because this operation usually involves gaining access to the WebLogic resource, Role Mapping providers are typically used with Authorization providers.

Question 2

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?

Assign more than one managed server to a physical hardware that allows better CPU utilization.
Assign more than one application to one managed server to better utilize threads within a single JVM process.
Assign the same application to more than one managed server to load balance requests between servers.
Assign the same heap size to the managed server across the cluster for easier control of memory footprint
Create a virtualized environment with hypervisor for an easier solution

Correct answer: BDE

Question 3

A highly available WebLogic cluster in UNIX is configured for automatic server migration. Node Managed is configured on both machines to start managed servers.

How should you simulate a managed server failure to test whether automatic server migration is working?

Shut down the managed server from the WebLogic console.
Shut down the managed server using the WLST command through Node Manager.
Run "kill -9" once to kill the managed server process.
Run "kill -9" to kill the managed server process, and run "kill -9" one more time if the managed server is restarting.

Correct answer: A

Explanation:

Note:It is recommended that you shutdown WebLogic Server instances through the Administration Console. If automatic server migration is enabled, the servers are required to contact the cluster leader and renew their leases periodically. Servers will shut themselves down if they are unable to renew their leases. The failed servers will then be automatically migrated to the machines in the majority partition.

Note:

It is recommended that you shutdown WebLogic Server instances through the Administration Console.
If automatic server migration is enabled, the servers are required to contact the cluster leader and renew their leases periodically. Servers will shut themselves down if they are unable to renew their leases. The failed servers will then be automatically migrated to the machines in the majority partition.

Question 4

A customer claims that while redeploying a web application in the production system all their customers have to log in again. What do you recommend?

Sessions can't be preserved when redeploying applications. The customer needs to consider redeployment during late nights when the traffic is low.
Change the flag responsible for the development mode of their environment. In the production mode, all sessions are preserved while redeploying application.
Change Hotspot to JRockit. Sessions can't be preserved on HotSpot when redeploying application.
Use flag -version when redeploying the application. This will switch on the Side By Side deployment feature and preserve existing sessions.
Open a service request with Oracle Support. This is unexpected behavior. Sessions are preserved without any extra settings.

Correct answer: D

Explanation:

Restrictions on Production Redeployment Updates WebLogic Server can host a maximum of two different versions of an application at one time. Note:* When you redeploy a new version of an application, you cannot change:An application's deployment targets An application's security model A Web applications persistent store settings To change any of the above features, you must first undeploy the active version of the application. Incorrect:(not A) Production redeployment enables you to update and redeploy an application in a production environment without stopping the application or otherwise interrupting the application's availability* to clients. Production redeployment saves you the trouble of scheduling application downtime, setting up redundant servers to host new application versions, manually managing client access to multiple application versions, and manually retiring older versions of an application. (not C) Not dependant on whether the application is JRockit or Hotspot. (not E) The production redeployment strategy is supported for:Standalone Web Application (WAR) modules and enterprise applications (EARs) whose clients access the application via a Web application (HTTP). Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests. All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services. Production redeployment is not supported for:Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules. Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server. Applications that obtain JDBC data sources via the Driver Manager API; in order to use production redeployment, an application must instead use JNDI to look up data sources. Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP. Reference: Reference; Deploying Applications to Oracle WebLogic Server 12c, Redeploying Applications in a Production Environment

Restrictions on Production Redeployment Updates

WebLogic Server can host a maximum of two different versions of an application at one time.

Note:

* When you redeploy a new version of an application, you cannot change:

An application's deployment targets
An application's security model
A Web applications persistent store settings

To change any of the above features, you must first undeploy the active version of the application.

Incorrect:

(not A)
Production redeployment enables you to update and redeploy an application in a production environment without stopping the application or otherwise interrupting the application's availability* to clients. Production redeployment saves you the trouble of scheduling application downtime, setting up redundant servers to host new application versions, manually managing client access to multiple application versions, and manually retiring older versions of an application.
(not C) Not dependant on whether the application is JRockit or Hotspot.
(not E)

The production redeployment strategy is supported for:

Standalone Web Application (WAR) modules and enterprise applications (EARs) whose clients access the application via a Web application (HTTP).

Enterprise applications that are accessed by inbound JMS messages from a global JMS destination, or from inbound JCA requests.

All types of Web Services, including conversational and reliable Web Services, but not 8.x Web Services.

Production redeployment is not supported for:

Standalone EJB or RAR modules. If you attempt to use production redeployment with such modules, WebLogic Server rejects the redeployment request. To redeploy such modules, remove their version identifiers and explicitly redeploy the modules.

Applications that use JTS drivers. For more information on JDBC application module limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.

Applications that obtain JDBC data sources via the Driver Manager API; in order to use production redeployment, an application must instead use JNDI to look up data sources.

Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use production redeployment with applications that include CMP EJBs, use EJB 2.x CMP instead of EJB 1.1 CMP.

Reference: Reference; Deploying Applications to Oracle WebLogic Server 12c, Redeploying Applications in a Production Environment

Question 5

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?

There may be a bottleneck in the application that additional hardware would not solve.
Adding more hardware is costly and time consuming.
Adding hardware at the application layer may place additional load on an already overloaded database, network appliance, or storage system.
Adding more hardware may introduce new configuration requirements that need to be tested.

Correct answer: AC

Question 6

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?

The Web Session Affinity feature of Active GridLink for RAC
WebLogic Clustering
The Transaction Affinity feature of Active GridLink for RAC
Coherence*Web Session Replication

Correct answer: C

Explanation:

WebLogic GridLink Data Sources supports transaction-based affinity. Reference: http://www.oracle.com/technetwork/middleware/weblogic/gridlink-rac-wp-494900.pdf

WebLogic GridLink Data Sources supports transaction-based affinity.

Reference: http://www.oracle.com/technetwork/middleware/weblogic/gridlink-rac-wp-494900.pdf

Question 7

A customer needs to implement a Highly Available solution for JMS that has a primary data center and a backup. Which three steps would you perform when designing your solution?

Store Transaction Logs in a database and use Database stores for JMS to make replication between sites easier.
Use file based Transaction Logs and JMS stores and implement a separate replication solution for files in addition to database in case database replication fails.
Implement Oracle RAC at each site to provide a highly available solution within each datacenter.
Configure Whole Server Migration to migrate WebLogic Managed Servers from the primary to the secondary site.
Configure Automatic Service Migration for JMS high availability within a datacenter.

Correct answer: ACE

Explanation:

Note:

Question 8

Which WebLogic optimization allows one non-XA resource to participate in a distributed transaction?

enabling Pinned to Thread
enabling Logging Last Resource
increasing the Statement cache size
setting the statement cache type to LRU
setting the initial and maximum capacity to the same number

Correct answer: B

Explanation:

Oracle WebLogic Server Logging Last Resource (LLR) An additional option for XA transactions is Oracle WebLogic Server’s Logging Last Resource (LLR) transaction optimization through JDBC data sources. LLR is a performance enhancement option that enables one non-XA resource to participate in a distributed transaction with the same ACID guarantee as XA. In a distributed transaction with an LLR participant, the Oracle WebLogic Server transaction Reference: http://www.oracle.com/technetwork/products/clustering/overview/distributed-transactions-and-xa-163941.pdf

Oracle WebLogic Server Logging Last Resource (LLR) An additional option for XA transactions is Oracle WebLogic Server’s Logging Last Resource (LLR) transaction optimization through JDBC data sources. LLR is a performance enhancement option that enables one non-XA resource to participate in a distributed transaction with the same ACID guarantee as XA. In a distributed transaction with an LLR participant, the Oracle WebLogic Server transaction

Reference: http://www.oracle.com/technetwork/products/clustering/overview/distributed-transactions-and-xa-163941.pdf

Question 9

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?

JMS Queue
Distributed JMS Queue
Uniform Distributed Topic
Partitioned Distributed Topic

Correct answer: A

Explanation:

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 have to be delivered in the order sent A JMS queue only guarantees that each message is processed only once. Reference: http://integrationspot.blogspot.com/2011/03/jms-queue-difference-between-queue-and.html

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 have to be delivered in the order sent A JMS queue only guarantees that each message is processed only once.

Reference: http://integrationspot.blogspot.com/2011/03/jms-queue-difference-between-queue-and.html

Question 10

A customer has a critical, performance-sensitive web application that connects to a multimode Oracle RAC database. Which feature of WebLogic can provide signification benefit?

The Web Session Affinity feature of Active GridLink for RAC.
WebLogic Clustering
The Transaction Affinity feature of Active GridLink for RAC
Coherence*Web Session Replication

Correct answer: C

Explanation:

Active GridLink for Oracle RAC In Oracle WebLogic Server 10.3.4, a single data source implementation has been introduced to support an Oracle RAC cluster. It responds to FAN events to provide Fast Connection Failover (FCF), Runtime Connection Load-Balancing (RCLB), and RAC instance graceful shutdown. XA affinity is supported at the global transaction Id level. The new feature is called WebLogic Active GridLink for RAC; which is implemented as the GridLink data source within WebLogic Server. Note:* The WebLogic Server JDBC subsystem has supported Oracle RAC since WLS version 9.0, originally developed for Oracle9i RAC. This support is based on a particular type of data source configuration, called a multi data source. A multi data source is a data source abstraction over one or more individual data sources. It serves JDBC connections from each of the member data sources according to a specified policy. A RAC multi data source configuration requires that each member data source obtain connections to a particular RAC instance. Reference: How-To: Use Oracle WebLogic Server with a JDBC GridLink Data Source

Active GridLink for Oracle RAC

In Oracle WebLogic Server 10.3.4, a single data source implementation has been introduced to support an Oracle RAC cluster. It responds to FAN events to provide Fast Connection Failover (FCF), Runtime Connection Load-Balancing (RCLB), and RAC instance graceful shutdown. XA affinity is supported at the global transaction Id level. The new feature is called WebLogic Active GridLink for RAC; which is implemented as the GridLink data source within WebLogic Server.

Note:

* The WebLogic Server JDBC subsystem has supported Oracle RAC since WLS version 9.0, originally developed for Oracle9i RAC. This support is based on a particular type of data source configuration, called a multi data source. A multi data source is a data source abstraction over one or more individual data sources. It serves JDBC connections from each of the member data sources according to a specified policy. A RAC multi data source configuration requires that each member data source obtain connections to a particular RAC instance.

Reference: How-To: Use Oracle WebLogic Server with a JDBC GridLink Data Source

Exam	Oracle WebLogic Server 12c Essentials
Number	1z0-599
File Name	Oracle.1z0-599.CertDumps.2017-12-10.91q.vcex
Size	822 KB
Posted	Dec 10, 2017
Download	Oracle.1z0-599.CertDumps.2017-12-10.91q.vcex

Download Oracle.1z0-599.CertDumps.2017-12-10.91q.vcex

File Info

How to open VCEX & EXAM Files?

Demo Questions