S90-08 practice question 29 of 35

Which of the following is not required for an atomic service transaction to be successfully carried out?

Full set: 100 questions
Answer options
A: participating services need to capture a snapshot of current data prior to making changes to it
B: a transaction management system that coordinates the actions of participating services
C: transaction participants need to be limited to atomic service agents Correct answer
D: transaction participants must be able to commit changes or rollback uncommitted changes
Correct Answer:
C. transaction participants need to be limited to atomic service agents
Explanation

An atomic service transaction relies on the ACID (Atomicity, Consistency, Isolation, Durability) principles, which are managed across distributed participants by a transaction coordinator. Key requirements include a central coordinator (transaction management system), and the ability of each participant to either commit its changes or roll them back to a previous state. Capturing a data snapshot is a common mechanism to enable this rollback. However, there is no requirement that participants must be a specific component type called "atomic service agents." Any resource manager, such as a database or a transactional service, that can enlist in the coordination protocol (e.g., Two-Phase Commit) can be a participant.

Why Incorrect

A. Capturing a data snapshot before making changes is a standard technique to ensure a service can roll back to its original state if the transaction aborts, fulfilling the atomicity requirement.
B. A transaction management system is essential for coordinating the distributed participants, ensuring they all either commit or abort together, which is the core function of an atomic transaction.
D. The fundamental capability of any participant in an atomic transaction is to be able to durably commit its work or completely undo it (rollback), ensuring the "all-or-nothing" nature of the transaction.

References

1. Erl, T. (2009). SOA Design Patterns. Prentice Hall. In the "Atomic Service Transaction" pattern description (Pattern 68, pp. 468-473), the text explains the need for a transaction coordinator and for participating services to be transactional (i.e., able to commit or roll back). It does not state that participants are limited to a specific type of agent.

2. Bernstein, P. A., & Newcomer, E. (2009). Principles of Transaction Processing (2nd ed.). Morgan Kaufmann. Chapter 10, "Distributed Transaction Processing," details the roles of transaction managers and resource managers (participants). It clarifies that any resource manager supporting a protocol like XA can participate, without restriction to a specific component type.

3. Oracle Corporation. (2021). Introduction to Oracle Tuxedo ATMI, About Transactions. Oracle Documentation. The documentation on distributed transaction processing explains that participants (resource managers) must be able to work with a transaction manager to coordinate a two-phase commit, defining the required capability, not a specific component type.

Scroll to Top