Microsoft Azure Infrastructure and Deployment (AZ-100日本語版) - AZ-100日本語 Exam Practice Test
Correct Answer: A
Explanation: Only visible for ExamsLabs members. You can sign-up / login (it's free).
Correct Answer: A,C
Explanation: Only visible for ExamsLabs members. You can sign-up / login (it's free).
Correct Answer:
See solution below.
Explanation
You can add private and public IP addresses to an Azure network interface by completing the steps that follow.
Step 1: In Azure portal, click More services > type virtual machines in the filter box, and then click Virtual machines.
Step 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:
Step 3: In the pane that appears for the NIC you selected, click IP configurations.
Step 4: Click Create public IP address.
Step 5: 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, as shown in the following picture:
References:
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-multiple-ip-addresses-portal
Explanation
You can add private and public IP addresses to an Azure network interface by completing the steps that follow.
Step 1: In Azure portal, click More services > type virtual machines in the filter box, and then click Virtual machines.
Step 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:
Step 3: In the pane that appears for the NIC you selected, click IP configurations.
Step 4: Click Create public IP address.
Step 5: 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, as shown in the following picture:
References:
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-multiple-ip-addresses-portal
Correct Answer: C
Explanation: Only visible for ExamsLabs members. You can sign-up / login (it's free).
Correct Answer: A
Explanation: Only visible for ExamsLabs members. You can sign-up / login (it's free).
Correct Answer:
Explanation
Box 1: No
Azure DNS provides automatic registration of virtual machines from a single virtual network that's linked to a private zone as a registration virtual network. VM5 does not belong to the registration virtual network though.
Box 2: No
Forward DNS resolution is supported across virtual networks that are linked to the private zone as resolution virtual networks. VM5 does belong to a resolution virtual network.
Box 3: Yes
VM6 belongs to registration virtual network, and an A (Host) record exists for VM9 in the DNS zone.
By default, registration virtual networks also act as resolution virtual networks, in the sense that DNS resolution against the zone works from any of the virtual machines within the registration virtual network.
References: https://docs.microsoft.com/en-us/azure/dns/private-dns-overview
Correct Answer: C
Explanation: Only visible for ExamsLabs members. You can sign-up / login (it's free).
Correct Answer:
Explanation
Note: More than one order of answer choices is correct.
Creating a local gateway (a logical object that represents the on-premise router) can be done at step 1, step 2 or step 3. The other three steps must be done in order: create gateway subnet then create VPN gateway then create the VPN connection. The VPN connection is a connection between the VPN gateway and the Local gateway.
Correct Answer: A
Explanation: Only visible for ExamsLabs members. You can sign-up / login (it's free).
Correct Answer:
Explanation
Box 1: RG1 only
Box 2: 99 years
With the latest update to Azure Backup, customers can retain their data for up to 99 years in Azure.
Note: A backup policy defines a matrix of when the data snapshots are taken, and how long those snapshots are retained.
The backup policy interface looks like this:
References:
https://docs.microsoft.com/en-us/azure/backup/backup-azure-vms-first-look-arm#defining-a-backup-policy
https://blogs.microsoft.com/firehose/2015/02/16/february-update-to-azure-backup-includes-data-retention-up-to-