6965. Operational Snapshots: billing-cycle snapshot — Recover from failure without violating consistency. — e-commerce — Node.js + Express + Sequelize

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

Scenario: A e-commerce system needs billing-cycle snapshot. Recover from failure without violating consistency. Define the snapshot boundary, consistency rules, failure handling, validation and recovery strategy.

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: Create billing-cycle snapshot with uncontrolled reads and assume the result is a

Create billing-cycle snapshot with uncontrolled reads and assume the result is always consistent.

Additional Explanation

A production snapshot needs an explicit consistency boundary and verification.

Verified

Option 2: Publish billing-cycle snapshot before validation and repair discrepancies later.

Publish billing-cycle snapshot before validation and repair discrepancies later.

Additional Explanation

A production snapshot needs an explicit consistency boundary and verification.

Verified

Option 3: Disable transaction/consistency controls to make billing-cycle snapshot faster.

Disable transaction/consistency controls to make billing-cycle snapshot faster.

Additional Explanation

A production snapshot needs an explicit consistency boundary and verification.

Verified Correct Answer

Option 4: Create billing-cycle snapshot with an explicit consistency boundary, parameteriz

Create billing-cycle snapshot with an explicit consistency boundary, parameterized SQL, deterministic validation and safe retry/recovery handling.

Additional Explanation

A production snapshot needs an explicit consistency boundary and verification.