Question 210
In the Northgate Collaboration pilot environment, a controlled verification is required for: An Azure CLI script provisions session hosts but stores a reusable host pool registration token in public build logs. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
The job creates registered hosts while the build transcript contains no reusable token or administrative credential. This is an independently observable result of the targeted change: Generate the host registration token with controlled scope and lifetime and pass it through a protected automation secret mechanism. It closes the specific Northgate Collaboration failure: An Azure CLI script provisions session hosts but stores a reusable host pool registration token in public build logs.
Incorrect Answers
A repeated deployment finishes without creating duplicates and preserves healthy existing hosts and user assignments. This is evidence for a DIFFERENT remediation: Use idempotent resource discovery and declarative deployment semantics so reruns reconcile with existing approved resources. That remediation addresses: A PowerShell host pool deployment is rerun after a partial failure and duplicates resources because it relies on names assembled from a counter. It does not establish resolution of the Northgate Collaboration problem: An Azure CLI script provisions session hosts but stores a reusable host pool registration token in public build logs. The required outcome here is: The job creates registered hosts while the build transcript contains no reusable token or administrative credential.
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 Northgate Collaboration problem: An Azure CLI script provisions session hosts but stores a reusable host pool registration token in public build logs. The required outcome here is: The job creates registered hosts while the build transcript contains no reusable token or administrative credential.
New users land on healthy hosts while existing sessions are drained and the patched VM returns to Available state. This is evidence for a DIFFERENT remediation: Enable drain mode on the affected session host and coordinate session logoff or migration before applying updates. That remediation addresses: A session host is undergoing OS patching but continues accepting new AVD sessions and disrupts users at reboot. It does not establish resolution of the Northgate Collaboration problem: An Azure CLI script provisions session hosts but stores a reusable host pool registration token in public build logs. The required outcome here is: The job creates registered hosts while the build transcript contains no reusable token or administrative credential.