Microsoft Microsoft Certifications AZ-800 Questions & Answers

• Question 211:

  HOTSPOT

  You need to configure network communication between the Seattle and New York offices. The solution must meet the networking requirements.

  What should you configure? To answer, select the appropriate options in the answer area.

  NOTE: Each correct selection is worth one point.

  Hot Area:

  

  Correct Answer:

  

  Reference: https://docs.microsoft.com/en-us/azure/virtual-wan/virtual-wan-expressroute-portal

• Question 212:

  HOTSPOT

  Configure network communication between the Seattle and New York offices to meet the networking requirements.

  Which action should you take to configure this? Select the appropriate options in the answer area.

  NOTE: Each correct selection is worth one point.

  Hot Area:

  

  Correct Answer:

  

• Question 213:

  HOTSPOT

  You need to configure Azure File Sync to meet the file sharing requirements.

  What should you do? To answer, select the appropriate options in the answer area.

  NOTE Each correct selection is worth one point.

  Hot Area:

  

  Correct Answer:

  

  Reference: https://docs.microsoft.com/en-us/azure/storage/file-sync/file-sync-planning

• Question 214:

  HOTSPOT

  You need to meet technical requirements for HyperV1.

  Which command should you run? To answer, select the appropriate options in the answer area.

  NOTE: Each correct selection is worth one point.

  Hot Area:

  

  Correct Answer:

  

  Box 1: hvc.exe

  A direct SSH session must be used to manage all the supported virtual machines on HyperV1.

  HyperV1 has the Hyper-V role.

  HyperV1 contains the virtual machines shown in the following table.

  *

  VM1 with Windows Server 2022 Datacenter. VM1 contains a local user named User1.

  *

  VM2 with Red Hat Enterprise Linux (RHEL). VM2 contains a local user named User2.

  *

  VM3 with Windows Server 2022 standard

  All the virtual machines on HyperV1 have only the default management tools installed.

  PowerShell Direct and HVC

  If you want to interact with your virtual machine running on Windows 10, you can use the Hyper-V Manager and the console to interact with the operating system directly. However, there are also two other options that allow you to manage and

  access the VMs using the command line. PowerShell Direct lets you create a PowerShell remoting session to the virtual machine using the VM Bus, so no networking is required. The same applies to Linux virtual machines and the HVC tool,

  which allows you to create an SSH connection directly into the VM. Both options also allow you to copy files to and from virtual machines.

  How to connect to Linux VMs using SSH Direct

  To connect to Linux VMs using SSH Direct (HVC) type hvc.exe into the command line or PowerShell. This will give you all the possible command options. Of course, SSH has to be configured inside the Linux virtual machine.

  hvc ssh Thomas@VMNAME

  To make this work, the SSH server inside the VM needs to be configured.

  Box 2: User2@VM2

  Only VM2 is Linux.

  VM2 contains a local user named User2

  Incorrect:

  * Connect-PSSession

  Reconnects to disconnected sessions.

  The Connect-PSSession cmdlet reconnects to user-managed PowerShell sessions (PSSessions) that were disconnected. It works on sessions that are disconnected intentionally, such as by using the Disconnect-PSSession cmdlet or the InDisconnectedSession parameter of the Invoke-Command cmdlet, and those that were disconnected unintentionally, such as by a temporary network outage.

  Example: Reconnect to a session Connect-PSSession -ComputerName Server01 -Name ITTask

  Id Name

  ComputerName

  State

  ConfigurationName

  Availability

  -- ----

  ------------

  -----

  -----------------

  -----------

  4 ITTask

  Server01

  Opened

  ITTasks

  Available

  This command reconnects to the ITTask session on the Server01 computer.

  * Connect-WSMan Description This cmdlet is only available on the Windows platform.

  The Connect-WSMan cmdlet connects to the WinRM service on a remote computer, and it establishes a persistent connection to the remote computer. You can use this cmdlet in the context of the WSMan provider to connect to the WinRM service on a remote computer. However, you can also use this cmdlet to connect to the WinRM service on a remote computer before you change to the WSMan provider. The remote computer appears in the root directory of the WSMan provider.

  About WS-Management Windows Remote Management is the Microsoft implementation of the WS-Management protocol, a standard SOAP-based, firewall-friendly protocol that allows hardware and operating systems from different vendors to interoperate. The WS-Management protocol specification provides a common way for systems to access and exchange management information across an information technology (IT) infrastructure. WS-Management and Intelligent Platform Management Interface (IPMI), along with the Event Collector, are components of the Windows Hardware Management features.

  * mstsc.exe It is a command interface to run Microsoft Remote Desktop Client (Remote Desktop Connection) in Windows. Then, you can establish a connection to a remote computer on the same network or different networks, if the Remote Desktop has been enabled on the remote PC.

  Reference: https://techcommunity.microsoft.com/t5/itops-talk-blog/hyper-v-for-developers-on-windows-10/ba-p/1062570 https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/connect-pssession https://learn.microsoft.com/en-us/powershell/module/microsoft.wsman.management/connect-wsman

• Question 215:

  HOTSPOT

  You need to ensure that data availability on SSPace1 meets the technical requirements.

  What is the maximum number of physical disks that can fail on each disk? To answer, select the appropriate options in the answer area.

  NOTE: Each correct selection is worth one point.

  Hot Area:

  

  Correct Answer:

  

  Box 1: 2

  The data on SSPace1 must be available always.

  SSPace1 contains the Storage Spaces virtual disks shown in the following table.

  Disk1, 8 physical disks, Three-way mirror

  Three-way mirror

  Three-way mirroring writes three copies of everything. Its storage efficiency is 33.3 percent - to write 1 TB of data, you need at least 3 TB of physical storage capacity. Likewise, you need at least three hardware fault domains - with Storage

  Spaces Direct, that means three servers.

  Three-way mirroring can safely tolerate at least two hardware problems (drive or server) at a time. For example, if you're rebooting one server when suddenly another drive or server fails, all data remains safe and continuously accessible

  

  Box 2: 2

  Disk2, 12 physical disks, Parity

  With parity, it depends if one if we use Single parity or Dual parity.

  Single parity allows only one failure.

  Dual parity allows two failures.

  Dual parity is the better recommended option.

  Note: Parity

  Parity encoding, often called "erasure coding," provides fault tolerance using bitwise arithmetic, which can get remarkably complicated.

  Storage Spaces offers two flavors of parity - "single" parity and "dual" parity, the latter employing an advanced technique called "local reconstruction codes" at larger scales.

  Single parity

  Single parity keeps only one bitwise parity symbol, which provides fault tolerance against only one failure at a time. It most closely resembles RAID-5. To use single parity, you need at least three hardware fault domains - with Storage Spaces

  Direct, that means three servers. Because three-way mirroring provides more fault tolerance at the same scale, we discourage using single parity. But, it's there if you insist on using it, and it is fully supported.

  Dual parity

  Dual parity implements Reed-Solomon error-correcting codes to keep two bitwise parity symbols, thereby providing the same fault tolerance as three-way mirroring (i.e. up to two failures at once), but with better storage efficiency. It most

  closely resembles RAID-6. To use dual parity, you need at least four hardware fault domains - with Storage Spaces Direct, that means four servers. At that scale, the storage efficiency is 50% - to store 2 TB of data, you need 4 TB of physical

  storage capacity.

  

  Reference: https://learn.microsoft.com/en-us/azure-stack/hci/concepts/fault-tolerance