6917. Operational Snapshots: aggregate-table refresh — Harden the workflow against privilege or data-exposure risks. — messaging — Java Spring/JDBC

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

Scenario: A messaging system needs aggregate-table refresh. Harden the workflow against privilege or data-exposure risks. 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 aggregate-table refresh with uncontrolled reads and assume the result is

Create aggregate-table refresh 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 aggregate-table refresh before validation and repair discrepancies later

Publish aggregate-table refresh 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 aggregate-table refresh faster.

Disable transaction/consistency controls to make aggregate-table refresh faster.

Additional Explanation

A production snapshot needs an explicit consistency boundary and verification.

Verified Correct Answer

Option 4: Create aggregate-table refresh with an explicit consistency boundary, parameteri

Create aggregate-table refresh 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.