Microsoft AZ-104 Practice Test - Questions Answers, Page 34

https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pimresource-roles-assign-roles

Reference:

https://docs.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns

Below are the steps you need to perform in this scenario. Refer the link mentioned in the reference section.

Download the installation file for the Azure Site Recovery Provider

To set up the source environment, you create a Hyper-V site and add to that site the Hyper-V hosts containing VMs that you want to replicate. Then, you download and install the Azure Site Recovery

Provider and the Azure Recovery Services agent on each host, and register the Hyper-V site in the vault.

Download the vault registration key

Download the Vault registration key. You need this when you install the Provider. The key is valid for five days after you generate it.

Install the Azure Site Recovery Provider on Host1.

Install the downloaded setup file (AzureSiteRecoveryProvider.exe) on each Hyper-V host that you want to add to the Hyper-V site. Setup installs the Azure Site Recovery Provider and Recovery

Services agent on each Hyper-V host.

Register the server

In Registration, after the server is registered in the vault, select Finish.

Reference:

https://docs.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-tutorial

Reference:

https://docs.microsoft.com/en-us/azure/active-directory/privileged-identity-management/pimhow-to-add-role-to-user?tabs=new

Owner: An owner can configure peering.

A Global administrator can configure peering.

Network Contributor:

The accounts you use to work with virtual network peering must be assigned to the following roles:

ß Network Contributor: For a virtual network deployed through Resource Manager.

ß Classic Network Contributor: For a virtual network deployed through the classic deployment model.

Reference:

https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/govern/resourceconsistency/ governance-multiple-teams

Statement 1: Yes

Vnet1 and Vnet3 are peers.

Statement 2: No

Statement 3: No

Peering connections are non-transitive.

Reference:

https://docs.microsoft.com/en-us/azure/architecture/reference-architectures/hybridnetworking/hub-spoke

Rule 2 is blocking HTTPS access (port 443) and has a priority of 500.

Changing Rule 3 (ports 60-500) and giving it a lower priority number will allow access on port 443.

Note: Rules are processed in priority order, with lower numbers processed before higher numbers, because lower numbers have higher priority. Once traffic matches a rule, processing stops.

Incorrect Answers:

A: HTTPS uses port 443. Rule6 only applies to ports 150 to 300.

C, D: Rule 1 blocks access to port 80, which is used for HTTP, not HTTPS.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-network/security-overview

Application Security Group can be associated with NICs.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-network/security-overview#application-securitygroups

Rule 2 is blocking HTTPS access (port 443) and has a priority of 500.

Changing Rule 5 (ports 50-5000) and giving it a lower priority number will allow access on port 443.

Note: Rules are processed in priority order, with lower numbers processed before higher numbers, because lower numbers have higher priority. Once traffic matches a rule, processing stops.

Reference:

https://docs.microsoft.com/en-us/azure/virtual-network/security-overview