WS-013 Azure

Stack HCI

© Copyright Microsoft Corporation. All rights reserved.

Module 1: Introducing
Azure Stack HCI
Module overview

A software-defined datacenter offers flexibility, elasticity, agility and automation, because

each of its building blocks is virtualized and available as a service. A variety of software and
hardware vendors offer their own software-defined solutions. This module provides an
overview of the solutions that are part of the Microsoft Azure Stack portfolio and focuses on
the Azure Stack HCI offering
 Lessons:
o Overview of Azure Stack

o Overview of Azure Stack HCI technologies

o Overview of Azure Stack HCI management tools

o Overview of Azure Stack HCI hybrid capabilities

o Overview of the Azure Stack HCI implementation process

Lesson 1: Overview of
Azure Stack
Lesson 1 overview

The purpose of this lesson is to describe characteristics of private and hybrid cloud solutions
that are part of the Azure Stack portfolio, consisting of Azure Stack HCI, Azure Stack Hub, and
Azure Stack Edge
 Topics:
o Azure Stack portfolio

o Azure Stack Hub

o Azure Stack Edge

o Azure Stack HCI

Azure Stack portfolio

The three Azure Stack products share the following characteristics, which reflect their
common goal of facilitating transition to a hybrid cloud model that takes advantage of Azure-
based capabilities:
 On-premises deployments
 Close integration with Azure
 Accelerated replacement and consolidation of legacy infrastructure
 Support for disconnected scenarios, without direct connectivity to Azure
Azure Stack Hub

 In the simplest terms, you can think of Azure Stack Hub as Azure for on-premises
environments
 To determine whether your workloads are suitable for Azure Stack Hub rather than Azure,
consider:
o Azure service dependency

o Performance requirements

o Cost

o Management and maintenance overhead

o Security and compliance

Azure Stack Edge

 Azure Stack Edge facilitates processing of on-premises data and transferring it to Azure
Storage
 Azure Stack Edge has three primary components:
o Azure Stack Edge physical, rack-mounted appliance that you can deploy on edge
networks of your on-premises datacenters to function as a network storage gateway.
It includes an integrated FPGA component, which enables accelerated AI inferencing
for ML models
o Azure Stack Edge resource accessible via the Azure portal that allows you to
administer and monitor multiple Azure Stack Edge physical appliance
o Azure Stack Edge local web UI, which provides direct connection to individual Azure
Stack Edge appliances, facilitating initial installation and supporting such
management capabilities as restarting the appliances or viewing and copying local
logs
Azure Stack HCI

 Azure Stack HCI consists of:

o Virtualized compute based on the Hyper-V server role
o Virtualized storage based on Storage Spaces Direct

o (Optionally) Virtualized networking based on SDN with the Network Controller server
role
 The most common Azure Stack HCI scenarios include:
o Branch office and edge

o VDI

o High-performance Microsoft SQL Server

o Trusted enterprise virtualization

o Scale-out storage
Lesson 1: Test your knowledge

Refer to the Student Guide for lesson-review questions

Lesson 2: Overview of
Azure Stack HCI
technologies
Lesson 2 overview

This lesson provides an overview of the technologies that serve as its underlying core
components of Azure Stack HCI
 Topics:
o Hyper-V
o Failover clustering
o Guest clustering with shared disks
o Hyper-V Replica
o Cluster Shared Volumes
o Scale-Out File Servers
o Storage Replica

o Software-defined storage

o Software-Defined Networking

o Guarded fabric

o Cluster sets
Hyper-V

 The Hyper-V role in Windows Server 2019 offers a wide range of capabilities:
 Hyper-V scalability
 Automatic virtual machine activation
 Host resource protection and discrete device assignment
 Runtime resize of VM memory, add and resize VHDX, Hot-Add and vNIC naming
 Checkpoints and live migration
 Virtual machine network and storage resiliency
 Start order priority for clustered guest virtual machines
 Windows PowerShell Direct
 Nested virtualization
 Virtualization-based security
 Rolling upgrades and Integration Services for Windows VMs through Windows Update
Failover clustering

 A failover cluster consists of the following components:

