6726. SQL Security Testing: LIKE escaping — Reduce cost/latency while preserving semantics. — SaaS — PHP PDO

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

Scenario: A SaaS application must handle LIKE escaping. 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 LIKE es

Disable database protections and repair inconsistent rows manually after LIKE escaping runs.

Additional Explanation

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

Verified

Option 2: Run LIKE escaping without defining transaction boundaries, retry behavior, or pr

Run LIKE escaping 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 LIKE escaping,

Use a parameterized, transaction-aware MySQL 8 implementation for LIKE escaping, 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 LIKE escaping.

Additional Explanation

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