New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft AZ-204 Exam - Topic 19 Question 45 Discussion

Actual exam question for Microsoft's AZ-204 exam
Question #: 45
Topic #: 19
[All AZ-204 Questions]

You are developing an Azure function that connects to an Azure SQL Database instance. The function is triggered by an Azure Storage queue.

You receive reports of numerous System.InvalidOperationExceptions with the following message: ''Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.''

You need to prevent the exception.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

With the Premium plan the max outbound connections per instance is unbounded compared to the 600 active (1200 total) in a Consumption plan.

Note: The number of available connections is limited partly because a function app runs in a sandbox environment. One of the restrictions that the sandbox imposes on your code is a limit on the number of outbound connections, which is currently 600 active (1,200 total) connections per instance. When you reach this limit, the functions runtime writes the following message to the logs: Host thresholds exceeded: Connections.


https://docs.microsoft.com/en-us/azure/azure-functions/manage-connections

https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale#service-limits

Contribute your Thoughts:

0/2000 characters
Stevie
4 months ago
Wait, are we sure the max pool size is actually the problem?
upvoted 0 times
...
Madalyn
4 months ago
I agree, Premium plan could really help with scaling.
upvoted 0 times
...
Thora
4 months ago
Not sure if changing the trigger to Event Hub will help here.
upvoted 0 times
...
Louis
5 months ago
I think going with option C is a solid choice!
upvoted 0 times
...
Loreen
5 months ago
Sounds like a classic connection pool issue.
upvoted 0 times
...
Kathrine
5 months ago
I’m leaning towards changing the type option to queueScaling in function.json, but I need to double-check if that really affects connection pooling.
upvoted 0 times
...
Marsha
5 months ago
The batchSize option in host.json sounds familiar; I feel like we discussed how it could impact performance in a similar practice question.
upvoted 0 times
...
Bok
5 months ago
I think converting to the Premium plan could help with scaling, but I’m not entirely convinced it’s the best solution for this specific timeout issue.
upvoted 0 times
...
Orville
5 months ago
I remember reading about connection pooling issues in Azure SQL, but I'm not sure which option directly addresses the timeout problem.
upvoted 0 times
...
Tamar
5 months ago
Wait, I'm not sure about that. Doesn't dpkg -r pkgname remove the package but leave the configuration files? I'll have to double-check the man page on that.
upvoted 0 times
...
Leonor
5 months ago
I think the answer might be Cisco Identity Services Engine, but I'm not 100% sure. Security is such a broad topic.
upvoted 0 times
...
Shelton
5 months ago
Ugh, inventory calculations are not my strong suit. I'll need to really focus and take this slow. Gotta make sure I don't miss any key steps in the formula.
upvoted 0 times
...
Bernardine
5 months ago
This is a tricky question, but I think I have a good strategy. The key is to identify the points of failure and address them using appropriate design patterns. The Asynchronous Queuing pattern seems like a good fit to handle the availability issues between the services.
upvoted 0 times
...

Save Cancel