Question 100
An Azure SQL operations team investigates: A team selects the cheapest SQL tier without measuring the database's stringent transaction latency requirement. 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 team selects the cheapest SQL tier without measuring the database's stringent transaction latency requirement. The specific supported administrative response is: Select an appropriate Business Critical service tier for supported high-IOPS and low-latency workloads where its architecture meets requirements. The technical risk is: Under-sizing storage IO or latency for transaction-heavy databases can cause persistent response-time problems. Confirm the correction with: Benchmark results show the chosen service objective meets transaction latency and availability targets within budget.
The acceptance evidence for this incident (A team selects the cheapest SQL tier without measuring the database's stringent transaction latency requirement.) is: Benchmark results show the chosen service objective meets transaction latency and availability targets within budget. It directly tests whether the remediation (Select an appropriate Business Critical service tier for supported high-IOPS and low-latency workloads where its architecture meets requirements.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Azure SQL database platform fit (1.1) addresses another technical failure: Moving an application with unsupported instance dependencies to a logical database can break its procedures or operations. The case states: A team selects the cheapest SQL tier without measuring the database's stringent transaction latency requirement. The most direct paired action and test is: Select an appropriate Business Critical service tier for supported high-IOPS and low-latency workloads where its architecture meets requirements.
Hybrid SQL server patch planning (1.1) would demonstrate or implement: Inventory and maintenance evidence show approved versions, tested failback and healthy application connectivity. The required paired action and test concerns Azure SQL business critical tier selection (1.2); a passing result for this alternative could leave that requirement unresolved.
Table partitioning for large tables (1.2) addresses another technical failure: Partitioning without a matching access pattern or maintenance plan can complicate administration without improving queries. The paired-answer requirement concerns Azure SQL business critical tier selection (1.2); this alternative does not provide the matching intervention and separate acceptance evidence.