o Nodes
o Clients
o Networks
o Clustered role
o Resources
o Cluster storage
o Witness (disk, file, cloud)
 The Failover Clustering functionality and architecture are dependent on:
o Functional level
o Quorum model
o Witness type
Guest clustering with shared disks (1 of 2)

 Failover clustering at the VM level ensures that cluster roles inside a VM are highly available
 You might need shared storage for the quorum, for cluster roles configuration, and for data
storage
 You can use for this purpose iSCSI, Fibre Channel SAN, or virtual hard disks (VHD Set) as
shared storage
 VHD Set files have several requirements:
o The virtual hard disk must use the .vhds format

o The virtual hard disk must be connected to a SCSI virtual controller

o A shared virtual hard disk can only store applications and data

o A shared virtual hard disk must be stored on a highly available location

o You can enable virtual hard disk sharing only if the VM is turned off

o To use virtual hard disk sharing, the VM must have Integration Services installed
Guest clustering with shared disks (2 of 2)

Capability Virtual Fibre iSCSI in a virtual

Shared virtual hard disk
Channel machine
Supported storage Storage Spaces, serial attached SCSI, Fibre Channel SAN iSCSI SAN
Fibre Channel, iSCSI, SMB
How storage is presented in the Virtual serial attached SCSI Virtual Fibre Channel iSCSI LUN
virtual machine LUN
Data flows through the Hyper-V No No Yes
switch
Storage is configured at the Yes Yes No
Hyper-V host level
Provides low latency and low CPU Yes (RDMA or Fibre Channel) Yes (Fibre Channel) No
use

Requires specific hardware No No

Yes

Switch must be reconfigured No Yes No

when the virtual machine is
migrated
Exposes storage architecture No Yes Yes
Hyper-V Replica (1 of 4)

 Hyper-V Replica is a disaster recovery feature built into Hyper-V that replicates VMs to a
secondary location and, if needed, to a third location
 Hyper-V Replica has several prerequisites:
o Windows Server with the Hyper-V role

o Sufficient storage

o Network connectivity

o Firewall rules that allow replication between the primary and replica sites

o Authentication (Kerberos or certificate-based)

Hyper-V Replica (2 of 4)

 You can establish Hyper-V Replica between the Hyper-V hosts irrespective of whether they
are nodes in a failover cluster or not
 Hyper-V Replica offers four different configurations from the resiliency standpoint:
o Both Hyper-V hosts are standalone servers

o The Hyper-V host at the primary location is a node in a failover cluster and Hyper-V
Replica is on the standalone server
o Each Hyper-V host is a node in a different failover cluster

o A Hyper-V host at the primary location is a standalone server and a Hyper-V host at
the secondary location is a node in the failover cluster
Hyper-V Replica (3 of 4)

Hyper-V Replica consists of the following components:

 Replication engine
 Change tracking module
 Network module
 Hyper-V Replica Broker
 Management tools
Hyper-V Replica (4 of 4)

Hyper-V Replica enhances security by providing the following configuration options:

 Delegation
 Server-level authorization
 Kerberos and certificate-based authentication
 Windows Defender Firewall with Advanced Security rules-based rules
Cluster Shared Volumes

 CSV enables multiple cluster nodes to concurrently access the same shared storage LUN
 CSV characteristics include:
o CSV file system
o Simplified CSV setup
o Uniform presentation of CSV
o Support for BitLocker
o Integration with SMB Multichannel and SMB Direct
o Integration with Storage Spaces
o Ability to use local storage through the Storage Spaces Direct feature
o Ability to scan and repair volumes while online
Scale-Out File Servers

 Scale-Out File Server is a failover clustering feature that allows multiple cluster nodes to
perform read and write operations targeting files on the same CSV
 A Scale-Out File Server provides the following benefits:
o Improved scaling

o Load-balanced utilization

o Nondisruptive maintenance, updates, and node failures

o Cluster Shared Volumes cache

o Automatic rebalancing of clients

o Support for multiple SMB instances per node

o Simplified management
Storage Replica

 Storage Replica enables storage-agnostic, block-level replication between servers or

