Exam AZ-103: Quiz

Install-Module Az -AllowClobber

Reference:

https://docs.microsoft.com/en-us/powershell/azure/new-azureps-module-az?view=azps-2.5.0

Connect-AzAccount, or alias Login-AzAccount

Reference:

https://docs.microsoft.com/en-us/powershell/module/az.accounts/connect-azaccount?view=azps-2.5.0

Get-AzSubscription

Reference:

https://docs.microsoft.com/en-us/powershell/module/Az.Accounts/Get-AzSubscription?view=azps-2.5.0

New-AzResourceGroup -Name MyRG1 -Location EastUS

Reference:

https://docs.microsoft.com/en-us/powershell/module/az.resources/new-azresourcegroup?view=azps-2.5.0

Remove-AzResourceGroup -Name MyRG1

Reference:

https://docs.microsoft.com/en-us/powershell/module/az.resources/remove-azresourcegroup?view=azps-2.5.0

False. Azure CLI works through the browser, and does not have interactive access.

Reference:

https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-cli

az vm restart -g MyRG1 -n MyVM1.

Notice that the command structure is different than cmdlets.

Reference:

https://docs.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az-vm-restart

By downloading the MSI from Microsoft (https://aka.ms/installazurecliwindows), or by using the following cmdlet:

Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi; Start-Process msiexec.exe -Wait -ArgumentList ‘/I AzureCLI.msi /quiet’

Reference:

https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-windows?view=azure-cli-latest

Open a command prompt or PowerShell. Type: az login.

Reference:

https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-windows?view=azure-cli-latest

An action group is a collection of notification preferences defined by the owner of an Azure subscription.

Reference:

https://docs.microsoft.com/en-us/azure/azure-monitor/platform/action-groups

media

2,000

Reference:

https://docs.microsoft.com/en-us/azure/azure-monitor/platform/action-groups

#1 Name: Enter a unique identifier for this action.

#2 Action Type: Select Email/SMS/Push/Voice, Logic App, Webhook, ITSM, or Automation Runbook.

#3 Details: Based on the action type, enter a phone number, email address, webhook URI, Azure app, ITSM connection, or Automation runbook. For ITSM Action, additionally specify Work Item and other fields your ITSM tool requires.

Reference:

https://docs.microsoft.com/en-us/azure/azure-monitor/platform/action-groups

Owner – Full access to all resources. Delegate access to others.

Contributor – Create and manage all types of Azure resources. Cannot grant access to others.

Reader – View Azure resources.

User Access Administrator – Manage user access to Azure resources.

Reference:

https://docs.microsoft.com/en-us/azure/role-based-access-control/rbac-and-directory-admin-roles

E. Azure Application Insights

Application Insights, a feature of Azure Monitor, is an extensible Application Performance Management (APM) service for web developers on multiple platforms.

Reference:

https://docs.microsoft.com/en-us/azure/azure-monitor/learn/tutorial-performance

5 Steps

#1 – Sign in to the Azure portal > Recovery Services.

#2 – On the Azure portal menu or from the Home page, select Create a resource. Then select Management Tools > Backup and Site Recovery.

#3 – In Name, specify a friendly name to identify the vault. If you have more than one subscription, select the appropriate one.

#4 – Create a resource group or select an existing one. Specify an Azure region. To check supported regions, see geographic availability in Azure Site Recovery Pricing Details.

#5 – Click Create.

Reference:

https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication

D. Advisor

Reference:

https://docs.microsoft.com/en-us/azure/advisor/advisor-cost-recommendations

https://docs.microsoft.com/en-us/azure/advisor/advisor-overview

B. Owner, Contributor, or Reader of a subscription

Reference:

https://docs.microsoft.com/en-us/azure/advisor/advisor-overview

An availability set

Reference:

https://docs.microsoft.com/en-us/azure/advisor/advisor-high-availability-recommendations

Azure Performance Diagnostics VM Extension

Azure Performance Diagnostics VM Extension helps collect performance diagnostic data from Windows VMs. The extension performs analysis, and provides a report of findings and recommendations to identify and resolve performance issues on the virtual machine.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/performance-diagnostics-vm-extension

8 Steps

#1 – Select Virtual machines as the resource.

#2 – From the list, choose a VM to back up.

#3 – In the Operations section, choose Backup. The Enable backup window opens.

#4 – Select Create new and provide a name for the new vault, such as myRecoveryServicesVault.

#5 – If not already selected, choose Use existing, then select the resource group of your VM from the drop-down menu.

#6 – To accept the default backup policy values, select Enable Backup.

#7 – On the Backup window for your VM, select Backup now.

#8 – To accept the backup retention policy of 30 days, leave the default Retain Backup Till date. To start the job, select Backup.

Reference:

https://docs.microsoft.com/en-us/azure/backup/quick-backup-vm-portal

7 Steps

#1 – Under Services, select Virtual machines.

#2 – In the Virtual machines page, select Add.

#3 – In the Basics tab, under Project details, make sure the correct subscription is selected and then choose to Create new resource group. Type myResourceGroup for the name.

#4 – Under Instance details, type myVM for the Virtual machine name and choose East US for your Region, and then choose Windows Server 2019 Datacenter for the Image. Leave the other defaults.

#5 – Under Administrator account, provide a username, such as azureuser and a password. The password must be at least 12 characters long and meet the defined complexity requirements.

#6 – Under Inbound port rules, choose Allow selected ports and then select RDP (3389) and HTTP (80) from the drop-down.

#7 – Leave the remaining defaults and then select the Review + create button at the bottom of the page.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/quick-create-portal

Individually

Floating IP concept is meant for port reuse scenarios. Floating IP is a portion of what is known as Direct Server Return (DSR). DSR consists of two parts: a flow topology and an IP address mapping scheme. At a platform level, Azure Load Balancer always operates in a DSR flow topology regardless of whether Floating IP is enabled or not. This means that the outbound part of a flow is always correctly rewritten to flow directly back to the origin.

Reference:

https://docs.microsoft.com/en-us/azure/load-balancer/load-balancer-multivip-overview

True

Reference:

https://docs.microsoft.com/en-us/azure/app-service/overview-authentication-authorization

False

Many web frameworks are bundled with security features, and you can use them if you like.

Reference:

https://docs.microsoft.com/en-us/azure/app-service/overview-authentication-authorization

4 Steps

#1 – Authenticates users with the specified provider
#2 – Validates, stores, and refreshes tokens
#3 – Manages the authenticated session
#4 – Injects identity information into request headers

Reference:

https://docs.microsoft.com/en-us/azure/app-service/overview-authentication-authorization

WaAppAgent.exe is the process for the RdAgent service, which is part of the VM Agent for Windows Azure Virtual Machines.

Reference:

https://azure.microsoft.com/en-us/blog/azure-vm-backup-pre-checks/

https://social.msdn.microsoft.com/Forums/azure/en-US/f4e87cc9-9f92-4adf-b1eb-4ddf7317a0e8/waappagentexe-100-cpu?forum=WAVirtualMachinesforWindows

443

Reference:

https://docs.microsoft.com/en-us/azure/migrate/migrate-appliance

Once again, the port is 443.

Reference:

https://docs.microsoft.com/en-us/azure/migrate/migrate-appliance

Azure Migrate provides a centralized hub to manage and track discovery, assessment, and migration of on-premises machines and workloads to Azure. Azure Site Recovery is a disaster recovery solution. Azure Migrate: Server Migration tool uses some backend Site Recovery functionality for lift-and-shift migration of some on-premises machines.

Reference:

https://docs.microsoft.com/en-us/azure/migrate/resources-faq

The connection can be over the internet, or use Azure ExpressRoute with public/Microsoft peering.

Reference:

https://docs.microsoft.com/en-us/azure/migrate/resources-faq

Performance data and metadata for VMware VMs.
Performance data and metadata for Hyper-V VMs.

Reference:

https://docs.microsoft.com/en-us/azure/migrate/resources-faq

A shared access signature (SAS) provides secure delegated access to resources in your storage account without compromising the security of your data. With a SAS, you have granular control over how a client can access your data. You can control what resources the client may access, what permissions they have on those resources, and how long the SAS is valid, among other parameters.

Reference:

https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview

Standard, Premium, Isolated

Reference:

https://azure.microsoft.com/en-us/pricing/details/app-service/windows/

Ad hoc SAS: When you create an ad hoc SAS, the start time, expiry time, and permissions for the SAS are all specified in the SAS URI (or implied, if start time is omitted). Any type of SAS can be an ad hoc SAS.

Service SAS with stored access policy: A stored access policy is defined on a resource container, which can be a blob container, table, queue, or file share. The stored access policy can be used to manage constraints for one or more service shared access signatures. When you associate a service SAS with a stored access policy, the SAS inherits the constraints—the start time, expiry time, and permissions—defined for the stored access policy.NOTEA user delegation SAS or an account SAS must be an ad hoc SAS. Stored access policies are not supported for the user delegation SAS or the account SAS.

Reference:

https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview

Premium & Isolated

Reference:

https://azure.microsoft.com/en-us/pricing/details/app-service/windows/

6 Steps

#1 – From the Azure portal menu, select Create a resource.
#2 – In the New page, select Compute > Function App.
#3 – Specify Function settings:

#4 – Specify Host settings:

Select the Next : Monitoring > button.

#5 – Specify Monitoring settings:

Select Review + Create to review the app configuration selections.

#6 – Select Create to provision and deploy the function app.

Reference:

https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-azure-function

4 Steps

#1 – In the portal, click More services > type virtual machines in the filter box, and then click Virtual machines.

#2 – In the Virtual machines pane, click the VM you want to add IP addresses to. Click Network interfaces in the virtual machine pane that appears, and then select the network interface you want to add the IP addresses to. In the example shown in the following picture, the NIC named myNIC from the VM named myVM is selected.

#3 – In the pane that appears for the NIC you selected, click IP configurations.

#4 – Complete the steps in one of the sections that follow, based on the type of IP address you want to add.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-multiple-ip-addresses-portal

2 Steps

#1 – In the portal, click Create a resource > Networking > Public IP address.

#2 – In the Create public IP address pane that appears, enter a Name, select an IP address assignment type, a Subscription, a Resource group, and a Location, then click Create.

Reference:

Review the following link…in detail. Know how to assign the public IP address to different resources:

https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-multiple-ip-addresses-portal

6 Steps

#1 – In the search box at the top of the Azure portal, enter virtual networks in the search box. When Virtual networks appear in the search results, select it. Do not select Virtual networks (classic) if it appears in the list, as you cannot create a peering from a virtual network deployed through the classic deployment model.

#2 – Select the virtual network in the list that you want to create a peering for (this means, virtual networks must exist—if they do not, create them).

#3 – Under SETTINGS, select Peerings.

#4 – Select + Add.

#5 – Enter or select values for the following settings: Name, Virtual Network Deployment model, I know my resource ID, Subscription, Virtual Network, Allow Virtual Network Access, Allow Forwarded Traffic, Allow Gateway Transit, and Use Remote Gateways.

#6 – Select OK to add the peering to the virtual network you selected.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-manage-peering

…

Reference:

link

…

Reference:

link

…

Reference:

link

…

Reference:

link

…

Reference:

link

…

Reference:

link

…

Reference:

link

…

Reference:

link