AZ-801 試験問題を無料オンラインアクセス

Your network contains an Active Directory Domain Services (AD DS) domain. The domain contains the servers shown in the following table.
Server3 contains a share named Share1.
On Server1, DHCP has the following configurations:
Conflict detection attempts: 3
An IPv4 scope named Scope1 that has the following settings:
1. Address Pool: 172.16.10.100 - 172.16.10.130
2. Address Leases:
* 172.16.10.100 computer1.contoso.com
* 172.16.10.101 computer2.contoso.com
Reservations: 172.16.10.101 computer2.contoso.com
Policies: Policy1
You perform the following actions:
* On Server1, you run
Export-DhcpServer -File \\Server3\Share1\File1.xml.
* On Server2, you run
Import-DhcpServer -File \\Server3\Share1\File1.xml
-BackupPath \\Server3\Share1.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.

Exhibit

Exhibit

正解：

Explanation:
CORRECTED ANSWER: Statement 1 (On Server2, Conflict detection attempts is set to 3): No. Statement 2 (On Server2, there is a reservation for computer2.contoso.com): Yes. Statement 3 (On Server2, Policy1 is applied to Scope1): Yes.
Detailed Explanation
Export-DhcpServer and Import-DhcpServer transfer the DHCP database ' s configuration objects-scopes, exclusion ranges, reservations, scope and server options, option/class definitions, and policies-as part of the exported XML, and reservations specifically travel with the scope configuration regardless of whether the - Leases switch is used, since -Leases only controls whether active client lease records are included. Conflict detection attempts, however, is a server-level behavioral setting (the number of ping tests the DHCP service performs before offering an address) that is configured and stored separately from the DHCP database ' s scope/option data, and it is not part of what these cmdlets migrate, so Server2 retains its own prior conflict detection configuration rather than inheriting Server1 ' s value of 3. DHCP policies such as Policy1 are scope- level configuration objects and are carried over with their associated scope during the import, so Policy1 remains applied to Scope1 on Server2 after the import completes.
Official Reference
Export-DhcpServer (DhcpServer) - https://learn.microsoft.com/en-us/powershell/module/dhcpserver/export- dhcpserver

Your company uses Storage Spaces Direct.
You need to view the available storage in a Storage Space Direct storage pool.
What should you use?

• A.the Get-StorageSubsystem cmdlet
• B.Disk Management
• C.Windows Admin Center
• D.File Server Resource Manager (FSRM)

You have an on-premises server named Server1 that runs Windows Server. You need to perform an on- demand backup of the files on Server 1 by using Azure Backup.
Which five actions should you perform in sequence? To answer, move the appropriate actions actions from the list of actions to the answer are and arrange them in the correct order.

正解：

Explanation:
1)From the Azure portal, create a Recovery Services vault. 2)From the Azure portal, download the Microsoft Azure Recovery Services (MARS) agent and the vault credentials. 3)On Server1, run the Microsoft Azure Recovery Services Agent Setup Wizard. 4)On Server1, run the Register Server Wizard. 5)On Server1, run the Schedule Backup Wizard.
Detailed Explanation
Backing up an on-premises server ' s files with Azure Backup begins with creating a Recovery Services vault in the Azure portal, since that vault is where both the agent installer and the registration (vault) credentials are generated and downloaded from. On Server1, running the Microsoft Azure Recovery Services Agent Setup Wizard installs the MARS agent and uses those downloaded credentials to register the server to the vault - which must happen after the credentials are downloaded, not before. With the agent registered, running the Schedule Backup Wizard on Server1 lets the administrator select the files and folders to protect, define the retention policy, and trigger the initial backup, which is how an on-demand backup of Server1 ' s files is produced through the MARS agent. A separate classic Backup vault is not part of this workflow, since the modern Recovery Services vault created in the first step already provides the storage and management plane the MARS agent registers against.
Official Reference
Tutorial: Back up Windows Server to Azure - https://learn.microsoft.com/en-us/azure/backup/tutorial- backup-windows-server-to-azure

Your network contains an Active Directory Domain Services (AD DS) domain. The domain contains a server named Server1 that runs Windows Server.

Exhibit

Exhibit
Exhibit

正解：

Explanation:
Detailed Explanation
The -ADAccountOrGroupProtector parameter of Add-BitLockerKeyProtector adds an Active Directory account or group as a key protector for a BitLocker-protected data volume (this protector type cannot be applied to an operating system volume, which matches the D: data volume shown in the exhibit). Pairing it with the -Service switch specifies that the protector is the computer ' s own service (machine) account, expressed as DOMAIN\ComputerName$, which lets that computer automatically unlock the volume without a signed-in user - the standard pattern for unattended or service-hosted data volumes. The second dropdown correctly resolves to -Service rather than -TPMandPinProtector or -TPMandPinAndStartupKeyProtector, since neither of those protector types is used together with an AD account/group protector.
Official Reference
Add-BitLockerKeyProtector (BitLocker module) - https://learn.microsoft.com/en-us/powershell/module
/bitlocker/add-bitlockerkeyprotector

You have three servers named Host1, Host2, and VM1 that run Windows Server. Host1 and Host2 have the Hyper-V server role installed. VM1 is a virtual machine hosted on Host1.
You configure VM1 to replicate to Host2 by using Hyper-V Replica.
Which types of failovers can you perform on VM1 on each host? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Exhibit
Exhibit

正解：

Explanation:
Detailed Explanation
Hyper-V Replica exposes different failover actions depending on whether you are working from the primary server or the replica server. A Planned Failover can only be initiated from the primary host, because it requires the source VM to be shut down cleanly and its final changes replicated before control transfers to the replica- an action that is unavailable from the replica side. Conversely, the replica server (Host2) offers Test Failover, which brings up an isolated copy for verification without disrupting ongoing replication, and (unplanned) Failover, used when the primary is unreachable, but it does not offer Planned Failover since that operation is scoped to the currently-running primary copy. This split of available actions by role is a deliberate safeguard against accidentally initiating a graceful failover from a passive replica.
Official Reference
Fail over a virtual machine with Hyper-V Replica - https://learn.microsoft.com/en-us/windows-server
/virtualization/hyper-v/replication-failover