clusters that are in the same or different sites
 Storage Replica supported configurations include:
o Stretch cluster

o Cluster-to-cluster

o Server-to-server

o Server-to-self

 Storage Replica has the following requirements:

o AD DS environment

o At a minimum, 2 GB of RAM and two CPU cores per server

o One or more Ethernet connections on each server

o Round trip latency at most 5 ms for synchronous replication

Software-defined storage (1 of 2)

 Windows Server 2019-based software-defined storage uses the following features:

o SMB3, SMB Transparent Failover, SMB Scale Out, SMB Multichannel, SMB Direct, and
SMB Encryption
o Scale-Out File Server
o Storage Spaces Direct
• Disaggregated deployment model
• Hyperconverged deployment model
o Storage QoS
o Data Deduplication
o Storage Replica
o Storage space tiering
Software-defined storage (2 of 2)

 Storage Spaces Direct provides an alternative to SAN storage

 Storage Spaces Direct has the following characteristics:
o Uses locally attached SAS, SATA, or NVMe drives across two or more servers that are
part of the same Windows Server 2016 failover cluster
o Requires a high-bandwidth, low-latency network between the nodes

o Leverages ReFS to provide additional performance improvements

 Storage Spaces Direct supports two basic architectural models:

o Disaggregated

o Hyperconverged
Software-Defined Networking

 SDN provides a method to centrally configure and manage physical and virtual network
devices
 SDN abstracts your network infrastructure, defines policies to control the network, and
gives you the tools to manage the network
o Network abstraction
o Network policies
o Network management
 SDN offers agility, security, and efficiency
 SDN consists of the following components:
o HNV
o Hyper-V virtual switch
o Network Controller
o RDMA and RoCE
o SET
Guarded fabric

 Windows Server 2019 supports shielded VMs by using BitLocker to protect them from
unauthorized access and tampering
 Shielded VMs can only run on a guarded fabric, which includes trusted Hyper-V hosts and
an HGS host or cluster
 Guarded fabric can run three types of virtual machines:
o Unprotected VMs

o Encryption-supported VMs

o Shielded VMs

 HGS can use one of three mutually exclusive attestation modes to authorize Hyper-V hosts:
o TPM-trusted attestation

o Host key attestation

o Admin-trusted attestation (deprecated)

Cluster sets

 A cluster set is a group of Windows Server 2019 compute, storage, and hyperconverged
clusters
 Cluster sets address two primary challenges:
o Availability

o Scalability

 A cluster set consists of the following components:

o Management cluster

o Member clusters

o Cluster set namespace referral Scale-Out File Server

o Cluster set master

o Cluster set worker

Lesson 2: Test your knowledge

Refer to the Student Guide for lesson-review questions

Lesson 3: Overview of
Azure Stack HCI
management tools
Lesson 3 overview

Managing Azure Stack HCI requires a range of management tools—beyond those commonly
used for traditional Windows Server management. This lesson provides an overview of these
tools and focuses on those that you will use throughout the course to deploy, configure, and
troubleshoot Azure Stack HCI
 Topics:
o Windows Admin Center

o Demonstration: Deploy hyperconverged infrastructure by using Windows Admin

Center
o System Center Virtual Machine Manager and Operations Manager

o PowerShell and PowerShell DSC

o Demonstration: Use PowerShell and PowerShell DSC to configure and manage

Windows Server 2019
o Azure Arc
Windows Admin Center

 Windows Admin Center is the recommended tool for managing Azure Stack HCI
deployments
 Windows Admin Center offers several benefits:
o Simple deployment

o Integration with existing solutions

o Access from anywhere

o Enhanced security

o Azure integration (Azure File Sync, Azure Monitor)

o Management of hyperconverged clusters (Cluster Creation, Cluster Manager)

o Extensibility
Demonstration:
Deploy
hyperconverged
infrastructure by
using Windows
Admin Center
System Center Virtual Machine Manager and Operations Manager

 The two System Center 2019 products that are of interest in the context of this course are:
