6149. Outbox & Inbox: outbox cleanup — Build success, failure, concurrency and scale tests. — healthcare — Go database/sql
DBMS
Published
Updated
0
Views
Verified
Scenario: A healthcare application must handle outbox cleanup. Build success, failure, concurrency and scale tests. Explain the invariant, SQL strategy, transaction/locking behavior, failure handling, observability and test plan. Use MySQL 8-oriented syntax where applicable.
Looking for the latest
Sarkari Result 2026
updates?
Check the latest government exam
results, merit lists and result updates
on Sarkari Resultess.
Answer & Explanation
4
Answers
Verified
Option 1: Use unparameterized dynamic SQL and rely only on application-side validation for
Use unparameterized dynamic SQL and rely only on application-side validation for outbox cleanup.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.
Verified
Option 2: Disable database protections and repair inconsistent rows manually after outbox
Disable database protections and repair inconsistent rows manually after outbox cleanup runs.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.
Verified
Option 3: Run outbox cleanup without defining transaction boundaries, retry behavior, or p
Run outbox cleanup without defining transaction boundaries, retry behavior, or production validation.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.
Verified
Correct Answer
Option 4: Use a parameterized, transaction-aware MySQL 8 implementation for outbox cleanup
Use a parameterized, transaction-aware MySQL 8 implementation for outbox cleanup, validate the invariant, and explicitly test concurrency, retries and recovery.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.