4. You configured Azure Autoscale but notice your app still slows down during peak hours. What is a likely cause?
medium
A. Azure Backup is running during peak hours
B. Azure Monitor is disabled
C. Autoscale rules are not set correctly for CPU or memory thresholds
D. The app is using Azure Security Center
Solution
Step 1: Check autoscale configuration
If autoscale rules do not trigger at correct CPU or memory levels, scaling won't happen on time.
Step 2: Rule out unrelated services
Monitor tracks metrics but does not scale; Backup and Security Center do not affect autoscale directly.
Final Answer:
Autoscale rules are not set correctly for CPU or memory thresholds -> Option C
Quick Check:
Incorrect autoscale rules cause slow app under load [OK]
Hint: Check autoscale thresholds if app slows at peak [OK]
Common Mistakes:
Blaming monitoring or backup services
Ignoring autoscale rule settings
Assuming security affects performance scaling
5. You want to design an Azure app that handles unpredictable traffic spikes efficiently. Which combination best follows the Performance efficiency pillar?
hard
A. Deploy multiple apps without scaling or caching
B. Use fixed VM sizes and manual scaling
C. Use Azure Backup and Security Center only
D. Use Azure Autoscale with Azure Cache for Redis and monitor with Azure Monitor
Solution
Step 1: Identify autoscaling for unpredictable traffic
Azure Autoscale adjusts resources automatically to meet demand spikes.
Step 2: Add caching and monitoring
Azure Cache for Redis speeds data access; Azure Monitor tracks performance to optimize scaling.
Step 3: Eliminate unsuitable options
Fixed VMs and manual scaling can't handle spikes well; Backup and Security Center don't improve performance; no scaling or caching causes slowdowns.
Final Answer:
Use Azure Autoscale with Azure Cache for Redis and monitor with Azure Monitor -> Option D