o System Center Virtual Machine Manager:
• Simplifies configuring and managing datacenter components as a single fabric in
VMM
• Can add, provision, and manage Hyper-V and VMware virtualization hosts and
clusters
• Manages adding networking resources to the VMM fabric
• Can discover, classify, provision, allocate, and assign local and remote storage
• Contains a library of file-based resources and resources that are not file-based
that are used to create and deploy VMs and services on virtualization hosts
o System Center Operations Manager:
• Simplifies monitoring of computers, devices, services, and applications
• Automatically analyzes health of monitored objects, sends alerts when problems
are identified, and provides information to help with troubleshooting
PowerShell and PowerShell DSC (1 of 4)

 PowerShell is a scripting language, a command-line shell, and a scripting platform

 PowerShell offers a range of management benefits:
o Extensibility through modules
o PowerShell Remoting
o PowerShell DSC
PowerShell and PowerShell DSC (2 of 4)

 Windows PowerShell Remoting uses an open standard protocol called Web Services for
Management (WS-Management), which relies on HTTP and HTTPS as its transport protocols
 PowerShell Remoting supports both workgroup and AD DS domain–based scenarios:
o PowerShell Remoting in workgroup scenarios:

• Needs to be explicitly enabled

• Should be configured to use the HTTPS transport protocol
o PowerShell Remoting in domain scenarios:

• Is automatically enabled
• Relies on Kerberos authentication
PowerShell and PowerShell DSC (3 of 4)

 PowerShell DSC implements declarative configuration management

 Windows server-based DSC relies on the LCM component, which serves as the execution
engine of the Windows PowerShell DSC scripts
 The LCM ConfigurationMode property determines how LCM handles PowerShell DSC
scripts:
o ApplyOnly

o ApplyAndMonitor

o ApplyAndAutoCorrect

 DSC scripts are implemented as configurations

PowerShell and PowerShell DSC (4 of 4)
configuration IISConfig
{
Import-DscResource –Module xWebAdministration

node ("localhost") {

WindowsFeature IIS {
Ensure = "Present"
Name = "Web-Server"
}
WindowsFeature AspNet45 {
Ensure = "Present"
Name = "Web-Asp-Net45"
}
xWebsite DefaultSite {
Ensure = "Present"
Name = "Default Web Site"
State = "Stopped"
PhysicalPath = “C:\inetpub\wwwroot"
DependsOn = "[WindowsFeature]IIS"
}
}
}
Demonstration:
Use PowerShell
and PowerShell
DSC to configure
and manage
Windows Server
2019
Azure Arc

 Azure Arc is a set of technologies for customers who want to simplify complex and
distributed environments across on-premises, edge, and multicloud environments
 Azure Arc hybrid capabilities:
o Azure Policy guest configuration

o Support for resource-context access to Log Analytics data

Lesson 3: Test your knowledge

Refer to the Student Guide for lesson-review questions

Lesson 4: Overview of
Azure Stack HCI hybrid
capabilities
Lesson 4 overview

Azure offers a wide range of services that provide integration capabilities. The purpose of this
lesson is to provide an overview of these capabilities applicable to Azure Stack HCI–based
scenarios
 Topics:
o Cloud Witness

o Azure Network Adapter

o Azure File Sync

o Azure Monitor

o Azure Backup

o Azure Site Recovery

o Azure Update Management

Cloud Witness

 Cloud Witness is a Failover Clustering quorum option optimal for distributed and cloud-
based scenarios
 To implement Cloud Witness, you must have an Azure Storage account with the following
configuration:
o General Purpose v1 or General Purpose v2 Azure Storage account kind

o LRS replication option

 When configuring a Cloud Witness, consider the following:

o Instead of storing an access key, Failover Cluster will use it to generate an SAS
token, which is then stored securely on the cluster nodes
o The SAS token is valid as long as the corresponding access key remains valid.
Update the Cloud Witness with the secondary access key before regenerating the
primary one, and vice versa
o Cloud Witness uses the HTTPS REST interface of the Azure Storage account blob
service. This means that HTTPS outbound traffic to Azure Storage needs to be
allowed on all cluster nodes
Azure Network Adapter

 Azure Network Adapter is a convenient method of establishing a point-to-site VPN to an

