4026. Replication & HA: multi-source channel control — Reduce cost/latency while preserving semantics. — messaging — Java Spring/JDBC

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

Scenario: A messaging application must handle multi-source channel control. Reduce cost/latency while preserving semantics. 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: Disable database protections and repair inconsistent rows manually after multi-s

Disable database protections and repair inconsistent rows manually after multi-source channel control runs.

Additional Explanation

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

Verified

Option 2: Run multi-source channel control without defining transaction boundaries, retry

Run multi-source channel control 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 3: Use a parameterized, transaction-aware MySQL 8 implementation for multi-source c

Use a parameterized, transaction-aware MySQL 8 implementation for multi-source channel control, 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 4: Use unparameterized dynamic SQL and rely only on application-side validation for

Use unparameterized dynamic SQL and rely only on application-side validation for multi-source channel control.

Additional Explanation

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