Question 90
An Azure SQL operations team investigates: A function app opens a database after extended inactivity and sees elevated first-connection latency. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A function app opens a database after extended inactivity and sees elevated first-connection latency.) is: Observed idle periods, startup latency and actual billing confirm that serverless meets the application service objectives. It directly tests whether the remediation (Use a supported Azure SQL Database serverless compute configuration for intermittent usage when automatic scaling or pausing suits latency requirements.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A function app opens a database after extended inactivity and sees elevated first-connection latency. The specific supported administrative response is: Use a supported Azure SQL Database serverless compute configuration for intermittent usage when automatic scaling or pausing suits latency requirements. The technical risk is: Auto-pause resume delay and compute minimum settings can be unsuitable for continuous low-latency traffic. Confirm the correction with: Observed idle periods, startup latency and actual billing confirm that serverless meets the application service objectives.
Incorrect Answers
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. This choice can be useful for that problem, but it does not establish the Azure SQL database serverless compute (1.2) control being assessed here.
Online migration with minimal downtime (1.3) would demonstrate or implement: A rehearsal verifies initial load, ongoing synchronization, controlled write freeze and post-cutover consistency. This case instead tests Azure SQL database serverless compute (1.2); the choice measures or changes another part of the system.
Azure SQL migration readiness assessment (1.3) addresses another technical failure: Choosing a target from server size alone can miss unsupported features and production performance needs. The required paired action and test concerns Azure SQL database serverless compute (1.2); a passing result for this alternative could leave that requirement unresolved.