AZ-600 Online Practice Questions and Answers

Correct Answer: D

For multinode systems, the user portal URL is formatted as https://portal... For an ASDK deployment, the URL is https://portal.local.azurestack.external.

In our case we must also direct any foreign principals (users in the Adatum directory without the suffix of adatum.onmicrosoft.com) to sign in using https:///adatum.onmicrosoft.com. If they don't specify the /

adatum.onmicrosoft.com directory tenant in the URL, they're sent to their default directory and receive an error that says their administrator hasn't consented.

Reference: https://learn.microsoft.com/en-us/azure-stack/operator/enable-multitenancy

Correct Answer: B

Reference:

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

Correct Answer: B

Instead: Solution: From a privileged endpoint (PEP) session, you run the Install-AzsUpdate cmdlet.

You can use the Azure Stack Hub administrative endpoints to monitor and manage your updates. They're accessible with PowerShell. For instructions on getting set up with PowerShell on Azure Stack Hub.

You can use the following PowerShell cmdlet to manage your updates:

* Install-AzsUpdate

Apply a specific update at an update location.

Reference:

https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-update- monitor?view=azs-2008

Correct Answer: AC

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

Correct Answer:

Reference: https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-backup-enable-backup-console?view=azs-2008

Correct Answer:

Reference: https://docs.microsoft.com/en-us/azure-stack/operator/azure-stack-windows-server-faq?view=azs-2102andtabs=az1%2Caz2

Correct Answer:

Correct Answer:

Step 1: Create a JSON file that contains the role definition. Rather than using an account that has Owner permissions in the Azure subscription, you can create a custom role to assign permissions to a less-privileged user account. This

account can then be used to register your Azure Stack Hub.

Create a custom role using PowerShell

Use the following JSON template to simplify creation of the custom role. The template creates a custom role that allows the required read and write access for Azure Stack Hub registration.

1.

Create a JSON file. For example, C:\CustomRoles\registrationrole.json.

2.

Add the following JSON to the file. Replace with your Azure subscription ID.

{

"Name": "Azure Stack Hub registration role",

"Id": null,

"IsCustom": true,

"Description": "Allows access to register Azure Stack Hub", "Actions": [

"Microsoft.Resources/subscriptions/resourceGroups/write", "Microsoft.Resources/subscriptions/resourceGroups/read", "Microsoft.AzureStack/registrations/*",

"Microsoft.AzureStack/register/action",

"Microsoft.Authorization/roleAssignments/read",

"Microsoft.Authorization/roleAssignments/write", "Microsoft.Authorization/roleAssignments/delete", "Microsoft.Authorization/permissions/read",

"Microsoft.Authorization/locks/read",

"Microsoft.Authorization/locks/write"

],

"NotActions": [

],

"AssignableScopes": [

"/subscriptions/"

]

}

3.

In PowerShell, connect to Azure to use Azure Resource Manager. When prompted, authenticate using an account with sufficient permissions such as Owner or User Access Administrator.

Connect-AzAccount

4.

To create the custom role, use New-AzRoleDefinition specifying the JSON template file.

New-AzRoleDefinition -InputFile "C:\CustomRoles\registrationrole.json"

Step 2: From Azure Cloud shell, run the New-AzRoleDefinition cmdlet.

Step 3: From the Azure portal, add a role assignment to sub1.

Assign a user to registration role

After the registration custom role is created, assign the role to the user account that will be used for registering Azure Stack Hub.

Sign in with the account with sufficient permission on the Azure subscription to delegate rights - such as Owner or User Access Administrator.

In Subscriptions, select Access control (IAM) > Add role assignment.

In Role, choose the custom role you created: Azure Stack Hub registration role.

Select the users you want to assign to the role. Select Save to assign the selected users to the role.

Correct Answer:

Step 1: Connect to the administrator portal Find a storage account The list of storage accounts in the region can be viewed in Azure Stack Hub by following these steps:

1.

Sign in to the administrator portal https://adminportal.local.azurestack.external.

2.

Select All services > Storage > Storage accounts.

By default, the first 10 accounts are displayed. You can choose to fetch more by clicking the Load more link at the bottom of the list.

Step 2: Open the Storage accounts blade.

Step 3: Select hr12943.

Once you've located the accounts you're interested in viewing, you can select the particular account to view certain details. A new pane opens with the account details. These details include the kind of account, creation time, location, and so

on.

Step 4: Select Recover.

Recover a deleted account

You may be in a situation where you need to recover a deleted account.

In Azure Stack Hub, there's a simple way to do that:

Browse to the storage accounts list. For more information, see Find a storage account at the top of this article.

Locate that particular account in the list. You may need to filter. Check the state of the account. It should say Deleted. Select the account, which opens the account details pane. (Step 3 above) On top of this pane, locate the Recover button

and select it. (Step 4) Select Yes to confirm.

Correct Answer:

Box 1: portal.

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...

* Portal (user) Portal..

Box 2: region1.

Note: Once your item has been successfully published to the marketplace, you can delete the content from the storage account.

All default gallery artifacts and your custom gallery artifacts are now accessible without authentication under the following URLs: https://galleryartifacts.adminhosting.[Region].[externalFQDN]/artifact/20161101/[TemplateN ame]/DeploymentTemplates/Template.json https://galleryartifacts.hosting.[Region].[externalFQDN]/artifact/20161101/[TemplateName]/ DeploymentTemplates/Template.json