Question 130
An Azure SQL operations team investigates: An application experiences worse singleton lookups after a broad columnstore conversion and needs to re-evaluate design. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (An application experiences worse singleton lookups after a broad columnstore conversion and needs to re-evaluate design.) is: Before-and-after size, CPU and representative query tests establish the net benefit of the selected compression. It directly tests whether the remediation (Evaluate row, page, or columnstore compression based on workload and service support rather than assuming one compression method fits all.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: An application experiences worse singleton lookups after a broad columnstore conversion and needs to re-evaluate design. The specific supported administrative response is: Evaluate row, page, or columnstore compression based on workload and service support rather than assuming one compression method fits all. The technical risk is: The wrong compression strategy can increase CPU overhead or degrade point-lookup performance despite smaller storage. Confirm the correction with: Before-and-after size, CPU and representative query tests establish the net benefit of the selected compression.
Incorrect Answers
Azure SQL database elastic pools (1.2) addresses another technical failure: Provisioning every idle tenant database for its own peak can waste capacity while a mis-sized pool causes noisy-neighbor contention. This choice can be useful for that problem, but it does not establish the Columnstore and row compression decisions (1.2) control being assessed here.
Online migration with minimal downtime (1.3) addresses another technical failure: A one-time copy while writes continue can leave the target behind unless changes are captured until cutover. This case instead tests Columnstore and row compression decisions (1.2); the choice measures or changes another part of the system.
Azure arc-enabled SQL server inventory (1.1) would demonstrate or implement: Connected eligible instances appear in centralized Azure management views with expected metadata and authorized access. The paired-answer requirement concerns Columnstore and row compression decisions (1.2); this alternative does not provide the matching intervention and separate acceptance evidence.