Microsoft AZ-600 Practice Test - Questions Answers, Page 18

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

Configure the integrated system to resolve external names by using a DNS Server that has an IP address of 10.100.100.100. Resolving external DNS names from Azure Stack Hub

To resolve DNS names for endpoints outside Azure Stack Hub (for example: www.bing.com), you need to provide DNS servers that Azure Stack Hub can use to forward DNS requests for which Azure Stack Hub isn't authoritative. For deployment, DNS servers that Azure Stack Hub forwards requests to are required in the Deployment Worksheet (in the DNS Forwarder field). Provide at least two servers in this field for fault tolerance. Without these values, Azure Stack Hub deployment fails. You can edit the DNS Forwarder values with the Set-AzSDnsForwarder cmdlet after deployment. Configure conditional DNS forwarding

Important

This only applies to an AD FS deployment.

To enable name resolution with your existing DNS infrastructure, configure conditional forwarding.

To add a conditional forwarder, you must use the privileged endpoint.

For this procedure, use a computer in your datacenter network that can communicate with the privileged endpoint in Azure Stack Hub. 1. Open an elevated Windows PowerShell session (run as administrator), and connect to the IP address of the privileged endpoint. Use the credentials for CloudAdmin authentication. $cred=Get-Credential

Enter-PSSession -ComputerName <IP Address of ERCS> -ConfigurationName PrivilegedEndpoint - Credential $cred 2. After you connect to the privileged endpoint, run the following PowerShell command. Substitute the sample values provided with your domain name and IP addresses of the DNS servers you want to use.

Register-CustomDnsServer -CustomDomainName "contoso.com" -Custom

Reference:

https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-integrate-dns

Use the Azure Stack Hub Readiness Checker tool to validate that generated public key infrastructure (PKI) certificates which are suitable for pre-deployment. Validate certificates by leaving enough time to test and reissue certificates if necessary.

The Readiness Checker tool performs the following certificate validations:

* Parse PFX

Checks for valid PFX file, correct password, and whether the public information is protected by the password. * Expiry Date

Checks for minimum validity of seven days.

* Signature algorithm

Checks that the signature algorithm isn't SHA1.

* Private Key

Checks that the private key is present and is exported with the local machine attribute.

* Etc.

Note: Perform core services certificate validation

Use these steps to validate the Azure Stack Hub PKI certificates for deployment and secret rotation:

1. Install AzsReadinessChecker from a PowerShell prompt (5.1 or above) by running the following cmdlet:

Install-Module Microsoft.AzureStack.ReadinessChecker -Force -AllowPrerelease 2. Create the certificate directory structure. 3. Etc.

Reference:

https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-validate-pki-certs

Topic 4, Misc. Questions

Box 1: Subject Alternative Name

Implement the App Service resource provider and the Event Hubs resource provider on the integrated system/ Only the Subject Alternative Name is used.

Box 2: DNS Name = =*.eventhub.east.azurestack.treyresearch.net

Event Hubs prerequisites

Procure public key infrastructure (PKI) SSL certificates for Event Hubs. The Subject Alternative Name (SAN) must adhere to the following naming pattern: CN=*.eventhub.<region>.<fqdn>. Subject Name may be specified, but it's not used by Event Hubs when handling certificates. Only the Subject Alternative Name is used. See PKI certificate requirements for the full list of detailed requirements.

Reference:

https://learn.microsoft.com/en-us/azure-stack/operator/event-hubs-rp-prerequisites

Box 1: 4

The infrastructure of the integrated system must be backed up as frequently as possible.

Enable backup for Azure Stack Hub from the administrator portal

The frequency in hours determines how often backups are created. The default value is 12. Scheduler supports a maximum of 12 and a minimum of 4. Box 2: Azure key vault

The integrated system backups must be retained for 28 days.

Online retention policy. This specifies the time period during which daily, weekly, monthly, and yearly backups are retained in the Azure Site Recovery vault that's associated with the local MABS instance.

Reference:

https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-backup-enable-backup-console

https://learn.microsoft.com/en-us/azure/architecture/hybrid/azure-stack-backup

Step 1: Create a config.file and save the file as Sloud-init.txt file.

Publish a custom cloud-init built image of a Linux virtual machine to Azure Stack Hub Marketplace on the integrated system. Add Linux images to the Azure Stack Hub Marketplace

1: Create a cloud-init.txt file with your cloud-config

Step 2: Upload the file to Azure Stack Hub storage account.

2: Reference cloud-init.txt during the Linux VM deployment

Upload the file to an Azure storage account, Azure Stack Hub storage account, or GitHub repository reachable by your Azure Stack Hub Linux VM. Step 3: Provision on Azure Stack Hub virtual machine by using Az PowerShell moduel.

You can create an Ubuntu Server 16.04 LTS virtual machine (VM) by using Azure Stack Hub PowerShell. Make sure to reference the cloud-init.txt as a part of the -CustomData flag:

$VirtualMachine =Set-AzVMOperatingSystem -VM $VirtualMachine `

-Linux `

-ComputerName "MainComputer" `

-Credential $cred -CustomData "#include https://cloudinitstrg.blob.core.windows.net/strg/cloudinit.txt"

Reference:

https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-linux?

Box 1: The Default Provider Subscription

A default Microsoft SQL Server instance will host the database of the App Service resource provider. In Azure Stack Hub Subscriptions, select the Default Provider Subscription. Azure App Service on Azure Stack Hub must be deployed in the Default Provider Subscription. Box 2:

Enter the SQL Server details for the server instance used to host the App Service resource provider database and then select Next. The installer validates the SQL connection properties.

Reference:

https://learn.microsoft.com/en-us/azure-stack/operator/azure-stack-app-service-deploy