Question 200
In the Granite Network Team pilot environment, a controlled verification is required for: A portal wizard deploys session hosts into an unrelated virtual network with no required AD DS connectivity, causing domain join failures. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
The completed portal deployment shows healthy domain membership, host registration, and a successful pilot desktop connection. This is an independently observable result of the targeted change: Select the correct subnet and supported domain-join settings during the AVD host deployment and validate prerequisite DNS and credentials. It closes the specific Granite Network Team failure: A portal wizard deploys session hosts into an unrelated virtual network with no required AD DS connectivity, causing domain join failures.
Incorrect Answers
New logons move to other available hosts and per-host memory utilization stays under the validated threshold. This is evidence for a DIFFERENT remediation: Set the host pool maximum session limit and a load-balancing algorithm consistent with the tested user density. That remediation addresses: A pooled host pool permits too many sessions per VM and users experience memory paging at busy times even though spare hosts exist. It does not establish resolution of the Granite Network Team problem: A portal wizard deploys session hosts into an unrelated virtual network with no required AD DS connectivity, causing domain join failures. The required outcome here is: The completed portal deployment shows healthy domain membership, host registration, and a successful pilot desktop connection.
The new hosts appear Available in the correct host pool and an entitled user successfully launches a desktop. This is evidence for a DIFFERENT remediation: Create supported session-host VMs through the AVD portal flow and supply the intended host pool, image, identity, and registration settings. That remediation addresses: A new Azure Virtual Desktop host pool exists but no session host can serve logons because the portal deployment omitted host registration and image parameters. It does not establish resolution of the Granite Network Team problem: A portal wizard deploys session hosts into an unrelated virtual network with no required AD DS connectivity, causing domain join failures. The required outcome here is: The completed portal deployment shows healthy domain membership, host registration, and a successful pilot desktop connection.
The affected host returns to Available and passes a real user-connection validation without changing unrelated licenses. This is evidence for a DIFFERENT remediation: Review agent and bootloader health, service connectivity, and registration status, then repair the actual host registration problem. That remediation addresses: An administrator mistakes a session host's 'Unavailable' health state for a licensing issue and ignores an expired or invalid AVD agent registration. It does not establish resolution of the Granite Network Team problem: A portal wizard deploys session hosts into an unrelated virtual network with no required AD DS connectivity, causing domain join failures. The required outcome here is: The completed portal deployment shows healthy domain membership, host registration, and a successful pilot desktop connection.