Answer: C 

Explanation: The Add-AzureVMImage cmdlet adds an operating system image to the 

image repository. The image should be a generalized operating system image, using either 

Sysprep for Windows or, for Linux, using the appropriate tool for the distribution. 

Example 

This example adds an operating system image to the repository. 

Windows PowerShell 

C:\PS>Add-AzureVMImage -ImageName imageName -MediaLocation 

http://yourstorageaccount.blob.core.azure.com/container/sampleImage.vhd -Label 

Reference: Add-AzureVMImage 

Answer:  

Answer: C 

Explanation: * When you get deeper into using Windows Azure Active Directory, you’ll run into new terminology. For instance, is called "directory" is also referred to as a Windows Azure AD Tenant or simply as "tenant." This stems from the fact that WAAD ()Windows Azure Active Directory.is a shared service for many clients. In this service, every client gets its own separate space for which the client is the tenant. In the case of WAAD this space is a directory. This might be a little confusing, because you can create multiple directories, in WAAD terminology multiple tenants, even though you are a single client. 

* Multitenant Applications in Azure A multitenant application is a shared resource that allows separate users, or "tenants," to view the application as though it was their own. A typical scenario that lends itself to a multitenant application is one in which all users of the application may wish to customize the user experience but otherwise have the same basic business requirements. Examples of large multitenant applications are Office 365, Outlook.com, and visualstudio.com. 

Reference: Multitenant Applications in Azure 

http://msdn.microsoft.com/en-us/library/azure/dn151789.aspx 

Answer: D 

Explanation: When you deploy your application to Azure Websites, you can deploy to a separate deployment slot instead of the default production slot, which are actually live sites with their own hostnames. 

Furthermore, you can swap the sites and site configurations between two deployment slots, including the production slot. Deploying your application to a deployment slot has the following benefits: 

* You can validate website changes in a staging deployment slot before swapping it with the production slot. 

* After a swap, the slot with previously staged site now has the previous production site. If the changes swapped into the production slot are not as you expected, you can perform the same swap immediately to get your "last known good site" back. 

* Deploying a site to a slot first and swapping it into production ensures that all instances of the slot are warmed up before being swapped into production. This eliminates downtime when you deploy your site. The traffic redirection is seamless, and no requests are dropped as a result of swap operations. 

Reference: Staged Deployment on Microsoft Azure Websites 

Answer:  

Answer: C 

Explanation: Example 

This example starts log streaming and show error logs only. 

Windows PowerShell 

C:\PS>Get-AzureWebsiteLog -Tail -Message Error 

Reference: Get-AzureWebsiteLog 

URL: http://msdn.microsoft.com/en-us/library/dn495187.aspx 

Answer:  

Answer: C 

Explanation: Specify a static internal IP for a previously created VM 

If you want to set a static IP address for a VM that you previously created, you can do so by using the following cmdlets. If you already set an IP address for the VM and you want to change it to a different IP address, you’ll need to remove the existing static IP address before running these cmdlets. See the instructions below to remove a static IP. For this procedure, you’ll use the Update-AzureVM cmdlet. The Update-AzureVM cmdlet restarts the VM as part of the update process. The DIP that you specify will be assigned after the VM restarts. In this example, we set the IP address for VM2, which is located in cloud service StaticDemo. 

Get-AzureVM -ServiceName StaticDemo -Name VM2 | Set-AzureStaticVNetIP -IPAddress 

192.168.4.7 | Update-AzureVM 

Reference: Configure a Static Internal IP Address (DIP) for a VM URL: http://msdn.microsoft.com/en-us/library/azure/dn630228.aspx 

Answer: D 

Explanation: The Azure Active Directory Graph API provides programmatic access to Azure AD through REST API endpoints. Applications can use the Graph API to perform create, read, update, and delete (CRUD) operations on directory data and objects. For example, the Graph API supports the following common operations for a user object: / Create a new user in a directory / Get a user’s detailed properties, such as their groups / Update a user’s properties, such as their location and phone number, or change their password / Check a user’s group membership for role-based access / Disable a user’s account or delete it entirely 

Reference: Azure AD Graph API 

URL: http://msdn.microsoft.com/en-us/library/azure/hh974476.aspx 

Answer: C 

Explanation: . Within the Azure Portal screen, scroll down to Recovery Services (on the left menu), and click on “Create a New Vault” (this is where your VMs will be replicated to) which will bring up a Data Services / Recovery Services / Site Recovery Vault option, select Quick Create . For the name of the Vault, give it something you’d remember, in my case, I’ll call it RandsVault, and I’ll choose the Region West US since I’m in the Western United States, then click Create Vault . Once the Vault has been created, click on the Right Arrow next to the name of your vault. Under Setup Recovery, choose “Between an on-premise site and Microsoft Azure” so that you are telling the configuration settings that you are going to be replicating between your on-premise datacenter and Azure in the cloud. . You will now see a list of things you need to do which the first thing is to create a key exchange of certificates between Microsoft Azure and your VMM server. 

Reference: Leveraging Microsoft Azure as your disaster recovery/failover data center