You are deploying an Azure Function App using the Azure Functions V4 runtime and a .NET isolated worker model on an Elastic Premium hosting plan. The function app is configured with a Service Bus queue trigger.
The Service Bus namespace is secured within a virtual network using a private endpoint, and public network access is disabled. The Function App has regional virtual network integration enabled on the same virtual network.
You need to configure the connection using the Function App's system-assigned managed identity instead of connection strings. Additionally, the Function App must scale out dynamically when the Service Bus queue length increases.
Which two configuration settings should you apply to the Function App?
- Create an application setting named ServiceBusConnection__fullyQualifiedNamespace and set its value to the fully qualified domain name of the Service Bus namespace.Cevap
- Create an application setting named WEBSITE_RUNTIME_SCALE_MONITORING and set its value to 1.Cevap
- CCreate an application setting named ServiceBusConnection__credential and set its value to SystemAssigned.
- DChange the Function App hosting plan to a Consumption plan to reduce idle costs while maintaining the private endpoint connection.
Cevap
Create an application setting named ServiceBusConnection__fullyQualifiedNamespace set to the fully qualified domain name of the Service Bus namespace, and create an application setting named WEBSITE_RUNTIME_SCALE_MONITORING set to 1.
The correct configurations involve using ServiceBusConnection__fullyQualifiedNamespace to configure an identity-based trigger with the system-assigned managed identity, and setting WEBSITE_RUNTIME_SCALE_MONITORING to 1 to allow the Elastic Premium scale controller to access the VNet-isolated Service Bus namespace.
Adım Adım Çözüm
Anahtar Kavram
Configuring identity-based connections and runtime scale monitoring for VNet-integrated Azure Functions V4 triggers.
Tahmini Süre:3m 0s