Question No : 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 No : 2
In the absence of shared storage between cluster nodes, which two actions can you take to
configure a High Availability architecture?
A. Move domain logs to a highly available database.
B. Move server logs to a highly available database.
C. Move transaction logs to a highly available database.
D. Move JMS persistent stores to a highly available database.
E. Move error logs to a highly available database.
Answer: C,D
Question No : 3
What are four benefits of recommended basic architecture?
A. Good load balancing between Presentation Tier and Object Tier
B. Easy administration
C. Flexible Load balancing
D. Optimal performance
E. Simple security
Answer: B,C,D,E
Question No : 4
How can you configure High Availability for interacting with a non-Oracle database using
WebLogic?
A. Configure multiple physical data sources and reuse the same JNDI name for each.
B. Use the "compatibility" option of Active GridLink to enable compatibility with non-Oracle
databases.
C. Configure a single physical data source for each node in a database cluster and wrap it
using Multi Data Source.
D. 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 dualported 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 : 5
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?
A. SAF Target
B. SAF Imported Destination
C. SAF Client
D. SAF Server
E. Distributed SAF JMS
Answer: C
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
No comments:
Post a Comment