Answer: C

Explanation:

Azure Site Recovery can protect Microsoft Hyper-V, VMware, and physical servers, and you can use Azure or your secondary datacenter as your recovery site.

From scenario: The company has a human resources (HR) application named HRApp that stores data in an on-premises SQL Server database. The database must have at least two copies, but data to support backups and business continuity must stay in Trey Research locations only. The data must remain on-premises and cannot be stored in the cloud.

References: https://azure.microsoft.com/en-us/services/site-recovery/

Answer: A,E

Explanation:

* Scenario:

/ Mitigate the need to purchase additional tools for monitoring and debugging.

/A debugger must automatically attach to websites on a weekly basis. The scripts that handle the configuration and setup of debugging cannot work if there is a delay in attaching the debugger.

A: After publishing your application you can use the Server Explorer in Visual Studio to access your web sites.

After signing in you will see your Web Sites under the Windows Azure node in Server Explorer. Right click on the site that you would like to debug and select Attach Debugger.

E: When the processes appear in the Available Processes table, select w3wp.exe, and then click Attach.

Open a browser to the URL of your web app.

References: http://blogs.msdn.com/b/webdev/archive/2013/11/05/remote-debugging-a-window-azure-web-site-with-visual-studio-2013.aspx

Answer: E

Answer: A

Answer: A

Explanation:

Deadlettering u2013 From time to time a message may arrive in your queue that just canu2021t be processed. Each time the message is retrieved for processing the consumer throws an exception and cannot process the message. These are often referred to as poisonous messages and can happen for a variety of reasons, such as a corrupted payload, a message containing an unknown payload inadvertently delivered to a wrong queue, etc. When this happens, you do not want your system to come to grinding to a halt simply because one of the messages canu2021t be processed.

Ideally the message will be set aside to be reviewed later and processing can continue on to other messages in the queue. This process is called u2021Deadletteringu2021 a message and the Service Bus Brokered Messaging supports dead lettering by default. If a message fails to be processed and appears back on the queue ten times it will be placed into a dead letter queue. You can control the number of failures it takes for a message to be dead lettered by setting the MaxDeliveryCount property on the queue. When a message is deadlettered it is actually placed on a sub queue which can be accessed just like any other Service Bus queue. In the example used above the dead letter queue path would be samplequeue/$DeadLetterQueue. By default a message will be moved to the dead letter queue if it fails delivery more than 10 times.

Automatic dead lettering does not occur in the ReceiveAndDelete mode as the message has already been removed from the queue.

References: https://www.simple-talk.com/cloud/cloud-data/an-introduction-to-windows-azure-service-bus-brokered-messaging/

Answer: A

Explanation:

A Microsoft cloud service administrator who wants to provide their Azure Active Directory (AD) users with sign-on validation can use a SAML 2.0 compliant SP-Lite profile based Identity Provider as their preferred Security Token Service (STS) / identity provider. This is useful where the solution implementer already has a user directory and password store on- premises that can be accessed using SAML 2.0. This existing user directory can be used for sign-on to Office 365 and other Azure AD-secured resources.

References: https://msdn.microsoft.com/en- us/library/azure/dn641269.aspx?f=255&MSPPError=-2147217396

Answer: A

Explanation:

* Scenario: Permissions must be assigned by using Role Based Access Control (RBAC).

* Role-Based access control (RBAC) in the Azure Portal and Azure Resource Management API allows you to manage access to your subscription at a fine-grained level. With this feature, you can grant access for Active Directory users, groups, or service principals by assigning some roles to them at a particular scope.

Create a role assignment

Use New-AzureRoleAssignment to create a role assignment.

Example: This will create a role assignment for a group at a resource group level.

PS C:> New-AzureRoleAssignment -ObjectID <group object ID> -RoleDefinitionName Reader -ResourceGroupName group1

References: https://azure.microsoft.com/en-gb/documentation/articles/role-based-access-control-powershell/

Answer: E

Explanation:

Custom Script Extension can automatically download scripts and files from Azure Storage and launch a PowerShell script on the VM which in turn can install additional software components. And just like with any other VM Extension, this can be added during VM creation or after the VM has been running.

References: https://azure.microsoft.com/en-us/blog/automating-vm-customization-tasks-using-custom-script-extension/

Answer: B

Explanation:

* Scenario: The partners all use Hotmail.com email addresses.

* In Microsoft Azure Active Directory Access Control (also known as Access Control Service or ACS), an identity provider is a service that authenticates user or client identities and issues security tokens that ACS consumes.

The ACS Management Portal provides built-in support for configuring Windows Live ID as an ACS Identity Provider.

Incorrect:

Not C, not D: Scenario: VanArsdel management does NOT want to create and manage user accounts for partners.

Answer: B

Explanation:

The Set-AzureRole cmdlet sets the number of instances of a specified role to run in an Azure deployment.

References: https://docs.microsoft.com/en-us/powershell/module/Azure/Set- AzureRole?view=azuresmps-4.0.0