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

The New-AzureADUserAppRoleAssignment cmdlet assigns a user to an application role in Azure

Active Directory (AD). Use it for the application report.

Reference: https://docs.microsoft.com/en-us/powershell/module/azuread/newazureaduserapproleassignment?view=azureadps-2.0

Reference:

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sql/virtual-machines-windowsportal-sql-alwayson-int-listener

Step 1: Deploy an EC2 virtual machine as a configuration server

Prepare source include:

Use an EC2 instance that's running Windows Server 2012 R2 to create a configuration server and register it with your recovery vault.

Configure the proxy on the EC2 instance VM you're using as the configuration server so that it can access the service URLs.

Step 2: Install Azure Site Recovery Unified Setup.

Download Microsoft Azure Site Recovery Unified Setup. You can download it to your local machine and then copy it to the VM you're using as the configuration server.

Step 3: Enable replication for VM1.

Enable replication for each VM that you want to migrate. When replication is enabled, Site Recovery automatically installs the Mobility service.

Reference:

https://docs.microsoft.com/en-us/azure/site-recovery/migrate-tutorial-aws-azure

URL Path Based Routing allows you to route traffic to back-end server pools based on URL Paths of the request.

In the question there are two different path from where the traffic is getting generated as below

https://adatum.com/internal

https://adatum.com/external

So in this case we can use URL path-based routing feature of Application Gateway.

Reference:

https://docs.microsoft.com/en-us/azure/application-gateway/url-route-overview

Azure Functions runs in two different modes: Consumption plan and Azure App Service plan. the Consumption plan automatically allocates compute power when your code is running. Your app is scaled out when needed to handle load, and scaled down when code is not running.

Incorrect Answers:

B: When you run in an App Service plan, you must manage the scaling of your function app.

Reference:

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

A content delivery network (CDN) is a distributed network of servers that can efficiently deliver web content to users. CDNs' store cached content on edge servers in point-of-presence (POP) locations that are close to end users, to minimize latency.

Azure Content Delivery Network (CDN) offers developers a global solution for rapidly delivering highbandwidth content to users by caching their content at strategically placed physical nodes across the world.

Reference:

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

Which settings are swapped?

When you clone configuration from another deployment slot, the cloned configuration is editable.

Some configuration elements follow the content across a swap (not slot specific), whereas other configuration elements stay in the same slot after a swap (slot specific). The following lists show the settings that change when you swap slots.

Box 1 : On

Settings that are swapped:

General settings, such as framework version, 32/64-bit, web sockets

App settings (can be configured to stick to a slot)

Connection strings (can be configured to stick to a slot)

Handler mappings

Public certificates

WebJobs content

Hybrid connections *

Virtual network integration *

Service endpoints *

Azure Content Delivery Network *

Features marked with an asterisk (*) are planned to be unswapped.

So web sockets settings will be swapped. So Production will have web sockets settings from "Off" to "On" after the swap slot.

Box 2: App1-prod.contoso.com

Settings that aren't swapped:

Publishing endpoints

Custom domain names

Non-public certificates and TLS/SSL settings

Scale settings

WebJobs schedulers

IP restrictions

Always On

Diagnostic settings

Cross-origin resource sharing (CORS)

So Custom domain names will not be swapped. So Production will have Custom domain names of its own after the swap slot.

Reference:

https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots#what-happens-during-aswap

If you have an existing virtual network, either select an existing empty subnet or create a new subnet in your existing virtual network solely for use by the application gateway.

Verify that you have a working virtual network with a valid subnet. Make sure that no virtual machines or cloud deployments are using the subnet. The application gateway must be by itself in a virtual network subnet.

Reference:

https://social.msdn.microsoft.com/Forums/azure/en-US/b09367f9-5d01-4cda-9127-b7a506a0a151/cant-create-application-gateway?forum=WAVirtualMachinesVirtualNetwork

https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-create-gateway

Anonymous access is an authentication method. It allows users to establish an anonymous connection.

Reference:

https://docs.microsoft.com/en-us/biztalk/core/guidelines-for-resolving-iis-permissions-problems