1Z0-599 Oracle WebLogic Server 12c Essentials

Exam Title: Oracle WebLogic Server 12c Essentials
Exam Number: 1Z0-599
Exam Price: $245.00 More on exam pricing
Format: Multiple Choice
Duration: 120 minutes
Number of Questions: 78
Passing Score: 63%
Validated Against: This exam has been validated against 12c

Take Recommended Training Courses

Complete one of the courses below to prepare for your exam (optional):

Oracle WebLogic Server 12c Implementation Specialist

Additional Preparation and Information

A combination of Oracle training and hands-on experience (attained via labs and/or field experience) provides the best preparation for passing the exam.
Training Opportunities for Oracle Partners (available to partners only)
Relevant OU Training: These courses are relevant to the exam, but may not cover all exam topics. Please carefully compare course topics and exam topics.
Oracle WebLogic Server 12c: Administration I
Oracle WebLogic Server 12c: Administration II
Oracle WebLogic Server 12c: JMS Administration
Oracle WebLogic Server 12c: Performance Tuning Workshop
Oracle WebLogic Server 12c: Troubleshooting Workshop
Oracle WebLogic Server 12c: Enterprise Manager Management Pack

Cloud Application Foundation (CAF) Fundamentals
Describe Cloud Application Foundation concepts
Identify components of WebLogic Suite
Identify differences between WebLogic Server (WLS) SE, EE & Suite
Describe the problem domain of Coherence with WLS
Describe Oracle Cloud Computing business drivers
Describe Virtual Assembly Builder Studio features
Describe supported and custom Appliances for Virtual Assemblies
Describe ActiveCache (WLS and Coherence)

Deploy Java Enterprise Edition (EE) Applications
Describe Java EE 6 and Developer Productivity features
Describe Java Integrated Development Environments (IDE) support
Describe Maven integration features
Describe Java SE packaging
Describe the structure and parts of a Java web application
Describe the structure and parts of a Java enterprise application
Deploy Java EE applications to WLS
Deploy Java EE applications using a Deployment Plan
Deploy WLS shared libraries and associate them with applications
Deploy applications using the WLS Administration Port and Side by Side Deployment
Use the Continuous Integration (CI) and Build Tools that WLS supports (ANT, Maven, etc.)
Enable and use WLS Fast Swap for Rapid Redeployment
Troubleshoot classloading conflicts with the ClassLoader Analysis Tool
Describe WLS Spring Support and how Spring can utilize WLS features
Secure Java EE applications

WebLogic Server Advanced Topics
Describe the value that WLS offers above an EE container
Describe JDBC
Describe WLS Distributed JMS
Describe WLS Clustering
Use Scripting with WLS
Use Automation options for WLS
Describe Remote Procedure Calls (RPC) & Web Services Standards supported by WLS
Describe Web Session and XA Affinity features of Active GridLink
Configure WLS to store Transaction Logs in a Database
Configure systems for High Availability
Configure and use advanced JMS features: Store and Forward
Configure and use advanced JMS features: Unit of Order (UOO) and Unit of Work (UOW)
Configure and use TopLink Grid – Java Persistence API (JPA) and Coherence
Configure systems for ease of Disaster Recovery
Configure and use ActiveCache (WLS and Coherence)
Implement High Availablity (HA) in WLS with Service and Server Migration

WebLogic Server Implementation Best Practices
Create WLS system design consderations
Create a WLS Domain using best practices
Configure a WLS Cluster and Managed Servers using best practices
Configure the JVM where WLS runs using best practices
Configure JDBC Connection Pools using best practices
Configure JMS using best practices
Use Work Managers using best practices
Install with Node Manager using best practices

Integrate Enterprise Manager and WebLogic Server
Integrate Enterprise Manager with WLS
Explain how to position WebLogic Management Pack EE
Describe Real Operation Automation
Describe Real Operation Insight
Use Enterprise Manager Lifecycle Management for WLS
Describe Enterprise Manager Real User Experience Insight
Describe Enterprise Manager Business Transaction Management for WLS
Describe Enterprise Manager Configuration Management for WLS

WebLogic Server Fundamentals
Describe the different WLS distributions that are available
Describe Enterprise Grid Messaging
Describe Active GridLink for Real Application Cluster (RAC) features
Explain WLS Domain concepts
Install WLS
Create and use WLS Domain Templates
Automate WLS administration tasks with WebLogic Scriptiong Tool (WLST)
Secure WLS resources and applications
Configure and use WLS Work Managers, Contexts and Constraints
Create and target JDBC Connection Pools
Create and target JMS Distributed Queues
Create and target JMS Distributed Topics
Configure and use WebLogic Diagnostic Framework (WLDF)
Configure and use JRockit Flight Recorder and WLDF integration
Tune the Application Server Environment including the Java Virtual Machine (JVM) for performance
Troubleshoot and debug WLS using logs and thread dumps

WebLogic Server Management
Use JRockit Mission Control to monitor WLS at runtime
Use JRockit Mission Control to view JRockit Flight Recorder and WLDF data
Monitoring and diagnose WLS for best performance
Use the WLS Admin Console to manage WLS
Start and stop WLS instances using the Node Manager

WebLogic Server System Architecture
Design a scaled-out solution with WLS
Architect a highly available WLS system
Use proxy web server
Use load balancer
Design a WLS system for maximum uptime, availability and business continuity

WebLogic Server Patching and Upgrading with SmartUpdate
Describe how patches are applied to WLS
Apply a rolling patch strategy to a WLS Cluster to ensure maximum availability
Upgrade from WLS 10.3.3 to newer versions
Upgrade from Oracle Application Server (OC4J/OAS) to WLS
Describe Oracle offerings for upgrading from non-Oracle platforms to WLS

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 an architecture with those requirement

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

Answer: B

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

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

Answer: B,D,E

Explanation:

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?

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

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.

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

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

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 application’s 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 DriverManager 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?

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.

Answer: A,C

Explanation:

Click here to view complete Q&A of 1Z0-599 exam
Certkingdom Review, Certkingdom PDF Torrents