Azure virtual network by using Windows Admin Center
 Azure Network Adapter has the following primary characteristics:
o Requires that you register the Windows Admin Center instance with Azure

o Requires an existing Azure virtual network with the gateway subnet

o Generates new certificates or uses existing certificates for authentication/encryption

o Provisioning of the VPN gateway might take about 25 minutes

Azure File Sync

 Azure File Sync consists of the following components:

o Storage Sync Service
o Sync group

o Registered server

o Azure File Sync agent

o Server endpoint

o Cloud endpoint

 Azure File Sync offers the following benefits:

o Multisite sync

o Cloud tiering

o Cloud backup

o Disaster recovery
Azure Monitor

 Azure Monitor provides comprehensive cloud-based monitoring for cloud and on-premises
environments
 Azure Monitor supports the following features:
o Collection and monitoring of metrics, activity, and diagnostics logs, and events from
a wide range of Azure services and computers residing in on-premises datacenters
and third-party cloud providers
o A quick way to assess the status of your environment in the Azure portal

o Archiving collected data for long-term analysis or compliance purposes in Azure

Storage or routing it to Azure Stream Analytics or non-Microsoft services via Event
Hub
o Storing and analyzing near–real time and historical data by using Log Analytics
Azure Backup

 Azure Backup provides the following options in hybrid scenarios:

o Integration with built-in Windows Backup feature
o Integration with Microsoft System Center DPM
o Microsoft Azure Backup Server
 Azure Backup provides the following functionality in hybrid scenarios:
o Local file, folder, and system state backups performed by using Windows Server
Backup
o Long-term storage of backups of Windows servers performed by using DPM
o Long-term storage of backups of Windows servers performed by using MBAS
 Azure Backup provides protection of backups stored in Azure Recovery Services vault,
including:
o Soft delete (enabled by default), which retains deleted backups for 14 days
o A custom PIN, which is required to stop protection and delete backup data
o Administrative email alerts and disabling or deleting backups
Azure Site Recovery

 Azure Site Recovery is a disaster recovery and business continuity service that provides
replication and orchestration
 Azure Site Recovery provides support for three disaster recovery scenarios:
o Failover and failback between two on-premises sites

o Failover and failback between an on-premises site and an Azure region

o Failover and failback between two Azure regions

 Site Recovery provides the following capabilities:

o Storage replication

o Orchestration of a planned failover and failback

o Orchestration of an unplanned failover and failback

o Orchestration of a test failover

o Integration with a wide range of applications

Azure Update Management

 Azure Update Management facilitates management and monitoring of OS updates in hybrid

scenarios
 Azure Update Management for Windows in hybrid scenarios consists of the following
components:
o Azure Automation runbooks

o Azure Automation Hybrid Runbook Worker

o Microsoft Monitoring Agent

o Microsoft Update or WSUS and, optionally, Microsoft Endpoint Configuration Manager

 Azure Update Management implementation:

o Requires the Azure Automation feature referred to as Hybrid Runbook Worker,
installed on target on-premises computers
o Requires linking the Azure Monitor's Log Analytics workspace with the Azure
Automation account that will host the Azure Update Management solution with
target servers running Hybrid Runbook Worker
Lesson 4: Test your knowledge

Refer to the Student Guide for lesson-review questions

Lesson 5: Overview of
the Azure Stack HCI
implementation process
Lesson 5 overview

Provisioning Azure Stack HCI is a relatively complex undertaking, yet practically every
implementation can be divided into the same sequence of high-level logical steps. This lesson
provides an overview of this process
 Topics:
o Plan for Azure Stack HCI

o Plan for and provision hardware

o Deploy Azure Stack HCI

o Configure Azure Stack HCI

o Test and deploy virtualized and containerized workloads

Plan for Azure Stack HCI

 Azure Stack HCI complements Azure Stack Hub and Azure Stack Edge products
 Azure Stack HCI use cases include:
