During a pilot, an administrator notices two newly split services constantly calling each other to complete what used to be a single unit of work. What does this symptom indicate?
Select an answer to reveal the explanation.
Short Explanation
Chatty services calling back and forth to finish one job is the classic sign a transaction got cut in half. You split a single atomic operation across two services without handling shared state and transactionality.
Full Explanation
The correct answer is the shared-state and transactionality explanation: when an operation that must commit as one unit ends up spanning two services, they compensate by calling each other repeatedly, which shows up as chatter rather than as a clean, independent call. The compute-sizing option is incorrect because more compute does not resolve a coordination problem caused by a misplaced boundary. The network-misconfiguration option is incorrect because the calls are happening successfully; the issue is that they need to happen at all. The incompatible-languages option is incorrect because language mismatch is unrelated to this symptom. For the exam, read repeated cross-service calls to finish one operation as a boundary defect.