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