You need to ensure that an Azure AI services resource is accessible only from a specific virtual network. Which configuration should you update in the Azure portal?
Private endpoints assign a private IP from your virtual network to the Azure AI services resource, removing public internet exposure. Configuring them on the Networking blade restricts inbound access to that specific VNet, satisfying the isolation requirement.
Why this answer
To restrict an Azure AI services (Cognitive Services) resource so it is reachable only from a specific virtual network, you configure a Private Endpoint on the resource's Networking blade. A Private Endpoint creates a private IP address from your VNet, mapping the service into your network via Azure Private Link, so public internet access can be disabled entirely. This is the standard portal-based approach for VNet-level isolation of Azure AI resources.
Exam trap
AI-103 often tests the misconception that tags, keys, or managed identities provide network isolation — only Private Endpoints (or service firewalls/VNet rules) actually restrict network reachability.
How to eliminate wrong answers
Option B is wrong because Resource tags are metadata labels used for organization, cost tracking, and policy scoping — they cannot attach a network security group or enforce any network restriction. Option C is wrong because disabling local (key-based) authentication only changes the authentication model to Entra ID; it does not restrict which network can reach the resource. Option D is wrong because assigning a User Assigned Managed Identity grants the resource an identity for outbound access to other services — it has no bearing on inbound network isolation.