Explanation

Reference:
https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-delegated-provider?view=azs-2008

Explanation
Assign the delegated provider role to User1.
Delegation steps
There are two steps to setting up delegation:
1. Create a delegated provider subscription: Subscribe a user to an offer containing only the subscription service. Users who subscribe to this offer can then extend the delegated offers to other users by signing them up for those offers.
2. Delegate an offer to the delegated provider: This offer enables the delegated provider to create subscriptions or to extend the offer to their users. The delegated provider can now take the offer and extend it to other users.
Note:
Move subscriptions between delegated providers
If needed, a subscription can be moved between new or existing delegated provider subscriptions that belong to the same directory tenant. You can move them using the PowerShell cmdlet Move-AzsSubscription.
Moving subscriptions is useful when:
* You onboard a new team member that will take on the delegated provider role and you want to assign to this team member user subscriptions that were previously created in the default provider subscription.
* You have multiple delegated providers subscriptions in the same directory tenant (Azure AD) and need to move user subscriptions between them. This scenario could occur when a team member moves between teams and their subscription must be allocated to the new team.
Reference:
https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-delegated-provider

Explanation
Note: Upgrade GPUs or add to an existing node
The following section provides a high-level overview of the process to add a GPU.
* The entire scale unit must be shut down, as a rolling GPU upgrade isn't supported. Stop Azure Stack Hub using the steps documented in the Start and stop Azure Stack Hub article.
* Add or upgrade the memory on each physical computer using your hardware manufacturer's documentation.
* Start Azure Stack Hub using the steps in Start and stop Azure Stack Hub.
Note: Stop Azure Stack Hub
Stop or shut down Azure Stack Hub with the following steps:
1. Prepare all workloads running on your Azure Stack Hub environment's tenant resources for the upcoming shutdown.
2. Open a privileged endpoint session (PEP) from a machine with network access to the Azure Stack Hub ERCS VMs. For instructions, see Using the privileged endpoint in Azure Stack Hub.
3. From the PEP, run:
Stop-AzureStack
Wait for all physical Azure Stack Hub nodes to power off.
Note
You can verify the power status of a physical node by following the instructions from the original equipment manufacturer (OEM) who supplied your Azure Stack Hub hardware.
4. (Optional) If the stop operation times out, you can monitor its progress using the following PowerShell cmdlet:
Get-ActionStatus Stop-AzureStack
Reference: https://learn.microsoft.com/en-us/azure-stack/operator/manage-gpu-capacity
https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-start-and-stop

Explanation

Explanation
A DNS entry is created for each endpoint in the external DNS zone that's specified at deployment time. For example, the user portal is assigned the DNS host entry of portal.<region>.<fqdn>.
* Azure Resource Manager (user)
Management.<region>.<fqdn>
Incorrect:
Not C: Portal (user)
Portal.<region>.<fqdn>
Not A, Not D: Azure Resource Manager (administrator)
Adminmanagement.<region>.<fqdn>
Note: Portal (administrator)
Adminportal.<region>.<fqdn>
Reference:
https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-integrate-endpoints