Examkin

Soru

Zorluk: ZorProvision and Configure Azure API Management

A company is planning to deploy a new Azure API Management (APIM) instance in the Premium tier. The instance must be integrated with an existing Azure Virtual Network (VNet) in Internal mode to expose APIs only to internal clients. During the deployment phase, the administrator attempts to provision the APIM instance inside a subnet that already contains several running virtual machines. The deployment fails during the provisioning stage. You need to resolve the provisioning failure and successfully deploy the APIM instance. Which of the following actions should you take?

  1. A
    Enable the Microsoft.Web service endpoint on the existing subnet, and configure a system-assigned managed identity to authorize the virtual machines to share the subnet.
  2. B
    Change the API Management pricing tier to Consumption, as the Consumption tier supports deployment into shared subnets with existing virtual machines.
  3. Create a new subnet that is dedicated exclusively to the API Management instance with a prefix of at least /29/29, and ensure no other resources are deployed in it.Cevap
  4. D
    Apply a Network Security Group (NSG) to the existing subnet that includes an inbound security rule referencing the @Microsoft.KeyVault prefix to authorize the virtual machines.

Cevap

Create a new subnet that is dedicated exclusively to the API Management instance with a prefix of at least /29/29, and ensure no other resources are deployed in it.
The correct solution involves creating a dedicated subnet for the API Management instance. Azure API Management requires a dedicated subnet that contains no other resource types. The subnet must be at least /29/29 (with /28/28 recommended for upgrades and scaling) to accommodate the IP allocations needed by the instance.

Adım Adım Çözüm

1
Identify the cause of the provisioning failure.
The deployment fails because the selected subnet is currently shared with virtual machines, which violates API Management provisioning constraints.
API Management requires a dedicated subnet that contains no other resource types.
2
Determine the subnet size requirements.
The subnet must have a prefix of at least /29/29, though /28/28 is recommended to support future scaling and upgrades.
API Management allocates multiple IP addresses within its subnet for internal load balancing, gateway nodes, and upgrade processes.
3
Create and associate a new subnet.
A new, empty subnet is created with the required size, and the API Management provisioning process is initiated targeting this new subnet.
This satisfies the network isolation and size requirements, allowing the Premium tier APIM instance to provision successfully in Internal VNet mode.

Anahtar Kavram

API Management Virtual Network Integration Subnet Requirements
Bu soruyu puanla

Konular

Provision and Configure Azure API Management