Reference:
https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-node-actions?view=azs-
2008&tabs=az1#repair

Reference:
https://docs.microsoft.com/en-us/azure/architecture/hybrid/azure-stack-vm-dr

Explanation

Reference:
https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-manage-portals?view=azs-2008
Topic 3, Trey Research
Case study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Overview
General overview
Trey Research is a pharmaceutical company that has an office in Boston.
Existing environment
Identity Environment
The on-premises network contains an Active Directory forest named treyresearch.net. The forest contains a user named User1.
The forest syncs to an Azure AD tenant named treyresearch.net by using Azure AD Connect.
Trey Research has an internal certification authority (CA).
Compute Environment
The datacenter in the Boston office contains a computer named CLIENT1 that runs Windows 10. CLIENT1 is an administrative workstation that connects directly to the Azure Stack Hub integrated system.
Planned changes and requirements
Planned changes
Trey Research identifies the following planned changes:
* Change the Azure Stack Hub integrated system registration to use an Azure subscription named Subscription3 that has a GUID of 12345678-1234-1234-1234-222222222222.
* Configure the integrated system to resolve external names by using a DNS Server that has an IP address of 10.100.100.100.
* Implement the App Service resource provider and the Event Hubs resource provider on the integrated system/
* Publish a custom cloud-init built image of a Linux virtual machine to Azure Stack Hub Marketplace on the integrated system.
* Create a new cloudadmin user named User2.
* Assign the delegated provider role to User1.
Azure Stack Hub Requirements
Trey Research identifies the following Azure Stack Hub requirements:
* Azure Stack Hub integrated system logs must be forwarded to an external security information and event management (SIEM) system named SIEM1. SIEM1 requires TCP with mutual authentication and TLS 1.2 encryption.
* A default Microsoft SQL Server instance will host the database of the App Service resource provider.
* The infrastructure of the integrated system must be backed up as frequently as possible.
* The integrated system backups must be retained for 28 days.
Business Requirements
Minimize software and licensing costs.

Explanation
Step 1: Connect to the Azure Resource Manager (ARM) endpoint
Compare to the steps in the note below.
Use https://adminmanagement.<region>.<domain>
Azure Resource Manager (administrator)
Adminmanagement.<region>.<fqdn>
Azure Resource Manager (user)
Management.<region>.<fqdn>
Step 2: Run the -Unregister-AzSGuestDirectoryTenant cmdlet.
Unregister a guest directory
If you no longer want to allow sign-ins to Azure Stack Hub services from a guest directory tenant, you can unregister the directory. Again, both the home Azure Stack Hub directory and guest directory need to be configured.
Configure guest directory
Step 3: Instruct the global administrator of fabrikam.com to run the -unregister- AzsWithMyDirectoryTenant cmdlet.
Configure guest directory
Note: Enabling AAD Multi-Tenancy in Azure Stack
Allowing users and service principals from multiple AAD directory tenants to sign in and create resources on Azure Stack. There are two personas involved in implementing this scenario.
1. The Administrator of the Azure Stack installation
2. The Directory Tenant Administrator of the directory that needs to be onboarded to Azure Stack Step 1: Onboard the Guest Directory Tenant to Azure Stack This step will let Azure Resource manager know that it can accept users and service principals from the guest directory tenant.
$adminARMEndpoint = "https://adminmanagement.<region>.<domain>"
$azureStackDirectoryTenant = "<homeDirectoryTenant>.onmicrosoft.com" # this is the primary tenant Azure Stack is registered to
$guestDirectoryTenantToBeOnboarded = "<guestDirectoryTenant>.onmicrosoft.com" # this is the new tenant that needs to be onboarded to Azure Stack
$location = "local"
Register-AzsGuestDirectoryTenant -AdminResourceManagerEndpoint $adminARMEndpoint `
-DirectoryTenantName $azureStackDirectoryTenant `
-GuestDirectoryTenantName $guestDirectoryTenantToBeOnboarded `
-ResourceGroupName "system.local" `
-Location $location
With this step, the work of the Azure Stack administrator is done.
Guest Directory Tenant Administrator
Step 2: Registering Azure Stack applications with the Guest Directory
Execute the following cmdlet as the administrator of the directory that needs to be onboarded, replacing
$guestDirectoryTenantName with your directory domain name
$tenantARMEndpoint = "https://management.<region>.<domain>"
$guestDirectoryTenantName = "<guestDirectoryTenant>.onmicrosoft.com" # this is the new tenant that needs to be onboarded to Azure Stack Register-AzsWithMyDirectoryTenant -TenantResourceManagerEndpoint $tenantARMEndpoint `
-DirectoryTenantName $guestDirectoryTenantName
Reference:
https://learn.microsoft.com/en-us/azure-stack/operator/enable-multitenancy
https://github.com/Azure/AzureStack-Tools/blob/master/Identity/README.md
https://learn.microsoft.com/en-us/azure-stack/operator/enable-multitenancy