Explanation
Correct: Solution: From a privileged endpoint (PEP) session, you run
Test-AzureStack -Group "UpdateReadiness".
Use a privileged endpoint (PEP) session and Test-AzureStack with UpdateReadiness.
Note:
Running the validation tool and accessing results
You can use the PEP to run the validation tool. The tool can take a while to run. The length of the time depends on the number of virtual machines in your system. Each test returns a PASS/FAIL status in the PowerShell window.
Here's an outline of the end-to-end validation testing process:
1. Establish the trust. On an integrated system, run the following command from an elevated Windows PowerShell session to add the PEP as a trusted host on the hardened VM running on the hardware lifecycle host or the Privileged Access Workstation.
2. Access the PEP.
3. Once you're in the PEP, run:
Test-AzureStack
Groups
To improve the operator experience, a Group parameter has been enabled to run multiple test categories at the same time. Currently, there are three groups defined: Default, UpdateReadiness, and SecretRotationReadiness.
UpdateReadiness: A check to see if the Azure Stack Hub instance can be updated. When the UpdateReadiness group is run, warnings are displayed as errors in the console output, and they should be considered as blockers for the update.
Reference:
https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-diagnostic-test?view=azs-2008