Microsoft AZ-103 Korean Actual Free Exam Questions & Community Discussion

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

Explanation

Step 1: Stop VM1.
Step 2: Detach Disk1 from VM1.
Step 3: Start VM1.
Detach a data disk using the portal
* In the left menu, select Virtual Machines.
* Select the virtual machine that has the data disk you want to detach and click Stop to deallocate the VM.
* In the virtual machine pane, select Disks.
* At the top of the Disks pane, select Edit.
* In the Disks pane, to the far right of the data disk that you would like to detach, click the Detach button image detach button.
* After the disk has been removed, click Save on the top of the pane.
* In the virtual machine pane, click Overview and then click the Start button at the top of the pane to restart the VM.
* The disk stays in storage but is no longer attached to a virtual machine.
Step 4: Attach Disk1 to VM2
Attach an existing disk
Follow these steps to reattach an existing available data disk to a running VM.
* Select a running VM for which you want to reattach a data disk.
* From the menu on the left, select Disks.
* Select Attach existing to attach an available data disk to the VM.
* From the Attach existing disk pane, select OK.
References:
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/detach-disk
https://docs.microsoft.com/en-us/azure/lab-services/devtest-lab-attach-detach-data-disk

Explanation

See solution below.
Explanation
Step 1: Navigate to the rg1lod7523691n1 storage account.
Step 2: Click on the settings menu called Firewalls and virtual networks.
Step 3: Ensure that you have elected to allow access from 'Selected networks'.
Step 4: To grant access to an internet IP range, enter the address range of 131.107.2.0 to 131.107.2.255 (in CIDR format) under Firewall, Address Ranges.
References: https://docs.microsoft.com/en-us/azure/storage/common/storage-network-security

Explanation

Box 1: always
Endpoint status is enabled.
Box 2: Never
After you configure firewall and virtual network settings for your storage account, select Allow trusted Microsoft services to access this storage account as an exception to enable Azure Backup service to access the network restricted storage account.

Reference:
https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows
https://azure.microsoft.com/en-us/blog/azure-backup-now-supports-storage-accounts-secured-with-azure-storage

Explanation: Only visible for EduDump members. You can sign-up / login (it's free).

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

See explanation below.
Explanation
Step 1:
Click Resource groups from the menu of services to access the Resource Groups blade

Step 2:
Click Add (+) to create a new resource group. The Create Resource Group blade appears. Enter corp7509086 as the Resource group name, and click the Create button.

Step 3:
Select Create.
Your group is created and ready for you to add members.
Now we need to assign a role to this resource group scope.
Step 4:
Choose the newly created Resource group, and Access control (IAM) to see the current list of role assignments at the resource group scope. Click +Add to open the Add permissions pane.

Step 5:
In the Role drop-down list, select a role Delegate administration, and select Assign access to: resource group corp7509086

References:
https://docs.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal
https://www.juniper.net/documentation/en_US/vsrx/topics/task/multi-task/security-vsrx-azure-marketplace-resou
Topic 6, ADatum Corporation
Overview
ADatum Corporation is a financial company that has two main offices in New York and Los Angeles.
ADatum has a subsidiary named Fabrikam, Inc. that shares the Los Angeles office.
ADatum is conducting an initial deployment of Azure services to host new line-of-business applications and is preparing to migrate its existing on-premises workloads to Azure.
ADatum uses Microsoft Exchange Online for email.
On-Premises Environment
The on-premises workloads run on virtual machines hosted in a VMware vSphere 6 infrastructure. All the virtual machines are members of an Active Directory forest named adatum.com and run Windows Server
2016.
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.
The offices connect by using a VPN provided by an ISP. Each office has one Azure ExpressRoute circuit that provides access to Azure services and Microsoft Online Services. Routing is implemented by using Microsoft peering.
The New York office has a virtual machine named VM1 that has the vSphere console installed.
Azure Environment
You provision the Azure infrastructure by using the Azure portal. The infrastructure contains the resources shown in the following table.

AG1 has two backend pools named Pool11 and Pool12. AG2 has two backend pools named Pool21 and Pool22.
Planned Changes
ADatum plans to migrate the virtual machines from the New York office to the East US Azure region by using Azure Site Recovery.
Infrastructure Requirements
ADatum identifies the following infrastructure requirements:
* A new web app named App1 that will access third-parties for credit card processing must be deployed.
* A newly developed API must be implemented as an Azure function named App2. App2 will use a blob storage trigger. App2 must process new blobs immediately.
* The Azure infrastructure and the on-premises infrastructure and the on-premises infrastructure must be prepared for the migration of the VMware virtual machines to Azure.
* The sizes of the Azure virtual machines that will be used to migrate the on-premises workloads must be identified.
* All migrated and newly deployed Azure virtual machines must be joined to the adatum.com domain.
* AG1 must load balance incoming traffic in the following manner:
* http://corporate.adatum.com/video/*
will be load balanced across Pool11.
* http://corporate.adatum.com/images/*
will be load balanced across Pool12.
* AG2 must load balance incoming traffic in the following manner:
* http://www.adatum.com
will be load balanced across Pool21.
* http://www.fabrikam.com
will be load balanced across Pool22.
* ER1 must route traffic between the New York office and the platform as a service (PaaS) services in the East US Azure region, as long as ER1 is available.
* ER2 must route traffic between the Los Angeles office and the PaaS sevices in the West US region, as
* long as ER2 is available.
* ER1 and ER2 must be configured to fail over automatically.
Application Requirements
App2 must be able to connect directly to the private IP addresses of the Azure virtual machines. App2 will be deployed directly to an Azure virtual network.
Inbound and outbound communications to App1 must be controlled by using NSGs.
Pricing Requirements
ADatum identifies the following pricing requirements:
* The cost of App1 and App2 must be minimized.
* The transactional charges of Azure Storage account must be minimized.

Explanation

Box 1: 6
4 daily + 1 weekly + monthly
Box 2: 8
4 daily + 2 weekly + monthly + yearly

Explanation

The virtual machines are registered (added) to the private zone as A records pointing to their private IP addresses.
Reference:
https://docs.microsoft.com/en-us/azure/dns/private-dns-overview
https://docs.microsoft.com/en-us/azure/dns/private-dns-scenarios

Explanation