You configure an Azure App Service with autoscale rules based on CPU usage. The rule scales out by adding one instance when CPU usage exceeds 70% for 5 minutes. What happens if CPU usage spikes to 80% for 3 minutes and then drops to 60%?
Autoscale rules require the condition to be true for the full duration specified.
Autoscale triggers only after the CPU usage exceeds the threshold continuously for the specified time (5 minutes). A 3-minute spike does not trigger scaling.
You need to store large amounts of unstructured data with high read throughput and low latency. Which Azure storage option best fits this requirement?
Consider storage optimized for large unstructured data and fast reads.
Azure Blob Storage in Hot tier is optimized for high throughput and low latency for unstructured data. File Storage is for SMB/NFS file shares, Table Storage is for NoSQL key-value, and Queue Storage is for messaging.
You apply a complex Network Security Group (NSG) with many rules to an Azure Virtual Machine subnet. What is the likely impact on network performance?
Think about how packet filtering works in Azure.
NSGs evaluate rules on each packet which can add slight latency, but Azure optimizes this process so throughput impact is minimal.
You configure Azure Cosmos DB with strong consistency. How does this choice affect read latency compared to eventual consistency?
Consider how data synchronization affects response times.
Strong consistency requires coordination among replicas to ensure the latest data, increasing read latency compared to eventual consistency which reads locally.
You have an Azure Function app that experiences cold start delays impacting user experience. Which approach best reduces cold start latency?
Consider plans that keep instances warm to avoid cold starts.
The Premium plan with Always On keeps instances warm, eliminating cold start delays. Consumption plan with pre-warmed instances is not available; increasing timeout or multiple apps does not reduce cold start latency.