Implementing a backup solution for App1 after the application is moved.

Backup Solution for App1

Question

Case study -

This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.

To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.

At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.

To start the case study -

To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Overview -

Contoso, Ltd. is a manufacturing company that has offices worldwide. Contoso works with partner organizations to bring products to market.

Contoso products are manufactured by using blueprint files that the company authors and maintains.

Existing Environment -

Currently, Contoso uses multiple types of servers for business operations, including the following:

File servers

Domain controllers

Microsoft SQL Server servers

Your network contains an Active Directory forest named contoso.com. All servers and client computers are joined to Active Directory.

You have a public-facing application named App1. App1 is comprised of the following three tiers:

A SQL database

A web front end

A processing middle tier

Each tier is comprised of five virtual machines. Users access the web front end by using HTTPS only.

Requirements -

Planned Changes -

Contoso plans to implement the following changes to the infrastructure:

Move all the tiers of App1 to Azure.

Move the existing product blueprint files to Azure Blob storage.

Create a hybrid directory to support an upcoming Microsoft Office 365 migration project.

Technical Requirements -

Contoso must meet the following technical requirements:

Move all the virtual machines for App1 to Azure.

Minimize the number of open ports between the App1 tiers.

Ensure that all the virtual machines for App1 are protected by backups.

Copy the blueprint files to Azure over the Internet.

Ensure that the blueprint files are stored in the archive storage tier.

Ensure that partner access to the blueprint files is secured and temporary.

Prevent user passwords or hashes of passwords from being stored in Azure.

Use unmanaged standard storage for the hard disks of the virtual machines.

Ensure that when users join devices to Azure Active Directory (Azure AD), the users use a mobile phone to verify their identity.

Minimize administrative effort whenever possible.

User Requirements -

Contoso identifies the following requirements for users:

Ensure that only users who are part of a group named Pilot can join devices to Azure AD.

Designate a new user named Admin1 as the service admin for the Azure subscription.

Admin1 must receive email alerts regarding service outages.

Ensure that a new user named User3 can create network objects for the Azure subscription.

You need to implement a backup solution for App1 after the application is moved.

What should you create first?

Introductory Info

Question

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

B

Scenario: Ensure that all the virtual machines for App1 are protected by backups.

You can back up Azure VMs using a couple of methods:

-> Single Azure VM: You can back up an Azure VM directly from the VM settings.

-> Multiple Azure VMs: You can set up a Recovery Services vault and configure backup for multiple Azure VMs.

https://docs.microsoft.com/en-us/azure/backup/backup-azure-vms-first-look-arm

To implement a backup solution for App1 after it is moved to Azure, the first thing that needs to be created is a Recovery Services vault.

A Recovery Services vault is an Azure resource that is used to manage backup and recovery of virtual machines, on-premises servers, and cloud services. The vault provides a storage location for backup data and can be used to manage backup policies and perform restores.

Once the Recovery Services vault is created, the next step is to create a backup policy. A backup policy is used to define the frequency and retention of backups for the virtual machines in App1. The backup policy can be customized to meet the technical requirement of ensuring that all virtual machines for App1 are protected by backups.

After the backup policy is created, it needs to be associated with the virtual machines in App1. This can be done by installing the Azure VM Backup extension on each virtual machine and then configuring it to use the backup policy.

Finally, a recovery plan can be created to define the steps that need to be taken in the event of a disaster or outage. The recovery plan can include steps for restoring virtual machines from backup and testing the recovery process to ensure that it works correctly.

In summary, to implement a backup solution for App1 after it is moved to Azure, the following steps should be taken:

  1. Create a Recovery Services vault.
  2. Create a backup policy that meets the technical requirements.
  3. Associate the backup policy with the virtual machines in App1.
  4. Create a recovery plan to define the steps for restoring virtual machines in the event of a disaster or outage.