6100. CQRS & Event Sourcing: event replay recovery — Review the design for production readiness and required changes. — logistics — C# ASP.NET + ADO.NET

DBMS Published 30 Sept 2026 Updated 30 Sept 2026 0 Views Verified

Scenario: A logistics application must handle event replay recovery. Review the design for production readiness and required changes. 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 Correct Answer

Option 1: Use a parameterized, transaction-aware MySQL 8 implementation for event replay r

Use a parameterized, transaction-aware MySQL 8 implementation for event replay recovery, validate the invariant, and explicitly test concurrency, retries and recovery.

Additional Explanation

Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.

Verified

Option 2: Use unparameterized dynamic SQL and rely only on application-side validation for

Use unparameterized dynamic SQL and rely only on application-side validation for event replay recovery.

Additional Explanation

Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.

Verified

Option 3: Disable database protections and repair inconsistent rows manually after event r

Disable database protections and repair inconsistent rows manually after event replay recovery runs.

Additional Explanation

Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.

Verified

Option 4: Run event replay recovery without defining transaction boundaries, retry behavio

Run event replay recovery without defining transaction boundaries, retry behavior, or production validation.

Additional Explanation

Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.