5442. Transactions & XA: savepoint strategy — Implement the workflow with safe SQL and application handling. — subscription billing — Python + FastAPI + SQLAlchemy

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

Scenario: A subscription billing application must handle savepoint strategy. Implement the workflow with safe SQL and application handling. 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: Disable database protections and repair inconsistent rows manually after savepoi

Disable database protections and repair inconsistent rows manually after savepoint strategy runs.

Additional Explanation

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

Verified

Option 2: Run savepoint strategy without defining transaction boundaries, retry behavior,

Run savepoint strategy 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 3: Use a parameterized, transaction-aware MySQL 8 implementation for savepoint stra

Use a parameterized, transaction-aware MySQL 8 implementation for savepoint strategy, 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 4: Use unparameterized dynamic SQL and rely only on application-side validation for

Use unparameterized dynamic SQL and rely only on application-side validation for savepoint strategy.

Additional Explanation

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