Question 360
An Azure SQL operations team investigates: An organization needs to decide when built-in ledger features suit audit evidence requirements. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (An organization needs to decide when built-in ledger features suit audit evidence requirements.) is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records. It directly tests whether the remediation (Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: An organization needs to decide when built-in ledger features suit audit evidence requirements. The specific supported administrative response is: Use supported ledger tables and digest verification for scenarios requiring tamper-evident SQL record history, with appropriate external digest storage. The technical risk is: Audit logs alone or editable records cannot guarantee detection of all later data history alterations. Confirm the correction with: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.
Incorrect Answers
Microsoft entra administrator for azure SQL (2.1) addresses another technical failure: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: An external digest and ledger verification detect a controlled unauthorized alteration of historical records.
SQL database auditing and audit storage (2.3) addresses another technical failure: Audit events written only to a disposable or broadly writable destination may be lost or tampered with. This choice can be useful for that problem, but it does not establish the SQL ledger tamper-evidence (2.3) control being assessed here.
Always encrypted secure enclave workloads (2.2) would demonstrate or implement: Supported comparison or indexing operations succeed through the enclave-enabled client and unauthorized plaintext access remains blocked. This case instead tests SQL ledger tamper-evidence (2.3); the choice measures or changes another part of the system.