5237. Stored Programs: procedure dependency audit — Harden the workflow against privilege or data-exposure risks. — School ERP — Python + FastAPI + SQLAlchemy

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

Scenario: A School ERP application must handle procedure dependency audit. Harden the workflow against privilege or data-exposure risks. 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 procedure dependency audit.

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 procedu

Disable database protections and repair inconsistent rows manually after procedure dependency audit runs.

Additional Explanation

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

Verified

Option 3: Run procedure dependency audit without defining transaction boundaries, retry be

Run procedure dependency audit 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 procedure depe

Use a parameterized, transaction-aware MySQL 8 implementation for procedure dependency audit, validate the invariant, and explicitly test concurrency, retries and recovery.

Additional Explanation

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