Identify what is wrong with this statement: "SOAP-based Web services A and B are participating in a runtime transaction that is carried out as per the WS-AtomicTransaction standard. When a message…

Question

Options

• AWS-AtomicTransaction does not support the rollback of changes that occur during runtime
• BWS-Policy definitions are not expressed as part of the service contract.
• CSOAP-based Web services cannot have policies and cannot participate in runtime transactions
• DThere is nothing wrong with this statement.

• A
  58% (18)
• B
  13% (4)
• C
  3% (1)
• D
  26% (8)

Explanation

Option A is correct because WS-AtomicTransaction (WS-AT) coordinates distributed transaction protocols - signaling participants to commit or abort - but it does not itself guarantee or execute the rollback of data changes already applied at runtime. Each participant service's own transactional resource manager (e.g., a database) handles actual data reversal; WS-AT only orchestrates the coordination signals, so claiming the transaction is simply "rolled back" overstates what WS-AT controls.

Option B is wrong because WS-Policy definitions can legitimately be expressed as part of a service contract (typically embedded in or referenced from a WSDL document), so that part of the scenario is accurate.

Option C is wrong because SOAP-based web services can both carry WS-Policy assertions and participate in runtime transactions - these capabilities are entirely compatible and commonly used together in enterprise SOA.

Option D is wrong because there clearly is an error: the statement incorrectly implies WS-AT itself rolls back runtime changes, when WS-AT is only a coordination protocol.

Memory tip: Think of WS-AT as a "traffic director" - it can signal all participants to stop (abort), but it cannot drive their cars backward for them. The actual undo of data changes is each service's own responsibility through its local resource manager.

No community discussion yet for this question.