Question 350
An Azure SQL operations team investigates: A DBA must evaluate whether the target Azure SQL service supports the specific capture feature and required retention. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The reported Azure SQL or SQL Server condition is: A DBA must evaluate whether the target Azure SQL service supports the specific capture feature and required retention. The specific supported administrative response is: Choose SQL change tracking or supported change data capture according to whether an integration needs row-change identification or detailed changed-data history. The technical risk is: Confusing lightweight change identifiers with historical before-and-after data can produce incomplete downstream synchronization. Confirm the correction with: A controlled INSERT UPDATE and DELETE sequence produces the required tracking metadata or captured changes for the chosen design.
The acceptance evidence for this incident (A DBA must evaluate whether the target Azure SQL service supports the specific capture feature and required retention.) is: A controlled INSERT UPDATE and DELETE sequence produces the required tracking metadata or captured changes for the chosen design. It directly tests whether the remediation (Choose SQL change tracking or supported change data capture according to whether an integration needs row-change identification or detailed changed-data history.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Diagnosing login and token failures (2.1) addresses another technical failure: Treating every database error as a firewall block can conceal authentication and access-control faults. This choice can be useful for that problem, but it does not establish the Change tracking and change data capture (2.3) control being assessed here.
Least-privilege database roles and grants (2.1) would demonstrate or implement: A permission check proves only the intended schema or table actions succeed for the dedicated workload identity. This case instead tests Change tracking and change data capture (2.3); the choice measures or changes another part of the system.
Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The required paired action and test concerns Change tracking and change data capture (2.3); a passing result for this alternative could leave that requirement unresolved.