Which option should you select on this non-XA data source to ensure that orders are still processed as global transactions?

You are responsible for configuration a WebLogic domain to support an order processing
application. This application will communicate with multiple JDBC data sources to fulfill each

customer order. To maintain data integrity across these databases, work will be performed within a
global transaction.
However, you have learned that one of the data sources in the transaction does not have an XA
driver. Which option should you select on this non-XA data source to ensure that orders are still
processed as global transactions?

A.
Ignore Heuristics

B.
Planned to Thread

C.
Password Encrypted

D.
Logging Last Resource

E.
Test Connections on Reserve

Explanation:
The Logging Last Resource option:
Enables a non-XA JDBC connection to participate in distributed transactions using the Logging
Last Resource (LLR) transaction optimization. Recommended in place of Emulate Two-Phase
Commit.
With this option, the transaction branch in which the connection is used is processed as the last
resource in the transaction and is processed as a one-phase commit operation. The result of the
operation is written in a log file on the resource itself, and the result determines the success or
failure of the prepare phase of the transaction. This option offers some performance benefits with
greater data safety than Emulate Two-Phase Commit.
Note: The transaction protocol for a JDBC data source determines how connections from the data
source are handled during transaction processing. Transactions within a JDBC data source are
either global (XA) and non-global (local).
Reference: OTN Home > Oracle WebLogic Server 10.3.1 Documentation > Administration
Console Online Help > JDBC Data Source: Configuration: Transaction