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

In Project Details, specify the project name, and geography in which you want to create the project.

Review supported geographies for public and government clouds.

Reference:

https://docs.microsoft.com/en-us/azure/migrate/how-to-add-tool-first-time

Box 1: New-AzureRmWebAppSlot

The New-AzureRmWebAppSlot cmdlet creates an Azure Web App Slot in a given a resource group that uses the specified App Service plan and data center.

Box 2: -SourceWebApp

Reference:

https://docs.microsoft.com/en-us/powershell/module/azurerm.websites/new-azurermwebappslot

Reference:

https://docs.microsoft.com/en-us/azure/event-grid/monitor-virtual-machine-changes-event-gridlogic-app

Action 1: Create an Azure Logic App

Action 2: Create an Azure Event Grid Trigger

Action 3: Create conditions and actions

Reference:

https://docs.microsoft.com/en-us/azure/event-grid/monitor-virtual-machine-changes-event-gridlogic-app

Reference:

https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topicssubscriptions

Box 1: retained until manually deleted

Since by default PeekLock shall be enabled in Queue, so it will move to DeadLetter after 2hours and stays there until manually deleted. Messages in the dead letter queue should be deleted manually.

Box 2: deleted immediately

Once a message is pulled, it will be deleted immediately. It does not make sense to keep the message further 5 minutes "locked" in the queue. Locking the message makes sense, for the case, when processing the message from a receiver, to lock the message, to avoid processing/receiving the message simultaneously by another receiver.

The receiving client initiates settlement of a received message with a positive acknowledgment when it calls Complete at the API level. This indicates to the broker that the message has been successfully processed and the message is removed from the queue or subscription.

Reference:

https://docs.microsoft.com/en-us/azure/service-bus-messaging/message-expiration

https://docs.microsoft.com/en-us/azure/service-bus-messaging/message-transfers-locks-settlement

Azure AD Privileged Identity Management introduces the concept of an eligible admin. Eligible admins should be users that need privileged access now and then, but not all-day, every day. The role is inactive until the user needs access, then they complete an activation process and become an active admin for a predetermined amount of time.

Reference:

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

Reference:

https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/app-service/web-sites-scale.md

Scale up : Correct Choice

Scale up: Get more CPU, memory, disk space, and extra features like dedicated virtual machines (VMs), custom domains and certificates, staging slots, autoscaling, and more. You scale up by changing the pricing tier of the App Service plan that your app belongs to.

Scale out : Incorrect Choice

Scale out: Increase the number of VM instances that run your app. You can scale out to as many as 30 instances, depending on your pricing tier. App Service Environments in Isolated tier further increases your scale-out count to 100 instances. For more information about scaling out, see Scale instance count manually or automatically.

Add continuous WebJobs : Incorrect Choice

WebJobs is a feature of Azure App Service that enables you to run a program or script in the same instance as a web app, API app, or mobile app. Add continuous WebJobs will Starts immediately when the WebJob is created. To keep the job from ending, the program or script typically does its work inside an endless loop. If the job does end, you can restart it.Starts only when triggered manually or on a schedule.

Add a virtual machine scale set : Incorrect Choice

A virtual machine scale set allows you to deploy and manage a set of identical, autoscaling virtual machines. You can scale the number of VMs in the scale set manually. You can also define rules to autoscale based on resource usage such as CPU, memory demand, or network traffic. It will not increase the slowness of the apps.

Reference:

https://docs.microsoft.com/en-us/azure/app-service/manage-scale-up

https://docs.microsoft.com/en-us/azure/app-service/webjobs-create#webjob-types

Instead: You create an Azure Log Analytics workspace and configure the data settings. You install the Microsoft Monitoring Agent on VM1. You create an alert in Azure Monitor and specify the Log

Analytics workspace as the source.

Reference:

https://docs.microsoft.com/en-us/azure/azure-monitor/platform/agents-overview