1Z0-133 · Question #102
You decide to use a database to store WebLogic Server transaction logs for a managed server. Which two steps are required to configure this?
The correct answer is A. Under the managed server's Services configuration, select"JDBC" as the type for the transaction C. Create an on-XA data source in the domain for the database transaction log. See the full explanation below for the reasoning.
Question
You decide to use a database to store WebLogic Server transaction logs for a managed server. Which two steps are required to configure this?
Options
- AUnder the managed server's Services configuration, select"JDBC" as the type for the transaction
- BUnder the managed server's Services configuration, select "Disable the Default store."
- CCreate an on-XA data source in the domain for the database transaction log
- DCreate an XA data source in the domain for the database transaction log.
How the community answered
(41 responses)- A73% (30)
- B7% (3)
- D20% (8)
Community Discussion
4
Dervla O.Apr 9, 2026A and C are your picks here, and the logic is clean: you need a non-XA data source (C) because the transaction log store itself cannot participate in XA transactions, and then you point the managed server's Services configuration to JDBC as the store type (A) to wire it up. D is the trap, since XA would create a circular dependency with the TX log, and B is pure noise because you are not disabling the default store, you are replacing it.
Bao N.Mar 28, 2026A is straightforward but C is where people burn themselves because they second-guess it and pick D thinking "transactions need XA," but the TLog store itself is a non-XA data source, so D is the trap. Lock in A and C.
Dervla O.Mar 31, 2026The C instinct is right but worth naming why: once you eliminate the XA-required distractors, C survives not because it sounds authoritative but because nothing in the remaining options actually conflicts with the constraint the stem gives you.
Prof. SaraApr 1, 2026The first time I sat with this one on a practice run, I almost circled D out of habit because XA feels right when you hear "transactions," but the TLOG store itself cannot participate in an XA transaction, so WebLogic specifically requires a non-XA data source paired with flipping the type to JDBC under Services, and that A-plus-C combo is what locks it in. Burn the phrase "TLOG needs non-XA" into your brain before test day and you will not give D a second glance.