6751. SQL Security Testing: stored-procedure injection defense — Design the database contract and invariants. — HRMS — Laravel Query Builder

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

Scenario: A HRMS application must handle stored-procedure injection defense. Design the database contract and invariants. 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: Run stored-procedure injection defense without defining transaction boundaries,

Run stored-procedure injection defense 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 2: Use a parameterized, transaction-aware MySQL 8 implementation for stored-procedu

Use a parameterized, transaction-aware MySQL 8 implementation for stored-procedure injection defense, 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 3: Use unparameterized dynamic SQL and rely only on application-side validation for

Use unparameterized dynamic SQL and rely only on application-side validation for stored-procedure injection defense.

Additional Explanation

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

Verified

Option 4: Disable database protections and repair inconsistent rows manually after stored-

Disable database protections and repair inconsistent rows manually after stored-procedure injection defense runs.

Additional Explanation

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