Question 110
An Azure SQL operations team investigates: An organization considers Hyperscale but has not checked application feature compatibility or workload cost. 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 considers Hyperscale but has not checked application feature compatibility or workload cost.) is: The target tier supports projected data growth and tested query and backup behavior under realistic load. It directly tests whether the remediation (Evaluate Azure SQL Database Hyperscale for workloads needing its supported scale-oriented storage architecture and compute choices.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: An organization considers Hyperscale but has not checked application feature compatibility or workload cost. The specific supported administrative response is: Evaluate Azure SQL Database Hyperscale for workloads needing its supported scale-oriented storage architecture and compute choices. The technical risk is: Choosing an unsuitable service tier can impose size or growth constraints on a rapidly expanding database. Confirm the correction with: The target tier supports projected data growth and tested query and backup behavior under realistic load.
Incorrect Answers
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. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: The target tier supports projected data growth and tested query and backup behavior under realistic load.
SQL server on azure virtual machines (1.1) would demonstrate or implement: The application passes functional acceptance on the chosen VM while OS patching, storage and backup responsibilities are explicitly assigned. This case instead tests Hyperscale storage and growth planning (1.2); the choice measures or changes another part of the system.
Columnstore and row compression decisions (1.2) addresses another technical failure: The wrong compression strategy can increase CPU overhead or degrade point-lookup performance despite smaller storage. The paired-answer requirement concerns Hyperscale storage and growth planning (1.2); this alternative does not provide the matching intervention and separate acceptance evidence.