What should you do in the Azure Stack Hub administrator portal?

Topic 3, Trey Research

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

General overview

Trey Research is a pharmaceutical company that has an office in Boston.

Existing environment

Identity Environment

The on-premises network contains an Active Directory forest named treyresearch.net. The forest contains a user named User1.

The forest syncs to an Azure AD tenant named treyresearch.net by using Azure AD Connect.

Trey Research has an internal certification authority (CA).

Compute Environment

The datacenter in the Boston office contains a computer named CLIENT1 that runs Windows 10. CLIENT1 is an administrative workstation that connects directly to the Azure

Stack Hub integrated system.

Planned changes and requirements

Planned changes

Trey Research identifies the following planned changes:

✑ Change the Azure Stack Hub integrated system registration to use an Azure subscription named Subscription3 that has a GUID of 12345678-1234-1234-1234-222222222222.

✑ Configure the integrated system to resolve external names by using a DNS Server that has an IP address of 10.100.100.100.

✑ Implement the App Service resource provider and the Event Hubs resource provider on the integrated system/

✑ Publish a custom cloud-init built image of a Linux virtual machine to Azure Stack Hub Marketplace on the integrated system.

✑ Create a new cloudadmin user named User2.

✑ Assign the delegated provider role to User1.

Azure Stack Hub Requirements

Trey Research identifies the following Azure Stack Hub requirements:

✑ Azure Stack Hub integrated system logs must be forwarded to an external security information and event management (SIEM) system named SIEM1. SIEM1 requires TCP with mutual authentication and TLS 1.2 encryption.

✑ A default Microsoft SQL Server instance will host the database of the App Service resource provider.

✑ The infrastructure of the integrated system must be backed up as frequently as possible.

✑ The integrated system backups must be retained for 28 days.

Business Requirements

Minimize software and licensing costs.

HOTSPOT

You need to configure the Azure Stack Hub infrastructure backups. The solution must meet the Azure Stack Hub requirements.

What should you do in the Azure Stack Hub administrator portal? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

View Answer

Answer:

Explanation:

Box 1: 4

The infrastructure of the integrated system must be backed up as frequently as possible.

Enable backup for Azure Stack Hub from the administrator portal

The frequency in hours determines how often backups are created. The default value is 12.

Scheduler supports a maximum of 12 and a minimum of 4.

Box 2: Azure key vault

The integrated system backups must be retained for 28 days.

Online retention policy. This specifies the time period during which daily, weekly, monthly, and yearly backups are retained in the Azure Site Recovery vault that’s associated with the local MABS instance.