Oracle WebLogic Server 12c Essentials
Question No: 41
How can you configure High Availability for interacting with a non-Oracle database using WebLogic?
Configure multiple physical data sources and reuse the same JNDI name for each.
Use the quot;compatibilityquot; option of Active GridLink to enable compatibility with non-Oracle databases.
Configure a single physical data source for each node in a database cluster and wrap it using Multi Data Source.
Configure a Data Source Group that contains a physical connection pool to each node in the database cluster.
Answer: C Explanation: Note:
A multi data source can be thought of as a pool of data sources. Multi data sources are best used for failover or load balancing between nodes of a highly available database system, such as redundant databases or Oracle Real Application Clusters (Oracle RAC).
(not B) A single GridLink data source provides connectivity between WebLogic Server and an Oracle Database service, which may include multiple Oracle RAC clusters
High Availability Storage Solutions
If you have applications that need access to persistent stores that reside on remote machines after the migration of a JMS server or JTA transaction log, then you should implement one of the following highly-available storage solutions:
/ File-based stores (default or custom)-Implement a hardware solution, such as a dual-
ported SCSI disk or Storage Area Network (SAN) to make a file store available from shareable disks or remote machines.
/ JDBC-accessible stores-Configure a JDBC store or JDBC TLOG store and use JDBC to access this store, which can be on yet another server. Applications can then take advantage of any high-availability or failover solutions offered by your database vendor. In addition, JDBC stores support GridLink data sources and multi data sources, which provide failover between nodes of a highly available database system, such as Oracle Real Application Clusters (Oracle RAC).
Reference: Oracle Fusion Middleware Configuring Server Environments for Oracle WebLogic Server 12c, High Availability Storage Solutions
Question No: 42
In WebLogic, the development feature to automatically load/refresh the changes of a Java classes at run time is called .
Explanation: Using FastSwap Deployment to Minimize Redeployment
Java EE 5 introduces the ability to redefine a class at runtime without dropping its ClassLoader or abandoning existing instances. This allows containers to reload altered classes without disturbing running applications, vastly speeding up iterative development cycles and improving the overall development and testing experiences. The usefulness of the Java EE dynamic class redefinition is severely curtailed, however, by the restriction that the shape of the class – its declared fields and methods – cannot change. The purpose of FastSwap is to remove this restriction in WLS, allowing the dynamic redefinition of classes with new shapes to facilitate iterative development.
With FastSwap, Java classes are redefined in-place without reloading the ClassLoader, thereby having the decided advantage of fast turnaround times. This means that you do not have to wait for an application to redeploy and then navigate back to wherever you were in the Web page flow. Instead, you can make your changes, auto compile, and then see the effects immediately.
Reference: Using FastSwap Deployment to Minimize Redeployment
Question No: 43
What is the architectural benefit of keeping WebLogic Server transaction log in the database?
Oracle does not allow replicating files between data centers, so keeping transaction log in database allows for replication.
Many transactions in WebLogic are database centric, so keeping log in database makes Two Phase Commit protocol possible.
It obviates the need to keep in sync two replication technologies (file and database) between data centers. The single replication technology is used for frequently changing data.
Transaction log in a file system is extremely slow so it cannot be efficiently replicated.
Explanation: You can configure a JDBC TLOG store to persist transaction logs to a database, which provides the following benefits:
Leverages replication and HA characteristics of the underlying database.
Simplifies disaster recovery by allowing the easy synchronization of the state of the database and TLOGs.
Improved Transaction Recovery service migration as the transaction logs to do not need to be migrated (copied) to a new location.
You can configure a JDBC TLOG store to persist transaction logs to a database, which allows you to leverage replication and HA characteristics of the underlying database,
simplify disaster recovery, and improve Transaction Recovery service migration.
not B: Read-only, One-phase Commit Optimization requires Oracle DB 18.104.22.168.3PSU or above.
Question No: 44
A customer has a WebTrade application that initially uses the embedded LDAP to authenticate users. To enhance security, the customer decides to use OAM to authenticate some of the users against an external LDAP store. For this to work, a customer configured an OAMAuthenticator, but was not sure what to select for the Control Flag. What Control Flag should the customer choose?
Answer: D Explanation:
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.
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:
Reference: Oracle Fusion Middleware Security Guide
Question No: 45
A customer wants to send JMS messages to a remote WebLogic server from a Java SE application over an unreliable network connection. Which feature of WebLogic JMS will enable the customer to send messages from a Java SE client to a JMS destination that is not always easily reached?
SAF Imported Destination
Distributed SAF JMS
Explanation: The JMS SAF Client feature extends the JMS store-and-forward service introduced
in WebLogic Server 9.0 to standalone JMS clients. Now JMS clients can reliably send messages to server-side JMS destinations, even when the client cannot reach a destination (for example, due to a temporary network connection failure). While disconnected from the server, messages sent by a JMS SAF client are stored locally on the client file system and are forwarded to server-side JMS destinations when the
client reconnects. See Reliably Sending Messages Using the JMS SAF Client.
Reference: Programming JMS for Oracle WebLogic Server, Using WebLogic JMS SAF Client
Question No: 46
In WebLogic 10.3.6 and WebLogic 12c on ExaLogic, performance of JMS is further improved through and .
Web Session Affinity
Concurrent Request Manager
Elastic Message Overflow
Answer: B,D Explanation:
D: Elastic message overflow is the ability for WebLogic JMS to take advantage of solid state disks, especially on Exalogic, for paging of JMS messages. This is especially important in spikes of traffic. Access to SSD is much faster than disks or the database, which are used for true persistent storage. This speed of writing and reading enables the system to absorb the spikes in traffic.
Question No: 47
You completed the development of a new application and want to create a new domain in a new environment for functional testing. You want to have the same settings for your new domain as your old domain, with the option of changing the configuration in the new target environment.
Which two actions should you execute?
Use the introspect () command in WLST to gather the configuration information from the original domain.
Use pack/unpack to transfer the domain from one machine to another.
Create a domain template from the original domain using the Domain Template Builder and use the Configuration Wizard to create a new domain from the template.
Use the Admin Console of the original domain to create a domain template from the original domain and use the Configuration Wizard to create a new domain from the template.
Explanation: Using the Domain Template Builder to Create Domain Templates
To create a domain, start the Configuration Wizard and choose a domain configuration template.
Reference: Creating and Configuring Domains Using the Configuration Wizard
Question No: 48
Which three JVM options would you add to investigate performance issues in a Hot-Spot JVM?
Answer: A,B,D Explanation:
Question No: 49
An application is using WebLogic JMS Store and Forward to forward messages from a local JMS queue a remote WebLogic JMS destination. You need to determine if the messages are being sent from the local Weblogic Server.
Where do you find information and metrics about Store and Forward components in the WebLogic Admin Console?
JMS Persistent Store
JMS Distributed Destination
JMS Store and Forward
Automatic Service Migration
Answer: A Explanation: Note:
Persistent messages are saved in the persistent store on the sending side until they are successfully forwarded to and acknowledged by the receiving side.
Question No: 50
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 quot;kill -9quot; once to kill the managed server process.
Run quot;kill -9quot; to kill the managed server process, and run quot;kill -9quot; 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.
|Lowest Price Guarantee||Yes||No||No|
|Free VCE Simulator||Yes||No||No|