Free AZ-800 Exam Braindumps
Administering Windows Server Hybrid Core Infrastructure Questions 129–136 (page: 18)

Explanation:

Box 1: $SRV3 $SRV3 is the target server.
Box 2: $SRV2 $SRV2 is the source server.
Set the PrincipalsAllowedToDelegateToAccount property: Use the Set-ADComputer cmdlet to modify the target server's AD object. The PrincipalsAllowedToDelegateToAccount parameter should be set to the source server's AD computer object. For example:
Code
# Get the source and target server AD objects $SourceServer = Get-ADComputer -Identity "SourceServerName" $TargetServer = Get-ADComputer -Identity "TargetServerName"
# Configure constrained delegation Set-ADComputer -Identity $TargetServer -PrincipalsAllowedToDelegateToAccount $SourceServer

Reference:

https://learn.microsoft.com/en-us/powershell/scripting/security/remoting/ps-remoting-second-hop

Explanation:

Box 1: Change the value of the AutoUpgradeMinorVersion property to true To ensure that the script runs again
AutoUpgradeMinorVersion:
This property is used during VM creation and while you upgrade the VM with a new configuration. *-> When set to true, it ensures that the latest minor version of the extension is automatically installed on the VM. It overrides the TypeHandlerVersion with the latest stable minor version available.
When you upgrade the VM configuration, if a new minor version is available, it's considered a configuration change. The extension is reinstalled with the latest minor version. In this way, newly created VMs keep up to date with the latest stable minor extension version. If you want to manually set the extension to a specific version, set this property to false.
Box 2: Remove the storageAccountkey property and add the managedIdentity property to the protectedSettings object. To minimize the risk of compromised key
In an Azure Resource Manager (ARM) template, protectedSettings are used to pass sensitive information to resources like virtual machine extensions, such as passwords or connection strings. This information is encrypted and not displayed in clear text, preventing it from being retrieved in logs or the plain text settings file on the VM. Instead of putting secrets directly in the main settings block, they are placed in protectedSettings for secure handling.
Azure Arc-enabled servers use a managed identity to authenticate and run extension scripts, which are downloaded to the server. The Azure Connected Machine Agent automatically creates and manages a system-assigned managed identity for the server, allowing it to authenticate to Azure and other resources without storing credentials. Extensions use this identity to perform tasks like deploying other extensions, updating server status, and accessing other Azure resources, such as Key Vault or Azure Monitor.
Incorrect:
* Move the storageAccountName and the storageAccountKey property to the protectedSettings object.

Reference:

https://learn.microsoft.com/en-us/azure/virtual-machines/automatic-extension-upgrade https://learn.microsoft.com/en-us/azure/azure-arc/servers/manage-vm-extensions-template https://learn.microsoft.com/en-us/azure/azure-arc/servers/managed-identity-authentication

Explanation:

To establish an SSH session from the first server to Server2 and sign in specifically as User2, use the following standard OpenSSH command syntax: ssh User2@Server2
Command Variations for Domain Environments Depending on your Active Directory configuration and how you prefer to specify the domain user, you can also use these variations: UPN Format: ssh User2@domain.com@Server2 *-> Down-Level Logon Name: ssh "domain\User2"@Server2 (Quotes are necessary to handle the backslash in many shells) Login Flag: ssh -l User2 Server2
Incorrect: [Not A, Not D] sshd (SSH Daemon): The program that runs in the background on the remote server. The "d" stands for daemon. It listens for incoming connection requests (usually on port 22), handles user authentication, and manages the secure session once you’ve logged in.

Reference:

https://www.unixtutorial.org/reference/ssh/

Explanation:

Box 1: 5 In a Windows Server Storage Spaces environment with 10 physical disks configured as a two-way mirror, the answer depends on the timing and the location of the failures.
The Short Answer Guaranteed Safety: 1 disk. Theoretical Maximum: 5 disks (only if they are the "wrong" 5 disks).
How it Works In a two-way mirror, Windows writes two copies of your data (slabs) across two different physical drives. Because you only have two copies of any given piece of data, the pool remains functional as long as at least one copy of every "slab" exists.
Box 2: 2 In a Windows Server Storage Spaces environment with 10 physical disks and a parity layout, the number of disks that can fail depends entirely on whether you have configured Single Parity or Dual Parity.
1. Single Parity This is the default setting for many basic setups. It functions similarly to RAID 5. Fault Tolerance: 1 disk failure.
How it works: Data and parity information are striped across all 10 disks. If one drive fails, the system uses the remaining data and parity bits to reconstruct the missing information.
Risk: If a second disk fails before the first one is replaced and rebuilt, the entire virtual disk (and all data) will be lost.
2. Dual Parity [Assume this, as it is more fault tolerant] This is available in Windows Server (and required for Storage Spaces Direct in many scenarios). It functions similarly to RAID 6. Fault Tolerance: 2 disk failures.
How it works: Two sets of parity information are calculated and stored. This allows the pool to remain online even if two disks fail simultaneously. Requirement: To use Dual Parity, you generally need a minimum of 7 disks (which you satisfy with 10).

Reference:

https://www.reddit.com/r/DataHoarder/comments/4eo5ou/is_raid5_raidz_ok_for_home_media_server/

Explanation:

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 2025 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 2025 standard All the virtual machines on HyperV1 have only the default management tools installed.
PowerShell Direct & 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

Explanation:

Reference:

https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/nested-virtualization

Reference:

https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/learn-more/use-local-resources-on-hyper-v-virtual-machine-with-vmconnect