Scenario: A e-commerce application must handle fact-table grain validation. 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 fact-table grain validation.
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 fact-ta
Disable database protections and repair inconsistent rows manually after fact-table grain validation runs.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.
Verified
Option 3: Run fact-table grain validation without defining transaction boundaries, retry b
Run fact-table grain validation 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 fact-table gra
Use a parameterized, transaction-aware MySQL 8 implementation for fact-table grain validation, validate the invariant, and explicitly test concurrency, retries and recovery.
Additional Explanation
Correctness depends on explicit invariants, safe SQL, transaction/concurrency handling and verification.