o Branch office and edge: reasonably priced yet highly available platform for business
applications and edge workloads that incorporate containerization and Azure IoT
Edge technologies
o VDI: large scale VDI deployments, with Microsoft Remote Desktop Services or
equivalent third-party products serving as a virtual desktop broker
o Highly performant Microsoft SQL Server: highly available, mission-critical Always On
availability groups–based deployments of Microsoft SQL Server
o Trusted enterprise virtualization: support for VBS to implement the virtual secure
mode as protection from operating system-based malware
o Scale-out storage: highly available, high-performing, and scalable storage that takes
advantage of locally attached drives
Plan for and provision hardware (1 of 6)

 Considerations that you must take into account when deciding on the optimal design
include:
o The total number of physical servers per cluster

o The number and type of processors per server

o The amount and type of memory per server

o Total storage capacity and resiliency levels, which directly affect the usable capacity

o Disk performance and caching/tiering

o The number and type of network adapters per server

o Network and storage traffic throughput and latency

 All of these considerations are driven by the intended workloads

Plan for and provision hardware (2 of 6)

Hardware guidance for branch office and edge:

 Workload characteristics:
o A small number of tenants running either containers or small to medium-sized VMs
hosting standard business applications
 Design guidance:
o A small physical footprint, such as switchless, two-node cluster is sufficient in most
scenarios, providing optimal combination of performance and hardware cost
Hardware considerations (per Requirements
node)
CPU  core count: low-medium
 frequency: low-medium
Storage  capacity: low
 performance/tiered layout: one-tier, all NVMe
Memory  capacity: high
 performance: medium
Network (east/west)  bandwidth: medium
 switchless configuration
Plan for and provision hardware (3 of 6)

Hardware guidance for VDI:

 Workload characteristics:
o Direct correlation to the type of VDI users (light, heavy, power)

 Design guidance:
o On average, plan for 40 users per node, with 10 light, 10 heavy, and 20 power users,
minimizing overcommit. Enable deduplication and compression, and account for
additional demand during boot, sign-in storms, maintenance events, and node
failures considerations (per Requirements
Hardware
node)
CPU  core count medium
 frequency: medium-high
Storage  capacity: medium
 performance/tiered layout: two-tier, NVMe + SSD
 15,000 IOPS are sufficient to account for boot and sign-
in storms
Memory  capacity: high
 performance: medium
Network (east/west)  bandwidth: medium
Plan for and provision hardware (4 of 6)

Hardware guidance for high-performance Microsoft SQL Server:

 Workload characteristics:
o Expected performance characteristics per SQL Server instance are 4 vCPU, 32 GB
RAM, 1 TB of storage, 50,000 IOPS, 500 MB/second throughput
 Design guidance:
o Avoid oversubscription of resources. Storage Spaces Direct storage performance
should take priority over storage efficiency, which, in this case, is secondary. You can
host up to 12 SQL Server instances per node
Hardware considerations (per Requirements
node)
CPU  core count high
 frequency: high
Storage  capacity: high
 performance/tiered layout: one-tier, all NVMe
Memory  capacity: medium-high
 performance: high
Network (east/west)  bandwidth: medium
Plan for and provision hardware (5 of 6)

Hardware guidance for trusted enterprise virtualization:

 Workload characteristics:
o A mix of tenants and workloads that are security-sensitive, including virtual
machines of different sizes with varying performance requirements
 Design guidance:
o Start by identifying performance requirements of individual tenants. At that point,
you can either determine hardware specifications necessary to facilitate the
intended tenant workloads or determine supported tenant workloads based on the
Hardware considerations
preselected (per Requirements
hardware specifications
node)
CPU  core count medium
 frequency: medium
 TPM 2.0 required
Storage  capacity: medium
 performance/tiered layout: two-tier, NVMe + SSD
Memory  capacity: medium
 performance: medium
Network (east/west)  bandwidth: medium
Plan for and provision hardware (6 of 6)

Hardware guidance for scale-out storage:

 Workload characteristics:
o Highly available and performant file shares

 Design guidance:
o Account for lower CPU and higher storage capacity requirements

Hardware considerations (per Requirements

node)
CPU  core count low
 frequency: low-medium
Storage  capacity: high
 high, performance/tiered layout: two-tier, NVMe
