Microsoft Azure Administrator Certification Transition (AZ-102日本語版) - AZ-102日本語무료 덤프문제 풀어보기

Explanation

Step 1: Download the OVA file for the collection appliance
Azure Migrate uses an on-premises VM called the collector appliance, to discover information about your on-premises machines. To create the appliance, you download a setup file in Open Virtualization Appliance (.ova) format, and import it as a VM on your on-premises vCenter Server.
Step 2: Create a migration group in the project
For the purposes of assessment, you gather the discovered VMs into groups. For example, you might group VMs that run the same application. For more precise grouping, you can use dependency visualization to view dependencies of a specific machine, or for all machines in a group and refine the group.
Step 3: Create an assessment in the project
After a group is defined, you create an assessment for it.
References:
https://docs.microsoft.com/en-us/azure/migrate/migrate-overview

Explanation

Box 1: VM1 only
To restore files or folders from the recovery point, go to the virtual machine and choose the desired recovery point.
Box 2: A new Azure virtual machine only
On the Restore configuration blade, you have two choices:
* Create virtual machine
* Restore disks
References:
https://docs.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm
https://docs.microsoft.com/en-us/azure/backup/backup-azure-arm-restore-vms

Explanation

Box 1: 10.20.0.0/16
Scenario: The New York office an IP address of 10.0.0.0/16. The Los Angeles office uses an IP address space of 10.10.0.0/16.
Box 2: Storage (general purpose v1)
Scenario: The New York office has a virtual machine named VM1 that has the vSphere console installed.

See solution below.
Explanation
First, create Recovery Services vault.
Step 1: On the left-hand menu, select All services and in the services list, type Recovery Services. As you type, the list of resources filters. When you see Recovery Services vaults in the list, select it to open the Recovery Services vaults menu.

Step 2: In the Recovery Services vaults menu, click Add to open the Recovery Services vault menu.

Step 3: In the Recovery Services vault menu, for example,
Type myRecoveryServicesVault in Name.
The current subscription ID appears in Subscription. If you have additional subscriptions, you could choose another subscription for the new vault.
For Resource group select Use existing and choose myResourceGroup. If myResourceGroup doesn't exist, select Create new and type myResourceGroup.
From the Location drop-down menu, choose West Europe.
Click Create to create your Recovery Services vault.
References: https://docs.microsoft.com/en-us/azure/backup/tutorial-backup-vm-at-scale

설명: (Fast2test 회원만 볼 수 있음)

Explanation

References: https://docs.microsoft.com/en-us/azure/governance/policy/concepts/definition-structure

Explanation

Box 1: 60
One alert per minute will trigger one email per minute.
Box 2: 12
No more than 1 SMS every 5 minutes can be send, which equals 12 per hour.
Note: Rate limiting is a suspension of notifications that occurs when too many are sent to a particular phone number, email address or device. Rate limiting ensures that alerts are manageable and actionable.
The rate limit thresholds are:
SMS: No more than 1 SMS every 5 minutes.
Voice: No more than 1 Voice call every 5 minutes.
Email: No more than 100 emails in an hour.
Other actions are not rate limited.
References:
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/monitoring-and-diagnostics/monitoring-overv

설명: (Fast2test 회원만 볼 수 있음)

설명: (Fast2test 회원만 볼 수 있음)

See solution below.
Explanation
Step 1: New-AzureRMResourceGroup -name MyResourceGroup
Before you create the DNS zone, create a resource group to contain the DNS zone.
Step 2: New-AzureRmDnsZone -Name corp7523690.com -ResourceGroupName MyResourceGroup A DNS zone is created by using the New-AzureRmDnsZone cmdlet. This creates a DNS zone called corp7523690.com in the resource group called MyResourceGroup.
References: https://docs.microsoft.com/en-us/azure/dns/dns-getstarted-powershell

Explanation

To access data sources on premises from your logic apps, you can create a data gateway resource in Azure so that your logic apps can use the on-premises connectors.
Box 1: From an on-premises computer, install an on-premises data gateway.
Before you can connect to on-premises data sources from Azure Logic Apps, download and install the on-premises data gateway on a local computer.
Box 2: From the Azure portal, create an on-premises data gateway
Create Azure resource for gateway
After you install the gateway on a local computer, you can then create an Azure resource for your gateway.
This step also associates your gateway resource with your Azure subscription.
* Sign in to the Azure portal. Make sure you use the same Azure work or school email address used to install the gateway.
* On the main Azure menu, select Create a resource > Integration > On-premises data gateway.
* On the Create connection gateway page, provide this information for your gateway resource.
* To add the gateway resource to your Azure dashboard, select Pin to dashboard. When you're done, choose Create.
Box 3: From the Logic Apps Designer in the Azure portal, add a connector After you create your gateway resource and associate your Azure subscription with this resource, you can now create a connection between your logic app and your on-premises data source by using the gateway.
* In the Azure portal, create or open your logic app in the Logic App Designer.
* Add a connector that supports on-premises connections, for example, SQL Server.
* Set up your connection.
References:
https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-gateway-connection

Explanation

Vm1 is in Pool1. Rule2 applies to Pool1, Listener 2, and site2.contoso.com