Plan and manage an Azure AI solution →hardMultiple ChoiceObjective-mapped

AI-102 Plan and manage an Azure AI solution Practice Question

Exhibit

{
  "name": "my-ai-project",
  "location": "eastus",
  "identity": {
    "type": "SystemAssigned"
  },
  "properties": {
    "aiResourceType": "Project",
    "hubResourceId": "/subscriptions/.../resourceGroups/.../providers/Microsoft.MachineLearningServices/workspaces/my-ai-hub"
  }
}

Refer to the exhibit. You are deploying an AI project in Microsoft Foundry using an ARM template. The deployment fails with an error indicating that the hub resource is not in the same region. What is the most likely cause?

⚠ Common exam trap

It's easy for candidates to confuse resource group boundaries with regional boundaries, assuming that resources in different resource groups cannot be linked, when in fact Azure allows cross-resource-group parent-child relationships as long as the regions match.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The hub and project are in different Azure regions

In Azure AI Foundry, the hub and project resources must reside in the same Azure region because the project is a child resource of the hub and relies on the hub's regional endpoint for metadata storage and compute orchestration. The ARM template deployment fails with a region mismatch error when the location property of the project specifies a different region than the hub's location, as Azure enforces regional affinity for child resources to ensure low-latency communication and data residency compliance.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The resource group for the hub is different from the project's resource group
Why it's wrong here
Resource groups can differ; region must match.
✗
The identity type is SystemAssigned, but the hub requires UserAssigned
Why it's wrong here
SystemAssigned identity is valid and does not cause region mismatch.
✓
The hub and project are in different Azure regions
Why this is correct
Project must be in same region as its hub.
✗
The location property is misspelled in the template
Why it's wrong here
Location property is correctly specified as eastus.

Go deeper

AI-102 Plan and manage an Azure AI solution Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question