(cache) + HDD (capacity)
 cache should remain within 5%–10% of total storage
Memory  capacity: low
 performance: medium
Network (east/west)  bandwidth: low
Deploy Azure Stack HCI

 Azure Stack HCI consists of hardware from OEM partners validated and certified by
Microsoft and several Windows Server 2019 Datacenter roles and features
 In general, when deploying Azure Stack HCI, use the following high-level steps:
1. Assign custom computer names to Windows Server 2019 physical Hyper-V hosts

2. Join the Hyper-V hosts to an AD DS domain

3. Add relevant Windows Server 2019 roles and features for each node

4. Configure a Failover Cluster witness

5. Configure network connectivity

6. Set up Storage Spaces Direct

7. Install Windows Admin Center

8. Optionally, deploy Software-Defined Networking

9. If applicable, follow OEM-specific configuration to complete the initial deployment

Configure Azure Stack HCI

 The post-deployment configuration of Azure Stack HCI is highly dependent on the intended
use case
 It is common to implement hybrid functionality by using Windows Admin Center:
o Azure File Sync

o Azure Monitor

o Azure Backup, Azure Site Recovery

o Azure Update Management

Test and deploy virtualized and containerized workloads

 Before you deploy production workloads into an Azure Stack HCI cluster, you should first
validate that your intended configuration actually meets the intended performance
objectives
 You can perform such testing by using:
o VM Fleet

o DiskSpd
Lesson 5: Test your knowledge

Refer to the Student Guide for lesson-review questions

Module-review questions (1 of 3)

1. Which platform should you use to implement virtualized workloads that rely on trusted
enterprise virtualization and provide you with full access to the underlying hardware?
2. Which platform should you use to implement virtualized workloads that can be deployed
by Azure Resource Manager templates and provide the minimum latency when
connecting from on-premises applications?
3. Which platform should you use to deploy a physical appliance that applies Machine
Learning (ML) models to process on-premises data and transfers it to Azure Storage?
Module-review questions (2 of 3)

4. Which of the following Hyper-V Replica components is used only when Hyper-
V hosts participating in the replication are members of a failover cluster?
a. Replication engine
b. Hyper-V Replica Broker
c. Change tracking module
d. Network module
5. Which of the following do you require to implement Storage Replica?
a. Active Directory Domain Services (AD DS) environment
b. Storage Spaces with SAS JBODs
c. Remote Direct Memory Access (RDMA)-based network adapters
d. Round trip latency no larger than 2 ms
Module-review questions (3 of 3)

6. Which of the following do you require to implement shielded VMs?

a. Virtual trusted platform module (TPM)
b. Nested virtualization
c. Discrete device assignment
d. Production checkpoints
7. Which two Azure resources must you provision first to implement Azure Update Managem
ent? Choose two.
a. An Azure Key vault
b. An Azure Site Recovery vault
c. An Azure Storage account
d. An Azure Automation account
e. An Azure Log Analytics workspace
Module-review answers (1 of 2)

1. Which platform should you use to implement virtualized workloads that rely on trusted
enterprise virtualization and provide you with full access to the underlying hardware?
 Azure Stack HCI

2. Which platform should you use to implement virtualized workloads that can be deployed
by Azure Resource Manager templates and provide the minimum latency when
connecting from on-premises applications?
 Azure Stack Hub

3. Which platform should you use to deploy a physical appliance that applies ML models to
process on-premises data and transfers it to Azure Storage?
 Azure Stack Edge
Module-review answers (2 of 2)

4. Which of the following Hyper-V Replica components is used only when Hyper-
V hosts participating in the replication are members of a failover cluster?
b. Hyper-V Replica Broker
5. Which of the following do you require to implement Storage Replica?
a. Active Directory Domain Services (AD DS) environment
6. Which of the following do you require to implement shielded VMs?
a. Virtual trusted platform module (TPM)
7. Which two Azure resources must you provision first to implement Azure Update Managem
ent? Choose two.
d. An Azure Automation account
e. An Azure Log Analytics workspace
Thank you

© Copyright Microsoft Corporation. All rights reserved.