Examkin

Question

Difficulty: Very hardCreate and Configure Azure Functions

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?

  1. Create an application setting named ServiceBusConnection__fullyQualifiedNamespace and set its value to the fully qualified domain name of the Service Bus namespace.Answer
  2. Create an application setting named WEBSITE_RUNTIME_SCALE_MONITORING and set its value to 1.Answer
  3. C
    Create an application setting named ServiceBusConnection__credential and set its value to SystemAssigned.
  4. D
    Change the Function App hosting plan to a Consumption plan to reduce idle costs while maintaining the private endpoint connection.

Answer

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.

Step-by-Step Solution

1
Configure the identity-based connection prefix for the Service Bus trigger.
Create the ServiceBusConnection__fullyQualifiedNamespace app setting.
Azure Functions V4 uses the __fullyQualifiedNamespace suffix on the connection prefix to initiate an identity-based connection using the system-assigned managed identity by default.
2
Enable the scale controller to monitor queue metrics inside the virtual network.
Set the WEBSITE_RUNTIME_SCALE_MONITORING app setting to 1.
Since the Service Bus namespace restricts public access and uses a private endpoint, the scale controller (which runs outside the customer VNet) requires runtime scale monitoring to query queue length metrics through the Function App's VNet integration.

Key Concept

Configuring identity-based connections and runtime scale monitoring for VNet-integrated Azure Functions V4 triggers.
Estimated Time:3m 0s
Rate this question

Topics

Create and Configure Azure Functions

More questions from this topic