5992. Sharding & Vitess: keyspace migration — 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 keyspace migration. 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 Correct Answer

Option 1: Use a parameterized, transaction-aware MySQL 8 implementation for keyspace migra

Use a parameterized, transaction-aware MySQL 8 implementation for keyspace migration, 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 keyspace migration.

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 keyspac

Disable database protections and repair inconsistent rows manually after keyspace migration runs.

Additional Explanation

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

Verified

Option 4: Run keyspace migration without defining transaction boundaries, retry behavior,

Run keyspace migration without defining transaction boundaries, retry behavior, or production validation.

Additional Explanation

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